slughead

I never had any issues with Win11 and the G2. Also motion reprojection was "ok". So it sounds like a configuration issue to me.

You're welcome.

@NineLine will do. There is one thing that ED may be able to help with. The ViperTQS has a rotary dial for the HDG control. This emits keypresses only and only one per "click" of the dial. That makes moving the HDG on the HSI incredibly slow. It would be wonderful if somehow DCS could detect the difference between slow turning and faster/rapid turning of the control and act accordingly. If this could be made generic so that it is not just for the ViperTQS, it would be useful for people using mini-keypads that incorporate dials that behave in the same manner. I have one of these mini-keypads that I am experimenting with to provide CRS, HDG and HMCS control. If there is a better place to raise this request, please could you point me in the right direction?

My point is that QVFR may not be necessary. I'd certainly welcome full-screen clarity and losing the minor pitfalls of QVFR if Vulkan helps our systems step up to the mark.

Yes. Here: https://discord.com/channels/933220354401398785/957312128728047626/1178261832545341540

Are you sure? It's not on the list of services on my machine.

Feel free. I'm happy to help where I can. Thrustmaster contacted me about a collaboration last Friday but haven't heard from them since.

If as you say your CPU, memory etc is top of the line you should be getting 72fps with all settings maxed out, perhaps bar shadows. You don't say what your testing method is, i.e. theatre, single or multiplayer, low over cities, or even what aircraft you are flying. That kind of information will help a bit. However, I can say I can achieve 72fps (mostly) low, fast high g turns over towns in Caucuses. Persian Gulf same scenario, no. Sinai, hell no! I am using a plethora of tools to reach this though. For example, I am using quad-view foveated rendering and FOV set to 0.85. I am using a Quest Pro. A few things to consider. Is the motherboard set to XMP for the memory? Have you forced ASW on? This will force the fps to be always half the frame rate. If you have forced it on, set it back Auto. Are you overclocking your CPU? If so, could it be thermal throttling and therefore causing it to actually run slower than you expect?

Update! DCS2Target has been rewritten to use the DCS "Hooks" method of accessing simulation data. What is the benefit of the "hooks" method? Hooks allows multiple mods or third-party scripts to run alongside each other without any interference. It's simply plug-and-play! Updated installation instructions and links to the new dcs2target.zip file in the first post. Be sure to remove the export.lua and associated DCS2TARGET lua files of the old release from your Saved Games Scripts folder before running DCS!

Many thanks indeed. Perhaps these tools will not be necessary in the future with improvements in technology such as Vulkan.

Two things... Are you using Oculus Link or Virtual Desktop? If Virtual Desktop, the OTT settings will have no effect as it only controls the settings for Oculus Link. You can test if the changes have taken place by loading the Oculus Debug Tool after making the changes in the OTT. You should see the same settings in the ODT. For example, change the FOV Multiplier to 0.85 for both horizontal and vertical and click save. That should immediately change the settings in Oculus. Now load up the Oculus Debug Tool and you should see the same values in the FOV-Tangent Multiplier section. If no changes are seen in the ODT, then try changing them in the ODT and see if it takes effect in the headset. If that works, try running the OTT as administrator as it may not have the right privileges to make changes to the registry.

Sounds good. I've not gone back to VD since VXDR was first released. With the latest v60 PTC on Oculus the sound glitches have gone so I'm a very happy chappie now.

Per eye? Ok. I thought it was the render resolution of the image. Surely per eye is the image render resolution anyway. The whole image has to be rendered per eye. Nothing can really explain why the text in the MFD is blurry/fuzzy with VD and not with Link other than render resolution. Unless there is a sharpening setting somewhere. As far as stability goes, I can't say that I have noticed any new stability issues with the latest DCS patch and Link. But we all use DCS differently I guess.

Ok. Let's go back a few steps. When you say Virtual Desktop, do you mean the app from here: Home | Virtual Desktop (vrdesktop.net). If not, what exactly do you mean? Pictures would really help.

Ok. I caved in and switched over to the PTC. V60, the audio glitches/dropouts are gone. Five flights, no glitches, just sublime. Thanks for informing us! Let's just hope that Meta doesn't break it on the next release! Oh, yeah. Running default settings in ODT.

Yeah, it does sound like he is using foveated rendering either via quad-view foveated rendering of the foveated rendering in openxr toolkit. If either, simple test is to disable them and see if it goes away. Then if he wants to use FR for extra fps gain, play about with the settings in line with the instructions on the relevant wikipages.

Revert to default. Messing in the ODT generally makes matters worse I found.

It would help if you told us more about your VR configuration. Are you using OpenXR Tookit and/or the quad-view foveated rendering tool? If you, what settings have you configured in these or other tools?

Update! The backlight of the Warthog HOTAS for the A-10C and A-10C II can now be controlled from the Console Lighting dial in the A-10C / A-10C II cockpit. It realistically mimics the state of the electric system in that either the APU must be running at 100% RPM along with the APU GEN PWR set to the on position or the left engine must be at 50% RPM or higher. Be aware that the Warthog throttle has only six levels of intensity with level 0 being off. I will endeavour to add the same functionality to the FA-18 Hornet in due course. The updated files are linked in the first post. Enjoy!

Sweet! The F-18 is currently supported on the Warthog only. I didn't intend to export F-18 data to the Viper Mission Pack / Panel as, well, it's not a Viper which is a single-engine aircraft. The Warthog is better suited for the F-18. Similarly for the F-15. I could be persuaded if there is enough interest. Ideally, it would be nice if Thrustmaster produced F-18 and F-15 specific throttles. Better still, a generic twin-engine throttle which has interchangeable throttle handles just as they did for the interchangeable F-16 and F-18 stick grips.

@yosson76, @Upload4u My apologies. There were two bugs and I fixed just one. Please try this export.lua file. Don't forget to provide your dcs.log file if you have any further problems. Export.lua

Can you also try this export.lua file, please? Export.lua

Try this, please. Export.lua

The line with "Error: (internal)" is a fault between TARGET and the device. That's not something I have caused or can fix. It is an internal TARGET fault. Which version of the TARGET script editor have you installed? You may find using the latest version solves your problem. It should be v3.0.23.1003.

If you want me to investigate, I need the DCS.log and the target console output. Select all the text in the console with your mouse, paste it into a text file and send that.