Fabri91

I had the same error when not including the Skynet script (I missed the file named skynet-iads-compiled.lua, specifically) correctly in the startup trigger - ensure that you've done that.

I seem to have the same issue - here's a video recording of it occurring:

As described in the title, today I noticed this issue while flying the F-14A for the first time after a long while: in short, the GBU-12s loaded on board appear ablative grey, as IIRC is used on naval aircraft, but upon dropping thebomb became "standard green": The DCS version used is the latest Open Beta - Multithreaded version 2.9.0.47168.

I've flown it yesterday and managed to complete it on my second try - turns out, I will likely try it again later this week! Well done!

Sometimes, even when starting hot on the runway or in flight, when setting up for an ILS approach the ILSN and ILST buttons on the HSI will not be present and appear/disappear seemingly at random. In this case, for example, they disappeared after I selected ILST mode and started tracking the localizer. At a later stage they re-appeared, as did the glideslope, far below my nose. Pressing the corresponding PBs didn't seem to have an effect on the system in this apparent "stuck" state.

So far with a buddy in MP we're able to reliably reproduce the crash: in both cases me as the WSO activated the A/G radar page, then my pilot selected the same page and only after that the radar knob was moved to OPER from STBY. At that very instant I, as the session host and the WSO, experienced the crash. A full, slow repair was run after the first test and *prior* to the second test.

Same issue still present on Caucasus.

Thanks for the amazingly quick reply! I'll test it out some and report back any issues. EDIT: I tried your example and it seemed to work, but upon changing the units (Tigr on red side with an Abrams on the blue side) the wreckage still appears to stick around - have attached some screenshots in addition to the modified mission file. Especially in the first one you can clearly see both the old and new vehicle. viper w uu mod.miz

If the change is here to stay, would it be possible to have a module that wipes a trigger zone of all objects? This way it could work like this: spawn clones -> when all are dead run this "wipe all" module -> when it's done run the delayTimer -> when it's done trigger a new spawn event. I'm thinking of having it be separate because if static objects are not tracked then it's "dangerous" to wipe them as part of the cloneZone everytime, so it might make sense to have it have to be invoked intentionally.

This really seems like a powerful set of tools, and the ability to do everything inside the sim's interface is something that is rather appealing to me! I've been experimenting with clone zones, and I'm having an odd issue: I'm trying to spawn a group that will re-generate upon destruction as a part of a training mission, and I think I got the clone zone and the timeDelay modules integrated well and they seem to work. However, upon destruction of the group the dead "carcasses" of the vehicles aren't removed, and so continue to clog up the spawn area, with a new vehicle often spawning exactly where a wreck is located since this previous instance didn't move before being destroyed. The preWipe attribute of the clone zone doesn't seem to do the trick (does it apply only to living units?). Is there a way to accomplish this?

Best case scenario it's the wrong build that has been pushed, which isn't too encouraging.

Thanks, a good list of up-to-date tutorials is exactly what I was looking for! :)

I was also able to reproduce this. Even though it's been reported here's a track file of the issue occurring during the "Convential Bombing" Caucasus Instant Action mission. Just select the Mk82 (also happens with other types) and release. I also noticed something similar happening with air to air weapons, but less often. No track of that yet. hornetMultipleBombsSinglePress.trk

I can confirm this issue. So far only tested in a clean mission without any other aircraft.

Well, no, but think of the first impression from a new DCS pilot: he/she may be following along the startup tutorial, but the module just doesn't work for no discernible reason. I seriously doubt this is going to leave a particularly good impression. This bug should just have been classified as a showstopper, there aren't any excuses if the startup sequence doesn't work. It's not like some obscure gauge giving a false reading in some uncommon circumstance, it's a key phase in the operation of the aircraft.