greatflash

I am sure it is somewhere. The initialisation on ssf is pretty long with the final stage being the opening of the full window/screen view. So. Seeing it balls out at around a quarter of this duration I would think it was not video related as I would expect the video initialisation to be later on the list? one thing I noticed in the events was the ssf.exe runs with virtualisation

I will give it a go when I get home. I didn't say it was killing a process, I was just looking at the two options so. It looks like something during the init of ssf is locked and causing it to drop back. Sadly ssf does not write a log and the source is not available, making it a little hard to debug. Shima has had requests for the source before and has not released it to anyone afik. Sadly, that leaves Yabuse! Benefit that there is no need for a virtual drive, bad news is that it is way behind ssf!

Yes, there are no logs at all.

Thanks for the 'shout' Stig There has also been quite a lot of work on the databases recently and the slow (but coming) addition of the new MAME system rom names. This can be seen when looking at the SNES database. GX currently does not know about the new data, but that will come once it is improved within the databases. There are also some other important additions, more about that at a later time. ps. I really must output another developer list You have to love the 64. It's pretty much what I cut my teeth on with coding games.

I didn't think this would make any difference, and it doesn't. As far as I am concerned, it has nothing to do with settings or anything else along them lines, it is a process or resource issue I believe.

I don't think log posts are going to be much use here. Gx does not report an event at all. All have to do is, launch gx and window it launch ssf ssf exits if I don't have gx running, all is fine. The thing I notice about ssf that is different to other emulators is, when opened it appears not to gain focus until it enables it's window view. The first part of the launch is just the title bar (a collapsed view) and gx kills it just before it opens the full window. The means it is one of two things (perhaps) ssf needs a locked resource that gx is using and fails because it cannot gain it (has anything changed here in the last few revisions?) Gx sees or confuses the process of ssf and kills it. Why this affects some and not others, I have no idea. I use Nvidia (not that it matters) and run Windows 10 ultimate 64bit along with the latest gx build. Though I am sure this has worked before on an earlier revision (though I cannot guarantee it). I will ill check later if ssf writes any kind of log. Forgot to check that this morning.

I have just ran into the exact same issue. It has nothing to do with any mounting options. If Gameex is running and I just launch SSF in the background, it is killed just before the SSF window becomes full-size. That is all it takes, just having GX running is enough to stop SSF from completing it's launch. All rather odd?

The databases are slowly evolving to add support for mame emulated systems. This is a big job though. Currently not sure if the enhanced database support will be in gemeEx or Evo first.

Um. Yep. Lol

There is a fairly extensive database for the Saturn.