Maybe if you can extract a replayable apitrace log for a few frames that reproduce the issue? Then they would need neither pcsx2, nor a bios or a game.
edit: oh, I forgot DirectX, well I don't know if DirectX has something like Apitrace, but I'm sure it has.
edit2: nvm, I'm stupid. Apitrace also works for Direct3D
Refraction was at some point trying to contact nvidia threw there forums as (he made an account month or so back) to come up with way with them that would allow them to accept bug reports, But I dont know what happen there.
I honestly dont think the bugs there new drivers been introducing will be fixed any time soon unless it get randomly fix by something they did to fix a pc game, which how the problems began some random change for pc games, broke things for pcsx2 gsdx.
(06-07-2014, 11:44 PM)tsunami2311 Wrote: [ -> ]Refraction was at some point trying to contact nvidia threw there forums as (he made an account month or so back) to come up with way with them that would allow them to accept bug reports, But I dont know what happen there.
I honestly dont think the bugs there new drivers been introducing will be fixed any time soon unless it get randomly fix by something they did to fix a pc game, which how the problems began some random change for pc games, broke things for pcsx2 gsdx.
Nobody ever contacted me *suprise*
(06-07-2014, 09:07 PM)Blyss Sarania Wrote: [ -> ]Yeah it's a known issue with the new drivers. It seems like Nvidia is on a mission to break PCSX2 whenever it can.
So what drivers version is recommended to use PCSX2?
(06-07-2014, 09:07 PM)Blyss Sarania Wrote: [ -> ]Yeah it's a known issue with the new drivers. It seems like Nvidia is on a mission to break PCSX2 whenever it can.
Do bugs like these also happen in other emulators with Nvidia GPUs ?
i don't wanna say they intentionally bugger that, but sh*t happens on the way... and they don't care about pcsx2. obvious.
i'm trying hard to think how that kinda "bugs" do appear in that high level api access gsdx is doing. i simply can't find a reason how this can happen with an intended and to be
expected result it's coded for in that
standard fashion. optimisation is a good thing but this is really sloppy on the nvidia side. and it's the second glitch that needs a custom nv fix that's not supposed to be. it's
off the specification. it's a
technical fault.
they'd have to fix it. no matter what.
the relevance matter is what makes that a bold post.
or how about we twist it... one can make pcsx2 a no nvidia zone. they just f*cking up their costumers/audience.
(06-08-2014, 03:04 PM)Monochrome100 Wrote: [ -> ]Do bugs like these also happen in other emulators with Nvidia GPUs ?
Haven't seen any for EPSXE or NullDC (yet). 2D emus are probably unscathed.
(06-08-2014, 03:54 PM)shinra358 Wrote: [ -> ]Haven't seen any for EPSXE or NullDC (yet). 2D emus are probably unscathed.
i think they all use dx9, which i believe is fine on GSDX, it's only the DX11 codepath that is affected.
The most popular GPU plugin for ePSXe (Pete's OpenGL2 PSX GPU) uses OpenGL 2.
And that is why if you want them to fix something, you should have a sample that shows the bug in their drivers. Otherwise it might be GSdx's bug, and is not their job to debug nor fix it.
#EDIT:
PIX, D3D11 and Windows 8 . Just in case, I didn't even know it was broken for Win 8.