reported F14 VR - VDI screen not usable in MT Version

[LOW_Hitman]

Am 8.3.2024 um 18:40 schrieb British_Dragon_14:

I'm having this issue now. I'm in VR, Multi-Threading.

The VDI TV screen is either black or bright green if I change the contrast.

Its a known bug but it wasn't fixed. Only way to solve this is to start a mission - quit mission - and press Fly - or fly again. Than the VDI work as it should.

[Schlomo1933]

Can’t believe that headblur is unable to reproduce this bug…. 
It happens everytime with the 1st flight with the f-14 after starting DCS. 

After restarting the mission it’s fine again.

[Bealdor]

On 3/31/2024 at 10:35 PM, Schlomo1933 said:

Can’t believe that headblur is unable to reproduce this bug…. 
It happens everytime with the 1st flight with the f-14 after starting DCS. 

After restarting the mission it’s fine again.

 

Because it doesn't happen to everyone / on every PC. I never experienced this bug for example.

And bugs that can't be reproduced reliably are almost impossible to fix unfortunately.

[draconus]

FYI: not fixed in 2.9.4.

[Raven (Elysian Angel)]

On 3/31/2024 at 10:35 PM, Schlomo1933 said:

everytime with the 1st flight with the f-14 after starting DCS

The TCS works fine if you jump into another aircraft before flying the F-14 though, as long as it's in the same session.

[speed-of-heat]

Yep i have started to find this problem more and more irritating 

[LOW_Hitman]

After all the last patches the VDI within the F14 module isn't working correctly. I always need to restart the mission to make the vdi working. First start = black screen and no camera picture.

Please ED fix this! This issue is known for a year or something!

[Flappie]

Heatblur is responsible for the F-14 module, not ED.

Check this thread, it might help:

 

[LOW_Hitman]

Thnx Flappie, restart the mission is working - but thats not a fix.

[Flappie]

Thanks for your feedback. I'll see if I can help with this bug (so far, I cannot reproduce it).

[LOW_Hitman]

vor 13 Stunden schrieb Flappie:

Thanks for your feedback. I'll see if I can help with this bug (so far, I cannot reproduce it).

Maybe only an MT version issue as far as i know AND thnx for your help!!

Edited May 20, 2024 by LOW_Hitman

[draconus]

Guys and gals, as our dear @Flappie silently tries to reproduce and find the culprit of the bug, can you please run some Tomcat mission, show off the bug and upload your \saved games\logs\dcs.log after the session. It takes only a few minutes but might help the devs and testers to come up with something. Thanks

[Flappie]

Hello @gyrovague. I've compared @draconus's log file (left, bug reproduced) with mine (right, no bug).

On the left, the sim complains about missing "mfd1", "mfd2" and "mfd3" textures. Does this ring a bell?

 

[speed-of-heat]

@Flappie Ok I give you three log files:

1) in 2D

2) in VR and not working

3) in VR and working with a reload (Shift R)

i get the same MFD1,2,3 message both VR scenarios, though it is absent in the 2D scenario 

TCS working in 2D.log TCS not working in VR.log TCS not working and then working with mission reload in VR.log

let me know if you need anything else

Edited May 28, 2024 by speed-of-heat

[Flappie]

Hi @speed-of-heat. Thanks! Your third log confirms it has to do with these "mfd#" textures not being found on the first run.

First mission loading:

2024-05-28 07:53:57.534 INFO    COCKPITBASE (Main): WebRTC VOIP init: enabled VOIP capability for radio ARC182
2024-05-28 07:53:57.534 INFO    COCKPITBASE (Main): WebRTC VOIP init: added guard receiver - ARC182
2024-05-28 07:53:57.595 ERROR_ONCE DX11BACKEND (Main): render target 'mfd1' not found
2024-05-28 07:53:57.600 ERROR_ONCE DX11BACKEND (4908): texture 'mfd1' not found. Asked from ''
2024-05-28 07:53:57.650 ERROR   COCKPITBASE (Main): Cockpit: failed to init geometry, pointer  was not found.
2024-05-28 07:53:57.654 WARNING LOG (20048): 1 duplicate message(s) skipped.
2024-05-28 07:53:57.654 ERROR_ONCE DX11BACKEND (11228): texture 'mfd2' not found. Asked from ''
2024-05-28 07:53:57.661 ERROR   COCKPITBASE (Main): Cockpit: failed to init geometry, pointer  was not found.
2024-05-28 07:53:57.733 WARNING LOG (20048): 1 duplicate message(s) skipped.
2024-05-28 07:53:57.733 ERROR_ONCE DX11BACKEND (3392): texture 'mfd3' not found. Asked from ''
2024-05-28 07:53:57.735 WARNING SECURITYCONTROL (Main): IC fail: scripts/aircrafts/_common/cockpit/kneeboard/indicator/definitions.lua
2024-05-28 07:53:57.754 WARNING SECURITYCONTROL (Main): IC fail: scripts/aircrafts/_common/cockpit/kneeboard/indicator/overlay_page.lua
2024-05-28 07:53:57.754 WARNING SECURITYCONTROL (Main): IC fail: scripts/aircrafts/_common/cockpit/kneeboard/indicator/objects_page.lua
2024-05-28 07:53:57.778 WARNING SECURITYCONTROL (Main): IC fail: scripts/aircrafts/_common/cockpit/kneeboard/indicator/map_page.lua
2024-05-28 07:53:57.778 WARNING COCKPITBASE (Main): Cockpit: MapObjectsBuffer . Specific element 3 not implemented, map may be incorrect
2024-05-28 07:53:57.790 ERROR   COCKPITBASE (Main): Cockpit: Clickable - Wrong connector name PNT_MCB

Second mission loading:

2024-05-28 07:54:56.637 INFO    COCKPITBASE (Main): WebRTC VOIP init: enabled VOIP capability for radio ARC182
2024-05-28 07:54:56.637 INFO    COCKPITBASE (Main): WebRTC VOIP init: added guard receiver - ARC182
2024-05-28 07:54:56.716 ERROR   COCKPITBASE (Main): Cockpit: failed to init geometry, pointer  was not found.
2024-05-28 07:54:56.792 WARNING LOG (20048): 3 duplicate message(s) skipped.
2024-05-28 07:54:56.792 WARNING COCKPITBASE (Main): Cockpit: MapObjectsBuffer . Specific element 3 not implemented, map may be incorrect
2024-05-28 07:54:56.803 ERROR   COCKPITBASE (Main): Cockpit: Clickable - Wrong connector name PNT_MCB

 

[speed-of-heat]

@Flappie, thanks m8, anything else you need? 

[Flappie]

Right now, I simply need to get Heatblur's crew attention to this thread. I've already pinged gyrovague, so let's wait for a few days to pass.

[speed-of-heat]

ack and thanks again!

[speed-of-heat]

Hey @Flappie any response from @gyrovague?

[KoN]

Can confirm as of today black VID , also comms menu won't show up , my end , can't rearm and refuel this only on F14B . Any ideas all works before patch yesterday in VR . 

Will test on single core later . 

Edited June 6, 2024 by KoN

[draconus]

9 hours ago, KoN said:

also comms menu won't show up , my end , can't rearm and refuel this only on F14B

OT, please make a new thread with short track file, log and keys used.

[KoN]

5 hours ago, draconus said:

OT, please make a new thread with short track file, log and keys used.

Will do . I'm flying one of the campaigns and the comms menu has gone , asks me to f10 for sead strike . ill test this weekend . 

See attached files this was taken today . Black VID screen . If i restart mission then works . 

I rebidded my key binds to use HOTAS . And still no comms menu . 

Edited June 7, 2024 by KoN

[Flappie]

@speed-of-heat gyrovague has not connected to the forums for a while apparently.

[speed-of-heat]

@Flappieany way to get this picked up by HB ? 

[Flappie]

I'll see what I can do.