Posts: 16
Threads: 2
Joined: Oct 2015
Reputation:
0
(10-17-2015, 08:20 PM)willkuer Wrote: What happens if you switch disks (hot swap vs system reset)? What happens on reset?
When I switch disk with game 1 not closed:
a) Just switching disk WITHOUT reset:
Game 1 just pauses in the middle of action, new game is not launching, not having any errors.
b) Swithching disk WITH reset:
Game 1 ends correctly, new game starts correctly with quick restart (skipping PlayStation logo)
Sponsored links
Posts: 5.076
Threads: 18
Joined: Oct 2010
Reputation:
154
10-17-2015, 08:33 PM
(This post was last modified: 10-17-2015, 08:34 PM by willkuer.)
So on switch there is no crash?
What happens if you run the emulation, close the gs window, open and close all available plugin configurations, and then shutdown?
Posts: 16
Threads: 2
Joined: Oct 2015
Reputation:
0
(10-17-2015, 08:33 PM)willkuer Wrote: So on switch there is no crash?
What happens if you run the emulation, close the gs window, open and close all available plugin configurations, and then shutdown?
Yes, on switch with reset there is no crash, game 1 finishes normally, game 2 starts correctly.
Tried to perform your described actions, still the same result. Also tried to close GS window, then change GS plugin, change any other plugins etc. - the same.
Posts: 5.076
Threads: 18
Joined: Oct 2010
Reputation:
154
Do you use folder memcard or file memcard?
Can you please try to find the revision that broke the shutdown for you. I would suggest a binary search algorithm: check if the oldest available git release reproduces the issues. Afterwards test always the revision directly in the center between earliest working and latest broken release. Using this algorithm reduces the amount of trials a lot.
Posts: 16
Threads: 2
Joined: Oct 2015
Reputation:
0
10-17-2015, 09:07 PM
(This post was last modified: 10-17-2015, 09:08 PM by Delmor_S.)
(10-17-2015, 08:46 PM)willkuer Wrote: Do you use folder memcard or file memcard?
Can you please try to find the revision that broke the shutdown for you. I would suggest a binary search algorithm: check if the oldest available git release reproduces the issues. Afterwards test always the revision directly in the center between earliest working and latest broken release. Using this algorithm reduces the amount of trials a lot.
I use file memcard.
Browsed orphis:
http://buildbot.orphis.net/pcsx2/index.php?m=fulllist
I DO NOT have this problem with the latest available 1.2.1 (v1.2.1-251-g1a483a7) build. (July 15 2014)
I ALREADY HAVE this problem with the oldest available 1.3.1 (v1.3.1-260-gb89f0cf) build. (May 9 2015) I guess, period of time is too big, so it may be even not possible to find the cause
Every time I performed the same operations and did not change plugins, and for 1.2.1 everything works correctly even with gigahertz's plugin.
Posts: 5.076
Threads: 18
Joined: Oct 2010
Reputation:
154
Please check this list as well. Revisions around 5870 is release 1.2.1
Posts: 20.326
Threads: 405
Joined: Aug 2005
Reputation:
554
Location: England
Hmm, I also can't reproduce this on my end :/
Posts: 16
Threads: 2
Joined: Oct 2015
Reputation:
0
10-18-2015, 04:45 AM
(This post was last modified: 10-18-2015, 04:53 AM by Delmor_S.)
(10-17-2015, 09:39 PM)willkuer Wrote: Please check this list as well. Revisions around 5870 is release 1.2.1
I checked latest available release 5932, PCSX2 1.3.0.r5927 (Mar 23 2014) and I do not have this problem. Should I? As I've already written, I checked everything with pcsx2-v1.2.1-251-g1a483a7-windows-x86 (in fact, when it is launched in log it is marked as 1.3.0-20140715112245 - compiled on Jul 15 2014) and also did not have this problem. This means, that I need newer build than this one, the next new build is v1.3.1-261-g5565544, and I already have this problem with it.
UPD: Also, the latest strings I always have in my logs, when finished incorrectly:
Closing plugins...
Closing DEV9
Closing FW
Closing USB
Closing CDVD
Closing SPU2
Closing PAD
Closing GS
Plugins closed successfully.
Decommitting host memory for virtual systems...
EE/iR5900-32 Recompiler Reset
And that is it. Upon recompiler reset pcsx2 just brokes.
Maybe it is Windows 10 specific? I can check it for Windows 7, if it is required.
Posts: 111
Threads: 15
Joined: Oct 2015
Reputation:
5
10-18-2015, 05:05 AM
(This post was last modified: 10-18-2015, 05:05 AM by .r5.)
(10-18-2015, 04:45 AM)Delmor_S Wrote: I checked latest available release 5932, PCSX2 1.3.0.r5927 (Mar 23 2014) and I do not have this problem. Should I? As I've already written, I checked everything with pcsx2-v1.2.1-251-g1a483a7-windows-x86 (in fact, when it is launched in log it is marked as 1.3.0-20140715112245 - compiled on Jul 15 2014) and also did not have this problem. This means, that I need newer build than this one, the next new build is v1.3.1-261-g5565544, and I already have this problem with it.
UPD: Also, the latest strings I always have in my logs, when finished incorrectly:
Closing plugins...
Closing DEV9
Closing FW
Closing USB
Closing CDVD
Closing SPU2
Closing PAD
Closing GS
Plugins closed successfully.
Decommitting host memory for virtual systems...
EE/iR5900-32 Recompiler Reset
And that is it. Upon recompiler reset pcsx2 just brokes.
Maybe it is Windows 10 specific? I can check it for Windows 7, if it is required.
I tried reproducing your bug in Windows 10 and couldn't.
Posts: 20.326
Threads: 405
Joined: Aug 2005
Reputation:
554
Location: England
I'm also running Windows 10.
Can you try clearing out your Inis folder (you can rename it if you want to keep your old settings for later), making 2 new memory cards and try running it as administrator?
|