speckfire

Beczl stop making my dreams come true LOL :D

Magnifico !!!!!

OK I see what Mastiff was doing. He's installing the CAW skin pack from lockonfiles. I don't really like the method used to edit graphic config files in order to install skins. It leads to issues like mastiff is having just to save some disk space, but that's my opinion. Good luck!

put up your discription.lua and the corresponding texture names along the path to the texture directory and let's have a looksie

Ok you seem to be confused. There is no need for a graphic.lua or a config.lua to add a skin in DCS world. Ignore all installation instructions of previous game versions. Remember your skins need to be in a dds format. Here is my setup Texture location F:\Eagle Dynamics\DCS World\Bazar\Liveries\su-25t\159th Splinter camo W Inside the "159th Splinter camo W" directory you have the following files. Then you edit the description.lua livery = { {"fuz-center", 0, "SU39-PAINT1-DEF-159.DDS", false}, {"wings", 0, "SU39-PAINT2-DEF-159.DDS", false}, {"SU39-PAINT2bis-DEF-01", 0, "SU39-PAINT2bis-DEF-159.DDS", false}, {"fuz-tail & fin", 0, "SU39-PAINT3-DEF-159.DDS", false}, {"tail & stab", 0, "SU39-PAINT4-DEF-159.DDS", false}, {"brake-L", 0, "SU39-PAINT5-L-DEF-159.DDS", false}, {"brake-R", 0, "SU39-PAINT5-R-DEF-159.DDS", false}, {"fuz-nose-steel", 0, "SU39-PAINT6-DEF-159.DDS", false}, {"SU-39-PILON", 0, "SU39-PILON-PAINT-DEF-159.DDS", false}, {"PILON_2_Su-39", 0, "SU39-PILON-2-PAINT-DEF-159.DDS", false}, {"numbers", 0, "rus-code-numbers-ver1-B-w-W.TGA", true}, {"PylonsSu-25T1", 0, "Su-25TPylon-DEF-159.DDS", false}, {"pylon25lateral", 0, "Lateral25TPylon.bmp", true}, } name = "159th GAR SC W" countries = { "RUS", } False at the end of each line means your texture is in the directory that you created and not in the game's zip texture files under \Bazar\world\... The last 2 lines are texture name that will appear in the editor and what country it belongs to. You should see your skin in the game

In DCS world forget about config.lua, that no longer applies for skins unless you're a masochist ;) You have to create a description.lua file and modify it to reflect the textures you're putting and it should be in the texture folder of your skin. The easiest way to create a description.lua file is to copy one from an existing su25T skin folder and modify it. Also as I mentioned, the folder name that you'll create under /.../bazar/liveries/SU25T is very important because that's going to be your skin name in the mission editor when you select one. In that folder the description.lua file will identify the where your skins will go on the 3d model.

Absolutely, I'm secretly hoping for one.

I hope so. It would be a shame otherwise.

Exactly not the T version !!!!

Can we expect the workhorse of the Russian air force to make a comeback in DCS world?

Yeah sure no problems. I have my squad skin showing up very nicely. Just check your description.lua entries and your textures should be in dds format. Create a folder for the skin under /bazar/liveries/Su-25T and put the textures there.

Looking good Silver

Thanks Shark-bait

Bllllaaaazing a new trail !!!!!! Thanks a lot Blaze :)

Auto what???? Noooooooooooooooooooo !!!!!!

+1000000000!!!!!!!!11111

Great work

Blaze, FCS Heater, great job guys !!!

As Grimes mentioned, there is no need to edit the graphics.cfg file to add skins in DCS world, BS2 or A-10C. All you need is to place the dds textures in the DCS World/Bazar/liveries/(aircraft)/(skin) and edit the description.lua file to reflect your skin names. Make sure you change the "true" at the end of each line identifying your texture name in the lua file to false. That will tell the program to look for the actual skin in the directory you put it in.

Thanks !

Exactly.. What's the point of showing them off?? Unless they want $$$ for them now that the paid option for addons has been implemented in the downloads area ;)

Great work on the F-16. Too bad it's for private use and used to tease ED members. It's freaking cruel :(

Good work Joey :)

LOL good one ENZIFER

Are you on full screen mode? ok try airdog's suggestion. He seem to have the same issue as you. Put back viewporthandeling.lua back to original and add the below code to the end of your SHKVAL_init.lua