slughead

I would try to uninstall and reinstall the OpenXR Toolkit and also disable/uninstall any other OpenXR mods such as QVFR and see if that helps. If you are using QVFR with OpenXR Toolkit, you should only use turbo mode in QVFR and not in OpenXR Toolkit as that can cause a crash if I remember correctly. It’s all explained in the QVFR and OpenXR Toolkit wiki.

No cable is certainly a good thing. How do you manage battery life without a cable? Are you using an external battery pack? I found when I tried out VD that as it used wifi it drained the battery much faster even with a cable attached for power. I should try it again for kicks to see if it has improved since the last time I used it although the recent v60 update from Oculus has fixed the audio glitches so at the moment I have no real need to switch.

I bought it and stopped using it. It crumples up fingers and it’s incredibly difficult to flip any switches with it.

Overloaded with help/support requests taking up too much of his life balance. He now focuses on VxDR (?) that’s part of virtual desktop. To be fair, he left his tools in a good state that shouldn’t need further work and so people should be able to “self-help” themselves with all the information and wiki notes that are available.

Sile is correct. You don’t notice any degradation of quality because the resolution is massively lowered in your peripheral vision where you can’t see sharply. The massive drop in resolution means less work for the game and less for the GPU which results in large fps gains. In the focus region, you increase the render resolution to boost clarity. The focus region is quite small and so does not have a huge impact on fps. I find the conjecture from people who haven’t tried this laughable. If you’ve not tried it, how can anyone give any credence to your “opinion”.

Deprecation usually means to be replaced with something entirely new. Therefore, the old tools\libaries\modules etc would be removed and/or further development ceased to concentrate on the newer technology.

In that case you'll need to take it up with Thrustmaster Support as this occurs during their initialisation code. Good luck! I found them to be as useful as a chocolate teapot.

It should be V23 for the throttle.

That's a Thrustmaster issue. Have you got the latest firmware installed in your throttle?

Make sure you have the latest version of the Thrustmaster T.A.R.G.E.T. software installed.

It's not your TARGET mappings that I need but actual cockpit screenshots. Nonetheless, as I don't have any of those modules, I can't code for them as I need to inspect the module's lua scripts to read the cockpit data from DCS. You're welcome to take my scripts and adapt them to your needs.

Can you provide screenshots to show what you mean? They say that a picture tells more than a thousand words. Ideally, draw on the screenshot to show the indicator in the cockpit.

What indicators, other than landing gear, would you display on the ViperTQS and for which aircraft?

Not that I know of.

Thanks for the medal! I cannot influence that as there is no means in the TARGET API to control the light intensity of the Viper TQS.

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?