Despayre

I don't think so, I believe you can only add smoke pods on 8A and 1A, but you do have various colour options (blue, green, orange, red, white, yellow).

Or some hardware isn't calibrated, and doesn't know it's at zero. You may need to add a dead zone to that hat.

I seem to recall reading that they were quickly welded closed by most units, they created more work than the advantages they provided.

Just the export.lua. It's the only one that's got those lines in it.

On my system, the export.lua path is c:\users\[username_here]\Saved Games\ DCS.openbeta\Scripts\export.lua So, inside the tree of your saved games folder And the 2 lines you're looking to move to the end are: local wwtlfs=require('lfs') dofile(wwtlfs.writedir()..'Scripts/wwt/wwtExport.lua') *Always make a backup before following instructions from some internet rando!

I'll be home in about 5 hrs, will update you if someone else doesn't come along before I get back (don't wanna give you the wrong path from memory).

I've found that unless I move the Winwing lines in the export.lua file to the end, Simapp doesn't seem to be able to talk to DCS, regardless of the Simapp setting to do so (I'm assuming you've already told it to sync with DCS via that Simapp setting). Once I did that, I was able to sync my throttle lighting to in-game, and the downloaded profiles for the shaker started working for me. (there's also an option in SimApp to turn off the editing of the LUA file, which you should do once it's working, otherwise, every time you start up SimApp, it puts the Winwing lines at the top again, and then it doesn't work again.)

That story isn't great, however... That looks like it might be easily fixed in 1 of 3 ways pretty quickly/easily: 1) You could slide up your idle detent to cover that gap, and adjust your throttle throw appropriately (I'm not crazy about reducing the throttle track, but it'd work). 2) You might even be able to crazy glue that, looks like it separated at a seam in the plastic, pretty clean break. 3) You can likely find the files, and have someone local 3D print you a replacement, probably cost you 10 bucks. I get that the thrust of this post wasn't about possible solutions, and more about how unimpressed you are with Winwing's responses, and that's reasonably valid, but at the end of the day, this still looks like a pretty minor fix that I don't know I would have called Winwing for in the first place (except to maybe call and ask how much for that specific rail to be mailed to me, and yes, $25.00 feels like a bit of a gouge, agreed).

I've landed, and taken off from the carrier. I wouldn't call it carrier "compatible", so much as carrier-possible. nullnull

I still run mine from the original .openbeta folder, and everything works fine. I am completely up to date.

Can you give us a specific loadout you're having trouble with? I haven't noticed that problem myself.

Nicely summed up. In short, yes, loading time could be shortened, and that's about it for benefits, but really, it's a bottleneck issue (as it always is with PC's), and I'm not sure I'd buy a new drive to get loading times down from 2 mins to even 1 minute, a couple times a day, rather than put that money aside and start my "gaming PC fund" instead. In real life terms, that extra minute feels a little pricey for a short-term fix (unless you meant it's 2 mins to load into missions [not the game itself], then, maaaybe), but given the vast majority of time in DCS is actually flying, and as noted above, this will do nothing for your FPS, I'm not sure the juice is worth the squeeze, so to speak.

Did not work for me, tried that, all GBU's. When getting in the plane, the laser code is always set to "4294967295"until I open the re-arming menu on the ground and reset all codes to 1688 in-mission.

For me, I also found that I had to move the Winwing lines in the LUA file to the end, otherwise, no linked lighting, and no shaker effects. Also, not clear what you mean about the Throttle. I have the Orion2, my throttle does not have any force feedback effects that I'm aware of, only the joystick does. Is there an Orion2 Throttle with FFB?

I've said before, it would be great if every time we got a new map, there were some basic updates to the instant action missions to have at least these basics available. Seems a little crazy to have a few 1000 users go into the ME and do the exact same thing to set them up, instead of one person taking 45 mins and including them with any new-map-shipping update (or the following release).

If it's making copies, that means you already have a version in the download folder, doesn't it? Although, with that icon, that makes me think you're accidentally downloading the entire page, not just the file. Top right, green button that says "<> Code", click on that, choose the last option, "Download ZIP", and that should do it. Or, you can just just click directly on this link to it. https://github.com/enertial/streamdeck-dcs-interface/archive/refs/heads/master.zip

Ok, here's what reliably works for me as a workaround. 1. Before leaving the ground, open the re-arm menu, and use the fuse menu there to copy 1688 to all of the same type 2. Wait for the rearm to be done before doing anything else 3. Once in the air, switch to A/G mode and wait for the pod to warm up, when he starts playing with the laser code jump in the back and manually set them to 688 and they will stay, I usually flip the stations on since I'm back there anyway, but Jester can do it too

A USB Controller can handle 127 devices each, but a daisy chain of only 5 hubs, as it's a maximum of 7 tiers in the USB spec (devices above and below any given hub make up the other 2 tiers). Ergo, use bigger hubs if you need to, the USB spec itself is not holding you back.

It seems to be laser code related. I just jumped into the Instant Action mission, Marianas, Clay Dagger, went to the kneepad, and it shows all my laser codes as "4294967295"... something tells me, that's not right. Also, I tried editing the mission, swapping out for other GBU's, didn't help, resetting the laser codes using the arming menu, did seem to solve the problem though.

I wouldn't be overly surprised to find out that something built 10 years later, has some improvements over the older plane. However, given that, I'll stick with the Tomcat... turns out, it's not the plane, it's the pilot.

Telephone poles aren't often noted for their nimbleness (and it WAS designed to hit bombers [at long range]!).

Since the previous update, most of the time, Jester just sits back there flipping the laser code's second number, and won't even lock targets. If I eventually manage to lock something, it always misses. Pretty disappointed there's no fix in this latest update.

Above my pay grade.

Also had the same problem yesterday, played a mission I've played many times before from the Instant Action menu (Marianas, Clay Dagger in the Dark), could see the laser code cycling, and Jester would not respond to any targeting commands.

I think you're looking for "Heading Hold GT" (GT = ground track), and good news, it already exists!