gorgar0

I think Oznerol256 bug post should be a model for other bug reports. He characterizes the problem very well. He describes very clearly how to reproduce it and includes a track.

I was on the insider builds so I reverted to the normal latest Windows 10 and it's working ok. I'm going to stop using the insider builds. Don't like having my aircraft grounded.

Ok, I reverted to the release version and tried starting DCS. Still gets an error but it produces a better report. I have attached it. dcs.log-20180607-163704.zip

I'm having the same issue too. It started when I upgraded my nvidia drivers to the latest. Also rolled back to 391.35 and still not working. I deleted all exe and dll's and did a clean and repair and same problem. logs attached Logs.zip

So just curious, and not trying to be coy, but what is it called in your training guides?

Don't expect any with your unnecessary sarcasm in your OP.

There was mention of this in the release notes: Known issues Player parkings on carrier are broken. External lights (flashlight, taxi light) are visible inside some cockpits. Spitfire tail wheel contact model with ground is broken. I guess the MiG 21 is one of them.

I used this one as a reference: https://www.digitalcombatsimulator.com/en/files/599/

It's amazing that ED is factoring this in the flight model.

I'm pretty happy. I bought it knowing very well it will be released at the end of spring. I think I'll do as NoJoe and read up on the NATOPS.

Nope. Just verified it with 2.5.1. No right click functionality with the Oculus Touch controllers. Would be nice to have it though.

I wonder if it's just a licensing issue: http://www.trademark.af.mil/Licensing/Current-Licensees/ Not sure if there's a cost in getting the license to use "United States Air Force."

Nice summary though, nessuno

Seems pretty clear to me. Identified issues Addressing issues (doesn't mean fixed) Working on the issues Release when issues are fixed.

But in all seriousness, I set the clock back and let Oculus update do its thing. I then set the clock to current time and my rift is running fine now.

Me? I just paid the 2 grand ransom to FB and got my rift back.

Here is an article that has some tips that may improve your VR experience: https://www.windowscentral.com/how-ensure-best-vr-performance-your-pc I haven't tried them yet but the SystemResponsiveness registry setting looks interesting.

Oculus is working fine for me with 2.5.

Did you try running cleanup and repair?

Resolved. :megalol: I just needed to delete the CoreMods/aircraft/F-86 folder and do a cleanup and repair. Apparently there was a bad file under that folder. :thumbup::thumbup: to DCS support staff. They were very helpful.

Yeah I did the tick/untick. All of my other modules work fine. Well must be something with my environment. Thanks for your replies.

My F-86 module shows up in the Installed Modules page but when I try to fly a F-86 quick start mission I get the A-10C instead. Also, the F-86 does not show up in the encyclopedia nor in the the mission editor's aircraft selection. I tried removing and reinstalling the module and did a repair but no joy. Has anyone else tried to fly the F-86 in 2.5?

The JF-17 looks like the love child of an F-16 and a Mirage 2000.

It's my understanding that by buying the early access that we are part of the testing process. If this was a production release I'd understand your frustration.

"On a serious note, might be worth reporting it if no devs turn up here and confirm WIP. I've noticed the stopwatch doesn't work either." The stopwatch is functional it's just that the buttons don't work in the cockpit (maybe that's what you mean). But you can bind the start/stop/lap functions to keyboard/hotas.