Lange_666

Just bought it, looks stunning. But then while creating a quick flight in the editor just to be able to fly around a bit i realized that this map has one big drawback and that is the distance between the Falklands and the mainland (Argentina or Chile). I wonder how many will fly the entire distance for an attack run only to get shot on the first approach over the target and then hit the refly button for another go which will take yet again the same amount of time to get there? Ex: A-10's will have a + one hour flight time to cross and one more to get back which makes it directly a +2 hour session and than i won't bring up heli's). Then carriers come into play but this limits the amount of flyable aircraft by a big amount.

WinWing subforum: https://forum.dcs.world/forum/605-winwing/

Don, we're talking about 2 different things here. I'm still talking about the images TylerPL666 posted above (i responded directly underneed it), you still talk about the 3D effect visible in VR.

I was referring to the images above my previous post Don, not what you see and i don't with the 5 settings. Since the images above are the same for everyone (because of not viewed in VR) i wonder what the real difference was which i don't seem to see on those. If you can see something different beside the camera standpoint being different and a pixelshift here and there, i'm just curious on what that is.

Well, i don't know what you guys are seeing differently but for me, beside the fact that the camera standpoint is not exactly the same, the quality of the images is the same. If not, maybe point it out with colored arrows where the difference is because i don't really see it.

I used to have that but deleted it a while ago together with my entire Cougar folder in which is resided. I do have a DCS target macro generator script if someone is interested. Just PM me for a copy.

I don't think so, if i'm correct they are re-created when you delete them.

You can remove the contents of both the fxo and metashaders2 folders (or delete the folders entirely, they are re-created when you first run DCS after they have been removed). Personally, i have never seen any difference in performance if these where not deleted (i've done both ways). Pagefile setting: fixed space (so not windows managed) and as large as your RAM is. So if you run 32GB RAM, set the page file max and min to 32 GB.

Yes, use the Custom Presets under the App Settings tab. Run the updater, start DCS, set your settings in DCS, quit and set a preset name for it. Repeat for more presets. When done, these are available under Select Preset on the main page of the updater.

I missed that part, just did read over it after reading that i should never use Windows Calibration to calibrate a controller (which i never do). Thx for the heads-up...

I'm using DX buttons for that, that way you don't send a keyboard command (or need to hold one). //Autopilot Select Switch MapKey(&Throttle, APPAT, Autopilot_PITCH_Switch_ALT_HOLD); // DX88 MapKey(&Throttle, APAH, Autopilot_PITCH_Switch_A_P_OFF); // DX86 MapKey(&Throttle, APALT, Autopilot_PITCH_Switch_ATT_HOLD); // DX85 PS: I'm using the 120DX button mod to get more then 32 DX buttons. Gives you plenty of option for not using the keyboard.

After contact with Milan and receiving the steps (same as in the manual) the problem still persisted. Flashing v5.0.9 resulted in full deflection already in the center, resetting the device as advertised did nothing, going back to v5.0.5 always solved the problem. Then Milan gave the tip to reset (set to default) the device in Windows Calibration. This worked. v5.0.9 is up and running.

I didn't calibrate with Windows Calibration, just used it to see the response of the Z-axis to confirm the behavior and what i saw in the controls setup in DCS. Just gave it a second try, followed the instructions step by step, same issue. Went back to firmware v5.0.5 (with the same instructions), all fine again.

Can't make this work on my V2. Flashed the new firmware (v5.0.9) through the MFG Configurator (and Bootloader) and after the flash all is fine in the MFG Configurator, the resolution doubled to 8192, pedals at rest (middle) show 4096, pressing full left gives 0, pressing full right 8192. However, in game or Windows Calibration or DIView it does not work, it shows 0 with full left pedal but gives 8192 at middle position and still 8192 at full right. Manual recalibration halfs the res instead of doubling it, full left is then 1224, middle 2048 and full right around 3072. Going back to auto after that goes back to original problem. Flashed back to v5.0.5 (redusing the resolution back to default) and all is fine again. Also, after the flash to v5.0.9 i'm unable to run the MFG Configurator 2.17. It runs (it shows up in taskmanager) but the program is nowhere to bee seen, not even after a reboot. The only way to run the configurator again was using version 2.15

So my Oculus software settings tells me that it's using OpenXR as runtime. Does it use the OpenXR from within the DCS dir or another one installed somewhere else by Oculus?

I'm having the same issue with my Rift S when running OpenXR but the shift of the whole cockpit is rather small (but enough for me to drop OpenXR). Reset WMR doesn't work for this and my room is well lit.

In DCS, go controls then disable hot plugging

Been there done that, works for a couple of times, then stops.

Been already a problem for years for me. Solution from support is always the same, we see nothing wrong but try a different e-mail adres. Works for while and then same problem roars its ugly head. Another e-mail adres solves the problem again for a few weeks and then all comes to a stop again. I just gave up on the newsletter all together...

Yes Can't answer your other question because i don't have anything Steam related. What i do know is that once you have the standalone version, you can make a copy (like for a second install, being it the stable version or one in which you install mods or try some other stuff) and update that copy to the version you want. And if you want to make your life easy: just use Skatezilla's updater/launcher: Also, everything Steam related is to be found here: https://forum.dcs.world/forum/284-steam-support/

Whatever, D3DCompiler_47.org or something.

Could you please please please link directly to the download file instead of an overview page with lots of directory's and files? If there is one thing that always confuses the hell out of me it's the Gitlab jungle. I never ever know what i need to download...

You will have more chance of getting an answer in the Input/output section of the forum: https://forum.dcs.world/forum/70-input-and-output/

Nope but then i don't have WMR installed, i'm running native Oculus, no need for all that <profanity>.

When in VR, my IHADSS view is slightly tilted to the right when i look straight forward. So the IHADSS horizon line doesn't match with the real horizon. I have to tilt my head a bit left to make then match. I find this annoying. Anybody else have this problem?