Hippo

Was wondering whether DS might have been off. Sorry, that was probably too obvious.

I had no idea that this even existed. Thanks for the heads-up. Hopefully it will implemented for all modules at some point. Quick question: Once the bookmarks are set, is it permanent, or do you have to set them up each time you start a mission?

What is your deferred shading setting in 2.5.0?

On 2.5.0 latest. Just flew this for the first time ever and failed for going outside low level altitude limits, just after starting the low level run. I was unsure whether I was supposed to stay in formation or not - could this be made clearer in the briefing? I suspect that if I attempt to stay in formation I will fail. I found that the instructor did make many yo-yo altitude changes. Next time I'll ignore the instructor on the low level bit and see how that goes. Suggestions (and for BFT11) as well: Have instructor say target airspeeds as they change. Show a screenshot in the briefing of what the formation positioning should look like from the cockpit.

I think I've been a bit harsh. It seems to be an Oculus Rift issue, right? Do other headsets also have this issue? My experience is: no DS - cockpit good - outside horrible. DS: with very low gamma (1.0 - 1.1), outside is pretty much black, which is ok, city lights are way too dark though, and the cockpit is too dark to be comfortably usable. With higher gamma everything washes out too much for my taste. Wouldn't ED have to make significant changes to get this "fixed", just for VR users? Doesn't seem very likely to me. That video is brilliant, and gives (imho) a very good representation of what night looks like.

DS = deferred shading. But there is no longer an option to disable it in 2.5.1 and later. Have you tried turning your gamma down?

Others don't seem so impressed. https://forums.eagle.ru/showthread.php?t=209337

It's a read-only forum :(. Thanks for replies.

Like a "say again"? That would be very helpful (and realistic). I think showing it on the kneeboard is not too unrealistic, as it's as if your in-game pilot just wrote it down. However, I really think all this should be down to DCS itself, with an option to show a log of all comms on the kneeboard, which I've suggested on their wish list. Whether something like that will ever be provided...?

RE having to write down co-ordinates (or any other instructions). It would have been nice to just have had these to hand in the (in-game) kneeboard. Not suggesting you change your existing campaigns, but might want to consider this for future ones. It is somewhat inconvenient when in VR to have to write these down, even in non-VR why expect the user to have to write them down? I don't think it's too much of a concession to realism to just provide them with the kneeboard briefing. I'm now going to have to go over the practice mission, screenshot the co-ordinates for each waypoint, and then place the screenshots into the kneeboard, before I can complete this mission. This is all very frustrating. For the hardcore who insist on physically writing them down, they can just choose to not use the kneeboard. Just a thought.

Sorry to post this here, but I couldn't find an appropriate forum. Can someone please point me to the official status of 1.5.8? In particular Will it ever get any updates? I understand there's no official support? Some of us are still using it (surely it's not only me), but there doesn't appear to be a forum for it where we can discuss it between ourselves. I assume products in early access when 1.5.x was still supported will not be updated for 1.5.8?

Good idea in principle, and nothing against it, but I suppose it will add complications as to how to distinguish between keyboard commands and keyboard input to the kneeboard. Much additional work for the devs? Extra delay to implement this (essential) feature. Adding tabs I suspect would not be a lot of work as all they would need to add would be two new key binds (next tab, prev tab), and placing the respective images into subfolders, with not too much extra code? The kneeboard wouldn't even need to look any different (although visible tabs would be nice), it would just be a minor change to functionality.

+1 Or have a log of all the comms in one of the kneeboard tabs.

Please tell me you've found some tweak or setting that gives you a good night experience in VR. For me, night is very disappointing. The cockpit is good. But outside the terrain is washed out (far too bright), and the sky looks horrible.

And changing my mind, again. Overall better with SPUD ON. With a gamma of 1.0, it's actually pretty good. If the ground lights were much brighter, it would be very good. Just have to live with the mura when looking to the sides, but as will spend most time looking forward with instruments in view, acceptable. All very subjective, and IMHO of course. **** EDIT **** and I have to change my mind yet again. Whilst first impressions were good, trying to fly the A-10 in another mission was impractical as switches were very difficult to make out. Sorry to say, DCS, night and VR are a huge disappointment. I guess I'll have to stay with DS off - the external environment looks bad, but at least the cockpit's usable.

DS: I think that the external environment looks better, but the cockpit environment looks worse. My own negativity comes from a > 50% frame drop at same settings (when I use 4xMSAA, PD 1.2). IMHO not having MSAA on in VR gives unacceptable image quality. As you say it was the REMOVAL of choice that is the issue, rather than anything against DS in itself.

I'll take that back now please. With DS, it definitely does make a difference*. The mura is eliminated but I'd say the blacks are no longer as black, almost as if there were a backlight washing everything out slightly. I'd also say the cockpit is more difficult to make out. So, looking to the front, better with SPUD on, looking to the sides - better with SPUD off. Overall, probably better with SPUD off. Ground lights are definitely way too dim. (All done in A-10C mission "Night Train to Georgia", I expect that results may vary with other aircraft. * I was not actually getting mura issues in 1.5.2, and mistakenly thought that this change might fix the sky texture problem - which it didn't. Has anyone tried night in the 2.5.2 Persian Gulf? How's that looking. Do the NVGs work? I suspect that getting a good night environment in VR is going to be very tricky.

From my limited testing, I come to the same conclusions :(.

I haven't looked at all the posts in depth, but I had come away with the impression 1.5 or 2.5. without DS = good, with DS = issues. To me 1.5 looks too bright, and that sky texture is awful. I've just tried 2.5.0 with DS. Which I think looks better / darker, but ground lights are too dark. And night vision goggles make the cockpit unreadable. But the mura issue described by the other poster is very noticeable now, maybe it's with DS that this is an issue? Going to gamma 1.0 almost eliminates the effect looking when looking forward, but look to the sides and it's back. Looks like whatever you do you can't win. I'll try the mura registry change in combination with DS, gamma 1.0 and see how that goes. Is my description representative of your own experience?

Thank you. Gave it a go, but I noticed no difference.

The option doesn't exist in 1.5.8. In 2.5.0, it's set to 2.2, but I can't change it (I have deferred shading set to OFF).

Hi - have had my Oculus for around six months, but haven't been using DCS as much as I'd have liked. I'd read that there were problems with night graphics with deferred shading, so haven't tried with that. But even with 1.5.8, 2.5.0, I tried the mission Midnight Train to Georgia, and - land looks too bright, and there is what I can only describe as a multicolour blob in the sky. The cockpit looks good. Are others seeing this as well, is it something that can be adjusted for? A deficiency with the way the Rift works?

Aw, don't say that, I was starting to like him!

Thanks for replying. It seems to be ok for OpenBeta ->2.5.1, Standard -> 2.5.0; but seems to be unaware of 1.5.8 (which I tried to assign to OpenAlpha).

I am trying to control this using the keyboard (Rctrl-Z, Rctrl-X), but I find it way too sensitive. It is also extremely difficult to recentre the knob. Am I doing something wrong?