slughead

Update! Added missing logic for the right engine of the A-10C/A-10C2 and F/A-18C Hornet and generator switches. Ground power logic is not yet available for the F/A-18C. This may not be possible as I am unable to find any data exposed by the simulation that indicates ground power is on or off. Updated files are in the first post. Only the dcs2target.zip has been updated.

Context: I am writing a tool that exports simulation data to a Thrustmaster Warthog HOTAS throttle controller. Amongst other things, it can control the backlight brightness of the Warthog in response to the F/A-18C "consoles" dial. I would like to know how to determine via lua scripting whether "ground power" is on or off. Thus when it is on, and by checking other simulation data, whether or not to illuminate the Warthog backlight. So far I have not been able to find anything to indicate this state.

Sounds like some change made in the ODT or OTT might be the cause. I leave everything at default other than the FOV. I have seen zero benefits of changes above default settings.

Update! Added backlight control of the Warthog HOTAS via the F/A-18C Hornet "Consoles" lighting dial. It realistically mimics the state of the electric system in that the left engine must be at 60% RPM or higher. Right engine logic will be added soon. Be aware that the Warthog throttle has only six levels of intensity with level 0 being off. Also, the user-programmable LEDs (currently used to indicate the speed brake position), will not illuminate if the Consoles dial is set to off. This is a limitation of the Warthog. The updated files are linked in the first post. Enjoy!

Yeah, there were a few hotfixes for v59 issued. They never tell you what they fixed though.

Maverick’s helmet on Top Gun…. It’s not Maverick…. It’s Mave and Rick. Now you’ve seen it, you’ll never unsee it null

How have you got v60 if you are not on the PTC? It hasn't been released other than via the PTC.

You can always disable your enrolment of the PTC but you will be stuck with the PTC version until the stable version is released.

Ok. So between now and Monday, I am "in between jobs". So if anyone has any suggestions for the other LEDs on the ViperTQS.... I'm all ears! Warp factor gauge?

DCS isn't aware of VD. It's just OpenXR as far as it is concerned. Have you tried restarting the Oculus service or rebooting the machine?

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.