Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
boot issue with the build version after v1.2.1-561-g08dc8b4
#1
I've downloaded the latest version v1.2.1-639-gfa3db52.
after I start it with default configuration,The Program log window just shows up with some information (Last line is "Plugins shutdown successfully".).and then it will just freeze there for about 5 min,Then it starts normally.
Every time I restart pcsx2,The Program log window will freeze there for about 5 min!
I've configured other plugins and bios .But no improvement.
Then I tried serveral other builds(like v1.2.1-598,592,etc) and found that any builds after v1.2.1-561-g08dc8b4 have such issue on my pc.(It looks like v1.2.1-561 version works fine )
Then I tried copy the plugins of v1.2.1-639 to v1.2.1-561,It works normal.(So the plugins don't cause the issue)
But after I tried overwrite the pcsxe2.exe with the v1.2.1-639 one.The issue happened again.Maybe the pcsxe2.exe is the problem.

When the log window get freezed ,emuLog is :
PCSX2 1.3.0-20141004113334 - compiled on Oct 4 2014
Savestate version: 0x9a0a0000

Host Machine Init:
Operating System = Microsoft Windows 7 Service Pack 1 (build 7601), 64-bit
Physical RAM = 16268 MB
CPU name = Intel® Core™ i7-4770K CPU @ 3.50GHz
Vendor/Model = GenuineIntel (stepping 03)
CPU speed = 3.491 ghz (8 logical threads)
x86PType = Standard OEM
x86Flags = bfebfbff 7fdafbbf
x86EFlags = 2c100000

x86 Features Detected:
SSE2.. SSE3.. SSSE3.. SSE4.1.. SSE4.2.. AVX.. FMA

Reserving memory for recompilers...
Reply

Sponsored links

#2
So it happens on 1.2.1-561. Just checking:

Have you tried 1.2.1-563:
https://github.com/PCSX2/pcsx2/commit/v1...3-gf7192b8

It seems 562 is not available but that should narrow the commit down Smile
Reply
#3
(10-23-2014, 01:20 PM)zwzplayer Wrote: and found that any builds after v1.2.1-561-g08dc8b4 have such issue on my pc.(looks like v1.2.1-561 version works fine )
.

well, if there isn't any issue on the other build then why dont you use them, and as per the crashes, did you try running them as administrator. and set the priority of pcsx2 to high in taskmanager if the issue still persists try reinstalling the version.
We're supposed to be working as a team, if we aren't helping and suggesting things to each other, we aren't working as a team.
- Refraction

[Image: 84t1dRu.png]
Reply
#4
(10-23-2014, 03:07 PM)s.sakash Wrote: well, if there isn't any issue on the other build then why dont you use them, and as per the crashes, did you try running them as administrator. and set the priority of pcsx2 to high in taskmanager if the issue still persists try reinstalling the version.
I've tried what you suggest,but it still freeze.
Currently I'm using the lastest 639 with the pcsx2.exe replaced by 561.It works fine.

(10-23-2014, 03:06 PM)pablocrossa Wrote: So it happens on 1.2.1-561. Just checking:

Have you tried 1.2.1-563:
https://github.com/PCSX2/pcsx2/commit/v1...3-gf7192b8

It seems 562 is not available but that should narrow the commit down Smile
I've tried 563.It will still freeze
Reply
#5
(10-23-2014, 03:40 PM)zwzplayer Wrote: I've tried 563.It will still freeze

Right well, that should narrow down the commit, I unfortunatelly have no clue how to go back from an orbis buildbot commit number to the GIT, can a developer/knowledgeable person comment on that?? Smile
Reply
#6
(10-23-2014, 04:46 PM)pablocrossa Wrote: Right well, that should narrow down the commit, I unfortunatelly have no clue how to go back from an orbis buildbot commit number to the GIT, can a developer/knowledgeable person comment on that?? Smile
I'm also curious about the changes made from 561 to 562/563.Just need a clue about 562/563's git commit link.
Reply
#7
If possible, rather than narrowing Git comments(*), run directly any of versions which the problem occurs on Visual Studio would be the most simple way to find a cause of the problem.

(*) You can confirm Git comments around 561 near Sep. 6 by using Git tools, but many commits are merged, therefore this makes you difficult to read them by chronological order like this:

[attachment=52831]

P.S.
I hope my updates like 611 are not a cause of the problem. Smile
Reply
#8
Can you try fixes suggested here?
http://forums.pcsx2.net/Thread-Latest-De...#pid409209
Reply
#9
I just glanced at the problem, but unfortunately the max resolution of my monitor is 1280 x 1024. Smile
Anyway, I'll check it later.
Reply
#10
(10-24-2014, 12:01 PM)rama Wrote: Can you try fixes suggested here?
http://forums.pcsx2.net/Thread-Latest-De...#pid409209
Thank you.I think that's the point.
Reply




Users browsing this thread: 1 Guest(s)