Chat et Souris is fixed, I misread the cpu spec and was dividing by the wrong number for the timer. Somehow no other game that used the timer cared about being off by a factor of 5, so I never noticed it.
I will (re)test PAL games and G7400 in next days.
I have test several US games and it work great, even the voices in "Spike".
Thanks for all your work Alyosha!
I will (re)test PAL games and G7400 in next days.
I have test several US games and it work great, even the voices in "Spike".
Thanks for all your work Alyosha!
Don't bother testing G7400 yet, it's just WIP and the graphics pipeline isn't coded yet. I just roughed in the framework so I can work on it as I have the time.
Also I don't believe there is an O2 version of chat et Souris (Mousing Cat in english.)
What 'Spike'? I can only find a Vectrex version of that.
I will (re)test PAL games and G7400 in next days.
I have test several US games and it work great, even the voices in "Spike".
Thanks for all your work Alyosha!
Don't bother testing G7400 yet, it's just WIP and the graphics pipeline isn't coded yet. I just roughed in the framework so I can work on it as I have the time.
Also I don't believe there is an O2 version of chat et Souris (Mousing Cat in english.)
What 'Spike'? I can only find a Vectrex version of that.
Ok, thanks for the informations!
Yes, I got the wrong topic, as I had posted just before in the VectrexHawk topic...
I (mostly) fixed 4 in a Row. This was actually a very difficult case. Just figuring out what the ROM format was took a lot more googling I expected (it's something called 'XROM' apparently, and only in 2 games.) After accounting for that there were several small bugs that needed fixing that slid under the radar until now.
There is still a problem that a counter interrupt is happening one scanline too late, but that kind of thing could take forever to properly sort out and I currently don't have the time. So for now it will have to be good enough, at least it's playable.
My time is really constrained now and I can't really focus on multiple things, so I'm thinking of setting Odyssey 2 to released soon and calling it a day, even if there are a couple left over bugs. At least then people can use it for 2.5.3 with nearly all games compatible.
If anyone has a bug that is actively preventing them from actually making a TAS, let me know and I'll try to fix it. Other then that I probably won't return to this.
Emulator Coder, Site Developer, Site Owner, Expert player
(3599)
Joined: 11/3/2004
Posts: 4739
Location: Tennessee
oh well, I wish we could have just done that for the past release. But ok, I was wondering what the status of this was, if you think it is pretty good for tasing (seems to be for US titles at least), then sure, I"ll make sure it gets officially released next time.
So, how exactly does this core work?
I tried loading the Pinball ROM for the Odyssey 2. The emulator accepts the ROM, but the screen is just black after that, and every frame is a lag frame (this is on BizHawk 2.6). Am I missing something?
I've run into similar issue with the Odyssey 2 core and can somewhat replicate it.
I believe this may be an issue related to savestates.
Using the Pinball ROM, I can show some images to explain a bit of what I'm encountering.
When I just load the ROM, open TAStudio and start running emulation; I get the following:
When I add input, the following occurs and I get the wall of lag:
Then after the input is in place, restarting emulation from the beginning will result in this:
Then sometimes (but not always), clicking to jump back the emulation at an earlier frame results in the big block of lag returning. In this example I clicked to jump back to frame 12:
I'm not sure if this is the same bug that Lobsterzelda is experiencing, but it sounds related.
Again, I'm guessing it's a savestate issue, but I'm not a coder to know how to investigate further. There are no error boxes/logs/reports occurring.
I'm not sure if this is the same bug that Lobsterzelda is experiencing, but it sounds related.
In my case, the screen just stays black, and the game never appears on screen. If you start from a fresh download of BizHawk 2.6 and try downloading and playing the Pinball Rom, does it work the first time? Or is there some other firmware that you need to download first?
You should only need 'Odyssey 2 Bios' to run it.
Something very strange is happening in TAStudio. When it loads a state the first CPU variable gets corrupted for unknown reasons. The weird thing is that when I change the order in which things are saved, the corruption goes away. quicksave states made outside of TAStudio never get corrupted.
I briefly tried to debug what is happening, without success. As far as I can tell every variable that needs to be in there is in there, so I think it's a TAStudio issue somehow. I won't be able to look that deeply into it for a bit. O2Hawk existed in 2.5.2 in basically the same form as in 2.6 and there is no corruption there though, so try 2.5.2 for now.
There was a problem I ran into with Super Cobra where the movie header didn’t list “PAL 1” to adjust the time for PAL playback, however I found that it still shows the incorrect time even if PAL 1 is on.
I made a ticket here a week ago: https://github.com/TASVideos/BizHawk/issues/2684
[14:15] <feos> WinDOES what DOSn't
12:33:44 PM <Mothrayas> "I got an oof with my game!"
Mothrayas Today at 12:22: <Colin> thank you for supporting noble causes such as my feet
MemoryTAS Today at 11:55 AM: you wouldn't know beauty if it slapped you in the face with a giant fish
[Today at 4:51 PM] Mothrayas: although if you like your own tweets that's the online equivalent of sniffing your own farts and probably tells a lot about you as a person
MemoryTAS Today at 7:01 PM: But I exert big staff energy honestly lol
Samsara Today at 1:20 PM: wouldn't ACE in a real life TAS just stand for Actually Cease Existing
There was a problem I ran into with Super Cobra where the movie header didn’t list “PAL 1” to adjust the time for PAL playback, however I found that it still shows the incorrect time even if PAL 1 is on.
I made a ticket here a week ago: https://github.com/TASVideos/BizHawk/issues/2684
When I add input, the following occurs and I get the wall of lag:
Then after the input is in place, restarting emulation from the beginning will result in this:
Then sometimes (but not always), clicking to jump back the emulation at an earlier frame results in the big block of lag returning. In this example I clicked to jump back to frame 12:
I'm not sure if this is the same bug that Lobsterzelda is experiencing, but it sounds related.
Again, I'm guessing it's a savestate issue, but I'm not a coder to know how to investigate further. There are no error boxes/logs/reports occurring.
