-
Can poeple post all known issues they've found with Zsnexbox related to the emulation (not feature requests). I DON'T mean little glitches here and there. Like one line of resolution flickers for 2 seconds and goes away or the game has a minor sound glitch in one part but not anywhere else.
I mean games crash consistantly, don't work, etc...i.e. major issues (the constant flickering in Chrono Trigger is my idea of a major issue as well as the incorrect speed of Starfox). Even better would be a savestate. Otherwise list exactly how to recreate the issue. I'm considering changing the base code to an earlier date:
For example:
The 2-17 release has perfect speed for Star Fox and no flickering in Chrono Trigger.
Better yet, if people could do the testing themselves with versions from: http://zsnes.ipherswipsite.com/
that would be great.
I need help determining what the best "overall" (not perfect) code base is (i.e. Games don't crash all the time, correct speed in Starfox, Top Gear 3000 works, etc...). So far the 2-17 version seems like the best candidate.
-
Battletoads and Double Dragon - The Ultimate Team doesn't get passed the RARE logo on Zsnexbox or any of the WIP beyond 2-17. I can at least get into the main game from 2-17 but I haven't throughly checked the game.
-
Ninja Gaiden trilogy and street fighter alpha 2 are much smoother (maybe perfect) in the 2-17 build.
Can someone test Super mario RPG to see if it freezes/crashes?
Bomberman 2-5 don't crash anymore with the 2-17 build
-
I tested Super Mario RPG and it didn't crash when hitting a turtle in the begining using the 2-17 build
It's looking more and more like the 2-17 code is the way to go.
-
Super Mario RPG has crashed on me as Mario gets shot out of the castle on WIP 2-17.
Megaman X runs much smoother.
-
The 2/19 build introduced many bugs, so if one of you discovers a bug with the 2/17 release, just keep going back a release or two to see if you can find a build that does work.
If any of you find any bugs, please report the name of the game and the build(s) used in your testing. If you find a build that works properly with said game, please report it as well.
-
BS Zelda - The 2/28/2005 build is the newest build that I could get to run it properly. The newer builds won't load it unless you disable sound emulation.
-
QUOTE(dohopoki @ Apr 25 2006, 05:19 AM)

Super Mario RPG has crashed on me as Mario gets shot out of the castle on WIP 2-17.
Megaman X runs much smoother.
Does it crash at the same place everytime, randomly, or rarely?
-
I just came up with an interesting idea. Since some games just won't work right no matter what build you use, I think an interesting work around would be to include the ability to add\edit rom notes. For games that work better in xSNES9x, you'd make a note to "Use xSNES9x." For a game like Breath of Fire 2, which requires you to save and reset the game to prevent freezing, you'd add "Save & reset game to prevent freezing."
-
QUOTE(Consoleman! @ Apr 25 2006, 01:20 PM)

More notes about the 2/28/2005 build:
- Battletoads and Double Dragon works
- BS Zelda works (last build to do so)
- Mega Man X runs smoothly
- Ninja Gaiden runs smoothly
- Street Fighter Alpha 2 works
- Top Gear 3000 works (first build to do so)
Still needing verification on:
- Bomberman 2-5 (crashing)
- Chrono Trigger (flickering)
- Ranma 1/2 Akanekodan (crashing)
- Starfox (correct speed)
- Super Mario RPG (crashing)
I didn't try the 2-28 build but the 2-19 build has incorrect speed for Star Fox and screen flashing in battles for Chrono Trigger.
2-17 was as high as I could go before those things happened.
QUOTE
Breath of Fire 2, which requires you to save and reset the game to prevent freezing
Does this happen on ZsnexBox?
-
QUOTE
I haven't tried any builds past the 2/17/2006 build. The build I'm currently testing is from last year (2/28/2005).
My mistake. I didn't notice the "2005" part
-
QUOTE(nes6502 @ Apr 25 2006, 09:59 AM)

My mistake. I didn't notice the "2005" part
What I found intriguing about the 2/28/05 build is that it's the only build in existence that supports both BSZelda and Top Gear 3000. If we can focus our attention on 2-3 builds, perhaps we can make a decision faster.
As for the newer builds, they may be breaking compatibility because the programmers are trying to re-code the games that have relied on emulation hacks.
An idea about the rom notes: I'm not sure if this interests you, but I think one way of doing this would be to use a highlighting system. For games that don't work, you can highlight the text in red or flag it with a red marker in front it's name (which may be better). For games that need workarounds, they could use a yellow marker\highlight. The rom notes could be accessed in a fashion similar to setting up a rom in Xport's emulators.
-
Why not just use the last stable build?
Newer builds don't mean squat if things are just getting progressively more broken (as seems to be the case).
-
QUOTE
Why not just use the last stable build?
Because Top Gear 3000 doesn't work in 1.42 and Star Fox doesn't run at the correct speed.
-
It seems like 2-28 may be the best candidate
-
QUOTE
build does have a minor graphical glitch at the save menu, however.
Does this happen if you uncheck New Graphics Engine or use old graphics mode 2?
-
QUOTE(Consoleman! @ Apr 25 2006, 08:39 PM)

Unfortunately, yes. It's a minor transparency bug. On each save slot, there's a single bar going across each unselected area which isn't shaded. The highlighted slot looks as it should, though.
Did you try Strfox or Super Mario RPG?
-
Ok, I changed my mind about testing Super Mario RPG. I just never played it much before, so I didn't know how long one needs to play for Mario to get shot out of the castle.
Anyway, here's the results:
Super Mario RPG - Froze 3 straight times inputting my name with the 2/17/06 build, but the 2/28/05 build had no problems whatsoever. I also got past the scene where Mario defeats Bowser and gets shot out of the castle.
-
Another bug in the 2-17 build was non transparent numbers for the count when an opponent gets knocked down. Can you test this on the 2-28 build?
It's still looking like 2-28 is the ideal build
Thanks to everyone for all the testing
-
Oh sorry. Yeah Super Punch out
-
Well unless somebody can make a good argument (and soon) as to why the 2-28 build is not the best build, then I will be reverting to this version. It seems to have the most benefit with the least problems.
-
However in xSnes9x Super Punchout has corrupt graphics in the backgound when the screen is scrolling diaganally before the second fight. The colors are wrong.
It's great that the other issues are not on xSnes9x. This will give people a way to play nearly all games using one emulator or the other.
-
QUOTE(nes6502 @ Apr 25 2006, 08:03 AM)

Does it crash at the same place everytime, randomly, or rarely?
It crashed 3 times in a row at the exact same moment. He get's shot out of the castle, he arks upwards and just as he's supposed to descend he freezes in the air. The water in the background continues to wave back and fourth and I believe even the little mario graphic keeps waving his arms, he's just stuck in the air and you can't skip past this.
-
what version is 2/28? 1.1?
-
QUOTE(Rababunny @ Apr 25 2006, 06:22 PM)

what version is 2/28? 1.1?
1.43
Grab it here:
http://zsnes.ipherswipsite.com/05/
-
QUOTE(Consoleman! @ Apr 25 2006, 11:28 PM)

Actually there is no official 1.43
The version used for ZsnexBox (all versions) is the code that was in CVS on 4-15-06 and is included (windows_version.rar) with ZsnexBox 1.2
He was assuming you were using the PC version
-
I'm trying Mario RPG on 2-28 now.
Update Mario RPG: It get's passed the part that was freezing and seemed to work fine through a couple of battles afterwards. If it's of anyworth, I've always used Snes9x for Mario Rpg but I've never tried it on xsnes9x.
What kind of crashing were we seeing in Bomberman 2-5?
-
Try and play any of the Bomberman games for more than 30 seconds. If there is no black screen freeze after a couple minutes, then it doesn't have the problem.
-
Which version of BS Zelda works with 2-28
I have several but only the one named: BS Zelda no Densetsu - Kamigami (J)(!).zip will start. However I can't get past the screen where you enter your name it allways goes back to the game selection screen with an empty one. It does this in 2-17-06 and 2-28-05
-
I played Bomberman 3, the main game and the battle game each. I went through two levels on the main game and one full match on the battle game with 4 CPU characters and didn't get any crash. Someone else will have to test the rest as 3 is the only one I ever play and have.
edit:On 2-28
-
Super Metroid - In 2-28, there's a line of random noise at the border of the background graphics and your health bar at the top. This problem only exists when you're standing in the rain near your ship. The 2-17 build doesn't have this issue.
-
QUOTE(Consoleman! @ Apr 25 2006, 07:36 PM)

Super Metroid - In 2-28, there's a line of random noise at the border of the background graphics and your health bar at the top. This problem only exists when you're standing in the rain near your ship. The 2-17 build doesn't have this issue.
I see what you're talking about, It's pretty minor.
-
I'm starting to get pretty good at this porting of ZSNES. I just did a complete port of the 2-28 code and it runs great on the Xbox.
Havn't figured out how to pause the emulation or run the SNES power cycle code because its different in this version. I'll have to dig around the sources some more.
One thing I did notcie. Star Fox 2 doesn't crash anymore (it's fully playable), however there is constant screen flickering.
-
Starting to? I'd say it'd be safe to say you were pretty good at it from 1.0.
-
Unfortunatly, Top Gear 3000 is virtually unplayable (from when the race starts).
However it doesn't have the INSANE Graphics flicker in the windows version so I must have messed something up in the port.
Can anybody tell me how to actually "enter" a name in BS Zelda. I can't get past the name entry screen. Everytime I click exit it erases what I entered and I have to do it again.
-
yeah i get that line in metroid on the latest version of zsnex also. Another annoyance ive found is in Front Mission. When you attack with a machine gun the game almost freezes, everything else is fine. I think its just the ammount of flashing going on or somthing. By almost freeze i mean it does freeze but if you hold the white button down to speed up the game it snaps outa the freeze.
-
QUOTE
Btw, have you given consideration toward making a Top Gear 3000-only version of Zsnexbox? This would open up the door for you to use the stable 1.42 source, which would work similar to the 2/28 build, but minus many of the WIP glitches.
That's certainly a good idea except Star Fox is incorrect in 1.42 as well. Theres not a lot of difference between 1.42 and the 2-28. I think 1.42 was released on 1-20-05 so they should be pretty close. I may consider this if I can't fix whatever I broke in the 2-28 port. It works great in Windows so I must have done something wrong. Everything is perfect except Top Gear 3000.
I will likely release a 1.42 version anyway, even though I hate the idea of having several versions being updated at the same time and having to ask every user "which" version the bug occured in. I could easily see this becoming a nightmare if there was a WIP version, a StarFox version, a 1.42 version, etc....I will probablly wait until I have the GUI and features at 90% before I do this.
What would be even better would be if I could figure out a way to have multiple cores in the emulator and let the user pick the core they wanted to use (like Surreal does). I may look into this.
-
QUOTE(nes6502 @ Apr 25 2006, 11:34 PM)

What would be even better would be if I could figure out a way to have multiple cores in the emulator and let the user pick the core they wanted to use (like Surreal does). I may look into this.
This is what I was going to suggest. Between 1.42, 2-28-05 and 2-17-06 There hasn't been anything we've found yet that won't work. At least not that I know of.
I'm going to test about 15 or so more games tonight on WIP 2-28 and 2-17.
-
I don't think I'm going to do a multi core. It takes me about 2 hours to change from one Zsnes core to another. To include multiple cores i would have to make each core unique so they wouldn't conflict with each other. That means I would have to change thousands of variables and function names everytime I added a core. It would take me two weeks verses 2 hours and the only benefit would be they would all be started from the same launcher.
I will likely make the 2-28 the official build until the newer code works as well. Essentially everything works perfect or close to perfect in this build.
I also don't have any interest in merging Zsnes with Snes9X. I doubt it would even be possible. That would only work if there was a feature that could be extracted out and used with Zsnes. This is what Snes9x did to get Megaman X2/X3 working. They took the Zsnes obj files for the C4 chip.
-
Did you find out what was wrong with your new port regarding Top Gear 3000?
-
QUOTE
Did you find out what was wrong with your new port regarding Top Gear 3000?
Not yet. I've been working on it all evening. I'm going to just start over and go much slower and be extremely carefull.
Everything else was perfect and drives me nuts that Top Gear wouldn't work. It requires some crazy timing and the 2-28 port I did was 98% 2-28 code and 2% current code. The problem is likely there.
QUOTE
I think most people will be pleased with the 2-28 build. It's the only build of either Zsnes or Snes9x that plays both BS Zelda and Top Gear 3000. It's older which means it doesn't have all of the current bug fixes, but adding these bug fixes would come at the expense of stability.
Agreed. The 2-28 seems to be very stable and works very well overall. I've made progress on adding more filters so all the people wanting Simple2X with Soften display will be pleased with the next release. The next release will likely be new filters and the 2-28 core. Not sure when though
-
It's not that frustrating. It took me 6 weeks from the time I decided to do the port to get it working. At least now I can do it in 2 hours.
-
Well, after two complete rewrites and 2 partial rewrites, it looks as if Top Gear will only be playable in 1.0-1.2 or a Top Gear 3000 release. The only thing I can assume is that the assembler used to build this back in 2-28 has changed. It was buggy back then and ZSNES had to make code adjustments to account for it. I am changing nothing with the DSP4 code or the timing code but the game is running as if the timing is off. I don't really feel like spending forever trying to fix it in this release (maybe never) when it can be played in a previous one. There too many other important things (like a stable core) that need to get released.
-
save and load state is already there
-
Perhaps this is just wishful thinking, but have you considered contacting pagefault about the Top Gear 3000 issue? Maybe he might know something.
If you're going to do a Top Gear 3000 release, let me know. I can scour through the builds and find one that fixes some of the other bugs as well.
-
I have already spoken with NACH about this. He said it did the same thing for him before some timing issues were fixed. However, I havn't changed any code reltated to the CPU or sound chips (where the timing is mainly at) or the actual timing code, so I can only assume it is something related to the difference in the XBOX cpu and a standard intel one (the Xbox is a RISC intel x86) or an issue with the compiler/assember in optimization. This is a bug I will likely never fix so a Top Gear only release is likely.
Also, if anyone can find a build where starfox 2 is fully playable without crashes (if it even exists), I will do a star fox 2 build as well. It is virtually perfect in the 2-28 code but the screen is constantly flashing.
Check your pm Consoleman
-
I wouldn't worry about finding a build that fixes any other bugs.
I think what I'm going to do is do a 1.42 build and make it the default build. I will then use the 2-28 code as the Star Fox version, the 4-15 code as the Top Gear Version, and whatever build works best as the Star Fox 2 version. Then in the next release I will include all 4
there will be:
default.xbe (the 1.42 version)
TopGear3000.xbe (the 4-15 version)
StarFox.xbe (the 2-28 version)
StarFox2.xbe (? version)
Then for the most part for almost all games the default will work well. The user can use one of the other ones if they want to play those games.
-
If StarFox runs correctly in 2-28 then wouldn't it be better to just make that the default build and have one less XBE?
-
QUOTE(Likklebaer @ Apr 28 2006, 11:32 AM)

If StarFox runs correctly in 2-28 then wouldn't it be better to just make that the default build and have one less XBE?
I'm fairly certain nes wants to have a stable core version. It would cover just about everything including a lot of things we just haven't got around to testing. 2-28 works great but we haven't tested every game on it and someone might find something that flat out isn't playable on it but is likely playable on official 1.42. 1.42 has been out long enough and is probably used by enough people that I think what doesn't work correctly is well known by now.
-
QUOTE(Likklebaer @ Apr 28 2006, 04:32 PM)

If StarFox runs correctly in 2-28 then wouldn't it be better to just make that the default build and have one less XBE?
The 2-28 build is almost perfect, but it did introduce some graphical glitches not found in the 1.42 version.
-
I don't have star fox 2 and if I had it I wouldn't know what to look for but has anyone tested it on WIP 2-19-06? It mentions in the notes about fixing star fox 2.
-
don't know
-
I'm also for 720p support.Please do it
-
QUOTE
I'm also for 720p support.Please do it
Please post these types of requests in the 1.2 thread. This is a thread about testing. Not for people who don't read the previous threads to post the same request OVER AND OVER AND OVER
I believe I may have even hinted at this in my first post. Of course I could be wrong:
QUOTE
Can poeple post all known issues they've found with Zsnexbox related to the emulation (not feature requests).
-
No problem
-
This is mostly about getting Zsnes to play BS Zelda.
First off I'd like to say that I've been using xsnes9x in the past and have chosen to still stick with it since I like the interface more. Putting that aside, there seems to be one problem in that xsnes9x doesn't seem to play the perfectly patched versions of BS Zelda that can be found at the officially non-offical, but official BS Zelda site. These roms have been patched perfectly to resolve the time issues, startup issues, translation, etc and it comes in three different roms. Best version, Classic version and Original Japanese untranslated version. These all seem to work perfectly fine when loaded up in the PC version of Zsnes, no problems, good checksums and ready to play. This however doesn't work using xsnes9x and currently does not work using the Zsnexbox 1.2. A shame too since I thought for sure that the Zsnexbox emulator would work for sure and I was planning on keeping the Zsnes one on board along with xsnes9x just so I could play the BS Zelda games. And that just has me wondering why really... Why would one Zsnes play it perfectly with no checksum problems while the other two emus complain about it and fail to start it up?
Good luck with your progress with Zsnexbox, I'm sure I'll continually download the newest versions to see the progress as while I'm pleased with xsnes9x in many ways, it is still far from perfect and it is nice to have a choice between the two emus.
-SkyeWelse
-
QUOTE
Why would one Zsnes play it perfectly with no checksum problems while the other two emus complain about it and fail to start it up?
The code for each emulator is allways changing. One version of Zsnes will play them while another might not.
The following BS Zelda versions:
fixed_bszelda.zip
lincalibu.zip
pbzelda.zip
bszelda.zip
ld-bszld.zip
play perfectly in the version of ZsnexBox (2-28-05 code) that will be released next.
-
QUOTE(nes6502 @ Apr 28 2006, 05:21 PM)

The 2-28 build is almost perfect, but it did introduce some graphical glitches not found in the 1.42 version.
Sorry to keep on; but which games did you find were affected by graphics glitches in this build?
-
Super Metroid and Chrono Trigger
-
50% too fast? Can we even really know that considering the game was never released? Id go with that version as 50% too fast (especially in a snes star fox where normally, the polygons are struggling to just be manifested) is definitely the least offensive of those three problems.
-
the sounds off in snes9x...

edit: i did do that for a while tho. Despite its compatibility at the moment, i have made the jump to znes openly because i really like the way the filters make it look and the sound is incredibly more accurate. I could never go back to the hell that was the opening sequence in ff3 on snes9x now that ive hear what a good job znes does replicating it. This is just a personal opinion but sound emulation is important for me.
-
QUOTE(Major Tom @ Apr 30 2006, 06:37 AM)

Must agree with Jonesy_47 on his comment about the sound emulation... this was also my main incentive for using Zsnes.... hope the rollback to the 2/28 version doesn't comprimise this too much.....
Unlikely too much
A good way to get a general idea would be to try out your roms on the 2/28 WIP vs the 2/17 WIP vs official 1.43 on your PC. I'm sure in the porting process could make little differences spring up in Zsnexbox but so far they've been more faithful than not. Personally, I haven't played anything that didn't sound identical in my ears between the 3 versions as oppossed to between snes9x (xbox and pc).
Also while you're trying them out, see if you can find any games that don't work or have severe bugs.
A compatibility list may be worth working on. Not one on every game necessarily just games that shouldn't be used on the main version and maybe not zsnexbox. I think Consoleman mentioned something like this for rom notes.
-
QUOTE(Thraxen @ Apr 29 2006, 05:45 AM)

Those ROMS play fine in xSNES9x 1.41-1. Fortunately, you can just put the XBE file for v1.41-1 in the same install directory as "V1.42 WIP 17 June 2004" (the most recent version on XBox) and they can share the same ROMS and other files. I just renamed the XBE file to default141-1.xbe and linked to it directly in the dashboard XML file (I use XBMC as my dash).
QUOTE(nes6502)
The code for each emulator is allways changing. One version of Zsnes will play them while another might not.
The following BS Zelda versions:
fixed_bszelda.zip
lincalibu.zip
pbzelda.zip
bszelda.zip
ld-bszld.zip
play perfectly in the version of ZsnexBox (2-28-05 code) that will be released next.
Thanks for the help guys. What Thraxen said about using the old .xbe file worked for that emu and I appreciate your clearing up why Zsnexbox wasn't playing it. Helps me understand a bit how these different build work and how much of a pain it must be for you guys to come up with a version that can play everything. I look forward to future releases of Zsnexbox.
-SkyeWelse
-
3 - In Star Fox/Starwing, there's some stuttering when the planet zooms-in in the briefing screen.
-
I just downloaded Zsnexbox1.2 few days ago and works good. But theres one weird problem I'm having, everytime I play any games and after a minute or so, my controls doesnt work. The games runs perfectly, its just the controls locks up and cant move anything in the game. Also during this control lock up, I can't do IGR or go back to the menu. I'm pretty sure its not my controller doing this.