RafaleC_77th Posted March 4, 2014 Posted March 4, 2014 Hey guys, I've been trying my hand at workin on some Su-33 skins where the bort numbers are removed. And I am having all kinds of issues with it. I have edited the description lua every which way. I used the T10k livery description as an example to work with for the description in my own Livery folder. I have been successful in the removal of the numbers themselves but the area in which the numbers are displayed are still showing a default texture. Do any of you have ideas on what can be done? I had already looked at the A-10C and P-51 threads for their examples. Those got me this far but nothing seems to be working for those bort number display areas. Here is what I got done so far.
Crashmo Posted March 7, 2014 Posted March 7, 2014 bort #s I don't have a perfect answer for you, but I remember the bort numbers belonging to the texture files. Look into Belsimtek and the Huey. Look into skins threads, someone was talking about how to make a squadron of successive bort number aircraft. There may be some info there. I have moved bort numbers around on some BlackShark skins. I'll take a look and see if I remember anything from a year ago. If I find something, you'll hear from me back here.
RafaleC_77th Posted March 8, 2014 Author Posted March 8, 2014 Thanks for replying. I would like to thank you for your response, I had thought I was overlooked or something. I will try another approach with this skin. I will try to see if I can atleast replace one of the existing skins already there for the Su-33. It maybe that the Bort Number material reference in the description lua is related to the default textures. If it works it'll be something I can work with.
Iberian Posted March 8, 2014 Posted March 8, 2014 The file with texture for the numbers, make transparent and of the same dimension in photoshop. [sIGPIC][/sIGPIC]
RafaleC_77th Posted March 11, 2014 Author Posted March 11, 2014 Thanks for assistance For the few that assisted me I want to say thank you. I think I have resolved this particular issue for now.
Recommended Posts