reported F14 VR - VDI screen not usable in MT Version

[LOW_Hitman]

is there a fix for this issue?? VDI within the f14 isn't useable in VR and DCS-MT. Its black or with the TGP on - its green and not showing the ground

Am 16.4.2023 um 13:52 schrieb westr:

there appears to be an issue with the image on the TCS when using the multithreading dcs.exe, when running the other DCS.exe (non multithreading) the image in the TCS is fine and target can be seen. In Mulththreading the screen is black and if you adjust the VDI you still cant see an image. Doing some searching this issue is discussed on Reddit. The advice given was to reduce Res of displays, or turn off MSAA. Neither of these options has worked for me. Could this be looked into.

is there a fix for this issue? F14 isn't usable in VR and its a shame that NOTHING happened since we all posted about this issue.

[LOW_Hitman]

Also a strange thing: the VDI is working correctly in the rio seat, its only a pilots vdi issue - AND NO!! THIS ISSUE IS NOT SOLVED!

Edited October 19, 2023 by LOW_Hitman

[westr]

48 minutes ago, LOW_Hitman said:

is there a fix for this issue?? VDI within the f14 isn't useable in VR and DCS-MT. Its black or with the TGP on - its green and not showing the ground

is there a fix for this issue? F14 isn't usable in VR and its a shame that NOTHING happened since we all posted about this issue.

Load a mission in the mission editor so you’re in the cockpit. Set the tcs in the front seat and you’ll see it’s not working. Then exit the mission back into the mission editor. Reload the mission and try it again and it should work. That’s my workaround for now. Unfortunately I don’t think the quick start missions work. 

[LOW_Hitman]

vor 1 Minute schrieb westr:

Load a mission in the mission editor so you’re in the cockpit. Set the tcs in the front seat and you’ll see it’s not working. Then exit the mission back into the mission editor. Reload the mission and try it again and it should work. That’s my workaround for now. Unfortunately I don’t think the quick start missions work. 

hi thnx! Iam only playing campaigns, so maybe a few reloads. What setting do you use for cockpit displays? mine is set to 512

[westr]

Just now, LOW_Hitman said:

hi thnx! Iam only playing campaigns, so maybe a few reloads. What setting do you use for cockpit displays? mine is set to 512

I use 1020 or whichever it is. The higher. Hope it works for you. 

[LOW_Hitman]

vor 1 Minute schrieb westr:

I use 1020 or whichever it is. The higher. Hope it works for you. 

thnx - i'll give it a try!

[westr]

14 minutes ago, LOW_Hitman said:

thnx - i'll give it a try!

Just reading the latest OB sounds like they may have added a fix. Not sure if your on OB. 

[draconus]

On 10/19/2023 at 7:30 PM, LOW_Hitman said:

Iam only playing campaigns, so maybe a few reloads.

Yes, start campaign mission, exit and cancel (do not click end mission), then start the same mission again and it should work.

I didn't update to 2.9 yet to test. Same problem in 2.9.

Edited October 23, 2023 by draconus

[gyrovague]

Curious to know whether latest OB from yesterday fixes this TCS issue on multithread for those that encountered it. Nobody on HB team was able to reproduce this, so unknown whether the potential fix works or not.

[LOW_Hitman]

vor 12 Stunden schrieb draconus:

Yes, start campaign mission, exit and cancel (do not click end mission), then start the same mission again and it should work.

I didn't update to 2.9 yet to test.

Thnx for that hint, i'll try it! No iam not on OB - Stable MT Version. The very strange thing about this issue is, it only happens to the Pilots-VDI, Rio is working well.

[Nealius]

I haven't done extensive testing, but is this map/settings-related? With MSAAx2, displays 1024, textures medium on Syria and Sinai the TCS works fine for me. I haven't tested any other maps or settings, but I do remember TCS not working last time I flew Fear the Bones on Caucasus. 

[gyrovague]

40 minutes ago, Nealius said:

but is this map/settings-related? 

We don't really know, since none of us (or extended tester team) could reproduce this at all (and it seems pretty rare in the overall playerbase). From the various posts in this thread, it seems to affect certain people on certain maps, and also not always for some (and always for others).  The (potential) fix is not settings or map related however, it was (maybe) an initialization order problem with multithreaded DCS.  So basically: 

[LOW_Hitman]

vor 17 Stunden schrieb draconus:

Yes, start campaign mission, exit and cancel (do not click end mission), then start the same mission again and it should work.

I didn't update to 2.9 yet to test.

Thank you very much! It worked, after the restart the VDI operates "normal" - hope there will be a fix soon within the stable version

[Raven (Elysian Angel)]

9 hours ago, gyrovague said:

Curious to know whether latest OB from yesterday fixes this TCS issue on multithread for those that encountered it.

No it didn't: it still happens (at least on my system).

[Lt_Jaeger]

Yeap, bug is still there

[draconus]

Unfortunately, not fixed in 2.9 for me either. At least restarting mission still works as workaround.

[todd022]

1 hour ago, draconus said:

Unfortunately, not fixed in 2.9 for me either. At least restarting mission still works as workaround.

Just sucks getting all the way through startup only to find out you have to restart the whole mission. 

[gyrovague]

Ugh, that's a pity. I'm going to double check whether the (potential) fix did indeed get included into DCS 2.9, since there was a bit of uncertainty around the merge window with the postponed release. 

[gyrovague]

3 hours ago, gyrovague said:

Ugh, that's a pity. I'm going to double check whether the (potential) fix did indeed get included into DCS 2.9, since there was a bit of uncertainty around the merge window with the postponed release. 

OK, so it looks actually as though this TCS (potential) fix did not end up in DCS 2.9.0.46801, despite it being included in the changelogs, so hope still floats for this. There may be a DCS hotfix release sometime soon, then the TCS (potential) fix should end up in that.

[DustyR]

This has been occurring for me 100% of the time.   I have only tested in single player single threading.  Restarting does nothing.  I noticed after the initial 2.9 update and it persists with the most recent 2.9 "patch". 

I run on a AMD Ryzen 9 7900X 12-Core Processor, 4701 Mhz, 12 Core(s), 24 Logical Processor(s).   I would have to look up the rest.  If I can help you find the solution just let me know how.  You guys have done fantastic work and are the reason I even built a computer.  Your module in DCS. 

 

[draconus]

5 hours ago, DustyR said:

I have only tested in single player single threading.

This would be something new as we've seen the bug only in VR and multi-threaded version. Please, make sure and look at your DCS main menu right bottom corner.

[draconus]

On 10/23/2023 at 11:48 AM, gyrovague said:

OK, so it looks actually as though this TCS (potential) fix did not end up in DCS 2.9.0.46801, despite it being included in the changelogs, so hope still floats for this. There may be a DCS hotfix release sometime soon, then the TCS (potential) fix should end up in that.

Is the fix supposed to be in 2.9.0.47168 hotfix? I'm still affected.

[gyrovague]

8 hours ago, draconus said:

Is the fix supposed to be in 2.9.0.47168 hotfix? I'm still affected.

It seems like it's still not included in the openbeta distribution, I'm not sure why.

[Schlomo1933]

Again no fix today ? Dont read anything from HB inside the patch nodes

 

[draconus]

20 minutes ago, Schlomo1933 said:

Again no fix today ?

Nope, just tested.