Mach3DS

Oh. i didn't mean to imply that I wasn't making them HG. They will remain. I used the first shot as reference. I just meant that some photos and video don't impart that translucent effect as good as other photos. But these are definitely HG. Those last 3 shots you posted show the Irridescent effect pretty well.

Looking at this video it actually doesn't look like these jets are Have Glass. It just looks like they have the dark paint job. That is quite normal. Have Glass is not used much from what I can tell. Or it's really slowly implemented.

Thank you! I have a few details to fix to make them a little more different but very close to finished.

Finished the 2 ship set of 18th FIS 87-0264 and 88-0409. I will post some screenshots after work today.

I don't use SP. FYI.

Look, I get it.....it's nice that someone is doing something. Congrats on spending whatever time it took to make what looks like an ultra simple livery. (that's not meant to mock the livery artist in any way, just that it's not an overly complex livery). But, this kind of thing is actually making it harder to get what we need, which is a fully functional Model Viewer and the library of all base textures (all Roughmets, Normals, albedos, for aircraft, pilot, tanks etc.). Without those, you can NEVER have a custom livery that actually looks correct. So while, time was spent on this, I fear that it will just cause a blind eye to be turned to the real issues with a "See, they're already making liveries, we don't need to do anything else" mentality. Which would be a terrible outcome.

Many thanks

It's too big for User files. But I think I've changed my mind and will make it public release. Along with some other content.

1000% A tanker asset pack with J57 equipped KC-135 would be incredible. We really need that engine variant. A KC-46 would be awesome for "future" scenarios. A KC-10 is also needed. But I think we need ED to allow for these others to actually be able to AAR?

WIP. @ST0RM DM me. Composite zoomed in view from MV to show detail.

I thought the first engine image was a photo. Really nice work!

HA! Thanks dude! appreciate it.

DL LINK: https://www.digitalcombatsimulator.com/en/files/3343906/ My take on this livery. Added the correct stiffener plates at the fin fillet and wing roots. Also the nose side lobe stiffeners. Instead of making it a right out of the paint hangar bird I've added in some used effects like fuel leaks and kept some dirt and grime. Also AAR door damage.

Also, from a visual standpoint, the v3 F-22A external model is missing NORMALS support. I've already told Grinnelli about it. I've simply reverted the external model back to the old one from 2021. Which has the normals support.

@cubanace You can't use Discord to host images anymore. They basically have a non static image link. It will break almost immediately up to a few days after you post it.

Hopefully it too is NOT encrypted!!! Although, if it is, then we know the direction that ED is moving. Time will tell I guess.

Thank you sir!

2. That's what I was referring to with needing a file path folder structure. We have no way of implementing them via the conventional method even if we were given a working model.viewer, files and LUA entries. 5. Clearly no. LOL. There's no way to access the files. They're hidden, as far as I'm aware.

Open the dds file and start creating duplicate layers from selected areas. Create UV mesh layers for alignment using MV dot files in blender.

It will "work" for the exterior. If you want to do anything custom, I've been told that there are no roughmets or normals included. THere's no pilot textures/roughmets/normals, Helmet, patches etc. If you want to do anything fully custom and have it look decent you will need all of those. For it to work in basic terms we will also need a folder path structure which doesn't exist either. Since it's currently encrypted. Where do you put said new textures? 9L has said they're working on it. But we really do need all those things. So it kind of begs the question, if they were do give us all those things as say PSDs, what's the point in encrypting anything other than the model file at that point? Just fix the model viewer to read the encrypted model file and open up the rest of the textures as usual. Then you don't have to create PSDs or do any additional work. We can all create templates from the DDS files. To me, that makes the most sense.