Jump to content

hflag

Members
  • Posts

    47
  • Joined

  • Last visited

Personal Information

  • Location
    France
  1. hflag

    VR FPS

    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
  2. hflag

    VR FPS

    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.
  3. For now... "...my favorite helicopter to fly for now... for now..." :thumbup:
  4. 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.
  5. 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 :)
  6. 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.
  7. The problem remains in 43872 Here's the track (VR Rift S) conflicting_shadow.trk
  8. 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...
  9. 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.
  10. 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.
  11. 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
  12. I was just a tiny bit provocative and it worked :-) Thank you Bignewy for the good news and Happy new year!
  13. 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.
  14. Yes, click once on the CRS setting knob and it switches to BRT setting.
  15. 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.
×
×
  • Create New...