kungfoo

Cool, thanks for posting this, MFAA does it. That's what I was looking for. Also pre-rendered frames to 3 makes motion sickness inducing stutters almost go away. Now I only need to get my prescription lenses for the headset, my glasses are kind of incompatible with it for actual flying for anything more than 30 mins.

what settings is everyone running these days? I tried 100% in steam vr app settings and the jaggies are driving me nuts. I also tried the magic number of 188% (which claims much higher than headset resolution per eye) and then the jaggies are much better ofc, but the performance kinda sucks. :/ Thinking about getting a 2080 Super.

That's fairly late in CEST, but maybe we can figure something out. :)

Still planning on running the server next time, on the 104th it was hard to get 'training' going properly last night. I've set up a discord server so we can coordinate the next session there and have voice working right away... Join: https://discord.gg/2PfBdkd Gonna run this mission next time: https://www.digitalcombatsimulator.com/en/files/1714752/ It has ground targets, even moving ones. It also has A-10 for lasing and other fun stuff.

I'll have to postpone until at least 2100 CEST...

Anyone have time tonight? Like 2000 CEST, which is 1900 GMT+1?

Great stuff. I happen to have a really fast internet connection, so I could possibly host for the start. I found a good training mission somewhere, let's try that one before annoying everyone on the 104th. :) Anyone of you use/know Discord? (I find it's a better/simpler alternative to Teamspeak, it also has persistent messaging).

Great, i think there's plenty of mirages on the 104th. is it okay for noobs to fly there? i only ever flew the a-10 on there...

Is there anyone in (or close to my) timezone (GMT+1) wanting to learn the ropes in the Mirage? Wanna join up?

I've tried to use the .reg files from the page that has instructions to deal with activation problems. This is on Windows 10, btw. The first module that fails to activate is Mig-21 and it is the first one that claims, it needs admin rights to do so. After that the OS dialog that asks for those privileges is opened and then, after actually doing the activation (it seems) it fails. This is 2.0.3 (the newest version available via the updater) and the error code displayed is:

I've changed my mainboard and my CPU to much faster ones. Now when I start 2.0 beta, it want to reactivate all of my modules. So far so good. Some of the modules worked to reactivate, such as F5-E and the Gazelle. However, Nevada terrain and the Mig-21 and the UH-1 module always fail after the reactivation actually seems to have worked. Is there any way I can fix this?

Out of pure curiosity: What is it that breaks? Is the output temperature getting too high? Or is it the torque?

Was the startup behaviour changed at some time lately? If you increase fuel flow too fast now, the startup will fail with a noise as if something broke. Took me some time to figure out. :)

Thank you, that fiex it. I looked at the threads, but somehow overlooked that one. Thanks for helping.

Activation consistently fails after update of Windows and Beta3 I have recently updated to Windows 10 and also today to the new beta release 3. When starting DCS, it detects a 'significant' hardware change and wants to activate Mig21. It can't activate Mig21-Bis, it just keeps going in loops without the activation ever working... all the other modules just work. What gives?