Mud Posted September 24, 2020 Posted September 24, 2020 (edited) Anyone else have this issue? I have deleted the UH-1 folder in Mods and Bazar/Liveries and then ran a repair. No change. Not running any mods. Br, Mud Edit: Running the latest open beta Edited September 28, 2020 by Mud Spoiler W10-x64 | B650E Gigabyte Aorus Master | AMD Ryzen 7 7800X3D | Noctua NH-D15 G.Skill Trident ZS Neo DDR5-6000 64Gb | MSI RTX 3080ti Gaming X Asus Xonar AE | VPforce Rhino + TM Hotas Warthog MFG Crosswind pedals | Valve Index
Rover Posted September 25, 2020 Posted September 25, 2020 Yea noticed it now, wonder where that texture has gone of to now... Huey. Intel X5660 4,2ghz, 24gb ddr3, gtx 1060 6gb AJS37. Cyborg evo Yak 52. Opentrack ir KA-50 P-47
... Posted October 2, 2020 Posted October 2, 2020 I have the same problem. https://launionescuadron.webnode.es/
Mr.Scar Posted October 6, 2020 Posted October 6, 2020 (edited) Same problem here, saw it yesterday. No mods on my side. Edited October 6, 2020 by Mr.Scar
BaD CrC Posted October 6, 2020 Posted October 6, 2020 I do! https://www.blacksharkden.com http://discord.gg/blacksharkden
Woody01 Posted October 6, 2020 Posted October 6, 2020 Multiple guys reporting this at Choppa Tuesday last night. The Flying Kiwis - Since ages ago... Find us at https://www.simcentral.co.nz
prccowboy Posted October 7, 2020 Posted October 7, 2020 (edited) the problem appears to be that the m261 is pointing to the wrong files: currently the m261 is looking for these files: "m261_diff", "m261_nm", and "m261_diff_roughmet" these files can't be found but the old ones still exist. So until ED fixes this, you can correct this in custom skins by adding the following code to the huey description.lua file: {"M261", DIFFUSE , "m261", true}; {"M261", NORMAL_MAP , "m261_nrm", true}; {"M261", SPECULAR , "m261_spec", true}; Edited October 7, 2020 by prccowboy
Tanuki44 Posted October 8, 2020 Posted October 8, 2020 Thanks for this info :thumbup: Would there be a generic solution for all liveries of UH-1 to avoid modifying files one by one ? I tried to create a description.lua in Saved Games\DCS.openbeta\Liveries\UH-1H but it doesn't work :(
prccowboy Posted October 9, 2020 Posted October 9, 2020 (edited) Thanks for this info :thumbup: Would there be a generic solution for all liveries of UH-1 to avoid modifying files one by one ? ( The only "generic" or global fix I can think of is: copying the aforementioned files (m261.dds, m261_nrm.dds, and m261_spec.dds) and renaming them to the names that the m261 is looking for ("m261_diff.dds", "m261_nm.dds", and "m261_diff_roughmet.dds") then putting them back into the AeroWeapons.zip file - However, This involves modifying core DCS files and I do NOT recommend that, but maybe someone else has a better idea EDIT: Actually, there is another fix which is to create a user files mod that replaces the default textures (without modifying core files). See my post below For me, luckily I only run my own skins, so I was able to make an easy fix Edited November 1, 2020 by prccowboy
prccowboy Posted October 9, 2020 Posted October 9, 2020 I tried to create a description.lua in Saved Games\DCS.openbeta\Liveries\UH-1H but it doesn't work :( Hopefully, ED will fix this soon, but until then: make sure there is a sub folder for each skin name, ex: "Saved Games\DCS.openbeta\Liveries\UH-1H\Army_Std_m261_fix" then put your description.lua in that folder and add the code I mentioned above to the other livery code for that skin. Here is an example of the description.lua for the "Army Standard" livery with the fix included: livery = { {"civ_uh1_main_dam", 0, "civ_uh1", true}; {"civ_uh1_main_dam", 2, "civ_uh1_spec", true}; {"civ_uh1_tail_dam", 0, "civ_uh1_tail", true}; {"civ_uh1_tail_dam", 2, "civ_uh1_tail_spec", true}; {"civ_uh1_main", 0, "civ_uh1", true}; {"civ_uh1_main", 2, "civ_uh1_spec", true}; {"civ_uh1_tail", 0, "civ_uh1_tail", true}; {"civ_uh1_tail", 2, "civ_uh1_tail_spec", true}; {"uh1_main_dam", 0, "uh1_us_army", true}; {"uh1_main_dam", 2, "uh1_spec", true}; {"uh1_tail_dam", 0, "uh1_tail_us_army", true}; {"uh1_tail_dam", 2, "uh1_tail_spec", true}; {"uh1_main", 0, "uh1_us_army", true}; {"uh1_main", 2, "uh1_spec", true}; {"uh1_tail", 0, "uh1_tail_us_army", true}; {"uh1_tail", 2, "uh1_tail_spec", true}; {"uh1_weapon", 0, "uh1_weapon", true}; {"pilot_UH1_01", 0, "pilot_UH1_01", true}; {"pilot_UH1_02", 0, "pilot_UH1_02", true}; {"pilot_UH1_helmet", 0, "pilot_UH1_helmet", true}; {"pilot_UH1_patch", 0, "pilot_UH1_patch_1_cavalery", true}; {"uh1_cov", 0, "uh1_cover", true}; {"UH1-cpt-door", 0 ,"UH1_door_c",true}; {"UH1-cpt_karkas", 0 ,"UH1_karkas_c",true}; {"UH1-cpt_karkas2", 0 ,"UH1_karkas2_c",true}; {"UH1-cpt_panel", 0 ,"UH1_panel_c",true}; {"UH1-cpt_central_box", 0 ,"UH1_boxs_c",true}; {"UH1-cpt_dev2", 0 ,"UH1_dev_2",true}; {"M261", DIFFUSE , "m261", true}; {"M261", NORMAL_MAP , "m261_nrm", true}; {"M261", SPECULAR , "m261_spec", true}; } countries = {"USA"}
Tanuki44 Posted October 9, 2020 Posted October 9, 2020 (edited) For me, luckily I only run my own skins, so I was able to make an easy fix Yes, but in some missions the skins cannot be customized ex: Spring Aparts 2025 :smilewink: @prccowboy Have you received my PM? Edited October 9, 2020 by Tanuki44
Tanuki44 Posted October 9, 2020 Posted October 9, 2020 Besides, copying the aforementioned files (m261.dds, m261_nrm.dds, and m261_spec.dds) and renaming them to the names that the m261 is looking for ("m261_diff.dds", "m261_nm.dds", and "m261_diff_roughmet.dds") then putting them back into the AeroWeapons.zip file - I don't know of a "generic" or global fix. (This involves modifying core DCS files and I do not recommend that), but maybe someone else has a better idea This is arguably the best and fastest way to fix all skins at once. :thumbup:
prccowboy Posted October 9, 2020 Posted October 9, 2020 This is arguably the best and fastest way to fix all skins at once. :thumbup: Although it is fast and easy, I do NOT condone modifying core files :music_whistling:
Tanuki44 Posted October 9, 2020 Posted October 9, 2020 Me too, but it's only temporary until the ED patch... and I always keep an archive just in case :smilewink:
rayrayblues Posted October 14, 2020 Posted October 14, 2020 Hopefully, ED will fix this soon, but until then: make sure there is a sub folder for each skin name, ex: "Saved Games\DCS.openbeta\Liveries\UH-1H\Army_Std_m261_fix" then put your description.lua in that folder and add the code I mentioned above to the other livery code for that skin. Here is an example of the description.lua for the "Army Standard" livery with the fix included: livery = { -snip- Thanks Cowboy, but...the way I look at it is this: I am just an end user. All of that code looks like an alien language to me. It might as well be Klingon. It is not my job to fix their core codes. As others have said, "it is not recommended to tamper with core codes." ED needs to do their job and fix this. I am not going to risk messing up my installation of this game. At 120+ Gb it would take me all day to re-download a new install. Where is BigNewy in all of this discussion? SLAVA UKRAINI MoBo - ASUS 990FX R2 Sabertooth, CPU - AMD FX 9590 @4.7Gb. No OC RAM - GSkill RipJaws DDR3 32 Gb @2133 MHZ, GPU - EVGA GeForce GTX 1660Ti 6Gb DDR5 OC'd, Core 180MHz, Memory 800MHz Game drive - Samsung 980 M.2 EVO 1Tb SSD, OS Drive - 860 EVO 500Gb SATA SSD, Win10 Pro 22H2 Controls - Thrustmaster T-Flight HOTAS X, Monitor - LG 32" 1920 X 1080, PSU - Prestige ATX-PR800W PSU
prccowboy Posted November 1, 2020 Posted November 1, 2020 I am hoping that ED fixes this in the next patch; but if not, I will upload a mod that fixes the problem (small user files mod that replaces the default m261 textures) EDIT: it looks like it was fixed by ED, so no need for me to upload a mod to fix it
Tanuki44 Posted November 5, 2020 Posted November 5, 2020 This seems fixed in yesterday's OpenBeta update, but still no fix for the altimeter setting ...
Recommended Posts