Shotsx74

Is there a key binding or a switch to turn on the light?

I think it is a cold start issue... or if u start in the air or on an airfield I don’t think the issue arises perhaps.

F-18, even with NWS active, will not re-engage the NWS HI or NWS after taking off from the carrier, and employing weapons and then landing back on the carrier (Super carrier). I have been able to re-produce this issue many times, however sometimes it works if I do not bolter and sometimes it doesn't. So, with the track, I started cold and dark. Loaded up my jet, took off without an issue. Deployed a couple weapons, then returned to the carrier. On this, track I did bolter, and when actually landing on the carrier, NWS does not engage the front wheel. Cycled on and off and still nothing. HUD displays NWS HI / NWS. Snowfox-BAW-v060-20200614-020357.trk

This is now an issue with the latest release. Full power, hook up. Wire keep dragging you back and never releases from the hook.

I just have major FPS issues when looking at the super structure, once I am passed it, it goes away. Also on Index, and 1080ti.

I haven't seen anyone bring this up or perhaps I didn't search correct titles, but how does one use the gray scale option on the DDI now? I see once you hit it, it brings up the scales but how do you set it to something or can you not do this? And if you can't what is its purpose of being there?

Through testing, it seems the carrier will only give instructions based on what the mission started. SO night starts into the morning when CASE I would be expected, you get a CASE III read back but it still stopped at the altimeter reading.

So, I don't have a track I can post here because of the file limit, but I do have a track file, if there is another way to post it please let me know. I started up on the carrier in the mid evening, it would be CASE I landing. Completed my mission and then returned which at this point was vary dark and CASE III approach would have been needed. I called in for the marshal and she would stop at the altimeter reading and it would cut off. I aborted my inbound and re did the approach call and she still stopped at the altimeter reading. I was unable to get any of the CASE III instructions.

the screens are apparently a "request"... and not a bug. Especially for VR users who can't really even see them. As for the lights I haven't noticed a change / difference. Every topic that gets created about dim screens gets moved even though in Wags' videos their bright as ****.

Not sure, I reported it before, it was changed to fixed internally, but I don't know what that means. I am still not getting a chaff flare message when using one or the other or both. The message was cycled between on and off again and still nothing was audible.

The display screens are very dark compared to Wag's videos on youtube and what other people report. The lines and self cross are almost unable to be seen and the display brightness rocker doesn't work at all it seems. This may seem like a request but it's a need if we want to use the plane at all depending on the situation. Compared the F-18 to the 16 screens, something needs to be adjusted with them, at least in VR....

MFD's extremely dark in VR The display screens are very dark compared to Wag's videos on youtube and what other people report. The lines and self cross are almost unable to be seen and the display brightness rocker doesn't work at all it seems. This may seem like a request but it's a need if we want to use the plane at all depending on the situation. Compared the F-18 to the 16 screens, something needs to be adjusted with them, at least in VR....

Squad mate and I were flying after the patch earlier and we were not getting the chaff flare messages upon dispensing of them. This was in multiplayer and in the CMDS page the announce option was on. I did even cycle between off and on and nothing changed.

There is the KC135MPRS, however either the baskets dont come out or the boom doesn't drop. I forget which one.

Did you do this in MP or SP? I think they cant reproduce this because they are doing it in SP and not MP. This seems to only be done in MP.

So is this a bug or ? Can anyone do this as well?

Figured it out.... So, when using a TGP with the Walleye. The TGP needs to be on the FLIR not the TV camera and the Walleye needs to be on the wrong channel. This then makes the sun flicker around causing the shader issues. Track attached This was in VR, idk if it works the same without VR or not. I would think it does. TNN_test-0919-20191025-140308.trk

I tried to attach the track but its too big. Ill see if I can get it up here shortly for ya. It actually seems like it is effecting the sun some how? Kind of weird.

Yes, once I switched to another munitions, or turned off the DL13 pod it Went away.

When using the Walleye and TPOD, as well as the DL pod, it seems I am unable to slew using the DL pod. In-fact, upon release the fuzz comes over the screen as if I had the wrong channel selected. AND if I have the tpod, I am unable to slew using the DL pod. The slew keys are still the same as normal for slewing the Walleye correct?

In VR, using the Walleyes, and then when the seeker is supposed to switch to the DL or Walleye for live link / slewing, the shadows flicker in the cockpit.

Track attached. I input the ILS for Batumi, but with one digit off. First time entering it is fine, however if you hit enter again, DCS crashes. TNN_test-0919-20191011-012615.trk

When entering the wrong ILS Freq on the DDI, the first time it will just flash as intended, however if you press enter again it crashes DCS. I'll get a track if needed, however it is very easy to re-produce.

I use the index, and it is very hard to read the MFD's especially when radar contacts are coming in and out of scope.

Second portion