currenthill

Military Asset Pack China 1.0.0 released! Changelog Version 1.0.0 Added tags to all assets Changed distribution of assets from singles to packages by country Fixed APS issues introduced with DCS 2.9 Fixed reload time log error message for all assets Fixed sensor height log error message for all ships Military Asset Pack Germany 1.0.0 released! Changelog Version 1.0.0 Changed distribution of assets from singles to packages by country Military Asset Pack Iran 1.0.0 released! Changelog Version 1.0.0 Changed distribution of assets from singles to packages by country Military Asset Pack Russia 1.0.0 released! Changelog Version 1.0.0 Added AI helicopter night landing feature for all ships Added Ka-52 trainable cannon and retractable gear Added Ka-52K trainable cannon and retractable gear Added Tu-95MSM Strategic Bomber Changed distribution of assets from singles to packages by country Fixed APS issues introduced with DCS 2.9 Fixed DShK HMG not targeting LM Fixed reload time log error message for all assets Fixed sensor height log error message for all ships Military Asset Pack Sweden 1.0.0 released! Changelog Version 1.0.0 Added AI helicopter night landing feature for all ships Added tags to all assets Changed distribution of assets from singles to packages by country Fixed Ag 90 missing normal map texture Fixed Hkp 15B retractable landing gear Fixed reload time log error message for all assets Fixed sensor height log error message for all ships Military Asset Pack Turkey 1.0.0 released! Changelog Version 1.0.0 Changed distribution of assets from singles to packages by country Military Asset Pack UK 1.0.0 released! Changelog Version 1.0.0 Added AI helicopter night landing feature for all ships Changed Aster 30 booster smoke thickness Changed Aster 30 maximum overload G Changed distribution of assets from singles to packages by country Fixed APS issues introduced with DCS 2.9 Fixed reload time log error message for all assets Fixed sensor height log error message for all ships Military Asset Pack Ukraine 1.0.0 released! Changelog Version 1.0.0 Added tags to all assets Changed distribution of assets from singles to packages by country Fixed ADM-160B Fixed Storm Shadow Fixed Taurus KEPD-350 Fixed reload time log error message for all assets Fixed sensor height log error message for all ships Military Asset Pack USA 1.0.0 released! Changelog Version 1.0.0 Added AI helicopter night landing feature for all ships Added B-21 rotary launcher Added [CH] prefix to B-21 Added tags to all assets Changed distribution of assets from singles to packages by country Fixed B-21 AGM-158B Fixed reload time log error message for all assets Fixed sensor height log error message for all ships

Sure, I can take a look. Send me a Discord message, it's easier to chat there.

During my research I found several sources who still mentioned the tail gun after the upgrade. Nevertheless, it's on there now. One example:

Yep, with all your continuous support and finding suitable models I would definitely like to make Polish assets. I thought ED was working on a CH-47? There are a lot of interesting Turkish assets, indeed. It's configured with a reload time of about 5 minutes reload time (as in real life). I just tried it. Make sure you have the latest version of the asset. I thought such mods already existed. Make sure you always have the latest version of the asset, especially since lately almost every DCS update requires changes in the mods to keep DCS from crashing. Definitely, I've already made a couple of older assets like the Strv 103 and the M551. All assets keep their unique IDs, so there shouldn't be an issue. Well, that's the point, the new setup isn't meant to keep assets individual. The lowest level of granularity I will support and update will be the country pack. Exactly! While I can't stop anyone from ripping apart a country pack into single assets, it's not something I will support. Yep, that might seem like a con, but it's actually a pro for me. Updating 100+ individual assets, with everything surrounding a change and release makes it an administrative nightmare. Remember that I'm a one-man-team, so every bit of time I spend on admin could have gone into developing instead. You should consider the country packs as the lowest level of granularity, which makes optimization a very logical choice at that level. Why have the same textures or configurations several times in the same package? Just enable the complete pack and you're good to go. Sorry, but I have to change from supporting individual assets to complete asset packs, otherwise I won't be able to continue the work. This approach will demand more downloads and storage space, but consider what you pay for my assets. I just tested a mission with the Su-24MU and MiG-29MU2 while flying the A-10C II. No issues for me. We'll see, I might look into it. Current status is that most of the cruise missile issues have been fixed. With the latest DCS update both the cruise missile and antiship missile issues are solved. But I had to make some changes to some of my weapons to get everything working again, these will be reflected in my country pack releases. Unfortunately the latest DCS update introduced a new issue with the JDAM-ER (and other weapons using the JSOW missile scheme).

I just updated the Ka-52 with the new parameters from ED, and it works great. So the next release (within the new Military Asset Pack Russia) will have a trainable cannon and retractable gear - without any jerry-rigged workarounds.

This is how it looks

Reorganizing I'm in the process of reorganizing my assets. It needs to be done in order to be able to manage them. Some of you will like it, and some won't. But it is what it is. I'm creating packages per country. CH Military Asset Pack USA CH Military Asset Pack Russia CH Military Asset Pack China etc By doing this I will be able to reuse configurations between assets, as well as managing updates easier. I will consider a whole country package an item for updates, so no more individual updates per asset. This will make it much easier to mitigate compatibility issues and for users to keep their mods at the latest version. The downside will of course be heavier downloads, but that's a sacrifice I will have to make. The first version will more or less be a consolidation of all assets per country, improvements in removing redundant textures and models will be made in later versions. This is to minimize the risk of introducing issues and errors in the consolidation process. Since I'm primarily using Dropbox for file sharing I'm going to test their Transfer service which will enable me to make packages (like my asset packs) available for download without downloads counting against the daily download bandwidth limit. I also just ran a mission with all and every version of my assets spawned at the same time (helicopters, planes, ships, vehicles etc), while my CPU and GPU didn't appreciate the workout I can report that there were no compatibility conflicts among my own assets.

I noticed that my JDAM-ER on the MiG-29MU2 doesn't work anymore. It's reported as a known error by Deka, as they use the same missile scheme for the LS-6-500.

Hey @Flappie! I'm using the latest Openbeta and noticed that the JSOW_C missile scheme, used by for example the LS-6-500 glide bomb (JF-17) doesn't seem to work as it should anymore. They spin and fall to the ground. See attached track. Edit: I noticed Deka reported this as a known error. But I'll keep this post as reference until it is fixed. LS-6-500 JSOW_C issue.miz

Nice!

Perfect!

I guess one solution would be to share upcoming structural changes in DCS core with mod makers beforehand, but I guess that's one of the perks of being a third party developer.

Good news! With the latest DCS patch it looks like I have what I need to get the cruise missiles and antiship missiles fixed. I'm currently working on updates for the assets that needs it. Also very good news: ED (through excellent support by @BIGNEWY) delivered on their announcement of removing the hardcoded issues preventing AI helicopters from using trainable cannons and retractable gear. I will be making updates to the Ka-52 shortly.

This is just great! Thank you for the quick work on this.

Thanks, I'll look into it.

I never set release dates. As soon as I'm done with all the features, I test and then release. But this time I won't be releasing until the next DCS update. I need the cruise missile fixes to be implemented, otherwise I can't test the missiles correctly.

Do you mean which version? It's suppose to be the Tu-95MSM.

Well, some projects takes more time to finish.

The Pantsir 57E6 family of missiles are command guided, so you will only get an warning when locked on by the Pantsir radar. Unfortunately, the Pantsir also have an electro-optical sight which it can use at short ranges. And those won't give you a radar warning. Your will need some sort of Missile Approach Warning System (MAWS) to detect incoming missiles of this kind. Or your head on a swivel and very sharp eyes.

Thanks for the suggestion! Well, I've been interested in making submarines and torpedoes, but DCS support for underwater warfare is a bit light. We'll see moving forward. Thanks, I'll look into it. Yep, it's my contribution to the Mars exploration. As you might have noticed, it's because of the cruise missile and antiship missile bugs in DCS. They are said to be fixed in the next DCS update. No plans at the moment, but I really like the M1070 and such beasts. Yep, you found the issue. I have it on my FAQ: https://www.currenthill.com/faq#h.vd47duult5df We'll see.

Nice!

Yep, I agree on the distribution/update issue. It's very inefficient at the moment. And I understand the hassle of keeping up with all my updates. But I really don't have much of a choice at the moment. The best solution for users would of course be to have them incorporated into core DCS. But since that's not possible at the moment, I've been thinking about different solutions. I've been offered solutions like the one you suggest. I haven't made up my mind yet, but I need to make some changes, that's for sure. I have described my process in my FAQ: https://www.currenthill.com/faq Yep, that looks much better. I will look into it. Correct, and I actually knew that. But sometimes in the videos, where everything is happening in real time, I forget. Yeah, but it's not very good looking, haha. I would be interested in making a newer Mi-28 version, but it won't happen until we have support for trainable cannons. Which is especially important for the Mi-28, where it's more or less the center piece. I haven't done anything to the mesh or textures for my updated Burke and Tico. My plan has been to replace the models to make them more accurate, like removal of the forward Phalanx etc. I agree.

Well, I'm not going to dwell on the subject. But it's important for anyone else reading this to get correct facts: My Ka-52 is per default not conflicting with any core units, it takes active tinkering with the configuration files to use the second version. Someone just downloading and installing the asset will never need to know about the second version, I can't really explain it any clearer than that. The reason I included the second version is the same as the reasoning behind all of my assets. I make them for myself, for my own amusement. And then I release them for anyone else to use them, if they're interested. Finally, let me give you an example why I included the second version: the difference between the trainable and non-trainable Ka-52 2A42 cannon is about 3 km.