Nooch

A good F-14 one with a retired RIO http://aviation-xtended.co.uk/ep-39-top-gun-days-and-the-f-14-tomcat/

Hi, I'm wondering what is a proper approach for the A-10C. I did the mission and found the procedures given by the instructor somewhat confusing and not complete, regarding adequate speeds especially. In the attachment below I've drawn how I am performing the approach in blue and red. Could someone please tell me if that's correct? Thank you.

Epic trailer! :thumbup:

Quel boulot! Je n'ai pas encore le module mais je regarderai ta vidéo en intégralité. Merci à toi :thumbup:

I understand your desire for a F-22 but be aware that if ED were to make one right now it would be complete crap. When all the documentation on the aircraft is classified what can you do really? Not much...

You would have to be out of your mind to not want a P-51 in DCS :D

Just for your information sfc /scannow performs an integrity check of your windows files. All it does is just check files, it doesn't actually do anything. If it were to find missing or corrupted data you would need to type an additional command line to initiate a repair. In case the repair would fail for some reason you would then have to use dism /online /cleanup-image /restorehealth. Long story short it has nothing to do with DCS.

What you're describing shouldn't be a cause of stutters. DCS does not use Nvidia PhysX (as far as I know) and the cpu clock speed ramping up above its advertised frequency is done automatically by the hardware within reasonable temperature limits.

I had the same issue where I wanted to assign a hotas key to something and it didn't register. I had to select it manually in the dropdown menu. It happened multiple times actually. I guess it's a known issue with the sim. It's quite frustrating because it makes you think there's something wrong with your hotas when in fact it's perfectly fine.

I used to run ccleaner back in the day about ten years ago but I stopped using it because my pc was running perfectly fine without. IMO this software is more a waste of time than anything else.

Pour le joystick je t'invite vivement à ne pas utiliser l'utilitaire de configuration Saitek mais plutôt d'assigner les touches uniquement via le menu de DCS. Sinon c'est le cauchemar total.

Strange... I have pixel density set to 1.0 and yet the HUD is very readable for me. Are you sure you set up your headset properly and your image is as crip as it can possibly be?

I found that what's working best for me right now is to make two quick five minute breaks every hour of VR flight and also avoid reading kneeboard checklists and stuff like that. At least that's what I did last time and I did not experience too much eyestrain at all. Stereo vision still feels awkward though. I guess that's something I'll have to get used to cause I can't do anything about it. :noexpression:

Yes clearly with a 1080 Ti you shouldn't be stuck at 14 fps. There's a problem here. Even with my 980 I'm sure I'd get more than that. :noexpression:

Je te conseille d'attendre encore un peu. Pour l'instant la 2.1 est en alpha donc synonyme de bugs à la pelle et comme si ça ne suffisait pas tu seras obligé d'installer à la fois la 2.1 et la 1.5 car tu ne peux pas voler sur la map caucase dans le 2.1 (qui ne contient que la Normandie et le Nevada). Donc c'est pas l'idéal. D'ici la fin de l'année (je pense) la 1.5 et la 2.1 vont fusionner en 2.5 et il n'y aurait plus que cette version là qui aura toutes les maps, moins de bugs etc.

You're right, after having played several hours with the oculus now I would definitely advise you to wait for the next gen. Right now the resolution is awful, so bad in fact that you cannot even read inscriptions in the cockpit and even in general, it's a big immersion killer. If you then add up the fact that everything out of the center of the image is blurry, plus the stereoscopic vision that feels uncomfortable right now, man... I don't know if it's actually better than a normal screen with Track IR...

Unfortunately, no :(

Are you sure about it? Cause I feel bad reading this, especially now that I've created a thread in the bugs section :doh: :lol:

Hi! I've started a thread in the Input and Output / Virtual Reality section of the forums and after I got some replies it seemed quite clear that there is an issue. Both "eye_shift" values you can find in \DCS World\Config\MonitorSetup\Stereo.lua are set to default values (0.032 and -0.032) that don't change according to the user IPD. This can create discomfort, especially if the correct values are quite far off. IPD (which translates here to lens spacing on the headset) is measured and known at all times by the Rift software and even by the user (part of the Rift initial setup) so all the sim needs to do is pull the value from it. If this isn't possible for some reason, the user should be able to manually enter the value in the sim VR settings window. EDIT: a forum member just suggested that stereo.lua is only used for 3D monitors and that the sim already gets the correct IPD value by itself. My apologies for creating this thread if it's indeed the case.

I'm glad this thread helped you as well! I will try to post something in the bug/problems section of the forum so that developpers can know about it. If things were done right, the correct value in stereo.lua should be set automatically without needing to edit it manually.

Last night I went and checked the file stereo.lua and indeed the default settings were wrong. But not by much. 0.032 instead of 0.033 so quite a small difference there. I fixed it and then launched the sim and stereo vision seemed a tad more comfortable. The problem though: my eyes were still very much strained after my session. That could be because of many different things. I did a lot of kneeboard (checklist) reading that night in VR and the fact that I was struggling to read those blurry letters certainly didn't help. Low resolution and the fact that everything that is away from the center of the image is blurry (by design on current VR devices) are a bummer and certainly contribute to eyestrain... Maybe the Rift isn't adjusted well on my head and I am either too far or too close to the lenses. Possible but really not likely because I spent quite a while adjusting the headset and tried multiple adjustments. Right now it sits tight (but not too tight) on my face and the image is as crisp as it can be. I can even see individual pixels at all times... Very hard to tell what's wrong there but I guess it's the subject of another discussion. Either I'll finally figure it out a bit later or I'll just have to sell my Rift...

Thanks for your input grifo. You're right to point that out, convergence weakness could have been the cause of my problem. However last time an ophtalmologist checked my vision, I had strong convergence and 12/10 vision so I think I'm good on this front. Perhaps I should have said it earlier.

Thanks! That's precisely what I was looking for. I'll have a look into this file and keep you guys updated. Sorry, in my long post I just lacked the proper vocabulary. I'll make an edit. Actually I meant that VR HMDs change your depth perception using the stereoscopic ability of your eyes (two different points of view that your brain combines into one) but without making your eyes accomodate. Because your eyes aren't used to that in real life, I guess that's what's creating eyestrain. Again I could be wrong though.

I may have figured out what was happening. I think it all comes down to what VR headsets are doing to give users distance perception. Basically they have to trick the brain into thinking you're looking at a more or less distant object when in fact you aren't because the screens (one for each eye) remain at the same distance from your eyes at all times. Let me explain in more detail. VR headsets change your depth perception using the stereoscopic ability of your eyes (two different points of view that your brain combines into one). For example, when you look in the distance, the angular difference between each point of view will be negligible. Depth perception will be minimal. On the other hand, when you look at something up close it will become quite important. Problem is VR headsets do this but without making your eyes accomodate which of course confuses the brain, which isn't used to this kind of scenario. Your brain then sends signals to your eye muscles to make adjustments when in fact, there is no need for it, creating discomfort and eyestrain. I could be wrong though. Please take what I said with a grain of salt.

Night and day...