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

[geert]

Ooops, I forgot to answer...I look at the fix...and it should work as it is, like with the Mirage 2000..

Did you try the mod (uparrow mode) without modifying anything ?

 

Yeah! It does work after all! Big thank you! :)

 

I was pretty sure I tried it, but apparently, I adjusted the MOD using my own settings immediately. I just tried the original 3.2 version of the MOD and now it seems to work. I always copy-paste my settings, like type, separation, convergence and y value and I use up arrow for outside view (extreme convergence, almost no separation) and left arrow for normal mode. Is it correct that now you have fixed the up arrow key to the shader of the Mi8 sight? So just better to use the up arrow key for HUD/gunsight mode adjustments?

[geert]

Problem with A-10C

 

I believe I found another problem. Haven´t flown the A-10 a lot recently so I don´t know when this bug was introduced. The TGP and maverick video feeds are rendered in wrong depth. They are pushed behind their actual screens. This is only for these video feeds, the rest of the info on the MFCD´s is on the correct depth. Activating / deactivating shader isolation (W=0 or 1) does not help. Only tested with the latest version of the 3dmigoto fix using my own settings. With the upcoming red flag campaign for the A-10 this may become a more important bug :)

[lefuneste01]

The TGP and maverick video feeds are rendered in wrong depth. They are pushed behind their actual screens. This is only for these video feeds, the rest of the info on the MFCD´s is on the correct depth

As I did not test a lot, it is possible that the textures used for this kind of display are not filtered.

Can you post a track ?

[lefuneste01]

Yeah! It does work after all! Big thank you! :)

So just better to use the up arrow key for HUD/gunsight mode adjustments?

Only for planes that do not have texture filtering. I have to post a tutorial in order to allow texture identification for planes that I will not buy.

[geert]

As I did not test a lot, it is possible that the textures used for this kind of display are not filtered.

Can you post a track ?

 

Here is the track. I pushed some arrows during the track also turning on / off texture filtering.

A-10C TGP and AGM65 video feed bug.trk

[lefuneste01]

I did not see any problem with the two MFDs during all the track. did you use the left arrow key to shift the HUD ?

[geert]

I did not see any problem with the two MFDs during all the track. did you use the left arrow key to shift the HUD ?

 

I touched all kinds of arrow keys, pretty sure lots of times the left arrow key. Strange that you couldn´t see the problem. I don´t know much about track files, do you see the image with the same depth and convergence? I use very high separation (85%) which may contribute? Also, the video feeds from TGP and maverick are pushed (with my settings) just a couple of centimeters or so behind the MFCD, definately very noticable for me, but not impossible to still use it. Maybe somewhen else can also check? Do you have some other suggestions maybe?

[lefuneste01]

Here is the V5.0 version of the mod.

Sun depth is fixed, with HDR now in 3D.

Horizon problem is greatly reduced (even if there may be a light blue line for one eye, things are far better)

 

As previously, some parameters are to be modified according to your separation/convergence settings. They are defined by default for separation = 30.0 and convergence = 15.

They can be modified in the [Constants] section of d3dx.ini and are the following:

x1 = 0.4 // modify here the value to add for HUD separation

y1 = 1.2 // modify here the value for label separation

z1 = 1.6 // modify here the value to add for SUN separation

w1 = 1.5 // modify here the value to sun HDR strenght

x2 = 0.2 // modify here the offset factor on horizon to remove the dark blue zone (higher separation = higher number).

 

There are two key section defined in order to have differents settings for cockpit and external view. They are commented by default, but you will only have to remove the ";" to make them work. Search for [key6] and [key7] in d3dx.ini. Of course you can modify separation and convergence settings, as well as the key to use to select these modes.

 

I had to overwrite the strenght of sun HDR effect, because the decompiled shader can not be run back by 3DMigoto. So the HDR will be different from the default one and too large when seen in external view. That could be modified, but then it will implies to spread the HDR strenght variable into different lines of 3dx.ini, this can be confusing. If there are two values for HDR seen from cockpit view and external view agreed by everyone, I can write them into the d3dx.ini file.

 

Thanks for testing this mod.

Edited January 23, 2016 by lefuneste01

[lefuneste01]

I touched all kinds of arrow keys, pretty sure lots of times the left arrow key. Strange that you couldn´t see the problem. I don´t know much about track files, do you see the image with the same depth and convergence? I use very high separation (85%) which may contribute? Also, the video feeds from TGP and maverick are pushed (with my settings) just a couple of centimeters or so behind the MFCD, definately very noticable for me, but not impossible to still use it. Maybe somewhen else can also check? Do you have some other suggestions maybe?

 

I do not know : here are screenshots I take on my PC when playing the track.

[Enduro14]

Here is the V5.0 version of the mod.

Sun depth is fixed, with HDR now in 3D.

Horizon problem is greatly reduced (even if there may be a light blue line for one eye, things are far better)

 

As previously, some parameters are to be modified according to your separation/convergence settings. They are defined by default for separation = 30.0 and convergence = 15.

They can be modified in the [Constants] section of d3dx.ini and are the following:

x1 = 0.4 // modify here the value to add for HUD separation

y1 = 1.2 // modify here the value for label separation

z1 = 1.6 // modify here the value to add for SUN separation

w1 = 1.5 // modify here the value to sun HDR strenght

x2 = 0.2 // modify here the offset factor on horizon to remove the dark blue zone (higher separation = higher number).

 

There are two key section defined in order to have differents settings for cockpit and external view. They are commented by default, but you will only have to remove the ";" to make them work. Search for [key6] and [key7] in d3dx.ini. Of course you can modify separation and convergence settings, as well as the key to use to select these modes.

 

I had to overwrite the strenght of sun HDR effect, because the decompiled shader can not be run back by 3DMigoto. So the HDR will be different from the default one and too large when seen in external view. That could be modified, but then it will implies to spread the HDR strenght variable into different lines of 3dx.ini, this can be confusing. If there are two values for HDR seen from cockpit view and external view agreed by everyone, I can write them into the d3dx.ini file.

 

Thanks for testing this mod.

 

Link no worky, will give this puppy a try

[mooimacow]

I'm having a problem with the link too. Thanks again for still working on this, lefuneste01. I don't think a lot of people realize just how great 3dvision is. As long as it still works, I'll probably be holding off until a 2nd generation HMD is out. Gotta be able to read that HUD :)

[lefuneste01]

Oops !

I made a last time update and did not know that it removes the "public" authorization.

It should work now....

[Enduro14]

You my friend have returned the glory of nvidia 3dvision in edge. Key 6 and 7 work amazing their is some tweaking to do on external view with horizon and sun but the joy of seeing the aircraft in uber 3D is back! In the pit it looks better to my eyes. And the horizon and sun is amazing now. Will continue to test, this was all in ka50

[Enduro14]

Ok one hing I have noticed with ka50 only aircraft tested so far is the sun you can see it through the cockpit frame and whole cockpit no biggeee but that is only bug I've seen in ka50 with version 5

[lefuneste01]

Ok one hing I have noticed with ka50 only aircraft tested so far is the sun you can see it through the cockpit frame and whole cockpit no biggeee but that is only bug I've seen in ka50 with version 5

I noticed that in Su25T too, the problem was that the HDR of one eye overlap the cockpit frame. Unfortunately, there is nothing I can do with my poor knowledge. I would also like to mask labels by cockpit frame...

[Enduro14]

I noticed that in Su25T too, the problem was that the HDR of one eye overlap the cockpit frame. Unfortunately, there is nothing I can do with my poor knowledge. I would also like to mask labels by cockpit frame...

 

No worries what we have now is beyond awesome and your work has made edge useable with nvidia 3dvision on my big screen again. I'll gladly ignore a sun flare!

[geert]

Thanks a bunch for the new fix! :)

[mooimacow]

What graphical features should I be sure to enable or disable to get the most out of 3dvision?

 

Edit: What depth and x1 values are everyone finding works best? In the first post, lefuneste01 mentioned he was using 50depth, 0.3convergence. I play 3dvision comfortably between 50 and 75, and if 50 is what's working best for him, that's what I want to be using too. I always find that I need to lower convergence from default, though. How can I check the value of my convergence after setting it in-game with CTRL-F5/F6?

 

One more question: How can I make the labels appear at the same depth at the HUD? Is this even possible? I tried chaging the y1 value to 0.4 (just like the HUD) but it didn't seem to make any difference. The labels were still not as far back as the HUD (which looks great).

Edited January 25, 2016 by mooimacow

[Enduro14]

Oh one thing to add the m2000c does not work correctly with just left arrow key. It's either hud is squared away and the pca and other lights goofed up or vice versa

[lefuneste01]

What graphical features should I be sure to enable or disable to get the most out of 3dvision?

 

Edit: What depth and x1 values are everyone finding works best? In the first post, lefuneste01 mentioned he was using 50depth, 0.3convergence. I play 3dvision comfortably between 50 and 75, and if 50 is what's working best for him, that's what I want to be using too. I always find that I need to lower convergence from default, though. How can I check the value of my convergence after setting it in-game with CTRL-F5/F6?

 

One more question: How can I make the labels appear at the same depth at the HUD? Is this even possible? I tried chaging the y1 value to 0.4 (just like the HUD) but it didn't seem to make any difference. The labels were still not as far back as the HUD (which looks great).

 

Set hunting=1 option in d3dx.ini to have the value of separation convergence written at the bottom of the screen.

But be careful to not use the numpad 3 or 6 keys with this option on, otherwise you will dump some shaders...

Did you use right arrow key to put labels in 3dmode ? By default they are in 2d mode...

[lefuneste01]

Oh one thing to add the m2000c does not work correctly with just left arrow key. It's either hud is squared away and the pca and other lights goofed up or vice versa

It s normal and will stay like this untill you find if they are texture that can be filtered. I just have to write a tutorial for this...

[Enduro14]

It s normal and will stay like this untill you find if they are texture that can be filtered. I just have to write a tutorial for this...

 

Ok cool they are the same as hud when hud changes they change from my observations.

[Enduro14]

I'm still getting crashes what driver version is everybody using with nvidia 3dvision? I've Been running 361.60 think I will roll back to older drivers

[average_pilot]

355.98

For no particular reason. It's just the version of the last time I went through the hassle of updating the nvidia driver. I hate losing my convergence settings every time I update it.

[Enduro14]

Cool man I actually fixed my crashing issues by turning all shadows to flat and turning off ground clutter. Weird as my system should handle it. Another error I a, seeing is the opposite side of the sky to the sun it seems to be almost a big HDR ish ball don't know if it has to do with the moon but is the moon wrong for anybody else? I also rolled back drivers too but still got crashes until I dumbed down settings.