I got some troubles with KMod 0.7
My dev rom make the emulator to hang where it work perfectly with Gens or Fusion.
I noticed some strange behavior with the previous version (KMod 0.6 beta), for instance, i got a bug in my Z80 init code which was setting 0x2002 bytes of RAM to 0 (instead of 0x2000). In theory the address just overlap but here that just make KMod to hang.
With version 0.7 i got some more troubles :-/ I'll complete the message as soon i discover what cause this trouble to KMod 0.7
Yo stef Actualy, sometimes, Kmod can appear hang because your code generate too many error / second (so it flood and litteraly freeze the message box log... until its full).
Are you sure it's not this problem? It was just an idea... sorry if its bigger problem than that.
Fonzie wrote:Yo stef Actualy, sometimes, Kmod can appear hang because your code generate too many error / second (so it flood and litteraly freeze the message box log... until its full).
Are you sure it's not this problem? It was just an idea... sorry if its bigger problem than that.
In fact i just realised it wasn't opening my rom.
It seems Kaneda made some changes in the command line stuff.
It doesn't use anymore the current directory as default directory or something like that. About the 0.6 version weird behavior, you're probably right, maybe a lot of message was generated making KMod look freezed, but wasn't really
^^ I found a little (we can call it a bug, maybe, its not a problem for me anyway) wierd thing.
In a 32x game, when you watch 32x framebuffer/palette, megadrive VDP palettes gets stretched/distorded.
It may not be important but maybe it can make the Kmod unstable, that's why I wanted to inform you about .
Fonzie wrote:Yo stef Actualy, sometimes, Kmod can appear hang because your code generate too many error / second (so it flood and litteraly freeze the message box log... until its full).
Are you sure it's not this problem? It was just an idea... sorry if its bigger problem than that.
In fact i just realised it wasn't opening my rom.
It seems Kaneda made some changes in the command line stuff.
It doesn't use anymore the current directory as default directory or something like that. About the 0.6 version weird behavior, you're probably right, maybe a lot of message was generated making KMod look freezed, but wasn't really
Yes...I changed the path to avoid language.dat/.... to be on the rom directory
I didn't try throught command line, you're right...sorry
Stef wrote:
I noticed some strange behavior with the previous version (KMod 0.6 beta), for instance, i got a bug in my Z80 init code which was setting 0x2002 bytes of RAM to 0 (instead of 0x2000). In theory the address just overlap but here that just make KMod to hang.
strange it hanges now, I didn't change the WriteByte stuff....
Stef wrote:
I noticed some strange behavior with the previous version (KMod 0.6 beta), for instance, i got a bug in my Z80 init code which was setting 0x2002 bytes of RAM to 0 (instead of 0x2000). In theory the address just overlap but here that just make KMod to hang.
strange it hanges now, I didn't change the WriteByte stuff....
I should retest it, in fact i was doing word write instead of byte write. I guess that KMod was logging them (incorrect Z80 access), making it looks like hanged, but it wasn't