Nightdare

Hey there @Szketya95 Mind me asking what the physical dimensions are for the ARC159 and 182?

An old Logitech G940 also isn't actually suited to be 'sitting' on a desktop either Not unless you want to anchor it down with 4 big screws, that thing would go all over the place, or you'd be fighting the FFB AND trying to keep it in place with 1 hand

seeing the slew of products the are gonna release, I'd say they got their hands full

The buttons most probably ...the screen otoh,... don't believe so

I don't think this is still relevant after almost 8 years

But my 5070 is just as powerful as a 4090!!!!1!!!

Like I said, there is also a concern our 'toy' grips won't hold up to these forces (over time), linear force, maybe, but any rattling FFB effects would be hammering the connector And I wouldn't be surprised a lot of people would dial the force down, I remember flying spitifre with my G940 wasn't so much fun after 2 hours

60Nm? We're gonna be seeing people come with posts about cracked grips Edit: I do love that extended roll axis design, though a little less applicable to helicopters

Found the RIO lights also translating when in the pilot seat Set my TWS Auto/RWS to A/A, A/G on my Orion2 with that

That's about $/€ 200 for the unit, $/€ 65ish shipping (no tax)?

Seems I didn't pay attention earlier, or it has been implemented recently Making your Switch box mockup (and able to add the result directly to cart): Builder – Switchology

I guess the somersaulting, cartwheeling and pirouetting deck crew from Hot Shots will forever remain a dream

Seeing no such warning I'm guessing you're using something else than Windows defender?

They teased an auto throttle-equiped Taurus a year ago, but I'm guessing that's too niche for most planes The Taurus IMO seems to have been the eye catcher for WW to get the ball rolling, I don't know their marketing if they are willing to invest in another as a prestige product

Ok, let's break that down: Moza said other grips don't work,...but they do ...the horror, the shame, , rivers of blood, , cats and dogs living together,...the non-news most people already know is incorrect, including you And here you are screaming "look what they did to me, these CONMEN! How dare they!" as if some great tragedy has struck you, that -of course, will engulf the entire world and you, our saviour have warned us of this terrible future All because a company with the main focus on sim racing, apparently has an employee that isn't up to speed handling the customer service desk How could we venture the assumption this employee isn't informed? Because their own software does support other brand grips So, conclusion: Someone appears to be in error All you are trying to do is create unnecessary drama over nothing Sure,... could be Moza does decide to retract their plan for open support, but currently, there is neither an official statement, nor has the functionality been taken out of their software We'll start the drama when they won't support Virpil's VFX grip

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