[Mud-H]

Just a little update about my issue, I think it's strictly related to TorqueLab PostFX system which I noticed it's not working well anymore, I guess there was some changes in the settings and I need to update my script. When I activate the HDR, I get weird result and once I deactivate it, I get the same result as the issue posted above.
Using the standard editor went better but I still got some "Unable to compile shaders" crash when playing with materials.

[L3zak]

Hi, I've found some issue with rivers - there is a missing part at lowLODdistance, also it happens only when You look from the first node side (on screenshot it's duplicated river, one is rotated by 180 degrees). There is no problem when using d3d9.

[Mud-H]

Typo error found in VignetteP.hlsl
Line 31:

Code: Select all

float4 base = tTORQUE_TEX2D(backBuffer, IN.uv0); 

Should be:

Code: Select all

float4 base = TORQUE_TEX2D(backBuffer, IN.uv0); 

[Azaezel]

Highly recommended for folks tracking multiple repos.

[Mud-H]

But I just read the Pull Request guide

Code: Select all

We like each pull request to have a reasonable revision history - not too many small commits with typo fixes, for example. Sometimes, we may ask contributors to rebase large numbers of commits into a single commit before the request is pulled.

Ah, I had missed the too many part. Okay I will try next time, preparing one for the PostFX scripts and manager

[Azaezel]

Was more pointing out you can PR to non-default repos, like Timmys. Note that also means if someone throws over a flawed PR it's entirely possible to help speed things along by PRing to *that* as well.

[Timmy]

Hi, I've found some issue with rivers - there is a missing part at lowLODdistance, also it happens only when You look from the first node side (on screenshot it's duplicated river, one is rotated by 180 degrees). There is no problem when using d3d9.

Thanks for that, issue is now fixed.

[PaulWeston]

Hey, great work everyone, wow Dx11 will really change things...

Noticed that the Oculus code in platform/input/oculusVR is still all dx9 - any chance you could take a look at porting that up too?

Am hoping to be able to make a build that uses latest oculus sdk and runtime, and a dk2, to make sure the engine is compatible moving forward with the consumer headsets. As noted in the DK2 thread, they deprecated dx9 after version 5 of the oculus sdk. And they are up to version 8 now. So, it would be awesome if that code was kept up with the other dx11 changes.

Thanks so much for all the hard work!

[Timmy]

I don't personally own a dk2 so i won't be able to do much here with porting it over sorry. I think JeffR does though??

Anyway with this dx11 stuff i'll be back on it next week, since the deferred shading stuff is going in first i'm going to help get that finished first and than have to merge all that with the dx11 code. So until that happens i would recommend waiting before testing this current dx11 branch any further.

[Timmy]

Just to keep this thread updated, should be an official PR for dx11 by next week. Instancing is all done, heaps of problems fixed and the port is now about 98% complete.