Topic: Zsnexbox 1.2 (Read 886 times)

Opoth · « **Reply #90 on:** May 01, 2006, 03:59:00 AM »

QUOTE(Harlock_Gbase @ May 1 2006, 10:52 AM)

can anybody tell me why none of my controllers works with Zsnes 1.2? Games load fine, but button presses are ignored by the emulator...

It says in the readme that if you have anything plugged into ports 3 and 4 of your Xbox when you start the emulator, your controllers might not work once you're in-game.

Harlock_Gbase · « **Reply #91 on:** May 01, 2006, 04:02:00 AM »

well of course i have controllers plugged in in ports 3 and 4, as i want play bomberman with 3 other players...

Harlock_Gbase · « **Reply #92 on:** May 01, 2006, 04:27:00 AM »

lol, yepp, already went back to xsnesx. Runs perfect for me...

dohopoki · « **Reply #93 on:** May 01, 2006, 06:09:00 AM »

3-4 player support isn't implemented yet.

fil · « **Reply #94 on:** May 02, 2006, 05:05:00 AM »

there seems to be some emulation bugs, ive had a few games crash, or go to a black screen and not load, and thats on standard unhacked roms, big games aswell, think bomberman 5 froze after level one, cant remember which ones exactly.. oh bonk 2 wont load, i'll try and make a more comprehensive list!

main thing i think could be added is ability to go back to the game after you pressed right thumb stick

and also ability to turn off the scrolling sound effect?

nes6502 · « **Reply #95 on:** May 02, 2006, 06:07:00 PM »

QUOTE(nes6502 @ Apr 24 2006, 12:29 AM)

I have already implemeted HQ2x. I havn't figured out how to clear the buffers when changing games so it wasn't released in 1.2

Unfortunatly, it doesn't look that great. It's blurry and hits the FPS hard. Most games are in the low 50's and it doesn't look any better than Super Eagle (in my opinion).

I will release it anyway in a later release.

Fixed HQ2X. I wasnt setting some variables and that is why it was blurry. It is definatly the best looking filter so far. It's also the most expensive. Some games still run at 60/60 with it, but many drop drasticlly. Chrono Trigger averages 30 FPS.

Jonesy_47 · « **Reply #96 on:** May 03, 2006, 12:13:00 AM »

Is there anyway to use a main core for the majority of roms and then program the emulator to open up a seperate .xbe used for that version of znes? Quick Example: It shows Star Fox on my main rom list and, when i click on it, the game starts up when, in reality, another .xbe with the correct build of znes used to play the game has begun and auto-lanunched the Star Fox rom for us, the common man never being the wiser of the action.
When you want to quit, it takes you back to the default.xbe. eh? eh?...

Please dont flame me if this is impossible or would handicap the emulator for some reason. I understand emulation but nothing about programming.

nes6502 · « **Reply #97 on:** May 03, 2006, 12:16:00 PM »

QUOTE(dtw_2005 @ May 3 2006, 07:03 PM)

I think that's possible, but i think nes talked about it. If i remeber right, he said it would be a mega huge pain because he would have 2 recode/rename alot of stuff so the 2 versions would have seperate files or something like that? and that the roughtly 2 hour port would take lots longer. I may be wrong though.

Keep up the good work nes! Many thanks

Actually this is a bit different. This is still two separate ports but "launched" from one xbe. This would be easier than a multi core, but I have no idea how to launch one xbe using another. If that were simple (i.e. someone can tell me how to do it), I might consider this type of functionality. Otherwise, the user will have to start the xbe they want directly.

However, this does have a downside. If the user wants to use the TopGear 3000 build to play Final Fantasy 3 (stable and PERFECT in the new WIP code) this would prevent it. This is because that build would be designed to auto launch a certain game and not be programmed to launch any game.

Jonesy_47 · « **Reply #98 on:** May 03, 2006, 02:07:00 PM »

QUOTE(nes6502 @ May 3 2006, 07:23 PM)

Actually this is a bit different. This is still two separate ports but "launched" from one xbe. This would be easier than a multi core, but I have no idea how to launch one xbe using another. If that were simple (i.e. someone can tell me how to do it), I might consider this type of functionality. Otherwise, the user will have to start the xbe they want directly.

However, this does have a downside. If the user wants to use the TopGear 3000 build to play Final Fantasy 3 (stable and PERFECT in the new WIP code) this would prevent it. This is because that build would be designed to auto launch a certain game and not be programmed to launch any game.

Ok, so why would it be that difficult (after the initial programming of getting the main core emulator to launch Star Fox with a different .xbe, Top Gear another, etc.) to just say, set up ff3 to ALSO auto launch the .xbe used for TopGear 3000? You could have one MAIN core, then when some games show compatibility problems with the main, you could just program them to auto-launch the other port that is more stable for that game...does this make any sense? Im not even sure how this differs from multi-core aside from the fact that we wouldn't be able to manually choose which znes build we would use to run our rom (as seen in Surreal). It would already have been chosen for us (the most stable choice being made by nes6502, of course) as to work seamlessly from the main rom list and keep us the hassle of having to load different .xbe's for about a handful of games.

Heres and example of what i mean

In the root dir for znes there would be a few .xbe's

Default.xbe
Starfox.xbe
starfox2.xbe
topgear.xbe

Ok. Now, my original idea was you browse your roms through default.xbe and there, Star Fox and Top Gear show up with the rest of the roms but, as i click on top gear, the default.xbe recognizes the rom, shuts itself down and auto-launches top-gear in topgear.xbe. Then, when we are done playing, it exits from topgear.xbe and returns us to default.xbe.
NOW, if Final Fantasy 3 is one of the few games that runs noticeably better on the topgear znes build (sorry, i dont know the dates. ie, 3-28-05 build and whatnot...) why not just write it into the code of the default.xbe as ANOTHER game that should auto-launch from the topgear.xbe?

At first, this sort of functionality could only be implemented for the few choice games (Star Fox, Star Fox 2, and Top Gear) that are a priority of running well. Then, if there turns out to be a few really good games that the znes build you eventually end up settling on for your next default.xbe doesnt play correctly, for the next update, you could have them auto-launched by one of the other 3 .xbe's.

If this makes no sense, i yet again apologize. I am a programming retard and it cannot be helped. This idea just makes sense to me, thats all and since, in theory, it would be shutting down one .xbe to load up another (and likewise) there wouldnt be memory issues either or at least no more than there would be for one port running at a time. The only little quirk i could see happening (aside from having a chance of being a programming impossibility...*shrugs*) is that you would have to set up your config options seperately for each .xbe the first time you ran one of the choice roms but even this wouldnt be a problem if a configuration mode is added by pressing in the right thumstick (a la xsnes9x and xport's slew of ports). If this worked, it could make Zsnexbox the most compatible super nintendo emulator on the xbox in about 2-3 more updates. I hope this isn't impossible to accomplish.

Thanks for this wonderful emulator by the way (playing it as i type).

nes6502 · « **Reply #99 on:** May 03, 2006, 02:45:00 PM »

I think perhaps the best idea would be to have "core" directory. This directory would contain the alternate cores. The user would have to select the core they wanted before launching the game. Once launched, this would execute the selected core. This would allow any game to bu run from any core and still have a common launcher. This is similar to a multi-core design but simpler to implement. I "may" look into this for a later release. There would be a considerable amount work that would have to be done and it would be tricky. I'm not saying it won't happen, but it is not high priority. Ideally ZSNES will become stable and there will be one build that does everything anyway.

Jonesy_47 · « **Reply #100 on:** May 03, 2006, 02:53:00 PM »

Ah ha ha. Yeah. Now, as for FINDING that ideal zsnes build...i know theres a lot of people testing them out to help contribute to zsnexbox tho so good luck. I was just throwin that idea out there since i really despise the idea of having to manually boot out of the main emulator just to play one game and then, to return to the main emulator, have to manually boot out AGAIN and reboot the main one.

dohopoki · « **Reply #101 on:** May 03, 2006, 04:55:00 PM »

QUOTE(Jonesy_47 @ May 3 2006, 05:00 PM)

Ah ha ha. Yeah. Now, as for FINDING that ideal zsnes build...i know theres a lot of people testing them out to help contribute to zsnexbox tho so good luck. I was just throwin that idea out there since i really despise the idea of having to manually boot out of the main emulator just to play one game and then, to return to the main emulator, have to manually boot out AGAIN and reboot the main one.

One nice things is, many games run identical/near identical in all versions of ZSNES so you might get lucky and not need the other versions. I can say that WIP 28 takes care of 99% of my collection just fine and 1.42 takes care of the other 1%.

of course, that's because I'm a top gear 2 type of guy

nes6502 · « **Reply #102 on:** May 03, 2006, 04:58:00 PM »

QUOTE

i know theres a lot of people testing them out to help contribute to zsnexbox

I wish there was. There seems to be only two.

Author Topic: Zsnexbox 1.2 (Read 886 times)