investigating Air Start - No HUD, No MFD's, No HSI

[Gilligan]

Was flying a mission, was shot down and respawned. When I respawned the aircraft had no HUD, no MFD's, and no HSI. I turned off the MFD switch and waited it tick, then flipped it back on. Nothing. Played with the HUD Brightness wheel, nothing. Pressed various OSB's. Nothing.

Ended the mission and booted up a standard instant action flight (track attached) and the condition persisted. 

No Screens.trk

[BIGNEWY]

Hi, 

can you give us some more information about how to reproduce, and the dcs log from the session.

 

thank you 

[Tholozor]

Verify the BATT switch was set to MAIN PWR?

[NineLine]

19 hours ago, Gilligan said:

Was flying a mission, was shot down and respawned. When I respawned the aircraft had no HUD, no MFD's, and no HSI. I turned off the MFD switch and waited it tick, then flipped it back on. Nothing. Played with the HUD Brightness wheel, nothing. Pressed various OSB's. Nothing.

Ended the mission and booted up a standard instant action flight (track attached) and the condition persisted. 

No Screens.trk 2.52 MB · 6 downloads

I see the displays cycle in your track but its so short I am not sure, and when I take control, the displays come back. If you have a better track or better steps to reproduce, we can look again. Thanks!

[Gilligan]

On 7/10/2025 at 5:52 AM, BIGNEWY said:

Hi, 

can you give us some more information about how to reproduce, and the dcs log from the session.

 

thank you 

I was playing a modified version of the Flaming Cliffs F15C mission - Strike Escort. Some time ago I re-saved a version of the mission where I set the player aircraft and wingmen to be F-16C's. I did this many months, if no longer, ago and have flowing it several times without issue. 

This most recent time that initiated this post I was shot down and respawned via the "briefing" option in the pause menu as I have done numerous times before. When I respawned the aforementioned screens/displays were nonfunctional. Both MFD's and the HSI were black screens, and the HUD display would not, render? I ejected from that aircraft and respawned again however the condition remained.

So I exited that mission and started the instant action flight in the attached track file with the condition again remaining persistent. 

 

Log attached. I found these 3 Lines in it:

2025-07-10 03:57:38.122 ERROR_ONCE DX11BACKEND (18732): texture 'MFD_LCD_F16_LEFT' not found. Asked from ''
2025-07-10 03:57:38.122 ERROR_ONCE DX11BACKEND (42144): texture 'MFD_LCD_F16_RIGHT' not found. Asked from ''
2025-07-10 03:57:38.123 ERROR_ONCE DX11BACKEND (43828): texture 'EHSI_LCD_F16' not found. Asked from ''

As well as a whole block of "Cockpit: Failed to create Element 'ceMeshPoly' - reason unkown" lines associted with the HUD, MFD's, & HSI.

 

The only time I've tried playing that mission again the game crashed a couple minutes in and I sent that crash report at the time. I have not tried since. 

 

dcs.log

On 7/10/2025 at 6:40 AM, Tholozor said:

Verify the BATT switch was set to MAIN PWR?

Honestly I don't remember at this point. I want to say I basically went through the startup procedure to make sure everything was as it should have been, in which case I would have verified BATT set to MAIN PWR but I cannot say with certainty. 

12 hours ago, NineLine said:

I see the displays cycle in your track but its so short I am not sure, and when I take control, the displays come back. If you have a better track or better steps to reproduce, we can look again. Thanks!

Interesting. I am speculating that the previous flight where the condition started set some sort of state/condition that was persistent for that play session, but that would not affect subsequent track files on machines that that state/condition set did not occur? Hopefully the log file helps. I will try to reproduce it this weekend. 

[NineLine]

3 hours ago, Gilligan said:

I was playing a modified version of the Flaming Cliffs F15C mission - Strike Escort. Some time ago I re-saved a version of the mission where I set the player aircraft and wingmen to be F-16C's. I did this many months, if no longer, ago and have flowing it several times without issue. 

This most recent time that initiated this post I was shot down and respawned via the "briefing" option in the pause menu as I have done numerous times before. When I respawned the aforementioned screens/displays were nonfunctional. Both MFD's and the HSI were black screens, and the HUD display would not, render? I ejected from that aircraft and respawned again however the condition remained.

So I exited that mission and started the instant action flight in the attached track file with the condition again remaining persistent. 

 

Log attached. I found these 3 Lines in it:

2025-07-10 03:57:38.122 ERROR_ONCE DX11BACKEND (18732): texture 'MFD_LCD_F16_LEFT' not found. Asked from ''
2025-07-10 03:57:38.122 ERROR_ONCE DX11BACKEND (42144): texture 'MFD_LCD_F16_RIGHT' not found. Asked from ''
2025-07-10 03:57:38.123 ERROR_ONCE DX11BACKEND (43828): texture 'EHSI_LCD_F16' not found. Asked from ''

As well as a whole block of "Cockpit: Failed to create Element 'ceMeshPoly' - reason unkown" lines associted with the HUD, MFD's, & HSI.

 

The only time I've tried playing that mission again the game crashed a couple minutes in and I sent that crash report at the time. I have not tried since. 

 

dcs.log 229.34 kB · 3 downloads

Honestly I don't remember at this point. I want to say I basically went through the startup procedure to make sure everything was as it should have been, in which case I would have verified BATT set to MAIN PWR but I cannot say with certainty. 

Interesting. I am speculating that the previous flight where the condition started set some sort of state/condition that was persistent for that play session, but that would not affect subsequent track files on machines that that state/condition set did not occur? Hopefully the log file helps. I will try to reproduce it this weekend. 

Thank you for the log. I will pass it along to the team to review.

[RogueSpecterGaming]

On 7/9/2025 at 8:14 PM, Gilligan said:

Was flying a mission, was shot down and respawned. When I respawned the aircraft had no HUD, no MFD's, and no HSI. I turned off the MFD switch and waited it tick, then flipped it back on. Nothing. Played with the HUD Brightness wheel, nothing. Pressed various OSB's. Nothing.

Ended the mission and booted up a standard instant action flight (track attached) and the condition persisted. 

No Screens.trk 2.52 MB · 12 downloads

If you are using a HOTAS make sure your throttle is out of the OFF position and in an IDLE or somewhere between IDLE and MIL.