Holding Shift+# selects the save spot at the same time as saving the spot, causing the text to overlap. (PLEASE don't eliminate Shift to save, Ctrl to load. It is a life saver to have the extra required key)
Annoyances:
Pressing C in the Ram Watch window clears all watches. If you have C set as the C button on the controller, this leads to having to reload, or possibly losing newly found ram locations.
The GameGenie area has a misspelling. It says Desactive all codes. Desactive is an interesting new word. (Hopefully the new cheat system will eliminate the need for Game Genie section)
Sage advice from a friend of Jim: So put your tinfoil hat back in the closet, open your eyes to the truth, and realize that the government is in fact causing austismal cancer with it's 9/11 fluoride vaccinations of your water supply.
I recorded from a savestate, and recorded only once (no rerecords) and when I played the file back the rerecord count was -1. As far as I know, I didnt do anything spectacularily different than usual.
The rom was Aero the Acrobat for genesis, and the .gst file is here
http://www.megaupload.com/?d=VGZKIQKF
adelikat wrote:
I very much agree with this post.
Bobmario511 wrote:
Forget party hats, Christmas tree hats all the way man.
In Shining Force 1 (and perhaps other games), in windowed mode, render mode EPX doesn't show the leftmost part of the playing screen, including some of the frame counter. Single and double work as intended.
Also, there is no check that all the other render modes (which are now greyed out), aren't selected via an old config file. At least I think that's what happened.
When recording a movie and then stopping it after a duration of time, sometimes Gens outputs a movie file with zero frames but has every rerecord you have done. It's easy to workaround by loading one of the latest save states of the movie while not in read-only mode.
Edit: I think I know how I caused this bug.
I was recording a movie and decided to playback a movie. So, instead of hitting stop I just went straight to Play Movie but then I hit Cancel and the emulator was still recording only it started over, from Frame 0. I hit stop and tried playing it back and it said 0 Frames and when I played it, it kept going and the input was going haywire.
Edit: I think I know how I caused this bug.
I was recording a movie and decided to playback a movie. So, instead of hitting stop I just went straight to Play Movie but then I hit Cancel and the emulator was still recording only it started over, from Frame 0. I hit stop and tried playing it back and it said 0 Frames and when I played it, it kept going and the input was going haywire.
This description is extremely helpful. this bug will definitely be fixed in 9.5c
How fleeting are all human passions compared with the massive continuity of ducks.
During movie playback/recording: When loading a save state that is inconsistent with a movie, you are prompted whether or not to load the save state. However, after selecting no, the save state loads anyway.
Additionally, it would be really nice if Gens would release files such as trace.log so you don't have to quit gens to edit it, delete it, and etc.
Sage advice from a friend of Jim: So put your tinfoil hat back in the closet, open your eyes to the truth, and realize that the government is in fact causing austismal cancer with it's 9/11 fluoride vaccinations of your water supply.
Let me correct your description.
During movie playback: When loading a save state that is inconsistent with a movie, you are prompted whether or not to continue playback. If you select no, the savestate loads, and movie playback is halted.
How fleeting are all human passions compared with the massive continuity of ducks.
Let me correct your description.
During movie playback: When loading a save state that is inconsistent with a movie, you are prompted whether or not to continue playback. If you select no, the savestate loads, and movie playback is halted.
My bad. I was recalling the instance from my head, since I temporarily am without internet in my apt.
Sage advice from a friend of Jim: So put your tinfoil hat back in the closet, open your eyes to the truth, and realize that the government is in fact causing austismal cancer with it's 9/11 fluoride vaccinations of your water supply.
Every once in a while, Gens will lock a movie file even if it's no longer in use. I'm 100% sure it has to do with that loading up a movie but hitting cancel instead only to see the movie was loaded up anyway bug.
This is how I've reproduced it. I loaded up a movie file and hit Play Movie and then, without hitting stop movie, I went to load the movie up again but hit cancel. It loaded the movie, like usual, so I hit stop and that's how the movie file became locked. And by locked, I mean that I was trying to edit the movie with TAS Movie Editor but Gens wouldn't let me save it, saying that it was still in use.
Just letting you know what else that bug does in hopes that it will help you out with fixing it.
One issue I've been having lately is that if gens is in windowed mode, i pause it and move another window over it, it leaves a "shadow" on the playing screen and cuts off that portion of the screen. Doesn't always happen, I am running vista if that helps to know too.
When creating an AVI w/ sound in gens, the sound is clipped (according to DeHackEd). Volume control seems to have no effect on this.
Sage advice from a friend of Jim: So put your tinfoil hat back in the closet, open your eyes to the truth, and realize that the government is in fact causing austismal cancer with it's 9/11 fluoride vaccinations of your water supply.
Gens Movie Test's 0-9 load keys can't be diabled,I want to disable these keys,I don't know if it is a bug,If it is a bug,I hope it will be fixed in later version.
Some instructions are disassembled in the trace incorrectly.
this applies to 9.5c as well.
ADDA.W with an immediate value is decoded incorrectly sometimes -- sometimes it shows you just a byte, and sometimes it shows you a long (and sometimes it shows you a word, correctly..)
for example, assembly code "D4 FC 03 64" gets decoded as
ADDA.W #$64,A2
instead of
ADDA.W #$0364,A2
this form is wrong sometimes, too:
ADDA.W $00(A2,D0),A2 -- wrong (though right in this case)
ADDA.W $0000(A2,D0),A2 -- right
also
ADDA.W #$001051CA,A1 -- wrong (51CA is the next instruction!)
ADDA.W #$0010,A1 -- right
SUBQ.W has a tricky error:
This instruction is made to work with values from 1-8. It uses 3 bits to store that 1-8 value (but 3 bits can only say 0-7). When the value stored is 0, it actually subtracts 8!
SUBQ.W #0,A2 -- wrong
SUBQ.W #8,A2 -- right
Some instructions are disassembled in the trace incorrectly.
this applies to 9.5c as well.
ADDA.W with an immediate value is decoded incorrectly sometimes -- sometimes it shows you just a byte, and sometimes it shows you a long (and sometimes it shows you a word, correctly..)
for example, assembly code "D4 FC 03 64" gets decoded as
ADDA.W #$64,A2
instead of
ADDA.W #$0364,A2
this form is wrong sometimes, too:
ADDA.W $00(A2,D0),A2 -- wrong (though right in this case)
ADDA.W $0000(A2,D0),A2 -- right
also
ADDA.W #$001051CA,A1 -- wrong (51CA is the next instruction!)
ADDA.W #$0010,A1 -- right
SUBQ.W has a tricky error:
This instruction is made to work with values from 1-8. It uses 3 bits to store that 1-8 value (but 3 bits can only say 0-7). When the value stored is 0, it actually subtracts 8!
SUBQ.W #0,A2 -- wrong
SUBQ.W #8,A2 -- right
I was aware of the SUBQ/ADDQ bug (which also affects any other instruction where there's a 0-7 value encoded in the instruction to represent a 1-8 operand). I hadn't noticed the ADDA problem, but I just looked into it, and I think I've fixed it now.
How fleeting are all human passions compared with the massive continuity of ducks.
