Goblin

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.

;-)

I bet 24/12 will seem pretty insignificant compared to 28/11 ;)

Rb04..! I have armed my share of AJ37's with those. Like hanging small airplanes under the wings ;)

:)

That sure looks nice!

There are key hardware differences between the DK2 and CV1. One thing is the refreshrate. 90/s in the CV1 and just 75/s in the DK2.

Hope you're right, MMJ! Some detailed info and pics would be awesome!

And here's my ejection handle... It's basically a rubber tube with black and yellow plastic braiding mounted to a extruded aluminium electronics box. It attaches to another box that contains a microswitch. The parts are held together with magnets. When the parts are separated, by pulling the handle (duh!), the switch is released, closing the circuit, and repeated button presses are sent. So, I no longer have any use for my wish, although I do beleive it is a good idea to implement a VR ejection mapping.

Yeah, you scared me..! ;) No, seriously, I was afraid that I came across as hostile. :) Attention to detail can never be negative! ;)

"Nothing further, you honour!" ;) Well, yes, I guess you could view the flight control inputs (stick and rudder) as a force sensing unit, since it translates the force, applied by the pilot, into flight control deflection. But I just meant that the translation was correct, and that there were no force sensors in the schematics. :). I just wanted to explain myself. Nothing sinister. ;)

Very cool score! Makes me think of the A320 Airbus for the Amiga. I could sit and listen to that tune for ages. :)