Vanguard

The issue we are facing is we have multiple years worth of tech and they don't suit each other. If your mission is old school with Tunkustas and Osa's, then the D is fine. When you add more modern units, say a Tor, you need a more modern weapon, like an L. The F K and L variants not only have larger warheads, they have larger standoff range as well. They're all meant to go hand in hand with each other. I'm a big fan of the new historic mode, but from I can see thus far, it's only for units, not the weapons they can carry. It's no different than flying a modern hornet with AMRAAMs against a 40 year old jet armed with SAHR missles... if you're using SLAMs against a Tunkuska for example, well, it's just unfair haha. Also, the L won't lock on to all the telephone poles ;)

I had a similar issue once. Rebooted, deleted the offending file manually and ran update and it was fine.

Stuff... literally. Whatever the pilot wants to shove under there, maps, charts, dashboard bobblehead, whatever

I see the code for it on line 5315: https://github.com/ciribob/DCS-CTLD/blob/master/CTLD.lua and in CTLD_TTI_SP_NEW.lua so I thought it should be working.

In before "here we go again" :megalol: Sorry, couldn't help myself.

Hey deadlyfishes, all of the AAA and SAM units are marked with hpriority and priority, but the JTAC never seems to get select them first, in fact, I've never seen them selected first. Had a look through the code, nothing obviously wrong. Have you/any else seen this?

Whenever I play DCS on MP, with TTI map for example, when we drop off a sling loaded cargo, it ends up suspended in the air about 100ft. I can't find a bug report, just many complaints around sling load in MP. Is this still an issue for everyone, or has the world just gone CTLD and thrown their hands in the air?

I don't know about "shortcoming", but it is a decision by the game dev to support UPNP or not, many do, and my understand is DCS does as well: According to: https://www.digitalcombatsimulator.com/en/support/faq/server/ Perhaps it's no longer the case? Some feel it's a security issue. Given you can disable UPNP in your router, I don't see why a game dev needs to make that decision for you but... whatevs

Depends on the netcode. While your CPU is offloaded, you are at the mercy of the server's CPU if the client is waiting on sync events before displaying frames. May not happen for certain frames or any depending on the netcode. For games that don't sync, you'll see a lot of "rubber banding", as the client continues to propagate AI down the vector they were on, then they snap over to where they are supposed to be when the info is received from the server. I've never witnessed too much rubber banding per say in DCS, more of a stutter, noticeable when trying to AAR in MP, which would lead me to lean towards a more synchronous netcode.

Yup, something is up, I couldn't find the gun sight last night either. Next time I witness it I'll save a track.

Something feels wrong for sure. The hud moves up and down a lot and I really have to "chin up" to see the SPI. Tried fixing it by looking down a bit when I re-center. Would be nice not to have to.

-1 Every rotary/dial is turn right to on, left to off. Switched, right up/on, left down/off. Push buttons... well, they toggle and should work with both left and right click, there is no obvious on/off with a toggle.

Sounds extreme and first reported case, so, first question, have you tried repair, second question , do you have any mods installed.

Inverter switch... Right click from ON position goes to OFF. Left click bounces down to the test position. I think right click should do nothing, and left click from just bring it down one notch to OFF, not all the way to test.

Hi Folks, In GBU-54 DSMS Profile, under change set, you can specify a target for the GBU-54. I entered the name of one of my WP, and it showed up and accepted it by the WP number. Save... Now what? All HUD indications are based on my current SPI in the HUD, no indication for the one programmed in the profile. Anyone know how it woks? Can't see a mention in the doc either.

+1. Any manual seat/head adjustment throws the HUD off which is annoying. Before it just meant looing around the corner for the steerpoint/tgp cues, but now with the GBU-54 release cue along the left edge, manual adjustments are impossible. Can't imagine the real plane works this way. I understand complaints from IRL pilots that some things were off the edge, but are you telling me if a 5'8" pilot and a 6'2" pilot get in the plane, they have a complete advantage/disadvantage over each other because it affects how much of the hud they can see??

I noticed the same, GBU-54 release was always within 3.5 miles, I didn't try the 38.

On my first load, with a TM Warthog I had to goto Joystick config and reset the category to default. My coolie down was unmapped and coolie up was mapped down.

Left/Right click behavior Not sure if this is a bug or wishlist... I'm happy the left/right click behavior has been standardized in this module but, can we prevent rollover? I want to spam right click on a switch and not have it flip down to the bottom position. Just like my fingers would feel for it and push it up in case it's not up. Sometimes it's deceptive based on perception if a toggle is in the middle or up position. Its brutal to have the system power off when you're just trying to ensure it's on.

Manual page 319 states DMS Long Left for sharing SPI. Should be updated to TMS Long Left.

Funny how the F-18 wants to always boresight (having to undesignate) for most things, and now the A-10 doesn't want to *facepalm*

Party Time :pilotfly:

Slowest 190MB download ever... hamster is running hard. Edit: Another 1.3GB for the aircraft itself BTW.

Patch notes are out: https://www.digitalcombatsimulator.com/en/news/changelog/ 30th Sept: DCS 2.5.6.55743 Open Beta Introduced new module: DCS: A-10C II Tank Killer by ED

You mean that's missing from V1, or this functionality should also be added to the block modeled V2? Maybe I just missed it, but in the current implementation EPLRS X's are currently shown in the TGP, donor SPIs are not, correct? Should they always have been and also will/should they be in V2?