Wyvern

I would be interested in helping Hit me up on discord, either through the link below, or just add me: @Wyvern613 Sent from my SM-N960F using Tapatalk

It might not I dont have the steam version installed anymore, but a friend might. Ill let you know if i find something out Sent from my SM-N960F using Tapatalk

did you install both the bin and the manifest?

Seems to be fine

@uboatsdo you think you can take a look at this?? fix the alt view and maybe add sat view option

Did you have fun playing oblivion? Haha xD Sent from my SM-N960F using Tapatalk

If you use the taptalk app to use the forums on your phone, it adds that to your posts Same with my post: Sent from my SM-N960F using Tapatalk

Afaik its up to the third party, and i believe they are not too interested

I wonder if there also would be a possibility to have a "Sattelite" option

aaaand bump "Raster Charts" seems to work fine While "Map Alt" seems to still have issues It only renders areas next to water, while the rest clips in occasionally.

Ill laugh so hard whenever someone comes around with a ripped model of the new F-5 and other EDCE models, aswell as the MiG-29 when its out. Simply because then you'll have to explain what the point of this measure is. Whoever made the decision to implement this, does not understand that the moment the model is on a users screen, it WILL be ripped by someone. ED is unnecessarily starting a fight with its content creators. We have seen this with the modding community: First when 2.5.6 came out, a lot of the scripts got encrypted. Making modding a lot harder and limited. That wasn't this bad until FC2024 came around. FC2024 has killed a lot of mods, and only raised the entry bar, so only those that where actually doing their own stuff without mostly relying on FC3 would be able to make stuff. Some mods literally only work because people reverse engineered FC3. You've seen it with the F-5 livery comp. Nobody will actually make stuff anymore. Especially not high quality skins. The RCAF camo was the best entry, and even that was still far from being good. The creator himself said that he cant work like this. But hey Me and a few friends have an idea: We will make Liveries like this if ED will code the game in notepad from now on. Because that is essentially what you're telling us to do. There is a reason nobody believes you when you say that ED is trying to come up with a solution. The same thing was said back with 2.5.6 about the files for all the weapons and planes. And look where those are. Possibly its just me being pessimistic. But i dont see ED doing anything in this situation, because they simply dont care. Maybe thats why they keep thanking us for our "Passion and support", because the passion is slowly dying on their end. I wonder if Tishin (Rest his soul) would have allowed any of this.

cant wait for it to be encrypted! If it is, I personally wont buy it I dont see a point of buying a plane i cant make liveries for. not if ED does the same stuff they did with the F-5 and encrypts all the textures and the EDM

you can make them with simple rectangles

@jack333 send me a DM on discord Im honestly just confused at this point my username is @wyvern613 Im geniunely confused about what is going on here

Can you post a picture of the files open? not in the game, but the actual Glass_new.dds from each folder in paint.net,gimp, or photoshop

it should be grey. This was broken since the FC2024 update

after actually looking at the description.lua picture you sent (what a concept, i know), i think im right. try replacing the part with the glass with this: {"F16_bl50_GLASS", 0 , "F16_bl50_GLASS", false}; {"F16_bl50_GLASS", 14 , "F16_bl50_Glass_new", false}; {"F16_bl50_GLASS", 13 , "F16_bl50_Glass_RoughMet", false}; {"F16_bl50__GLASS_СLear", 0 , "F16_bl50_GLASS", false}; {"F16_bl50__GLASS_СLear", 14 , "F16_bl50_Glass_new", false}; {"F16_bl50__GLASS_СLear", 13 , "F16_bl50_Glass_RoughMet", false};

hit me up on discord, I would like to take a closer look. -> @Wyvern613 To put it simple, I believe you two are using different settings in the F-16s "Special settings" tab. One of you seems to be using the "clear" option, while the other one has the "tinted" option This setting is reflected in multiplayer, and you can actually see who has what selected. You can replace the texture through the description.lua though, without changing the tint for the F1 view

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