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?

Sorry, I was not recording a track. Can I start recording one at any point? Maybe I should record tracks by default. @Cik: I will try doing that the next time I break one of the MFDs (it is kinda hard to reproduce that failure by getting ever so slightly hit by a SAM) :)

I've flown the mission where you destroy bunkers up the river. While returning home (with my guards kinda down) I got hit by a SAM right from behind. I was able to land the plane, even though I had a hydraulics failure and EAC failed and the gear was torn and all... :thumbup: On the ground (with broken gears) I requested repairs. Promptly the ground crew replied and after the timeout repaired my hog. After the repairs, the right MFD was still broken. I turned it off and tried resetting it, but it definitely was still broken. So I repaired again. The MFD was still broken. I could not be fixed. I then exited the mission, because flying attacks with only one MFD is kinda not really 'comfort zone'.

This ha happened to me in both Sims quite frequently. This is on win 7, 64bits and a nvidia card. I don't know how it really should look...

I use now use a curve that is very similar to the one suggested and it f'ing rocks! Thanks for the suggestion!!

What he said. Thanks so much for this!

Just did a startup the old way, and it completely confuzzled me, that neither my PFM and VVI did worl correctly. Went down again after take off, crosswind landing, with no FPM, nice. Did all the BITs again, nothing. Thanks for pointing this out!

Happened to me last time I was playing "the dam" with a friend of mine. Tried to fix this for so long I got shot donw by a SA-19.

Have fun, thus achieve perfection. They proved that you are way better at remembering things, when you have positive emotions about something.

One good trick is also to turn on ground power, so you can fire up the EGI and the CDU way before even touching the APU or the engines. That way, I end up with the CDU at something like 2.4 by the time I'm done with the startup and BITing all stuff. I then proceed to do the profiles, and by that time it's usually through. You could also take off, and put it in INFLGHT alignment mode, though I do not know, how much less precise it will be and what it affects. I guess it also affect JDAMs and any other PGM...

Ok, so I've been finally able to sit sown at the PC and get the profile. :) I took this profile here http://forums.eagle.ru/showthread.php?t=59208 and modified till it suited my style. You can see that I've mapped the mini stick on the throttle using bands, so that it acts as the trim stick. I kinda like this setup, because the mini stick was not useful to me in any other way. I have also assigned the "D" button on the throttle so it acts as "Left Shift". This enables me to bind the throttle 4-way hat in the sim as follows: Throttle Hat: All DMS functions Throttle Hat + LShift: All TMS functions. This way, I have DMS and TMS not split up into two separate modes on the X52Pro, but accessible from all modes. A-10C_shifted.zip