Joined
·
42 Posts
Another answer.
i have found another answer. this only applys to indivuals with beefy systems. if you change the cpu settings to normal (render as fast as possible) and set the custom frames to 150 and all other options to 0. doing this make the game render so fast that it doesnt register as much of the (what im going to call a polygon hence forwth) glitch. but allowing it to be set any higher or lower causes the polygon glitch to get processed and thus crashing your system. you still have to save frequently and it will still crash, but it saves you the time of having to switch between zerogs and gsdx.
Also on another note... i played all (seven when i played though it) sections that this polygon glitch occurs. and this seemed to help tremendously. some of the instances i didnt even have to start pcsx2 again. i made it through the whole glitch with some psychedelic rendering in most cases.
i hope that this tutorial has helped some of you.
seeing as pcsx2 is more processor laden then gpu.... its only sound logic to understand that this is some kind of cpu glitch. (spock reference) or that just muscling through it saves you time.
like i said this only worked on my tower. not my laptop.
my tower is:
Core i7 920, gtx 285 and 3gigs ddr3
my laptop is:
turion processor and freaking everything else on the mother board punk laptop POS.
good luck to everyone... FFX effing rocks my socks off.
i have found another answer. this only applys to indivuals with beefy systems. if you change the cpu settings to normal (render as fast as possible) and set the custom frames to 150 and all other options to 0. doing this make the game render so fast that it doesnt register as much of the (what im going to call a polygon hence forwth) glitch. but allowing it to be set any higher or lower causes the polygon glitch to get processed and thus crashing your system. you still have to save frequently and it will still crash, but it saves you the time of having to switch between zerogs and gsdx.
Also on another note... i played all (seven when i played though it) sections that this polygon glitch occurs. and this seemed to help tremendously. some of the instances i didnt even have to start pcsx2 again. i made it through the whole glitch with some psychedelic rendering in most cases.
i hope that this tutorial has helped some of you.
seeing as pcsx2 is more processor laden then gpu.... its only sound logic to understand that this is some kind of cpu glitch. (spock reference) or that just muscling through it saves you time.
like i said this only worked on my tower. not my laptop.
my tower is:
Core i7 920, gtx 285 and 3gigs ddr3
my laptop is:
turion processor and freaking everything else on the mother board punk laptop POS.
good luck to everyone... FFX effing rocks my socks off.
