For those which are using 3DVISION/stereoscopic 3D display with DCS

[Enduro14]

Ok more results as his is all in 2.0 I will go now to test in 1.5 but for your weather it has to be a base of 300 and thickness at 200 otherwise we experience the lighting and shadowing bug. Sweet looks great by the way when this works right

[Enduro14]

Same success in 1.5. Well you have to be above 300 m agl at least odd bug at least in Nevada you are above 300 m no mater where you are in caucus not so much

Edited January 31, 2016 by Enduro14

[Enduro14]

So to summarize a conclusion it appears you must be above what the weather is set at as far as base and it seems the thickness settings need to be on the lowest.

[Enduro14]

so dont know if this helps or anybody understand this but this is the bottom of the crash log in my logs folder i only crash when i run 3d either with your mod or not.

 

00347.181 ERROR DX11BACKEND: failed to create index buffer. Reason: DXGI_ERROR_DEVICE_REMOVED

00347.181 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED

00347.186 INFO DCS: try to write dump information

00347.193 INFO EDCORE: # -------------- 20160201-142019 --------------

00347.196 INFO EDCORE:

00347.200 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 92660030 00:00000000

00347.206 INFO EDCORE: 00000000 00000000 0000:00000000

00347.213 INFO EDCORE: 92660030 0014F500 0000:00000000 CreateDirect3D11SurfaceFromDXGISurface()+1C2D0

00347.217 INFO EDCORE: 5EF71218 0014F570 0000:00000000 D3D11CreateDeviceAndSwapChain()+B608

00347.220 INFO EDCORE: 5F67B1BE 0014F5E0 0000:00000000 ??1DX11Renderer@RenderAPI@@QEAA@XZ()+2E5FE

00347.223 INFO EDCORE: 66041559 0014F6A0 0000:00000000 ??4DirectoryIterator@io@@QEAAAEAV01@AEBV01@@Z()+45069

00347.226 INFO EDCORE: 6604129B 0014F6D0 0000:00000000 ??4DirectoryIterator@io@@QEAAAEAV01@AEBV01@@Z()+44DAB

00347.229 INFO EDCORE: 6608885F 0014F700 0000:00000000 ??4Random@ed@@QEAAAEAV01@AEBV01@@Z()+23BF

00347.230 INFO EDCORE: 7FF2EC19 0014F760 0000:00000000 ED_gettext_init()+849

00347.230 INFO EDCORE: 2F536F08 0014F7C0 0000:00000000

00347.230 INFO EDCORE: 2F54D174 0014F7F0 0000:00000000

00347.230 INFO EDCORE: 2F54D0C4 0014F820 0000:00000000

00347.231 INFO EDCORE: 2F5FD4CC 0014FED0 0000:00000000

00347.232 INFO EDCORE: 2F601705 0014FF10 0000:00000000

00347.233 INFO EDCORE: 97FE8102 0014FF40 0000:00000000 BaseThreadInitThunk()+22

00347.233 INFO EDCORE: 98C2C2E4 0014FF90 0000:00000000 RtlUserThreadStart()+34

00347.388 INFO EDCORE: Minidump created.

00347.390 INFO DCS: try to write track file

[lefuneste01]

So to summarize a conclusion it appears you must be above what the weather is set at as far as base and it seems the thickness settings need to be on the lowest.

Ok, I have found the problem and fixed it. It was the same as for the smoke, a register used both for fix parameter and for HDR.

But, as it is the second time that this kind of problem occures, I want to dump all shaders in order to check if there will not be more side effects.

[JunMcKill]

stereo.lua for side by side

 

Maybe you can try to comment the line "surface_createmode=1" in the [stereo] section of d3dx.ini, but you will have again the problem with night illumination.

Which driver version do you use ?

 

Good post, do you have any monitorseup\stereo.lua settings for side by side stereo rendering? means for use without 3D Vision or TriDef.

[lefuneste01]

The 5.1 version should be OK for the sun light and shadow: https://s3.amazonaws.com/lefuneste/DCS_stereoscopic_3dMigoto_51.zip

Normally there is no more register conflict, but it seems that some shaders can not be dumped, so I still have a little doubt. Can you test it as usual ?

[geert]

Problems after new update

 

The new version (2.01) doesn´t work well with the MOD. I can´t get any HUD / gunsight to work and horizon/sun problems seem to be back as well. I only tested Mi8, A-10C and Sabre (Sabre still works because of the LUA based fix). Tested using 5.0 and 5.1 version. Hope this is fixable, thanks!

[Enduro14]

hey ill swap the tv's out in the morning and give it a try like always appreciate the work.

[Enduro14]

The new version (2.01) doesn´t work well with the MOD. I can´t get any HUD / gunsight to work and horizon/sun problems seem to be back as well. I only tested Mi8, A-10C and Sabre (Sabre still works because of the LUA based fix). Tested using 5.0 and 5.1 version. Hope this is fixable, thanks!

 

I was wondering how it would work considering the new patch brought in more lightining and shadow effects... looks great at 4k but ill give a try in 3d and see if i have same problems

[Enduro14]

Ok your latest version 51 works great in 1.5 sun and shadows working great now. But with the new update on 2.0 huds are not working as stated above. Wonder if they revamped a bunch of shaders or maybe huds are like 1.2 again?

 

One thing I noticed in 1.5 is smoke will change brightness and also the texture around destroyed tgts flicker. But let me disable Sli to make sure it's not that.

Edited February 8, 2016 by Enduro14
Additions

[geert]

Ok your latest version 51 works great in 1.5 sun and shadows working great now. But with the new update on 2.0 huds are not working as stated above. Wonder if they revamped a bunch of shaders or maybe huds are like 1.2 again?

 

One thing I noticed in 1.5 is smoke will change brightness and also the texture around destroyed tgts flicker. But let me disable Sli to make sure it's not that.

 

Thanks for testing/confirming

[lefuneste01]

For the 2.0 problems: It looks like they change the shaders or the textures. I will not be able to access my PC until the end of the week. Can you try the tutorial posted in thread 151 to look where the changes are ?

If only the texture have changed, you will find the news one in the shaderUsage.txt (you must make the dump when using the planes for which you want to fix the HUD). Try to modify in d3dx.ini the texture related for your plane with the ones you find in the shaderUsage.txt.

You can also check if there are some changes between the shaders...

For the 1.5 problems : if they are confirmed, can you check them with the previous version of the mod ? Some shaders can not be dumped, maybe I chosse a register used in them...

[Enduro14]

will do when i get home

 

on a side note im still trying to figure out what is exactly causing it to crash at times in 3d on my system. I have turned down my draw distance and seems to have helped knock on wood. I wonder if its something with the Vram and too many objects on setting ultra and above. Its normally a driver crash, I do have 2x980 with 4gb vram and not overclocked so hmmm.

Edited February 8, 2016 by Enduro14

[Enduro14]

Ok update on 1.5 I have ruled out sli as cause of the destroyed vehicle texture flicker and also the smoke from destroyed vehicles turn from black to a light gray and back and forth depending on angle and sun /shadow conditions. So with or without sli I have this problem with 51

[Enduro14]

Just tried the hunting mode in 2.0 and it won't give me the hud mfd. indication at top. Hit the left and right arrow all the way through all textures and no status change. Awaiting further guidance.

[Enduro14]

I posted a thread in bug area as a call for support from the devs, maybe we can get some insight on what exactly needs to be fixed in new 2.0. which by the way is amazing with the new dynamic light and shadows.

 

http://forums.eagle.ru/showthread.php?p=2671198#post2671198

[Enduro14]

Indeed, 2.0 looks gorgeous, and fps are improved in my side with latest patch.

But we've never had any support from ED regarding HUD collimation with 3d vision, though. Of course, you are free to try.

 

This is becoming extenuating. Sometimes I'm like forgetting about having proper HUD's until my Oculus Rift arrives. But is so sad to fly with half-functional HUD's.

 

ya i hear ya look forward to my rift also, i loved dk2 in 1.2 but i moved and left the dk2 in storage havent tried Edge in rift yet but looks very promising for CV1. Anyways back to 3d ya ive been flying dcs world in 3d for years and its always been a struggle, but in my mind nothing can replace that depth and awesome perception you get in flight while in 3d. Well atleast we have 1.5 working until this friday when they update it and i assume the new graphical changes they did in 2.0 last patch will follow...

 

constant struggle but i wouldnt give up i think vr will bring all this 3d stuff back to the must have lists.

[lefuneste01]

Ok update on 1.5 I have ruled out sli as cause of the destroyed vehicle texture flicker and also the smoke from destroyed vehicles turn from black to a light gray and back and forth depending on angle and sun /shadow conditions. So with or without sli I have this problem with 51

Can you post a track ?

[Enduro14]

Can you post a track ?

 

yes after dinner i will be back in the pit and the mission i used was ka50 Range its in the mission folder for ka50.

 

well after another test it was all daylight no shadows aka no clouds and their was no problem with smoke or those textures let me get back to that other mission with lots of clouds

Edited February 8, 2016 by Enduro14

[geert]

I tried the shader hunting thing on the Mi8 and found both shaders for the sight (I did not get the "HUD+MFD message, as Enduro also mentioned). I then searched the shaderusage.txt file for “0015dc5ba3778d8b” and “2b83090b7feaa999” shaders but none were found.

What to do now??

[Enduro14]

ive no clue either but deep down im hoping the huds are back to way they where in 1.2 and where modded for 3d via lua file. But i honestly have no clue and learning as Lefuneste puts out info thats for sure.

[lefuneste01]

I tried the shader hunting thing on the Mi8 and found both shaders for the sight (I did not get the "HUD+MFD message, as Enduro also mentioned). I then searched the shaderusage.txt file for “0015dc5ba3778d8b” and “2b83090b7feaa999” shaders but none were found.

What to do now??

That means that they have changed the shaders numbers. So nothing easy for you now. I will check that as soon as I have time. My idea is to document how to convert the 1.5 fix to 2.0 by renaming shaders files and modifying d3dx.ini, I do not want to maintain 2 version of the fix, too much work.

[lefuneste01]

ive no clue either but deep down im hoping the huds are back to way they where in 1.2 and where modded for 3d via lua file. But i honestly have no clue and learning as Lefuneste puts out info thats for sure.

I will not use anymore the lua method for the HUD.

At first I tried to use it for the 1.5, but it was not working anymore because the HUD was not drawn as far as 10 meters in front of the plane. Seems that they modified the clipping box and I did not find a way to extend it.

Beside that, they always make changes to HUD lua files, so it was a huge work to maintain it.

As there are anyway other things (sun, HDR, horizon, labels, Mig21 HUD, FC3 planes HUD) that can only be fixed with a d3d mod, I do not want to maintain 2 version of fix.

[Enduro14]

No worries buddy I imagine this Friday update 1.5 will be same as 2.0 last update so hopefully only require the one version after Friday