Shadow KT

I've been on DCS for so long that I wish that I was joking anytime I had to post anything on the forums... T-72B3 helicopter prototype.trk Do enough of the above and it eventually turns into an actual helicopter, especially in multiplayer. As soon as you use the laser rangefinder, the issues starts protrudings through the curtains

I believe this issue is also present on the T-72B3 It can even turn into a helicopter tank, like this: https://tenor.com/8kEK.gif

Seems like on some servers, the command to follow leader does not seem to work, although units are in a group and you are in the lead vehicle. Please investigate. DSMC_The Enguri Campaign-20250215-233834.trk

Hello, as the tittle says and the track shows.... The L118 has hit box issues, having rounds go through it and taking close to no splash damage, unless you hit directly beneath it with a HE shell. L118 Light Artillery Gun No Hit Box.trk

Try in the AI (Non-Combined Arms issues) part of the forums.

Then it would show less weight than the Checklist page, which as shown in the screenshots it did not. Also the answer by Vader in that post makes no sense to me... can someone elaborate? How does that work, is the checklist weight programmed, or is it an actual weight reading on the gear? If it's a sensor on the gear, how does it differentiate between pylons and actual "cargo", i.e. weapons? If the pylon is not part of the aircraft, then it's cargo as well.... what?

Seems like this classic of a bug from time past has returned. Loadout menu and Checklist weight/ ME (small difference between Checklist/ ME) do not match. Discrepency changes based on loadout and weapons used/ re-fueling (air). I've seen from +2K LBS to -3K LBS. I've attached quick few tracks that display the issue at its basic, by demonstrating the difference in weight on a hot start with different loadouts. In all the tracks, the checklist weight shows higher weight than the loadout screen, which is not that bad. The real trouble is when your checlist page shows a lower weight than your actual. Was flying an op (shoutout to CVW-69), had to hit the tanker on the way back, before recovery, emergency fuel state (Was down to 1200LBS). Fueled up 35000 LBS indicated on the Checklist page. This put me at around 6K LBS fuel, which did make me rise an eyebrow for a moment, but checklist shows we are at 35000 LBS (will burn at least 1K by the time I get to the deck; CASE III), so we should be good. Well, ended up with a bent gear on landing, thankfully I trapped first try. I was rather surpsied that I damaged the gear, taking into consideration that this is a Hornet we are talking about, made to land on carrier, random failure must be was my first thought, even shut down the jet... Then again... started the right engine just to check: Checklist page shows 33.8K with 5.4K internal, two fuel tanks and a HARM on the jet..... Yeah, it is not adding up. Opened up the fuel rearming panel, which shows your current fuel level percentage, removed what was not on the jet from the starting loadout and the weight indicated near 3K above, what the checlist was showing. Reduced the fuel until I matched what was currently on the checklist page hit rearm and sure enough, crew started taking off fuel. Ended up with 2.4K fuel to match the previously shown checklist weight and as suspected the checlist page now showed 30.9K: Weight 1.trk Weight 2.trk Weight 3.trk Weight 4.trk

TrackIR and more practical camera/walking controls for AirBoss and LSO stations, pretty please

Would be a must, if you ask me. Way too bright, especially during night ops.

Its an age old .... gimmick might be the correct word here, that's present on most tanks. Game has a set max range for AP rounds - usually around 3200meters for most MBTs (2500m for M60). The Abrams also used to be a victim of this gimmick, but it got quietly fixed. The Chinese MBT, subsequently, as an Abrams copy, within DCS, also works similarly to the abrams. There was a thread about this somewhere, with the typical answer of... ugh, do you have proof, that the FCS can actually calculate for such a range, hurrr durr. I am sure the Challenger 1 which hit a T-55 from 5000meters was actually just blind luck and kentuchy windage, the gunner probably visually aimed the gun by looking out the hatch.

Ah, I thouhg I was going crazy, as I can swear that last week, the advisory showed, now it doesn't.

Has been like this forever unfortunatelu. Bind a button to "Change cursor mode" and cycle it once you enter isometric view. Should give control back to your pad. That said, you need to do it every time you change view. In my opinion, it is not worth it. Just use mouse and keyboard and change aiming modes for the FCS to work.

Can't call something broken, when it never existed. T-72B3 came this way, when it was introduced into DCS... so it was a design choice, not a bug.

Although, I've seen it happen once on the Caucasus, I cannot seem to reproduce it. That said, I can reproduce it 100% on Syria. Is this not reportable, because it happens on a map different from the Caucasus?

Some sort of a variation is still going on. Seems like ROE is playing an effect on what is happening when changing states. In Spot ROE.trk you can observe how if ROE is set to HOLD, and as an example you go from RED to GREEN, dishes will stop spinning, but the target will remain visible on the map and vice versa. I have not tested what is seen from a pilot's perspective (RWR). @Flappie Spot No Radar 2.trk Spot No Radar.trk No Spot Rada On.trk