hflag

The "Full screen" option is not the specific cause of the problem because you literally toggle the value each time to get the "option restart". Any option change that generate a forced restart does the trick. Changing the relevant value in the options.lua before starting DCS does nothing, a hard "Options restart" is the only way to go. A correction to this problem would be very welcome in the upcoming hotfix

I couldn't describe with better words what I experience since the last update with the F15 E. I tried many things but didn't think of the "Full srceen" option, good catch! and thank you. I will try this solution tomorrow.

For now... "...my favorite helicopter to fly for now... for now..." :thumbup:

Yes it's already been reported long ago. It's the kind of little things added to other little things that bring the feeling to be there in VR. I guess we will see moving hooks when the model is completed.

I didn't notice the third central shadow yesterday. I tried every shadows settings even no shadows at all and this bug is still there (VR) with the instrument panel flood light knob out of its zero position. Am I really the only one to see this? The track for VR I provided in the message above is still valid :)

I see this since the initial release of the Viper: setting the console flood light knob to a position other than 0 brings up an immediate stutter. It's very obvious when looking at the moving landscape at a 90° angle. The rock solid 40 fps (Rifs S) before turning the knob is now fluctuating from 33 to 40 fps.

The problem remains in 43872 Here's the track (VR Rift S) conflicting_shadow.trk

Yes I delete fxo and metashaders2 after each update, it's second nature now :-) I am currently downloading today's patch and will provide a track as soon as possible, maybe the problem will be gone...

I looked at this again and actually you need the full MFD brightness in VR (Rift S) to hardly see the entered value. In 2D the black on white text is very thin but still visible. With brightness set to minimun, only the white seemingly empty rectangle remains on the MFD.

Noticed that too. You have to click down several times on the brightness setting rocker to see the black on white text appear. I guess some more work is needed on the MFDs.

Its been reported before and corrected some patches ago but they are back with 2.5.6 with instrument panel flood light on. This time, the lateral consoles with consoles flood light on are not affrected. https://forums.eagle.ru/showthread.php?t=256446

I was just a tiny bit provocative and it worked :-) Thank you Bignewy for the good news and Happy new year!

I am wondering if this Viper cockpit lighting issue has become a taboo subject because it is (we are) utterly ignored by ED... quite disappointing, to say the least.

Yes, click once on the CRS setting knob and it switches to BRT setting.

It's still tagged [Cannot reproduce]. So, officially there's no problem with the light knobs. I don't understand the silence from ED about this one. https://forums.eagle.ru/showthread.php?t=257702 @ Der Hirte yes, in my mind too, flood means plenty.

Here's the track, please tell me the max position you get compared to the screenshot I posted earlier. rotaries.trk

The light rotaries bug remains after the last update. Is it still considered as non existant and therefore will never be fixed?

I used the 2 warthog throttle axis, the throttle slider and the X and Y joystick axis to have all the knobs at the same time set to axis and indeed the knobs go all the way up to 100% but stop at 80% or so when the mouse is used. How can this still be tagged [NOT A BUG]? Please compare the 100% (mouse) knob position in your Viper with the attached picture.

I observe the same behavior as I already said in the other thread. Maximum rotating knob position reached with mouse vs axis binding. The console floodlight knob is not affected.

Brilliant idea and good catch! It's better in VR with the full knob range but I still think the 100% floodlight setting should be brighter. I agree with DEE-JAY when he says that the pit should not look like a Christmas tree and ruin our (virtual) night vision but the rehostat is there to fine tune the lighting in relation to ambiant lighting and the amount of time spent in the dark.

Far beyond nitpicking but I couldn't resist :) Should be 139R

Absolutely, I have the very same result at night. If it works as before for someone, because it's [no bug]!!!, please post a screenshot at night with floodlight set to max.

For the interior lights and particularly the instrument panel flood light, here's what I get since the last patch. I have to admit the light is a little more vsible in game. Although I pushed the brightness on this image, the difference is hard to see. Can someone post a screenshot of a working instrument panel flood light with the last patch because my other post on the subject is tagged [cannot reproduce]

See ams999 post #19

The flood light was perfect before the last patch.