Debugger Resolution Question
Debugger Resolution Question
Quick ? about using Mame: I've been using Mame since 98 but just started using the debugger on the windows Mame 0.65. Whenever I play a Rom, the debugger first appears and kicks me out of fullscreen and I don't know what to change in the Mame.ini to put the debugger in the same resolution as the games (keeping the rom resolutions to auto). I have debug resolution set to auto.
-
Tourniquet
- Posts: 163
- Joined: Wed Sep 19, 2001 1:00 am
- Location: UK
- Contact:
You need to have MAME in a window for using the debugger I'm afraid, the Window's port displays the debugger in a seperate window.
It makes sense to have two builds. One with debug and one without (for playing) because when you have compiled with debug then the Volume/Overclock menu is inaccessable (independant of the -debug/-nodebug switch) and the profiler is enabled (LShift-F11) which makes it a lot slower.
i.e.
I have (at any one time),
1) a binary based on the current MAME release
2) a binary with whichever games are stable since the last MAME release,and a few patches here and there to use on my rotating lcd etc.
3) a stable debug build (same as above but with a couple of things disabled
4) + 5) debug and non-debug unstable (lots of extra crap on whatever I'm playing with atm) builds that I'm working on atm. Usually with hwstretch disabled so I can see clearly what's going on.
Oh, and if for any reason something major is broken in the current release and not fixed yet I might keep an old binary around
It makes sense to have two builds. One with debug and one without (for playing) because when you have compiled with debug then the Volume/Overclock menu is inaccessable (independant of the -debug/-nodebug switch) and the profiler is enabled (LShift-F11) which makes it a lot slower.
i.e.
I have (at any one time),
1) a binary based on the current MAME release
2) a binary with whichever games are stable since the last MAME release,and a few patches here and there to use on my rotating lcd etc.
3) a stable debug build (same as above but with a couple of things disabled
4) + 5) debug and non-debug unstable (lots of extra crap on whatever I'm playing with atm) builds that I'm working on atm. Usually with hwstretch disabled so I can see clearly what's going on.
Oh, and if for any reason something major is broken in the current release and not fixed yet I might keep an old binary around