currenthill

Thanks!

I'd be grateful for every bit of info or clue to make it better I can get my hands on. But I don't see how the 3d model could be the issue. During my testing I used the in game Mi-28 as a test subject. I can create all the code and use EDs 3d model for it. But the trainable nose cannon will only work if I code the aircraft as the in game ID. As soon as I create a custom ID the feature disappear.

You have to separate AI from human. They may seem like the same asset, but in configuration they are totally separate. Making a player controlled aircraft has its limitations, but you have a lot more wiggle room for workarounds since you can code around them. With AI you don't have much freedom at all, and with helicopters your freedom of configuration is tiny. But I don't really understand why ED has chosen to block some of these really basic features (like retractable gear) for helicopters, doesn't make much sense to me. Like for the EOS, it took me like a minute to get it working in the TB2 UCAV since it's a fixed wing aircraft, but the same feature seem to be blocked in helicopters. In ships or ground vehicles I can add weapon stations to my liking, but this does not apply to helicopters.

Thank you! But I should clarify that the issues mentioned above are not due to DCS 2.9, they are restrictions made by ED choice and design. Core modules and third party modules don't have these limitations. That said, there are still a lot of bugs introduced with 2.9 still present. Hopefully most of the vital ones will be solved in a patch or two.

Thanks guys. To manage expectations. This is an AI asset, and there are some things that doesn't seem possible to achieve with a mod due to hard coded restrictions compared to in-game aircraft assets. For example: Having an EOS externally following the target only seem to work on ground, sea and fixed-wing assets (I have it turned on take-off to simulate activation). Having a trainable cannon only seem to work on ground and sea assets (I only have recoil and muzzle flash). Ejection only seem to work on fixed-wing assets (no known workaround, the pilots go down with the aircraft). Retractable landing gear only seem to work on fixed-wing assets (I simulate landing gear animation with workarounds, not perfect).

Puma A1 IFV (Germany) version 1.0.0 released! Changelog Version 1.0.0 Release version

I have a test mission containing Arleigh Burke firing Tomahawks. Half of them still went into orbit.

By the way, unfortunately the latest DCS update doesn't seem to fix the erratic cruise missile behavior of going into orbits.

That is correct! Thanks! This is the A1, but I was planning to add the S1 version with the MELLS in the future. I just need to add the launcher.

PCL-181 SPG (China) version 1.2.0 released! Changelog Version 1.2.0 Changed 155mm unguided HE minimum range to 3 km Changed elevation limits to 7-70 degrees when clear from the cab Changed max engagement azimuth to 120/120 Changed range and azimuth markers in ME In this updated version I have extended the rotation limits to 120/120 degrees. And when you have cleared the cab at around 25/25 degrees the cannon will elevate down to 7 degrees for the really short range targets.

That's not surprising, I haven't released the updated version yet.

Yep, that's the issue here. I went with the OSINT data regarding cannon elevation, but it doesn't really add up. Since the elevation is between +20 and +70 it doesn't really give it room to stretch out. I've been looking for more info on the asset while fiddling around with it and noticed on some photos that the elevation goes closer to +-0 when it's rotated (and the cab isn't in its way). And that is how I plan to implement it. If you want to fire at close range targets you will have to turn the vehicle more perpendicular to the target.

Thanks. I see what the issue is. The combination of propelling charge and elevation limits doesn't allow it to fire in your particular mission setup. The minimum 20 degrees elevation would need a less powerful propelling charge, since its maximum elevation of 70 degrees makes it impossible to lob the shell at the close range target.

I just tried it. I could fire the unguided shell between 3.3 - 21 nautical miles (6-40 km). Edit: And the 6 km minimum range isn't that far off. A minimum of 3-4 km is often found in sources. PCL-181 test 8.miz

As I mentioned, when I upgraded the unguided shell to 40 km I had to increase the minimum range. I will make a note and look at this later.

Be sure to check your range to the target. The range upgraded unguided shell has an increased minimum range.

MiG-29MU2 Fighter (Ukraine) version 1.4.0 released! Changelog Version 1.4.0 Fixed JDAM-ER missing its target

PCL-181 SPG (China) version 1.1.0 released! Changelog Version 1.1.0 Changed 155mm unguided HE maximum range to 40 km Changed max engagement azimuth from 30/30 to 45/45 degrees

LD-3000 C-RAM (China) version 1.1.0 released! Changelog Version 1.1.0 Fixed LD-3000 destroyed models size issue Fixed LD-3000 mobile size issue Fixed LD-3000 stationary size issue

M1A2 MBT (USA) version 1.1.0 released! Changelog Version 1.1.0 Fixed log errors introduced in DCS 2.9 Fixed size issue

M10 LT (USA) version 1.1.0 released! Changelog Version 1.1.0 Added laser targeting Fixed cannon elevation restrictions while rotating Fixed cannon muzzle flash position Fixed log errors introduced in DCS 2.9

I have no issues with all three assets.

Yep, I'm aware. With 2.9 ED chose to add additional warning messages (the same as they've done in earlier releases). In this case it's a warning message, so it's not critical and won't impact the functionality of my assets. But because I don't like warning or errors messages in the log, every time I update an asset I fix this. But there is no point in updating all the assets at once since it won't make any difference at all for the users.