prccowboy

the first name ("F_16_Tank_370") is the material name. This is currently correct. You do NOT change this. The 2nd name in your example ("F-16_Tank_370_diff") is the texture filename that you want to use. This should match the filename of your custom texture. In your example they don't match (one is "F-16_Tank_370_diff" and the other is "fuel_tank_370gal_diff") You can EITHER change your dds file name to match the lua text or change the description lua text to match the filename.

note: it is NOT a simple thing that you would be asking. The author would have to modify a lot of 3d geometry, change materials, cut new UV texture maps and try to do it in a way that doesn't mess up any existing liveries

You could politely ask the author to redo the 3d model. Those items are NOT painted on - they are part of the 3d geometry. At best, you can change the colors from red/white/blue to something else; but the shape will remain.

@Spino thanks for covering the M-28 on your youtube channel @Neo47thanks for sharing the German liveries @crazyeddie thanks for sharing all the new liveries (E-7a and M-28). When I started modding, someone told me that "when crazyeddie approves of your mod, then you have truly achieved something" I feel honored to have a few of my creations now graced with your liveries

the typhoon props look ok, do you mean the Kursk? That one requires a change to the base model by the author (missing prop animation)

that cargo model was NOT supposed to be in the package. It was a simple Proof-of-Concept build that I mistakenly included when I bundled stuff up for the stand alone release. edit: I don't mind anyone using that paracargo model with the M-28 mod (I'm in no rush to remove it and post a new package), but it's not "supported"

I'm guessing that the nose sensor is obstructed for rear aspect and that the retractable belly sensor is to allow full 360 view. I can't remember forum policy on external links, so I am just going to post a photo here from an article on "the Drive" titled "MC-145B Wily Coyote Special Ops Planes Will Be Able To Launch Stealth Cruise Missiles" that shows an operator station. Photo implies that the demonstrator used a MX-20 for the belly EO. also note the implication of synthetic aperture radar

let me know if you notice that happening again. I've never seen it miss in my testing... was something else maybe lasing on the same code? did you touch the sensor code when you added the zuni's?

as stated above, I have NOT included any paratroopers in this release. The capability is built-in for future development. nevertheless, some smart people out there who already have paratrooper models built and coded as a weapon system (ex: Hercules, DC3, private mod, etc.) might figure out that all they need to do is add the corresponding loadout to line 787 of the M28 lua file. That smart person would also know that they would then use "ground attack" in the mission editor with unguided bombs to drop the paratroopers. And finally, they would use a script to identify when those paratrooper "bombs" hit the ground and spawn troops at that point. I do not condone or support any unauthorized changes to my mod to do such a thing edit: as stated above, I intend to develop paratroopers, paradrop cargo, etc. at some future date (in fact, I mistakenly forgot to remove an early test build cargo model that I was using to evaluate paradrop capability from this release -- but you won't find it in-game). If anyone has a good paratrooper model that they are willing to share (public domain), please do so.

as someone who has experienced the modding rollercoaster, I understand your feelings. Projects may take months or years of effort and there is, frankly, little external payback or gain. Updates may break something you spent exhausting hours completing, you may receive criticism and demands from people that received the results of your effort for free, and you are constrained by what can actually be accomplished within the mod environment. That being said, I hope you climb back into the saddle and release this project. Your work is appreciated, and it would be a shame to see another good contributor leave the community.

There are 100's of An-28 / M-28 operated by dozens of countries; meaning there are still MANY liveries in existence that I have not touched in this release. I am not opposed to fictional skins (released separately), but they are low on my priority list for now. edit: the 1st on my list of fictional would probably be the paint in the MC-145B promotional material. The actual liveries I've seen on the Wily Coyote were not appealing to me (ex: airline livery from former operator, etc.)

I haven't ignored your request. I tried a few styles to convert that flanker pixel livery over to a transport - wasn't happy with the result. I will look at it again if I get around to fictional liveries

Eddie, Did you notice that they announced the livery design? looking forward to your update

M28 Skytruck / MC-145 Coyote and Antonov AN-28 (AI only) mod by PRCCOWBOY v1.0.0813 The PZL Mielec M28 Skytruck / Bryza is a multi-mission aircraft that can be deployed in troop and cargo transport, med-evac, maritime patrol and reconnaissance missions. It is an improved version of the Antonov An-28 aircraft. This mod includes multiple variants of the M-28 / MC-145 / AN-28 using loadouts to choose the various configurations. The types are split between two plane "assets" which are displayed as the 'M-28/MC-145 (CLP)' and 'An-28/BRYZA (CLP)' in the Mission Editor - alphabetically listed with the C's (Cowboy's Livery Pack M-28/An-28). ========================= Now available. Download link in 1st post of this thread ========================= Included are various liveries, including: - (RUS) Aeroflot - (POL) An-28 BRYZA 1R 1006 - (POL) PZL Factory paint - (POL) Air Force M-28B/PT 0221 - (POL) Border Guard M28-05 SAR SN60YG - (POL) NAVY M-28B1-RM 0810 - (UKR) Antonov Airlines UR-NTE (added in 1.1.1007) - (USA) MC-145A 00321 Variants include, by plane: An-28/BRYZA (CLP) - An-28 Cargo - An-28 Passenger - An-28 TD - An-28-1R "Bryza" M-28/MC-145 (CLP) - M-28 Cargo - M-28 Passenger - M-28B / PT - M-28-05 SAR - M-28B-1RM "Bryza Bis" - MC-145A "Coyote" - MC-145B SOMA "Wily Coyote" The MC-145B SOMA variant can also be equipped with: - AGM-114 - M-260 HYDRA rockets - External fuel tanks Note: there is a "CARGO" slot included with no payload options currently. This is reserved for future development to allow loading paratroops, paradrop cargo, etc. As always, this is my artistic representation based on photos of the actual aircraft / my modeling skills, and not necessarily 100% accurate. Furthermore, as multiple variants have been combined into "all-in-one" packages some variants may possess capabilities that are not realistic (ie. detection capabilities, countermeasures, etc.) known bugs: -- prop blur remains after engine destroyed -- An-28 engine sounds "odd" =========================== Installation: unzip the files and copy the entire contents of the 'Mods' folder in the zip file to your DCS user files folder, example: C:\Users\[YOURNAME]\Saved Games\DCS.openbeta\ (You should end up with a "CLP_M28_SKYTRUCK" folder under Mods/aircraft, example: "C:\Users\[YOURNAME]\Saved Games\DCS.openbeta\Mods\aircraft\CLP_M28_SKYTRUCK\") ---------------- To UNINSTALL: simply delete the "CLP_M28_SKYTRUCK" folder from the above location (Do NOT delete the entire 'Mods' folder as this will remove any other mods you may have installed) =========================== Changelog: v1.1.1007: added UKR livery; modified props/damage model; modified textures; modified flight performance; other appearance bug fixes v1.0.0813: Initial Public Release TLDR After reading an article about the "Wily Coyote", I decided it would be a good subject for my 1st aircraft modeling attempt in DCS. Although I learned a lot from the experience, the result was something that I was not satisfied with. Furthermore, as I learned more about the aircraft and it's history I wanted to expand to other variants. As such, after a little more experience in modding, I decided to go back and make a 2nd attempt at modeling the MC-145 and different variants of the An-28/M-28. As with all my mods, I attempted to balance enough detail to make it immersive and somewhat realistic with the fact that it is basically a "NPC" (AI) that should NOT be resource heavy to the detriment of performance in the game. That means that this is a bit of a hybrid "all-in-one". I decided not to make separate assets for each variant. Instead, I broke it into 2 for this release. The An-28 that covers variants produced before 1993 and the M-28 for everything afterwards. This release is not "complete." I have included a "CARGO" slot which is currently empty. This is intended for future development of paratroopers, paradrop cargo, etc. I'm sure some of you smart folk will realize that the plane model is already set, coded and animated for this use and will plug in your own favorite paratroopers, etc. (if so, and you have a public domain asset that can be shared with the rest of us, please do because I don't know when I will release a model for this. I don't like modeling people - as you have probably noticed from all my mods) As with my other mods, a simple paint kit will be provided by request (if you ask nicely and I like you). PM me if interested. However, I ask that you share with the community the result of your work. Although not all variants are ISR, I decided to include it in this thread as I still consider it a part of the "magic collection"

Thanks @RustyGunner I am trying to wrap up the project soon. I have many variants included of which both the MC-145A and B are available. I admit though that since the announcement last week that the Armed Overwatch contract went to another platform some of the wind has been taken out of my sails for this project. Nevertheless, even though it doesn't look like the Wily Coyote will find a service home soon it will still be included in my release. This is what I have currently for the A and B models:

I think he meant to type "link" is not working

will AI planes land on this? or is it essentially a flat strip added to a FARP?

the AO looks ok to me but what file format are you using for your textures? it appears that you are using a tga with alpha transparency? I suggest a dds with mipmaps

that might be an ambient occlusion layer problem. is the red channel in your roughmet bright white or shaded grey/black?

Hellfires stopped working in a recent OB update. Hotfix is in 1st post. edit: fix is now included in main download (v1.0.0722 or higher)

1) You can use various image types for your texture, but preferred is .dds with mipmaps. You will need to create a combined Roughmet texture from your Metalic and Roughness (R=AO, G=Roughness, B=Metallic). there is a pinned thread for this topic. The Normal texture needs to be G = -Y for DCS 2) In Blender under the Object Properties=>EDM, select Rendertype = "RenderNode"; MaterialType=Solid; 3) set Diffuse filename to your "BaseColor"texture 4) select "Use normalmap" (filename = your Normal texture and set normal map value =1). 5) select "Use specular map/Roughmet" (filename = your combined Roughmet texture and set specular map value =1). All of this has already been covered in some detail in these forums...

checking interest in the M-28 Skytruck / MC-145 Coyote (and/or the AN-28 / Bryza variants). Post livery requests if you have them.

I think I recall the AI spoilers operating during aerial maneuvering and during landing; but honestly, I can't remember. It has been so long since I saw them working that if it wasn't for the fact that the models have the animation rigged and that the args are documented as being used for that purpose I would doubt my recollection.

The E3 model doesn't use the spoiler animation arguments (args 120-125); instead, it combines the spoiler animation with the flaps. However, every model that uses the animation args 120-125 for the spoilers appears to be impacted. Thanks for the response