Welcome, Guest.
Username: Password: Remember me

TOPIC: reshade and 3d vision

reshade and 3d vision 2 years 3 months ago #1

Hi,

Is reshade compatible with 3d vision?

I've managed to get it working fine in 2d with swtor (including MXAO), but when I enable any effect (even non depth based ones) with 3d vision the image glitches.

More specifically, in 3d, if I remove the glasses the two overlayed images seem to separate vertically with any reshade effects enabled, and with 3d vision enabled in the control panel, but disabled in game, the whole 2d image seems to move slightly to the right and down, and everything blurs somewhat, if that makes any sense.

Is it generally incompatibility with 3d vision, or just a game issue here?

Incidentally, I can get most reshade effects working fine in tridef, with swtor (no such image shifting glitches mentioned above), but not MXAO (the ambient occlusion shading seems to flicker from one of the overlayed images to the other).

Thanks for any help
The administrator has disabled public write access.

reshade and 3d vision 10 months 3 weeks ago #2

In case anyone is wondering, I went to play swtor again after a year in which I have gained some experience of directx programming, and I have managed to ascertain and resolve the issue.

In DX9 there is a texel/pixel offset problem, which every Reshade effect fixes in the vertex shader. To do this, the PostProcessVS shader needs to know the texel size, which is presently passed into the shader via constant 255. It seems swtor overwrites this constant with a different number (maybe only in 3d vision?), causing the offset issue I described.

I downloaded Reshade and have simply changed the constant to register 254, and after compiling everything is working as it should. I had a brief look, but it seems that this register is hard-coded and not changeable in the ini, but I may be wrong?
Last Edit: 10 months 3 weeks ago by davegl1234.
The administrator has disabled public write access.

reshade and 3d vision 10 months 3 weeks ago #3

It's hardcoded, yes. There hasn't been a reason to make it configurable until now.
Cheers, crosire =)
The administrator has disabled public write access.