Goblin

I have been a flightsimmer since the -80ies and the Commodore 64. VR is the single most important invention in flightsimming, ever. That's the short version. The long version is of course more complicated. Even if todays VR HMD's have better than HD resolution, your eyes are so close to the displays that you can see the void between the pixels. This produces a grid, commonly known as 'the screen door effect'. This, of course, means that you will see the pixels as well. Sitting 3 ft away from your 4K screen can not be compared to VR. It just can't. Not if you're interested in picture perfection and clarity. In addition, your PC has to produce two separate display feeds for VR. One for each eye. That's not something a PC does without breaking a sweat. So, you may have been spoilt by great FPS in ultra high graphics settings, on a 4K screen, like I was. Ok, I had a curved UWD screen but anyway... I got a Oculus Rift CV1, and I can't fly on a 2D screen any more... The perfect view tracking and the 3D vision, with depth perception, is so close to reality (yes, I fly real aircraft for a living) that a 2D screen and TrackIR just won't cut it any more. Turning my head 90 degrees to my side to see the the side view, and the fact that if I focus on the wing everything beyond that will become out of focus, just like in the real world, makes my simple mind believe that there actually is a wing and a world out there, inside my VR HMD. I don't care that it's not 4K resolution. I get so bloody immersed in the experience that I try to lift my hand to shield my eyes from the sun, or reach for the canopy handle... VR isn't about screen resolution, although advances in technological hardware will improve upon this as well. Once we enjoyed sims at 640x480, or even lower resolutions. Advancing technology have increased the resolution, and we all reap the benefits of that. But that doesn't mean we weren't having fun at lower resolutions...

Perhaps a slight digression, but as we are talking about Viggen accidents, this one is special. http://www.svfplhist.com/37/37hav032.htm Simulated naval attack, birdstrike and hitting the sea surface. The pilot was ejected but didn't survive. He was found without his helmet... A few months ago, a guy shows up on a Norwegian Facebook group where I'm a member, showing pictures of what is clearly a SwAF pilot helmet. He found this on the southern shores of Norway, in the -70ies, as a kid. He recently found it again and started thinking that it most likely had a grim story to tell. As it turns out, it was the helmet from the accident mentioned above. The helmet was returned to the squadron at F7, to which the pilot belonged. I know the Norwegian media is on the case, so there will most likely be some sort of coverage, eventually.

Yes, ASW works! No doubt about that! It's just that I can't change the modes. It's stuck at auto.

1. The registry is edited as per instructions found here: There is a difference if I set the AswEnabled to 0. ASW definately works, but seem to be stuck at auto. 2. I have Win10 64bit. 3 FPS is either 45 or 90 (+/- 3 FPS occasionally) no matter what I do with the Ctrl Keypad 1-4 commands. If AswEnabled is set to 0 the FPS will vary continously.

No, I don't really think so either. Just trying to troubleshoot this...

ram0506, What type of keyboard do you have? I have the Corsair K95 RGB.

Tried it with numlock on and off...

I'll try another keyboard....

If DCS 2.5 becomes the true sandbox sim that I imagine it will, core development of DCS shouldn't be affected by 3rd party mods.

None of them have VR support though...

As for WWI being a niche market, just look at how big RedBaron II/3D got, back in the days. And more recently, the excellent Rise of Flight. There are even modders making WWI mods for Combat Flight Simulator, called Wings over Flanders. Imagine that bunch getting into DCS..! As for flight data. This was when flying still was being invented. Not very aerodynamically advanced crates. At such slow speeds, I would believe that a good wind tunnel simulation would make pretty good approximations. And if you partner up with The Vintage Aviator Ltd in New Zeeland, you could probably get a lot of good info. I bet The Fighter Colletion could pull some strings... ;)

I have moved over this to the ASW thread, but I have tested disabling ASW in the registry, and there is a noticeable difference, so it definately works. But I can't switch between the different modes.

And this allows you to switch between the modes, on the fly, while in DCS..? I mean, if you press Ctrl 3 (numpad 3), does the FPS lock to 45/s? That's what I expect it to do, but maybe I'm wrong in my assumption?

Numpad, keypad... We're both talking about the numeric keypad to the right of the keyboard, right..? Or am I missing something?

Yeah... I tried disabling ASW in the registry, and there was indeed a big difference. With ASW enabled I get either 45 or 90 FPS. With ASW disabled, the FPS vary and the lower FPS is noticeable, whereas with ASW it's much smoother. But it seems like ASW is stuck at mode 4 (auto), and none of the other modes (1,2&3) work. So, the question is really why can't I alter the modes with Ctrl+1/2/3/4?

Any 980TI user that can confirm that ASW works on their PC's? If you press Ctrl+KP2 or3, does the FPS lock at 45? I have done the registry hack, but the Ctrl+KP1/2/3/4 doesn't make any changes to the FPS...

My point was that waiting is too long, no matter how long it takes... Release could be tomorrow and it would still be too far in the future. But like posted above, someone is actually making a study sim class VIGGEN!!! :)

Yeah, it's in the release notes today :)

Indeed! :)

Yes. Hmmm... I have disabled hyper threading in BIOS. Could that have anything to do with this? I'm on Oculus runtime 1.9, and after some googling I have found some users with similar problems and 980TI's...

Hi Frusheen and thanks for helping! I found two rows containing "asw": 03/11 19:51:40.791 {DEBUG} [ASW:NV_FrameEstimator] Encoder caps ASYNC=1 MEONLY=1 03/11 19:51:40.821 {INFO} [VirtualDisplay] ASW Enabled Edit: If I look in the reports from where I ran DCS I get more hits, like these: 03/11 18:09:57.835 {DEBUG} [ASW:FrameEstimator] Unable to lock extrapolation thread 03/11 18:09:57.837 {DEBUG} [Localization] Language Tag: en-US, fbt locale:en_US, cldr:en 03/11 18:09:57.840 {DEBUG} [ASW:FrameEstimator] Unable to lock extrapolation thread 03/11 18:09:57.840 {DEBUG} [ASW:FrameEstimator] Unable to lock extrapolation thread 03/11 18:09:57.842 {DEBUG} [ASW:FrameEstimator] Unable to lock extrapolation thread 03/11 18:09:57.845 {DEBUG} [ASW:FrameEstimator] Unable to lock extrapolation thread 03/11 18:09:57.845 {DEBUG} [ASW:FrameEstimator] Unable to lock extrapolation thread 03/11 18:09:57.847 {DEBUG} [ASW:FrameEstimator] Unable to lock extrapolation thread 03/11 18:09:57.848 {DEBUG} [ASW:FrameEstimator] Unable to lock extrapolation thread 03/11 18:09:57.885 {INFO} [ASW:NV_FrameEstimator] Breaking promise vsync distance 19847.7

And to our graves... ;)

So, I have finally had time to try the ASW feature... I did the registry edit, but the Ctrl+KP1/2/3/4 commands doesn't seem to work. I expected to see the FPS to lock at 45 when pressing Ctrl+KP2 or 3, but it still varies up to 90. How can I check that ASW is enabled? I have Win10 64bit and a 980TI with the latest drivers.

AA: Heatseekers only. AG: Bombs. Rockets. Remote controlled missiles. Anti-ship missiles. Gun pods. Mavericks.

;-)