Ok, I found the error, it starts from GSdx R.5685, look into the changes from gregory.
Log message
all: gcc warning clean (round 2)
* reorder static initialization list
* Add missing virtual desctrutor to virtual object <- This could cause the Problem here.
* int -> uint/u32/uint32 cast of for loop index
* add a missing return in pxTrySetFocus
* fix size parameter of memset m_clut
* disable missing-field-initializers warning
* disable unused-local-typedefs warning
Good find
I will link it in the googlecode.
just to be certain, it definitely doesnt happen in r5684 correct? (gsdx will probably be r5682)
(08-19-2013, 09:36 PM)refraction Wrote: [ -> ]Good find I will link it in the googlecode.
just to be certain, it definitely doesnt happen in r5684 correct? (gsdx will probably be r5682)
I've checked it twice, no doubt GSdx SVN R.5685 is the polluter.
Thank you for your testings
(08-19-2013, 11:22 PM)refraction Wrote: [ -> ]Thank you for your testings
No problem, I hope we can work together once again in the future.
Awesome, it's always such a hassle to hunt evil revs down.
Will we every get a solution for "
Impossible blend for D3D: (Cd - Cs) * As + Cd"
Fire
HW (The problem)
SW
I know its not the biggest concern...
[attachment=45425]
Fatal Frame 2's been suffering some glitchy texture pop-in (I'm on build 5722).
Haven't been able to test which build caused it (I'm super lazy and busy), but I thought it'd be worth mentioning for now.
(08-29-2013, 12:46 PM)devina40 Wrote: [ -> ]Fatal Frame 2's been suffering some glitchy texture pop-in (I'm on build 5722).
Looks painful
.
FF\PZ 2 & 3 has always had minor glitches in HW-mode,
however I checked with r5725 using 16:10 ws-pnach and 2x Resolution,
but didn't have the glitch-problem in your screen-dump.
You should have a look at your "Emulation Settings" & "GSdx Settings".