Hi,

I have a request for the debugger of bluemsx.
I'd be happy if there could be a possibility to change the content of the (V)RAM memory.
I was thinking about working on some existing games (improving the gameplay/speed),
and it would be nice to have the possibility to change the RAM content, so that I could learn more about the structure of the games.
(by changing for instance a call $xxxx into a nop nop nop, I can figure out when routines occur at what place.

I think that is possible already. Just click on the hex values in the memory window. It may not be enough for what you want to do though and it only works on memory that is writable (e.g. VRAM, RAM, but not ROM).

A similar feature that has been requested is to be able to write asm code and compile it into RAM directly in the debugger. For the case you mentioned thats probably even better. But I'm not sure when we'll get to this feature.

I'm playing a game (undeadline) and I change the content of RAM.
Then I press F5, to continue the game, I press pause again,
and again I try to change the same content of this part of RAM.
The second (or sometimes third) time, I cannot change it anymore... ???

Quote:

I'm playing a game (undeadline) and I change the content of RAM. Then I press F5, to continue the game, I press pause again, and again I try to change the same content of this part of RAM. The second (or sometimes third) time, I cannot change it anymore... ???

Maybe if you are on the same physical address you are changing some unmodifiable rom.
Are you sure that when you break the execution on this address there is always the same page enabled ?
Maybe the program switch pages and the first time you are changing data on a page the second on another or similar.

Quote:

Are you sure that when you break the execution on this address there is always the same page enabled ?

yes I am...
What about changing the content of VRAM ?
Sometimes this doesnt work either ??

for me always worked fine. (bmsx2.6)

For me this has not been working ever. There is no way to change any RAM on debugger.

Most times it also doesn't work for me (like right now). But I remember, that I was able to change a byte one or two times in the past Maybe some special preconditions are needed.

Its always been working for me too. Maybe its a machine specific problem. What MSX machine are you using?

You can also try this: http://openmsx.sourceforge.net/manual/commands.html#debug
Or get the GUI debugger from here: http://openmsx.sourceforge.net/temp/openmsx-debugger-win32-bin-snapshot.zip (We should replace it with a newer snapshot though.)

;-)

@manuel
I can see that OpenMSX is a bit more advanced when looking technical details, but BlueMSX is more user friendly.
I don't see why you have to promote OpenMSX every time BlueMSX is mentioned... Dvik is not doing the same...

@dvik
I usually use default Turbo-R config

Sorry, I hope you saw the winky. I was just mentioning an alternative, in case you couldn't get it working. I didn't mean to annoy people. Besides, I'd like to get more feedback on the debugger, especially on the GUI... So, I'm trying to get people to test it a bit. So far, response as been fairly low.

Quote:

Its always been working for me too. Maybe its a machine specific problem. What MSX machine are you using?

just the standard msx2 machine