Nightdare

Well I would think in the WWT/Aircraft folder/ufcPatchHuey.lua it would be defined by math.floor(MainPanel:get_argument_value(124) Then one would need to copy/past and edit a 'section' with however the syntaxes would work My guess at first was: --Torquex????x local Torquex????x= { math.floor(MainPanel:get_argument_value(124) } local Torquex????x = "" for index, value in ipairs(Torquex????x) do local Torquex????xToAppend = value end where "x????x" has either a 'string' or 'digit name', depending on the line You'd also need to change option4 = "UH1H" Changing "UHU1" into Torquex????x (...digit or ...string)as source But since I didn't even get an error, but zero change from the normal lua, it was evident I mucked it up, and missing the skill to debug the error

Jar 72, care to share what wheeled pots/encoders that are and maybe a pic from the underside on how you have them mounted?

If it's F/A, it technically is not an equivalent to the Tomcat It's why the whole VFX program was set up, to get the ultimate in fighter fleet defense in which the F-111 (which technically was an F/A plane) didn't suffice It's attacker role 20 years after the fact was merely an attempt to keep the plane in service longer, but as an F/A it was inferior to many of its contemporaries

WOW!! ...they can't even program a reliable seat motor

Well, at least 1 -A did in 1995

Well, technically, you're posting in the wrong section this subforum has more traffic on the subject: And I believe there are some more threads on the subject there

I get 150-ish with my 4080s in Mariana's without DLSS in pancake mode I'll get about half that if I load at the same setting in Beer goggles Like @jnr4817 stated, Monitor is not comparable to VR, though I'll add that you don't need an 8K headset to see severely diminished FPS

It is addressable as per @wwWolfcom screenshot

Been trying to wrap my head around the code the past night, diving into whatever DCS profiles I can find What seems to be the source for torque pressure in the UH-1H is (124) Now I tried to copy an element and switch things in the code to get it to work but alas, I still see "UH1H" in window 4, guess my programming skills never did exceed Virtual cockpit

What would be great would be a kind of DCS bios aimed at Winwing hardware The instructions for WW are fixed on F-18 commands, it would need something that can convert like whatever signal a "gears up" is from DCS to the "Gear up F-18" command for WW (Of course it would be even better if WW just changed their firmware to understand DCS Bios commands)

I installed it for fun just to try it out (since I'm in VR) and found it 'spoofing' the F-14 on the UFC just fine with the (probably) general profile It shows vertical indicator, heading, speed, altitude, remaining fuel in minutes, flares, chaff But (since I have all lights on in Simapp) On the PTO2 it lose the lights for Landing gear, Jet. ordinance, flaps, caution and hook On the Orion2 it loses the AG/AA lights I wonder what/how Simapp exports the data to the other Winwing peripherals

On pancake? yes Beer goggles asks a lot more from the hardware

First off, loading into a map usually kills FPS for a moment, but shouldn't do so for more than a minute what you can check for now, is increasing your virtual memory (page/swap file), 32gb isn't a lot for VR, if that stops/diminishes the stuttering you may have found your problem I also noticed after Nvidia 572.16 some more stuttering than usual with my specs, see what happens with the prior driver

Hm, but isn't a 12v that comes with a PSU ALSO a "1st party" cable? Imagine the pillar -> post Nividia: "Your connectors melted because you didn't use OUR Cable" PSU manufacturer "Your connectors melted because you didn't use OUR Cable"

Another funny detail ...why do we never see "user error" at the PSU side?

Installed this script, and I notice the Orion2 throttle and PTO2 also being addressed For example: the PTO shows 4 lighted pylons when I fly the Apache, just 1 when I fly the F-14

Forgot those settings were implemented (Got my throttle prior to this update)

On the other hand, it would force game coders to start programming and optimizing their games more efficiently Because this would be an admit to defeat to increase the performance of hardware for fidelity

It's the Firmware that so far kept me from getting the Moza, and since WW didn't change their firmware when they did have a TM/VPC adapter, I doubt they will now

But not compatible with TM/Virpil grips

That's what I was waiting for, now if only Virpil comes with news (but they are probably too busy with their yoke to get some FFB goodness out this year)

600W cable, GPU's pulling 630 watts consistently,... what could possibly go wrong?

For hardware that has a detent at 80%, yes Personally, I'm glad I have 1:1 translation, saves me a lot of reconfiguring curves for other modules It just strikes me as odd the AB value in control indicator for the F-14 does not translate 1:1 It would be more clear for setup if the AB lines correspond to where AB actually begins, that the physical axis needs to be virtually reconfigured where 80/20 physical, becomes 50/50 virtual

Yes, but not as an encoder One might need to change the settings of the button with the help of the "turbo" option, but I never delved that deep, so cannot claim this to be a workable method

I had these same ones the first time, apparently, they are not compatible with Bodnar boards, only with Arduino @ITR1102 To add, though i could be mistaken: it seems any basic encoder without PCB should work for Bodnars