Open GoogleCodeExporter opened 9 years ago
can you confirm where it broke and if older gsdx's have the same shadow issue
as a
lot of work on shadows in gsdx has just been done.
Also games will look more serrated than the real ps2 because televisions blur
the
picture.
Original comment by refraction
on 28 Apr 2009 at 8:39
will set it to gabest for now (best guess :P)
Original comment by refraction
on 28 Apr 2009 at 8:46
Original comment by refraction
on 28 Apr 2009 at 1:56
Tested with lots of different versions. The problem of the shadows happened even
with the first versions of the plugin. I noticed that with GSdx 0.1.12 the cars
have more reflection, but they got some graphics corruptions and sometimes the
cars disappear.
Didn't know that this technique of the television blur was still used by some
developers of games. It was very used in Mega-drive and Super Famicon
generation...ow well =)
Original comment by juniorth...@gmail.com
on 29 Apr 2009 at 12:16
I found another bug forgot to say.
The car in first place has the front wheels floating for a few seconds then
returns
to normal and vice versa. The cars in other positions don't have this problem.
It happens most like with all versions of GSdx DX9
Made another GSdx DX9 dump for this if helps:
http://www.4shared.com/file/102365148/17ef547/weirdwheel_dump.html
Original comment by juniorth...@gmail.com
on 29 Apr 2009 at 6:36
Attachments:
Tested with: PCSX2 r2271,GSdx r2270 (HW/SW),ZeroGS,,SPU2-X r2217.
Proper reflection only in DX10 SW (much faster than HW too). Shadows bad
everywhere
Original comment by pcsx2gu...@gmail.com
on 8 Dec 2009 at 1:30
I could make a donation by Paypal for the coder who make Ridge Racer V fully
playable without graphical glitchs on the Gsdx DirectX 10 hardware plugin. ;-)
Original comment by f...@live.fr
on 13 Oct 2010 at 9:21
The game has problems with the intro FMV on DX9 hardware mode. THe game hangs
with weird characters on screen during FMV.
With software DX9 the FMV plays fine.
Original comment by juniorth...@gmail.com
on 17 Jan 2011 at 2:30
Original issue reported on code.google.com by
juniorth...@gmail.com
on 28 Apr 2009 at 12:46Attachments: