Lua file will not use user skin _Bomb Rack - HB_F14_EXT_BRU_34

[Elwood_Blues]

Okay, I have skinned stuff before..but I cannot get this file to work in the F-14B lua file.

Everything else works fine..but no matter what I do it will not accept the false statement in the Lua and will no matter what..pull the texture from the ordinance folder. 

If I swap out the skin I made for the one in the ordinance folder using the same name..it works fine..but then ALL F-14Bs use it....any suggestions of how, what, or why this is happening and how do I fix it?

Elwood

[LanceCriminal86]

1 hour ago, Elwood_Blues said:

Okay, I have skinned stuff before..but I cannot get this file to work in the F-14B lua file.

Everything else works fine..but no matter what I do it will not accept the false statement in the Lua and will no matter what..pull the texture from the ordinance folder. 

If I swap out the skin I made for the one in the ordinance folder using the same name..it works fine..but then ALL F-14Bs use it....any suggestions of how, what, or why this is happening and how do I fix it?

Elwood

The name of the texture may not be the name of the material on the jet. It's not always 1:1. You'd need to do the LUA export in model viewer but that function may have been broken recently.

[Elwood_Blues]

I used the Model Viewer to find the part....The F-14B lua file does not pull it.. it is put on automatically from what I see.

My problem is where is this file getting its marching orders to go on the plane?

I can paint it red, copy and overwrite the one in the Ordinance folder...and it uses it. But then it is global for all F-14B's.

But I cannot find the code or command line that tells it to do this.

No other texture/skin on this AC does this....its frustrating.

 

[LanceCriminal86]

These are what I have from an old skin for the BRU-42 and BRU-34

 

{"HB_F14_EXT_BRU-34", 0 ,"HB_F14_EXT_BRU_34",false};
{"HB_F14_EXT_BRU42", 0 ,"HB_F14_EXT_BRU42",false};

 

Just verified again, this does work. Like I said, some material names don't match the texture name. The material on the jet is BRU-34 but the texture is BRU_34. I'm looking at a painted BRU-34 on my jet in Model Viewer right now from an old skin I made. In Model Viewer you can use the Connector Tool to mount the BRU-34, you then have to select the BRU-34 in the "Scene" dialogue by clicking the loaded BRU-34 model, then using the livery tool to again select your skin.

Edited March 9, 2023 by LanceCriminal86

[Elwood_Blues]

Hmmm..Mine is HB_F14_EXT_BRU_34.....the rest is the same...in the Ordinance folder it is the same as what I typed....I will change it and see if is a syntax issue..been looking at the loa code till my eyes crossed....and it is funny..ALL the other textures in the ordinance file work fine EXCEPT THIS ONE!!!  AAAHHHHH!!

{"HB_F14_EXT_BRU_34", 0 ,"WP_F14_EXT_BRU_34",false};

Going to rename the Ordinance to your HB....-34..see if it works...then try a few other things....

It is my Bru 34 file...the 42 works fine.

Thanks for any and all input/help..will post what I find out for future references

Elwood

 

Edited March 10, 2023 by Elwood_Blues

[Elwood_Blues]

OKAYYYYYY!!!   

Changed the ORIGINAL file in the ordinance folder to -34 instead of _34 and THAT was it....Why....I don't know why it works now when before when I named MY file the same name it worked..but globally...but with the -34 it now lets the lua decide...WOW...I hate code.....LOL

Thanx for the tips and hints  guys!

 

Elwood

[LanceCriminal86]

You missed what I said then: In each line of the LUA for a livery, there are a few components:

{"HB_F14_EXT_BRU-34", 0 ,"HB_F14_EXT_BRU_34",false};

 

"HB_F14_EXT_BRU-34"

The first portion is the material in the model. This is what I was telling you, it is not the same as what the texture file was, it's where the texture file is going to get slapped on the model. In your case, it doesn't work because the MATERIAL in the model is not called BRU_34, it's BRU-34.

 

0

This is telling it which material type the texture is, in this case it's the diffuse, or the color/paint.

 

"HB_F14_EXT_BRU_34"

This is telling it the name of the TEXTURE file that's in your custom livery folder. You can actually name that whatever you wanted technically, as long as it's in your livery's folder and has the same name. Note that it doesn't contain .DDS or anything.

 

false

This is telling DCS to load the file that's in your livery folder instead of the default texture inside the module in F14/Textures/Diffuse_Roughmet or whatever the folder is.

 

Why are you overwriting the defaults in the ordnance folder?

 

 

[Elwood_Blues]

I took the original textures out of the ordinance folder and made new ones and put them into the aircraft folder, this way the aircraft files/textures are all self contained, modified the lua and all was good...

I had to search for certain AC components like the BRU, Lantirn pylon etc so skin them for the AC...found them and I copied the textures as they were labeled in the ordinance folder..
ALL TEXTURES WORKED except this one.
That was my conundrum....I could not figure out why or find the proper syntax or file that explained why it worked for everything else but this one file.

When you showed me your file name, I changed the original file name to -32 in the ordinance folder and in the lua file and it worked fine.

I understand all you said...

I did not overwrite any file in the ordinance folder except for testing purposes. 
The filename in my ordinance folder was _32   NOT -32.
I copied and pasted the files to alter the skin..I keep the same names. Hence why I was frustrated.

It is just odd that the file name, regardless of being the same in the lua code as in the ordinance folder with a false statement would not pull my skin. It had to have the -32....

 

Thanx for checking on your files and that is something I always find useful when trying to fix things.

 

S!!

 

Elwood

 

Edited March 10, 2023 by Elwood_Blues

[LanceCriminal86]

26 minutes ago, Elwood_Blues said:

I took the original textures out of the ordinance folder and made new ones and put them into the aircraft folder, this way the aircraft files/textures are all self contained, modified the lua and all was good...

I had to search for certain AC components like the BRU, Lantirn pylon etc so skin them for the AC...found them and I copied the textures as they were labeled in the ordinance folder..
ALL TEXTURES WORKED except this one.
That was my conundrum....I could not figure out why or find the proper syntax or file that explained why it worked for everything else but this one file.

When you showed me your file name, I changed the original file name to -32 in the ordinance folder and in the lua file and it worked fine.

I understand all you said...

I did not overwrite any file in the ordinance folder except for testing purposes. 
The filename in my ordinance folder was _32   NOT -32.
I copied and pasted the files to alter the skin..I keep the same names. Hence why I was frustrated.

It is just odd that the file name, regardless of being the same in the lua code as in the ordinance folder with a false statement would not pull my skin. It had to have the -32....

 

Thanx for checking on your files and that is something I always find useful when trying to fix things.

 

S!!

 

Elwood

 

 

Okay, for a moment I thought you were still trying to overwrite stuff in the Ordnance folder. Makes sense now. Yeah you can name the texture whatever you want you just have to make sure it matches the LUA and that the material name is right.

 

For those curious early in the paint kit thread there was a dumpout of all the LUA options for the various external parts. There may be parts in there that even the model viewer tool wouldn't dump out. I believe it was a few pages in.