Wyvern

This is likely a Block 2, given we haven't had a lot of info about its internals so far. As for the video, you can see in it that it has the smaller HUD, but ADI int the top right. Wouldn't surprise me if the Block2 has a few software upgrades.

Are you sure youre exporting with the correct colorspace? You seem to have exported it with a sRGB space, rather than Linear. also, Megalax wasnt entirely wrong, if the texture has the wrong aspect ratio, it will come out completely black, as it can read it, but not recognize it. It will only show a missing texture camo if it cant find the texture at all

Alright, after taking a look at this: The A-50 and KJ-2000 dont seem to be able to feed target information into the JF-17. If you select the E-2 or E-3, it seems to work. I added the miz files with all the different AWACS. Missions are all identical, only difference is the AWACS. E-2 and E-3 seems to work fine, A-50 and KJ-2000 dont feed info. JF17DL_AWACS_E2.miz JF17DL_AWACS_E3.miz JF17DL_AWACS_KJ2000.miz JF17DL_AWACS_A50.miz @uboats I think this is an ED/Deka issue to fix, looks like the A-50 and KJ-2000 dont have the datalink function. While the E-3 and E-2 do have it,

I will take a look, i think it MIGHT be the A-50 that is the issue, but i cant say. Ill let you know once I try

Im just wondering about one thing. If someone comes around tomorrow, and figures out how to crack the new models, (which I have been told is already possible) What then? I understand the IP protection argument, even if I personally think its nonsense. If someone REALLY wants the models, they WILL get ripped, its not a "if", but rather a "when". There are so many issues with DCS, even if you focus on the models. -Some of the new Su-27 liveries missing half their stencils, -the Su-33s tailnumbers missing the Normal map support, -the J-11A being almost completely abandoned by both Deka and ED -the Su-27 and Su-33 templates havent been updated since 2013 -the "decal" layer on most planes missing PBR support -the Su-27 bortnumbers being assigned glass properties instead of decal properties -All FC3 planes missing a few net_animation values for things like brakechutes (ironically the J-11A has them) Those are just a few smaller issues that I could think of from the top of my head, with 3 planes only. There are MANY more issues that I wont name here now, as it would be a list thats just too long to put here. Most of those things above could probably be fixed within a day -even within one or two hours - by a single dev. Instead, they are tasked with creating "fixes" for things like this, where it sadly just inconveniences people and takes time away from other issues. Sent from my SM-N960F using Tapatalk

It might have to do with how the rockets are set up, FF modules usally are coded a bit more in-depth than FC3 and similar. Meaning that some weapons wont work on certain planes.

I personally just use Paint.net (program, not site) Lets you convert a full skin rather quickly and while I work on something, i dont save it without compression

Yeah... the canopy is a thing. I keep forgetting to seal it too, thats normal. If you never lost your canopy, youre not a real Jeff player xD as for the ground weapons, thats an ED issue, since they changed the weapons to their own code, they have been a bit iffy. Also make sure that you have "unrestricted Satnav" turned on in the settings (gameplay or misc). Since the Jeff is technically a red plane, it gets downgraded GPS on blue if the setting is off.

This should explain it!

aswell as the LOD_6 and Landing gear

I personally would be very interested if the MV could be included into the Encyclopedia. This was you actually would have a use.

no just no

New radar issue, discovered by youtuber: https://www.youtube.com/watch?v=_Gvf3ALv-og Steps to reproduce: 1. Optional: switch to Air-to-Air mode 2. Enter VS and adjust the scanning pattern as you need it, set velocity range to 24 3. Once you detect target, attempt to locking him, it will likely break the lock 4. Attempt again (in attached track, the second target), now you have it in STT mode with no range 5.Press lock briefly again, you will be back into VS mode but with alternating distance 6. Works both in NAV and AIR mode, except you can not shoot in NAV mode. In this the missile missed, since the AI barrel rolled. But the hits were consistent. Note: It worked against the Tomcat, but not against the F-16. Has not been tested on players yet. JF-17 VSTTWS.trk @JG54_NF2 Issue reported in Deka Discord: https://discord.com/channels/1216953784702472282/1332744184301359105/1332744184301359105

There has to be another way tho. I mean, it wouldnt seem unrealistic to sue people who do it. Just giving us textures and a lua file will not cut it for livery making. My suggestion would be: Include the ModelViewer as a function into the game. This would be a perfect use for the Encyclopedia tab. However, that would pose the question of how you can add in the functions we have in MV. Let me show you which tabs I have open when working on something, and give a general overview of the modelviewer and its important functions: Just to explain why we make such a big deal out if it. (this ended up being a bit longer than I thought) i added some color help to make it easier to understand: LiveriesToolPlugin With this tool we select the liveries we are working on. It gives us a list of all liveries, for all units in the game that have liveries in the first place. CONNECTOR_TOOL_PLUGIN With this tool we cal select the connectors on the aircraft, which is how we usally put on Fuel Tanks, to see how they look on the plane. Scene Window Here we can select the object we are viewing. If you add an Object with the Connector Tool (lets say a Fuel Tank), we can go to the Scene Tab and select it. After this, we can click on the livery in the Livery tool to change the texture we are viewing. This is where the abilities on the Mission Editor ends. Argument Viewer With this tool we can see all the arguments (aka animations and Blendshapes) We use this to extend the gear, open the canopy, move the ailerons and flaps, so we can texture in more detail. Without it, we would have to load into a mission, and then fly and maneuver in certain ways, just to see the flaps fully extended. On some planes (like the flanker for example) The arguments also change the visual shape of the pylon. While on other planes (like the F-16) it controls where or how the Bortnumbers look, aswell as the number they display. Overall, this is one of the most important tools we have, as it saves an excessive amount of time. Texture Viewer Here we can see (most) textures that are being loaded. We can use it to navigate to the folder that has the texture in it, we can view the UV layout, and we can view the texture in detail. Here it shows both the Default, but also the modified textures the livery has loaded. This tool is EXTREMELY useful, as not all textures are located where you would expect them to be (F-16 Fuel tanks are a great example with them being in Bazar, and not in the F-16 Core Mods folder) Reload Textures As you might guess, this button reloads the textures. If you would use the game to look at your changes, you would have to re-launch the game each time you make a change. Obviously, having this button is 500x times faster, which obviously is going to be better than waiting 5 minutes to start the game and load into a mission, just to see that you need to move the camo by a few pixels to make it align across different textures. Environment/Lighting This here lets us view the loaded object in different Lighting conditions. From Dusk, night, cloudy, desert, or Woodland, its a good thing to have, as this way we can get a reference how the skin will look with certain weather options and maps. Generate Lua File This button lets us generate a Lua file, that has all the texture-names and lines for the Description.lua on the aircraft/object we are viewing. Other Notable Tools: FOV tool: Lets us zoom into the aircraft to view areas with more focus Free Camera movement: We can rotate and move the model to get better lighting angles and such, which is very important and irreplacable for making camos, especially when they have smooth, gradients as edges. F1-F12 keys: They let us view the textures in different overlays, those being the following: F1 Regular Lighting F2 Wireframe F3 Base Color (with no lighting, just shows the diffuse textures how they are with no reflections) F4 Normal map (shows the normal maps in a special color view, that helps to see the effect of the normals) F5 Roughness (shows the Green Color Channel of the RoughMets in greyscale, this controls how Rough (matte) or smooth (shiny) the surface is) F6 Metallic (shows the Blue Color Channel fo the RoughMets in greyscale, this controls wether a surface is Metal or not) F7 Emissive (shows areas that emit light (Formation lights, F-15E Afterburner Cans, etc) F8 Material Errors (honestly, i still have no actual understanding what this does specifically) F9 Ambient Occlusion (shows the Red Color Channel of the RoughMets in greyscale, this shows where a surface has a shadow (in simple terms)) F10 Cavity Maps (shows the Alpha/transparency Channel of the RoughMets in greyscale, this adds some extra shade for seams and screws) F11 Combined View (shows all the previous views, has been broken for a few years now) F12 Cockpit Global Illumination (not sure if im correct, but it shows how and where exactly shadows are being applied on the model Shift+F11 Diffuse Light (technically shows how much light is being applied on each area of the model, can be used to see the normal maps better than F4 view) This is a basic overview of the tools we have in Model Viewer, and as you see, most tools we NEED to make skins, are only avialable in the ModelViewer Sorry for the giant message, but i feel like ED/the community mods dont fully realize the importance of the tool, and why we need what we are asking for. I hope this helps with understanding, have a nice day!

Then how about ED settles with Razbam and actually uses their legal team to actually sue said individuals instead.