Sl1ck

Hi guys, please see attached track file. 2 x GBU31 on same weapon station. 1st bomb flies high losing energy then becomes unpredictable. 2nd bomb flies DIRECT trajectory as programmed and as expected. 2 bombs on 2 different weapon stations fly DIRECT trajectory correctly. Regards PYLON ISSUE.trk

Hello all, Please see attached track files. Firstly NOSE/TAIL/N/T has no effect. Bomb always penetrates far too deep into the terrain and does not destroy ammunition depot. In comparison, same weapon dropped from F18/F16 destroys ammunition depot with 2 bombs. F15E does not. F15 GBU NOSE-TAIL FUZ NOT WORKING.trk F15 GBU NOSE FUZ NOT WORKING.trk F15 GBU TAIL FUZ NOT WORKING.trk

I'm in the same boat, Did a complete reformat of my drive, reinstalled everything. Still same issue. Performance far reduced from before the update. Frame times are rather spikey. Only solution I've found to allow me to play, is to turn down resolution multiplier in VR / reduce graphics settings :(((

Completely agree it's not straight forward. I'm lucky enough to get to fly through them on a regular basis. Certain cloud types don't generate much / any turbulence at all. thin, wispy stratus layers for example. However, certainly Cumulus / Cumulostratus / Cumulonimbus clouds do. Forgive me, I know nothing for coding, but a preset amount of turbulence per cloud type then biased against a slider perhaps would suffice. There is far more wrong with DCS than this, but just a suggestion that will make it more immersive.

Turbulence in clouds?

Thanks Harker, It's a bit daft that the default format in the TGP and waypoint system, is one the IAMS itself cannot accept..... Either default should change, or IAMS be updated. Thanks again

I'm pretty sure it's incorrect, lat and long should come up same way as weapon lat long

I've entered waypoints in the past. It doesn't work anymore, I press POSN and lat and long do not come up. Check my track file.

As per the title, After pressing POSN button, no LAT / LONG fields become available to enter data. Please see track file. Unable to enter edit waypoint LAT LONG via UFC .trk

Hi guys, TGP and waypoint data page use and show LLDM Coords: N 34 54 7745 for example, trying to enter this, with precise mode enabled into the TGT UFC field for a JDAM PP attack, does not work. UFC will only accept PLL coords, N 45 54 46.39 Please see track file Aircraft won't accept types of coordinates.trk

My original post has nothing to do with what you're talking about. Though there may also be a problem regarding target elevation, I'm not sure, it's a little more fundamental at this point. My scenario was M0.9, 35000ft, target at Sea level. Pretty straight forward situation. DLZ gives 18/19NM max range. Bomb never ever makes it. F16 Lasing and JTAC lasing the target the whole time. My question is, how and why is the DLZ saying to launch at 18/19NM if it can't achieve that, and if it is supposed to be able to make it, what's missing. Please see attached track files for the 10th time. GBU24 VS GBU12 JTAC + F16 LASE.trk

Absolutely agree to default to zero. But have more realistic options.

Attached is a realistic example of what you would expect to see happen in the real world. Wind is 10kts initially straight down the runway at Dubai RWY 30L/R 1600ft is greyed out annoyingly, the difference in wind direction between surface and 1600feet can be quite large. All numbers used are real basic averages from the charts mentioned previously. Of course in real life, atmospherics are incredibly dynamic. This certainly beats flying around in 0 wind. At least from a realism perspective. Wind example.trk

How is the GBU24 going to reach it's target at 19NM from 35000 M.9 which is the max range according to the DLZ programming, if it can't see the laser spot from the JTAC till 8nm away. GBU24 VS GBU12 JTAC + F16 LASE.trk