prof_laser

what razo+r said. doesn't show up in the module manager in-game.

same here. updated DCS, repaired DCS, viper is greyed out, asks me to buy it. I'm shown the ED shop, it says it was already delivered?

latest OpenBeta, no mods, track and mission attached When the AI F-18 is instructed to hit a group of ground units with JSOWs, the pilot points his nose towards the ground unit when running in. After he pickles the JSOWs, they start with their "oscillating" vertical path. That leads to the JSOW impacting on the F-18. Explosions test.miz JSOW suicide.trk

This speaks for itself. Well done, ED! You can seriously be proud of yourselfs!

Same here.

OpenBeta 2.5.5.31917 When flying - in a bank of more than 50 degrees, - low-level, - nose pointing above the horizon, - and then going wings level, the GCAS fires at around 35 to 40 degree bank for a split-second. Betty tells the pilot to "pull up" and the GCAS cross appears in the HUD. The TVV is always above the horizon. bug A-10C GCAS.trk

OpenBeta 2.5.5.31917 When parked on the ground, the button to deploy the ladder does nothing. bug A-10C ladder does not deploy.trk

OpenBeta 2.5.5.31917 Trackfile, dxdiag and screenshot attached. When the TGP points directly aft, you can see through parts of your own A-10C. For example you can see through the wire-frame at the backside of the TGP. Screenshot shows situation after an attack run. Note the small white dot below the coordinates, it shows it's pointing aft. In the lower right corner, you can also see parts of the hull, with the segment in the lower right corner being transparent. bug see-through A-10C.trk DxDiag.txt

Yes, it's fixed.

Can confirm everything. But most importantly: the FLIR is fixed!!!! Thanks, ED!!! :D

Signing up in A-10C, BLUEFOR. Callsign is 132nd.Professor

Guys from Eagle Dynamics, is anyone working on this?

That's good and simultaneously not good to hear. Since this bug can't be triggered at will, I think it might be good if we can test this on many different machines. If you read this, please download the mission, grab a friend and play it with him for 30 to 60 minutes. In our experience, the bug should have occured after this much time. Then please confirm or deny that it happened for you.

This is OpenBeta 2.5.4.29585. This requires a bit of pretext, since this bug occurs sporadically. I can't reproduce it at will. But I noticed it the first time about two months back. I have set up a mission for my buddy and me to do dogfighting training in the F-18. We start heads on, same speed, same altitude, 9 nm apart. Mission is attached. In the track files we picked the slots at 38 T LN 49 61 (Groups are "Mountains Sidewinder Blue" or respectively "Red"). We go and kill each other, then I pause the server, we go to spectate, select the same slots again, and I unpause the server. In the dogfight we typically start by picking each other up in the radar using ACM and HACQ before merging. But sometimes after respawning, we cant get a radar lock on each other. Sometimes only one player is affected, sometimes it's both. According to the HUD, the radar is directly on the other player, but it doesn't lock. Not only that the bug occurs sporadically, it also doesn't show up in the track files. In the attached file, the bug occured close to the end. When we notice this bug happens, I restart the server by selecting the same map again in spectator mode. Then the bug is gone. After about 10 minutes, it happens again.... Since it's hard to reproduce, I will upload a video of the issue. EDIT: Video is uploading. Should be available in high quality in the ZULU morning hours. It shows a total of 5 times this bug occurs. server-20190416-235810.trk F-18 multiplayer dogfight.miz

https://forums.eagle.ru/showthread.php?p=3879983#post3879983

[REPORTED] GBU-38 and Mavericks broken in latest OpenBeta Latest OpenBeta version 2.5.4.29585 GBU-38s do not track coordinates. They behave like free-fall bombs. Maverick track files will follow shortly. EDIT1 See also: https://forums.eagle.ru/showthread.php?t=238668 EDIT2 Mavericks sometimes do not hit targets. They "loft" in the wrong direction. A-10C GBU-38.trk A-10C GBU-38 test.miz A-10C AGM-65D.trk Tacview-20190412-143010-DCS-A-10C AGM-65D.zip

Can confirm, same problem here. See attached tacview file. The first maverick is "lofting" left and then going towards the target. Maverick_run.zip

I remember setting radar to 1 bar puts the upper and lower limit to the same value (probably not correct). But if what Cp said is true, then using 2 bars should NOT result in half the covered altitude from 4 bars, since it then has only 1 overlap instead of 3.

When setting the sling length in the ME for Ka-50, the length is not used in the mission, but a length of 80 to 90 feet is used. DCS OpenBeta 2.5.4.29079 Ka-50 sling loading length.trk Ka-50 slingloading test.miz

Thanks for the response! I have to ask one "nasty" question, though: Is this behavior properly documented somewhere? If it is not, there is another bug related to documentation.

I prepared a mission where I want some Aircraft to spawn at the runway for immediate take-off. In single player mode, this works fine. In multiplayer mode (using exactly the same mission file), these aircraft spawn at their parking positions over other aircraft, and crash when they start to taxi. See attached files. DCS OPEN BETA 2.5.4.28840 ME bug.miz ME Bug Single Player.trk ME Bug Multi player.trk

I tried it. Complete aircraft shutdown, starting up again, error is still persistent.

Fun fact: Do a cold and dark startup, and while still on the ground simply turn down the oxygen flow dial. Blackout within 20 seconds.

on hoggit multiplayer

Wizard, thanks for the explanation. This makes sense so far. What it doesn't explain though, is that once the engines are started up and I press FCS RESET again, the error is not cleared (forgot to mention in my original post). It also doesn't explain why this only affects the ailerons, and not the other control surfaces. Sierra, I'm basically omitting some checks that should not have an influence on the startup (warning lights test, fire test and cycling bleed air, ...)