Missing Ka-50 textures in Death Valley mission? (v1.2.3)

[zarqa]

Hi all, just upgraded from stand-alone BS2 to DCS World 1.2.3 and have been trying to set it up.

 

In the Death Valley stand-alone mission for the Black Shark module, as soon it loads up I get two Ka-50s directly ahead with the orange "missing texture" texture. Does anyone else get this or have I corrupted my install already?

 

Extra info: I have been editing config files (with notepad++) and trying some graphics tweaks (i.e. overwriting stuff in bazar/effects), so that could have broken something, but I ended up reverting those from a backup so I'm at a bit of a loss

[zaelu]

what skin it supposed to be? Check mission file. Look in that skin directory what it contains and check the description.lua from it to see if it points to main missing textures.

 

in DCS folder/Config/graphics.cfg

 

you should have a line that says:

 

path = ".\\Bazar\\World\\textures\\Ka-50_general";

 

in

 

VFSTexturePaths

 

zone

 

but no main skin file is in there

Edited March 27, 2013 by zaelu

[zarqa]

Ok, so I opened the .miz file for Death Valley and most of the Ka-50s are fine: they have the "Russia Standard Army (Worn)" livery, which is in the "bazar/liveries/ka-50" folder.

 

However, one Ka-50 has the livery "standard" and another has "standard (faded)". I can't find either of these in "bazar/liveries/ka-50" for DCS World, but they both exist for BS2 stand-alone. I've attached the description.lua files from the BS2 liveries in case that helps. Any ideas?

 

EDIT: Sorry, just read the rest of your post. The description.lua's reference a lot of textures which don't seem to be in "Ka-50_general.zip". E.g. "KA-50-PAINT4-DEF-01.bmp" is in the .lua but the closest things in "Ka-50_general.zip" are "ka-50-paint3_n-c.bmp.dds" and "ka-50-paint3_n-c_1.bmp.dds". Just copying over the "standard" and "standard (faded)" livery folders from BS2 into DCS World had no effect.

description_standard.lua

description_standard (faded).lua

Edited March 27, 2013 by zarqa

[ajax]

I believe the reason the orange skin shows up is that not all necessary files are packaged in the default skin: ".\Bazar\World\textures\Ka-50_general.zip"

 

If you open the zip file you will notice that the following files are missing:

 

ka-50_st_paint1.bmp.dds

ka-50-lrm_b.bmp.dds

ka-50-lrm_centre.bmp.dds

ka-50-lrm-1.bmp.dds

ka-50-lrmpart-1.bmp.dds

ka-50-paint1-def-01.bmp.dds

ka-50-paint1-def-02.bmp.dds

ka-50-paint1-def-03.bmp.dds

ka-50-paint1-def-04.bmp.dds

ka-50-paint1-def-05.bmp.dds

ka-50-paint1-def-06.bmp.dds

 

These are the same files that show up in the error log as missing textures.

 

I fixed my orange skin problem by copying these files from the "standard army" skin and including them in the zip file.

[zarqa]

Success!

 

I've attached a corrected image of the Ka-50s.

 

After some tinkering I think I've figured out what's happened: Between BS2 and DCS World the livery folders got restructured and renamed. E.g. "standard (faded)" was renamed to "Russia Standard Army (Worn)" (textures were taken from "WorldTexturesBMP3.zip", but that's a whole other story). It seems that most units in the Death Valley mission file had their liveries renamed, but a few got overlooked.

 

A hacky way to fix them is to duplicate and rename the new DCS World liveries so that "Death Valley.miz" can find the old folder names it's looking for:

"Russia Standard Army" => "standard"

"Russia Standard Army (Worn)" => "standard (faded)"

 

Ideally though, you could edit "Death Valley.miz\mission":

 

Change line 5084 from

["livery_id"] = "standard (faded)",

to

["livery_id"] = "Russia Standard Army (Worn)",

 

and line 5125 from

["livery_id"] = "standard",

to

["livery_id"] = "Russia Standard Army",

 

Anyone know how to contact ED so I can ask them to update the .miz file for all players?

 

 

 

---------

I also found out that editing "Ka-50_general.zip" is a bad idea with fun results (see other image) :-)

[zaelu]

I'm glad you solved it.

 

I think the Richardo Blue HD cockpit mod has some fixes for some default schemes... I never wondered what they fixed but maybe this is what they did. I never played the campaign so I didn't encountered this bug.

[Nate--IRL--]

The Fix for this is to simply resave the Miz in the current version of the Mission editor IIRC.

 

Nate