Found a bug? Please report it, but remember to follow the bug reporting guidelines.
Missing a sane feature? Let us know!
But please do NOT request ports to other systems.
When I try to begin a new game, suddenly zsnes closes itself, before the scene of the ocean, this does not happen with version 1.42. I do not know in which version it began this problem.
Are you running any specific filters(graphics and/or sound)? Please specify and list your systems specs (OS, video, RAM)
I have no problems running Chrono Trigger.
As a suggestion though.. delete all the .cfg and .dat files in the folder ZSNES is in when you are dealing with 1.42 and post-1.42 WIPs... those files are incompatible with each other and can cause problems with games. Of course this is avoidable if you are running each different ZSNES version in a separate folder.
Deathlike2 wrote:Are you running any specific filters(graphics and/or sound)? Please specify and list your systems specs (OS, video, RAM)
I have no problems running Chrono Trigger.
CPU: Pentium 4 1.6
OS: Windows 98 SE
Video: Radeon 7200
RAM: 256 MB
Sound: VIA AC'97
Video: 640x480 DR F
Filter: Interpolation
Triple Buffering: ON
Vsync: ON
Sound options: default
I have the same configuration that in version 1.42, with its respective differences, with version 1.42, I do not have this problem. The problem arises just before the scene of the ocean (just before when the gulls fly on the ocean) perhaps the problem is that I use Windows 98 SE, but it is rare that with version 1,42, I do not have any problem, basically with the same configuration.
Deathlike2 wrote:
As a suggestion though.. delete all the .cfg and .dat files in the folder ZSNES is in when you are dealing with 1.42 and post-1.42 WIPs... those files are incompatible with each other and can cause problems with games. Of course this is avoidable if you are running each different ZSNES version in a separate folder.
That is what I do, a different folder for each version.
ZSNES even allows both of these to be checked at the same time? I realize it's most likely ignoring the vsync option, but that's still ... odd.
Sorry to go offtopic, that just stuck out at me.
Yes. You can enable both. I don't know if the emulator actually ignores VSync then.
whicker: franpa is grammatically correct, and he still gets ripped on? sweener2001: Grammatically correct this one time? sure. every other time? no. does that give him a right? not really.
After being using different versions, I found that with this version (September 09 2005 WIP) I do not have this problem either, with the same configuration of November 26 WIP, it seems to be that all the versions of October and November give the same problem to me.
The fact that you can enable both or that vsync is ignored when Triple Buffering is checked?
That fact that when you enable both, VSync is actually ignored (disabled) even though it's marked as enabled.
whicker: franpa is grammatically correct, and he still gets ripped on? sweener2001: Grammatically correct this one time? sure. every other time? no. does that give him a right? not really.
From what I can tell, it's currently good to have both checked in ZSNES, and here's why:
In fullscreen, if I can only have triple buffering checked and vsync unchecked, then when I go back to windowed mode, I'll have to go back into the video menu and enable vsync again. In other words, when I disable vsync in fullscreen mode, ZSNES doesn't remember that I would still want it enabled in windowed mode. I'd rather have both enabled so that I can be lazy.
I hope that makes sense. I guess it is a bug. ZSNES needs to remember that I want vsync enabled in windowed mode, disabled in fullscreen mode, and triple buffering enabled in fullscreen mode.
That's a better reason, but triple buffering works the same in windowed mode as it does in fullscreen. You still only update the screen during the vertical blanking period. And in fact, you could optimize it further by updating as soon as the scanline counter reached below the emulator window, potentially a lot sooner than vblank.
Neither really work, as most people who like their eyes won't use 60hz as a desktop refresh rate on anything less than a nice LCD monitor.
The other minor detail is that Vsync+Triple buffering are usually separate options in which vsync generally is enabled so triple buffering benefits the most...
Also... triple buffering is not available for windowed modes because of some "limitation" of DirectX... you probably can google the specifics as to why (I'm only recall this from memory).
I believe this is true for the most part.. since this is been true for every 3D game... not too sure what to make of ZSNES, but it follows the same rules...
I'm curious as to what the heck is going on with your comp... because it is making no sense as to why it is crashing.
The only thing that may be causing it is either the CPU/OS combo (I doubt it is entirely safe to use Win98SE on a more recent processor) or you need to redownload your copy of the WIPs (data corruption?)
For a thought, try to isolate your problem by starting fresh in ZSNES... Basically.. you want to start ZSNES like if it were the first time (just don't configure anything), and run Chrono Trigger.. see if it works. If it works, then there is something wrong with an option you have enabled/disabled and work your way up to a point where it does crash. That way, you can see what option is causing the problem.
On a separate note, make sure MMX support is enabled...
Also, consider updating your video card drivers.. I know ATI has limited support for Win98SE.. but it could be the problem.