Nightdare

Take a breath and count to 10 Perhaps read other's posts as well: I know this doesn't support what Moza told you, but since the contrary evidence is a GOOD thing, you're really trying too hard to paint Moza as some kind of "Big Bad Corpo Entity" Your kind of hyperbole really is what's wrong in today's social media

Well, this is for the most standard F-14 indicators Made "Center"-station the NWS Engage indicator, all 4 others are added to the backlighting The only thing I'm wondering ATM is if adding Orion2 throttle was necessary, as my MFDs and UFC/HUD work with the console lights when SimApp sync option was selected as well aircraft_name: ['F-14B', 'F-14A-135-GR'], isResetLight: true, recv: [ // F-14B { // PTO2 BACKLIGHTING dcs_id: '0.1801', process: (dcs_id, dcsmag) => { // 临时作为反向处理 // Temporary as reverse processing dcsmag = 1 - dcsmag; return dcsmag; }, device_name: 0, led: ['Backlight', 'INST_PNL_Backlight', 'LI', 'RI', 'LO', 'RO', 'Orion_Throttle_Base_II'] }, { // 起落架指示灯 // Landing Gear Indicator // 目前暂时将起落架指示灯映射为起落架手柄灯 // Currently, the landing gear indicator is temporarily mapped to the landing gear handle light dcs_id: '0.15001', device_name: ['F18_TAKEOFF_PANEL', 'TAKEOFF_PLANEL_2'], led: ['Landing_gear_lights'] }, { // JETT dcs_id: '0.15031', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['JETT'] }, { // Master_Caution dcs_id: '0.9200', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['Master_Caution'] }, { // HOOK dcs_id: '0.15090', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['HOOK'] }, { // FLAPS dcs_id: '0.15046', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['FLAPS'] }, { // LEFT GEAR dcs_id: '0.8302', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['LEFT'] }, { // NOSE GEAR dcs_id: '0.8301', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['NOSE'] }, { // RIGHT GEAR dcs_id: '0.8305', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['RIGHT'] }, { // HALF SPEEDBRAKE dcs_id: '0.8307', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['HALF'] }, { // FULL SPEEDBRAKE dcs_id: '0.8308', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['FULL'] }, { // NWS ENGAGE dcs_id: '0.9353', device_name: ['F18_COMBAT_READY_PANEL', 'TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['CTR'] }, ] },

You probably need to add plane names and component values/addresses of the lights/functions But DCS Bios isn't my forté Have a look in this post from @Invictus84 Where he posted a few github links where you can find most component names and values of most modules And in case you were unaware It's also possible to get (limited) data of other planes on your UFC Check this thread for more info

@prestonflying Got that working Though I think I did find the error in my code,... a comma missing after the "hook" section The only thing now is that I have 2 error codes 0x0012, 0x0013 in environment, but that may be due to WWT, after resetting the Simapp data, since I can't see any data on my UFC anymore

Keep in mind using buttons you might need for modules, yet are using for other functions, might give some issues with muscle memory I tend to have to 'adjust' to the reverse movement of my Orion 2 when switching from plane to helo and back again after flying helo's a while ...and yes, in panic situations this will at times have the wrong results

Seems I have the initial trouble of module ID I tried "F-14A-135-GR" / "F-14" / "F14" / "F-14B" / "F14" / "HEATBLUR_F-14" Same Could be I removed some [] or {} This is what I tried out module.exports = [{ // Receive signals from multiple aircraft aircraft_name: ['F-14B', 'F-14A-135-GR'], isResetLight: true, recv: [ // Bind the device id of the DCS to the lighting of the physical device { // Landing gear lights dcs_id: '0.15001', device_name: ['F18_TAKEOFF_PANEL', 'TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['Landing_gear_lights'] }, { // FLAPS dcs_id: '0.15046', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['FLAPS'] }, { // HALF dcs_id: '0.9205', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['HALF'] }, { // FULL dcs_id: '0.9204', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['FULL'] }, { // LEFT dcs_id: '0.8302', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['LEFT'] }, { // NOSE dcs_id: '0.8301', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['NOSE'] }, { // RIGHT dcs_id: '0.8305', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['RIGHT'] }, { // JETT dcs_id: '0.15031', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['JETT'] }, { // Master_Caution dcs_id: '0.9200', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['Master_Caution'] }, { // HOOK dcs_id: '0.15090', device_name: ['TAKEOFF_PLANEL_2'], // Multiple device names. 0: means all devices led: ['HOOK'] } ] }, ];

Seems a case of uninformed customer service employee instead of company fraud ...but I guess that doesn't create half as interesting posts

You can tilt the units somewhat on the clamps

You are forgetting the very costly yet low performing 5080 This isn't the 'high end' it's the last regular consumer card, AND a performance AMD may be able to match, if not undercut at slightly lower (Mostly RT) performance at a MUCH better price

Just imagine that 4090 performance, that's just as good the same thing

Well, concerning the new gen, unless AMD puts up a very good 9000 XTX, I'm not having any buyers remorse for getting the 4080 super late in the lifespan (especially compared to 5070ti and 5080) IMO (heavy) RT still is a problem for mid-tier, even for Nidia, making it a somewhat wasted feature, so AMD focusing on raw power works to their advantage I'd say, nice effort of AMD

@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