..:: PCSX2 Forums ::..

Full Version: Big issue with r1122
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
See attachments 1 & 2.
The emu crashes when trying to execute any ISO or DVD. I don't know what the problem is, only that there's no new revision right now through the trunk. I've tried an older version (r1088) and it's working.

Version used: PCSX2 0.9.6 SVN r1122
CPU config
MTGS checked
DualCore mode checked
VuRec0 and VuRec1 checked
Using normal frame limit mode
Default cycle mode
INTH hack

Plugins used:
- GSDX 1.15 r1076
- SPU2-X 1.1.0 r968
- LilyPad svn (r1034) 0.10.0
Resolution: Windowed option activated.

My pc:
Intel Core2Duo E7300 2.66Ghz
Gigabyte G31-G31M-S2C motherboard
XFX 8800GS 384MB PCI-e
2x1GB DDR2 800MHZ Kingston
HITACHI 500GB SATA-2
Windows XP SP3
LG Flatron W1941S 18.5"
Hey, try to find the specific revision that it's not working. 1022 is Linux changes only, and it should not touch your pcsx2 ( Windows compile )
Well, I've checked and seems it's r1114, made by Jake.Stine.

Removed VU-Skip [helps simplify the frameskipper logic] -- Use the VU Cycle Stealer hack instead for better, faster, more stable speedups of the VU1 unit.

One of the files says
/trunk/pcsx2/x86/ix86-32/iR5900-32.cpp

which is what is causing the error mentioned above.
Also weird 'cause I have Normal Frame Limit mode activated and not VU skip.
Seems weird, I can compile and run game with that revision.
Maybe the console log will be helpful
Finally found it, this error start from revision 1116.
Leave it to developer, but let's see what I can do Tongue
(05-03-2009, 04:49 AM)Funnnny Wrote: [ -> ]Finally found it, this error start from revision 1116.
Leave it to developer, but let's see what I can do Tongue

Ok, thanks! Smile
Quote:mcase(0x1f80847c):
ret = psxHu32(addr);
break;
Insert it into ps2/Iop/IopHwRead.cpp, line 434 ( before the jNO_DEFAULT ).
It may break other things, but I can boot and play some game with this
Here the patch if you know how to use it
I've checked and this issue appears to be fixed since r1129 with your patch. Thanks for the help anyways!