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

That's understood, So with the Bomb not able to see the laser beyond 8nm and the requirement to designate immediately after release, where and how do we use the bomb when the DLZ is giving us a max range of 18/19NM? Are we missing something? Regards

Look at my track files. tried using a local JTAC that Auto-lased the target. As well as my ownship + JTAC Still did not work from max range in the DLZ. It's as if laser spot can't be seen from so far away by the bomb, OR the autopilot part is not working properly. If based on the documentation you have, the DLZ is correct, then how is the bomb intended to be used at max range, given our ownship lasing distance limit? As mentioned before I tried a JTAC that lased the target continuously, but the bomb was still not able to make it to target. Please see track files uploaded previously.

Thanks for your video contribution. My track files show a similar story. In future I will make a video, I don't think people actually bother to watch track files. I could get a splash from just over 15NM but the bomb is very much heading into the ocean before grabbing the laser at the very last moment and pitching up to glide in very slowly at low level to the target, as opposed to a more optimal / normal trajectory.

Show me Dear NineLine, Please see attached track files. Given the previous replies regarding the maximum distance of the laser, I figured I'd try a JTAC Lasing the target for me. Again the GBU24 has no hope at the max distance, the GBU 12 behaves as expected as a baseline. (unless the bomb itself has a maximum distance it can see the laser) but then again how can it hope to achieve 18+NM in either case. Tried JTAC ONLY and both F16 + JTAC Lasing. Unless there are new features coming to the GBU24 to making it somehow glide further before homing in on the beacon, then I don't quite understand the use of the DLZ. GBU24 VS GBU12 JTAC ONLY + F16 LASE.trk GBU24 VS GBU12 JTAC ONLY.trk

Chaps, Watch the attached track file. My aircraft is stationary at 15NM and the GBU makes it all that way. And there is no other laser source. My problem isn't regarding lasers, if there is a limit then so be it, though it doesn't seem like there is. My problem is that the F16 reckons you could get a GBU24 to a target at 18+NM according to the DLZ at 35000 and 0.9M, Therefore there is something not right in the coding. GBU24 15NM.trk

Good day all, After having implemented moving clouds (which are fantastic by the way) I realised they do not move unless of course there is wind. It then dawned on me that most of my experience in DCS is without wind. At best some servers / mission makers add some surface wind but the upper atmosphere winds are often left at 0 as is the default in the mission editor. Due to Coriolis effect and Surface friction, In the Northern hemisphere a surface wind of 5kts from the North would equate (on average) to the wind at 18000 feet being 44kts from the East and continue to increase in strength the further up you go. Less so in direction as above 18000 feet (on average) we are in free moving air. "Southern hemisphere would be 44kts from the west" My suggestion would be that even with 0 wind on the surface or 1kt from the North, that some wind be in as a default in the upper levels Exactly as MSFS does. A good feature would be that when a surface wind is entered that the remaining higher levels are auto-populated in accordance with known averages in meteorology. Of course in the real world there are many more variables, but we can start with International standard atmosphere and averages. Also not sure how the weapons would cope, and if DLZ's and CCRP's etc would continue to be accurate. Regards

That doesn't explain the issue regarding the DLZ giving a max range cue at 18+NM That also doesn't explain how with my aircraft stationary at 15nm the bomb made the target.

Track files attached F16 and FA18 tested 35000ft M0.9 GBU-24 DLZ Max range is at 18NM in my test, Bomb has no chance. Same exact test in the FA-18 max ranges at around 9-/10NM works as you would expect. Also I don't believe your statement regarding laser slant range limit stands true, In my second track named laser test I active paused at 15nm (within the DLZ but right at the upper limit of the bomb actually getting there) You'll see the bombs do indeed pick up the laser, so beyond the 8nm you mentioned. I'm sure they're not infinite, but my problem I'm illuding to is mostly to do with the DLZ being massively inaccurate. GBU24 Laser test.trk GBU24.trk

Hi guys, Try dropping a GBU-24 from high altitude, high speed at max range. Bomb never catches sight of the laser (on from launch) and never makes it to target. Regards

This is a very good question. VR doesn't work quite like monitor's do. At 100% in steamVR, the resolution is already about 40% more than native to counteract a certain distortion present in the lenses / way its projected. The higher and higher you go the better. At 150% at roughly 3900x3900 per eye. It's like you're inside a spherical monitor. Unbelievable clarity and immersion.