I did read the whole thing. Your most recent explanation of the problem was "Just enter a game, wait for title screen, Alt+F4, then close Dolphin program and you get a crash dialog." That explanation doesn't mention anything about running the same game twice, and it says that a crash dialog appears when closing Dolphin, not when launching a game. Now, I'd like to ask... Does clearing the shader cache affect your ability to launch a game like it does for the poster of this topic?
Crash on 2nd+ use?
|
02-16-2016, 04:17 AM
If you really had read "the whole thing" you would have read not only my last words on clearing cache, settings, etc and testing on a blank slate, but also the initial problem description of the issue:
Quote:What's the problem? Describe what went wrong. That's practically a copycat bug description of the one described here. But if you delve deeper (something I don't expect everyone to do since it takes TIME), I got to the extent of finding that Dolphin is on the whole very unstable AFTER THE FIRST GAME RUN. So you name it; second game run, close Dolphin, whatever you decide to do leads to a crash. Currently I can only think two things, it's a problem with Dolphin portable, it's a problem with older drivers, it's another Dolphin buried problem. 02-17-2016, 10:18 PM
(02-16-2016, 04:17 AM)eckso Wrote: If you really had read "the whole thing" you would have read not only my last words on clearing cache, settings, etc and testing on a blank slate, but also the initial problem description of the issue: Mentioning savestates makes your description rather different, but I'm going to ignore that because you later said that using savestates isn't necessary for triggering the bug. All we have left then is "Program crash after re-entering a game", which sounds similar because of how few details there are, but what you're describing actually not the same as I'll show next: (02-16-2016, 04:17 AM)eckso Wrote: But if you delve deeper (something I don't expect everyone to do since it takes TIME), I got to the extent of finding that Dolphin is on the whole very unstable AFTER THE FIRST GAME RUN. So you name it; second game run, close Dolphin, whatever you decide to do leads to a crash. That's what doesn't match the issue that this topic is about. First, this topic's issue only happens when launching a game, not when doing other things, like closing Dolphin. Second, because this topic's issue is a shader cache issue, it happens when launching a game after that specific game already has been launched once, regardless of whether it was in the current session of Dolphin. On the other hand (please correct me if I'm wrong), your issue happens when entering any game after entering any other game. (I'm assuming it doesn't carry over to the next Dolphin session, but I don't want to make a point of that since you didn't make that fact clear.) I would still like to know if deleting the shader cache folder affects your issue. 02-21-2016, 04:55 AM
Without portable, I get white screen after the 2nd time I open a game on opengl only.
02-23-2016, 12:38 PM
(01-01-1970, 10:00 AM)JosJuice I think it's pretty straight forward... "Crash on 2nd+ use" includes: "very unstable AFTER THE FIRST GAME RUN. (...) Whatever you decide to do leads to a crash" I'm not sure what's so hard to understand. The issue report states it very clear that I deleted the cached shaders (I wouldn't recommend deleting the cache folder). This goes to show that in order to criticize somebody you still need to get your facts together and read a bit. I said that I know what the problem is, most likely a driver issue, and asked for a dump feature so I can give you all the nitty gritty details you are craving were you or weren't going to read them afterwards. 02-23-2016, 07:07 PM
(02-23-2016, 12:38 PM)eckso Wrote: I think it's pretty straight forward... "Crash on 2nd+ use" includes: Who's the one only reading the title now? The first post says "any time a game is opened for a second time, it immediately crashes". In your issue, it can happen at other times than precisely when opening a game. (02-23-2016, 12:38 PM)eckso Wrote: The issue report states it very clear that I deleted the cached shaders (I wouldn't recommend deleting the cache folder). I apologize, I did in fact miss that line. Anyway, it doesn't seem like clearing cached shaders affects your issue, which is yet another difference from this topic's issue. (02-23-2016, 12:38 PM)eckso Wrote: I said that I know what the problem is, most likely a driver issue, Okay, but that's not much to go on. (02-23-2016, 12:38 PM)eckso Wrote: and asked for a dump feature so I can give you all the nitty gritty details you are craving were you or weren't going to read them afterwards. "some dump feature" is very vague. I don't understand what it would be supposed to dump. 02-24-2016, 01:12 AM
(02-23-2016, 07:07 PM)JosJuice Wrote: Who's the one only reading the title now? The first post says "any time a game is opened for a second time, it immediately crashes". In your issue, it can happen at other times than precisely when opening a game. Since when admitting a fact, automatically denies every other single fact? (02-23-2016, 07:07 PM)JosJuice Wrote: "some dump feature" is very vague. I don't understand what it would be supposed to dump.Every half-serious program has a dump feature for when it crashes, I don't think I need to explain these kind of things at this level, but anyways; build version, portable or not, video driver, OS, game version (incl. hash)... that's as simple as you would get, in addition you get reports on what modules, memory areas the crash occurred, and every other assertion log you might have implemented in code, detailed log included. You are welcome. 02-24-2016, 03:00 AM
Dolphin has a log feature, but you need to enable it since it's disabled by default due to it taking a performance hit on some systems. Under View, check Show Log and Show Log Configuration. Then turn on all the logs and try to run the game.
02-24-2016, 03:21 AM
(02-24-2016, 03:00 AM)KHg8m3r Wrote: Dolphin has a log feature, but you need to enable it since it's disabled by default due to it taking a performance hit on some systems. Under View, check Show Log and Show Log Configuration. Then turn on all the logs and try to run the game. That log isn't useful for debugging crashes in most cases. |
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)