Nightdare

@prestonflying I was on recon in the files Trying to find things like jettison, landing gear, hook, flaps and master caution as these are buttons/lights represented in the F-14 as well as on the PTO2 (Too many hardpoints on the F-14 to represent on the station select buttons, nor do I use them for any weapon management)

Very noob question: How do I 'recognize' these arguments? I've been diving in my F-14 directory, since there is no "MainPanel" folder, looking around in various .Lua's, looking for something simple like the 'Jett' light and in draw_args.lua, I found numbers like: WARN_EmergJett = 15031 PILOT_JETT_Light = 701 WEAP_Emer_Jettison = 239

Send the files to your own email Either way, having a second drive is never a bad thing

Seems more like wishful thinking Comparing a 9070xt to a 5070ti while that can be overclocked as well, then thinking it will reach the next tier ...sure, maybe if that 5080 is missing rops

That should get you well on your way regarding most modules (as stand in, that O2 with EX grip will do great for flying apache as well)

IIRC the SR-71 'skimmed' the borders of Warsaw Pact nations to make pictures from distance and not actually fly over This why you never heard about 'continious invasion of airspace' from the Soviet aligned nations

Again, go for the one with the most buttons

Most probably this, DCS tends to assign existing key binds to new peripherals

Oooh, I thought you used wheel encoders, instead you simply mounted regular PCB mount encoders sideways Briliant!

I sincerely doubt that market is greater than the combat aircraft market

Using Voice Attack instead of VaiCom never gave me problems (since it's basically Keyboard commands)

Seems that the base has issues with different Virpil grips?

"A Small Batch"??? Looking back at their launch, basically that means almost the entire stock

The USMC became interested, but pulled out when they learned ground attack wouldn't be forthcoming

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