Can anyone tell me if this is a bug in FCEUX or in the NES?
I noticed that leaving the PPU increment mode bit (xxxx x1xx in $2000) set to 1 and exiting NMI causes the background colour to get screwed up. It had already caused a lot of frustration so it would be really nice to know where this bug is so I know do I need to worry about it in the future.
On FCEUX interim build 3028 on Windows 7 x64, TAS Editor crashed and it crashes every time I reload the .fm3 which remained when it crashed first time. I don't remember exactly what I did when the crash happened, but I overwritten an existing bookmark just before the crash.
I put the .fm3 causing the crash. The game is "Heisei Tensai Bakabon (J)" (md5 of headerless ROM: b1b94bbfddea3e2a40834919183c302d)
http://www.mediafire.com/download/nd1f1nw60pobwf0/Bakabon-testrun.zip
When I load the .fm3 and do a frame-advance, FCEUX crashes. "Save Compact" and "Export to FM2" work, so I tried saving a compact .fm3 including input/markers/bookmarks and reloading the compact .fm3, but FCEUX crashes again when I do a frame-advance. "Export to FM2" seems to export a valid .fm2.
On FCEUX interim build 3028 on Windows 7 x64, TAS Editor crashed and it crashes every time I reload the .fm3 which remained when it crashed first time. I don't remember exactly what I did when the crash happened, but I overwritten an existing bookmark just before the crash.
I put the .fm3 causing the crash. The game is "Heisei Tensai Bakabon (J)" (md5 of headerless ROM: b1b94bbfddea3e2a40834919183c302d)
http://www.mediafire.com/download/nd1f1nw60pobwf0/Bakabon-testrun.zip
When I load the .fm3 and do a frame-advance, FCEUX crashes. "Save Compact" and "Export to FM2" work, so I tried saving a compact .fm3 including input/markers/bookmarks and reloading the compact .fm3, but FCEUX crashes again when I do a frame-advance. "Export to FM2" seems to export a valid .fm2.
Since there's no stable to reproduce it, we can't tell what needs to be fixed in the code, but you can fix the file by disabling Adjust input according to lag (and enabling it back when you advance there). Somehow lag flag is broken for that last frame, and it crashes on vector manipulation, but not during input adjustment - it happens while doing the hotchanges stuff. Again, I can't know what exactly is wrong without reproducing it. Maybe you saved the bookmark while it was unpaused or something. Or it was trying to adjust nothing, as it was the last frame of the movie.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Since there's no stable to reproduce it, we can't tell what needs to be fixed in the code, but you can fix the file by disabling Adjust input according to lag (and enabling it back when you advance there). Somehow lag flag is broken for that last frame, and it crashes on vector manipulation, but not during input adjustment - it happens while doing the hotchanges stuff. Again, I can't know what exactly is wrong without reproducing it. Maybe you saved the bookmark while it was unpaused or something. Or it was trying to adjust nothing, as it was the last frame of the movie.
Thank you! I loaded the .fm3 and temporarily disabled "Auto-adjust Input according to lag" option, then FCEUX didn't crash. I saved the .fm3 and it seems to work well.
TAS Editor saves me from a lot of routine. It's cool :)
2 bugs in 2.2.2 (01:48:45 Sep 24 2013)
1. If I set pause after playback, when dump the avi, the last frames of the fm2 file didn't dumped.
2. Set load full savestage-movies first. For example, there is a 2000-frames-movie. I made a savestage at 1000/2000. when I load this savestage and goto work, and stop at 1011, these new inputs be added to the end of file, the file frames became to 2011, and there are nothing changed between 1000 and 1011.
If I want to against this bug, I need save stage at 1011 first.
You mean, you need to save after your new inputs to have them written into the movie when load full savestage-movies is checked? I think it's so by design.
Pausing triggers before it desides whether it should dump that frame or not, so it's also by design.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
You mean, you need to save after your new inputs to have them written into the movie when load full savestage-movies is checked? I think it's so by design.
Pausing triggers before it desides whether it should dump that frame or not, so it's also by design.
But this new inputs be added to the wrong place. This new 11 frames inputs should be insert from 1000 and stop at 1011, but in fact, there are added to after 2000, if I didn't save this stage, and choose stop movie.
I just found this bug when I encode my new movie. F28756 is lost. And in that page, my old encode is lost 1 frame too.
http://tasvideos.org/forum/viewtopic.php?p=420467#420467
When I select End Movie after I load such a state in read+write mode and record some inputs, they simply aren't in the movie at all (until I save a state) for some reason...
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
FCEUX 2.2.3 has been released!http://www.fceux.com/web/download.htmlhttp://www.fceux.com/web/pressrelease-2.2.3.html
The 2.2.3 release fixes a number of emulation bugs, features overclocking (for lag reduction) and Dendy mode, and adds support for a bunch of new ROM dumps (mostly unlicensed). Reverse engineering tools and Lua scripting have got some updates, new input devices are supported, new palette files have beed added. The SDL port has been fixed and updated as well.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Hi! While the NSF file is loaded when I try to open the Code/Data/Logger, the emulator crashes since svn r3187 and fceux version 2.2.3.
It works when the ROM is loaded.
Nice. Were the improvements made by Alyosha implemented on FCEUX too? If not, any plans to?
Of course not. The core is forbidden since forever.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
No they are not. Clean unzip with no config changes makes proper screenshots for me.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
This bug still exist from svn version 3187.
Code/Data/Logger for NSF playback crashes.
So I still using svn version 3186 until this problem gets fixed.
