NRG-Vampire

Maybe the Exporter does not (yet) but Python and DCS does ;)

:D Hey George, that's not a texture bug that's a very nice feature. :thumbup: Frankly. That's an Ambient Occclusion Texture Shift (shading) for the armour plated parts and for the wing/hardpoint hanger rods :smilewink: Use Arg 458 change that effect, and type it into the corresponding description.lua (possible values: 0.0, 0.1, 0.2 and 0.3) :yes: custom_args = { [458] = 0.3 -- Ambient Occclusion Shift }

Looks nice, but please upload it to the dcs-user-file-skin section too. :thumbup:

nice job :thumbup: however please fix the crashed normals around the windows and on the sidewall of the ship - those are causing the strange shadows and please make animated propellers and rudder, transparent water is coming for dcsw thanks

:smilewink: I hope someone release the J-20 model as well :thumbup:

▲ nice :thumbup: draw over that raf roundel with the u.s. star-roundel till we got the official template imho

was that the former base of your virtual squadron Sawa ? good to know that ;)

Would be nice to win that flightpack because I have never had/used pedals for flightsims :D :joystick: Would be a nice Xmas gift to me :santa: and I like that device, especially the shape of the throttle :thumbup:

pity, this is not funny but true unfortunately there is no other solution yet - for DCS usage

yeah. awesome. nice find :thumbup:

good point :D however in the Spitfire startup tutorial video the Normandy map looked good enough for an early alpha release imho :D

I am wondering maybe the WW2 Normandy map comes tomorrow as well next to the Spitfire ? :bounce:

nice 1 above ▲ but i think we will need this livery as well: :thumbup: of course skin makers will need top and other side view too for correct paint

honestly iv never tried to paint the uh-1h but you are correct :thumbup: i checked the description.luas in the bazar/liveries/uh-1h folders and i see the damage materials also use the fuselage textures (as "false") :thumbup: that will be the problem and MYSE1234 maybe you will need to paint this part too: {"uh1_cov", 0, "uh1-es-un_cover.bmp" ,false};

pretty sure the description.lua file is corrupt just like here: https://forums.eagle.ru/showpost.php?p=2982703&postcount=10 choose a good description.lua file from bazar/liveries/uh-1h copy to your livery folder open with notepad++ and edit/overwrite the texture names with your new texture filenames save it, try it

description.lua was corrupt. badly saved. wrong format. use notepad++ next time and paint1 and paint2 names was swapped on texture files, i changed back multiple places vica versa in the description.lua description.lua :smilewink:

yes this screenshot is not rich in detail and in map options but pretty old. intentionally. sorry.

Try this ;) livery = { {"civ_uh1_main_dam", 0, "uh1.bmp", true}; {"civ_uh1_main_dam", 2, "uh1_spec.bmp", true}; {"civ_uh1_tail_dam", 0, "uh1_tail.bmp", true}; {"civ_uh1_tail_dam", 2, "uh1_tail_spec.bmp", true}; {"civ_uh1_main", 0, "uh1_swe.bmp",false}; {"civ_uh1_main", 2, "uh1_spec.bmp", true}; {"civ_uh1_tail", 0, "uh1_swe_tail.bmp",false}; {"civ_uh1_tail", 2, "uh1_tail_spec.bmp", true}; {"uh1_main_dam", 0, "uh1.bmp",true}; {"uh1_main_dam", 2, "uh1_spec.bmp",true}; {"uh1_tail_dam", 0, "uh1_tail.bmp",true}; {"uh1_tail_dam", 2, "uh1_tail_spec.bmp",true}; {"uh1_main", 0, "uh1_swe.bmp",false}; {"uh1_main", 2, "uh1_spec.bmp",true}; {"uh1_tail", 0, "uh1_swe_tail.bmp",false}; {"uh1_tail", 2, "uh1_aah_tail.bmp",true}; {"uh1_weapon", 0, "uh1_weapon.bmp",true}; {"pilot_UH1_01", 0, "pilot_UH1_01.bmp", true}; {"pilot_UH1_02", 0, "pilot_UH1_02.bmp", true}; {"pilot_UH1_helmet", 0, "pilot_UH1_helmet.bmp", true}; {"pilot_UH1_patch", 0, "pilot_UH1_patch_.tga",true}; {"uh1_cov", 0, "uh1-es-un_cover.bmp",true}; {"UH1-cpt-door", 0 ,"UH1_door_c_gray",true}; {"UH1-cpt_karkas", 0 ,"UH1_karkas_c_gray",true}; {"UH1-cpt_karkas2", 0 ,"UH1_karkas2_c_gray",true}; {"UH1-cpt_panel", 0 ,"UH1_panel_c_gray",true}; {"UH1-cpt_central_box", 0 ,"UH1_boxs_c_gray",true}; {"UH1-cpt_dev2", 0 ,"UH1_dev_2",true}; {"uh1_rotor_alfa",0,"uh1_swe_blade.tga",false}; } name = "Swedish Airforce" --countries = {"USA"} --> skin will be visible for all/any countries

would be good to know how looks your deficient skin. it's important. (sometimes PS save/export able to screw up textures) so is that the greenish missing texture on it ? or is it white/light gray, or maybe black/dark gray ? or send me the texture files and I will fix it to you. ;)

If you ignore countries line -- (like this▼) then that skin will be usable for any/all countries. -- countries = {"RUS",}

Please name the files/textures what you are using for your new skin. Where did you put those files ? Into a zip file or where the description.lua is placed ? (use "false" only for your new files if you put next to description.lua) Show some screenshots of your (faulty) skin. A modelviewer or an in-sim image would be good.

all of those skins are compatible with latest and with future versions as well but need some correction in description.lua and correct texture files (correct dx5 alpha channel with correct darkness of it for glass parts/materials) https://forums.eagle.ru/showpost.php?p=2975921&postcount=7

Hi guys please post your exact version number and the description.lua livery file of your skin what cause that canopy texture problem. One more: check ALL of your "installed" user file F-16A/MLU/Block50/Block52 description.lua files. If you see this line then it's the guilty: {"texture F-16.tga f2 g0",0,"f-16-glass.bmp",true} !!! "true" if the texture used from a zip file of from a pre-definied folder/user-zip or from the bazar/temptextures folder "false" if the texture is located in the folder where the associated description.lua file placed f-16-glass.bmp.dss !!! is corrupt. It can cause wrong canopy texture look on factory skins too !!! (if you used the corrupt livery earlier - with the corrupt canopy-glass texture) check texture file in the bazar/temptextures folder as well https://forums.eagle.ru/showthread.php?t=168074

think about on it a bit guys angled deck on carriers is for safety BUT to avoid similar cable snap situations perhaps they should consider this: especially by the russain navy - they operate aircrafts on a nearly (or completely) empty deck landing and take off as well SO image this: on carrier with ski jump if the aircaft approaches and lands on a perfect longitudinal axis of the ship, and one of the wire snaps at close to zero speed of the aircraft then it will be able to take off again - there will be more or less enough distance for a take off emergeny run on the deck towards to that ski jump with an agled deck landing this re-fly wont be able of course this theory will needs redesigning the cable systems and the carrier safety/operating patterns and orders as well (and maybe new wider carriers too) maybe on flat deck us/french carriers as well ...my 2 cents brainstorm ;)