..:: PCSX2 Forums ::..

(08-04-2011, 01:24 PM)abdo123 Wrote: [ -> ]yes it is much better keep up the good work

Thanks to your encouragement I continued to work on this logo.You have an eye of a painter.Thanks again.

we appreciate your work, but would it be possible to create your own thread about this ?
I guess it'll be better...

(08-03-2011, 10:19 PM)abdo123 Wrote: [ -> ]well ps2 games wont benefit from DX11 tessellation as far as i know

dx11 is more than just tesselation. some generic compute shaders, maybe?

(08-04-2011, 04:34 PM)lol Wrote: [ -> ]dx11 is more than just tesselation. some generic compute shaders, maybe?

Many IT beginners believe that the difference between directX 10 and directX 11 is just a good tessellation.

(08-04-2011, 07:25 PM)Cristo4pcsx2 Wrote: [ -> ]Many IT beginners believe that the difference between directX 10 and directX 11 is just a good tessellation.

so can you tell me when it will add to the gsdx plugin becouse it realy cool logo i want it.

(08-04-2011, 07:32 PM)godofwarcraft Wrote: [ -> ]so can you tell me when it will add to the gsdx plugin becouse it realy cool logo i want it.

The new logo will be implemented when developers of GSDX plugin will want.Maybe I will create my own thread about this.
Do not forget that the visual identity, image, attract new users.
Thanks.

Hi Gabest, I made a logo for GSDX plugin (for direct x 11) because the actaual, represent just direct x 10.
I hope you like this logo.

(01-24-2010, 07:10 PM)sdml Wrote: [ -> ]It seems something wrong with Alpha Correction when using DX10.
DX9 with Alpha Corr looks so

DX9 without AC looks so

And DX10 looks so

Something between 1st and 2nd.
PS: This is Xenosaga II.

the problem is DX10 has an issue with the layer that the PC's shadow is in, skipdraw=3 resolves it, but may introduce issues further into the game.

History likes to repeat itself:X
I started playing story mode in DBZ:Budokai Tenkaichi 2 and saw it's currently completely messed up, soo I fixed it, hopefully this time not only I knew what I'm doing(thanks to Shadow Lady teaching me a bit earlier), but actually didn't even need such knowledge here:3.

Here's some screenshots of how it looks NOW in svn:
Normal/duel map looks nice:
[attachment=29519]

Destroyed map/after change completely messes up chars in both texture and missing body parts(althrough hard to see that last here):
[attachment=29520]

Story mode map - works ok, but have empty space instead of objects shadows:
[attachment=29521]

Dragon Summon - completely messed up textures:
[attachment=29522]



Well ok, now my fix for the fix, actually just a skipdraw changed values, took me some time to test even while it was easy to change, >.>...

Normal map/duel mode - same as before, no bugs here:
[attachment=29523]

Map after destruction - both bugs fixed:
[attachment=29524]

Story mode map - rivers are a bit off now, but looks better anyway:
[attachment=29525]

Dragon summon - completely fixed:
[attachment=29526]

And finally .patch for current svn:
[attachment=29528]
Added also one unknown crc for this game from a closed thread.

~ enjoy, tested in my pal, and at friend ntsc versions soo should work pretty much on everything.

Edit: just to make the info complete, same model/texture bugs were in story mode dialogues ~ also fixed now.

And info for anyone wanting to try to mess around it more. First skipdraw fixes the models and their textures, the second one is killing the blurry copy of shining objects(including all monkey-blonde-guys;P).

[Bug Report] Burnout revenge / Burnout 3 [NTSC]

# PCSX2 version: 4870
# CPU options: EErec on, VUrec0 and VUrec1 on, MTGS on, no hacks
# Plugins used: GSdx 0.1.16 (hardware and software, dx9 / dx 11),
# Description: Incorrect textures windows of the cars + the underside of the cars (purple). It occures only in SSE2 in combination with an AMD GPU. SSE2 mode on Geforce seems to be fine.


For more information see this thread: http://forums.pcsx2.net/Thread-purple-wi...ure-glitch

Bug is being reproduced by multiple users and it seems to be a specific GSdx bug on AMD gpu's therefor my post in this thread instead of the normal bug reporting thread