Gunz Posted February 19 Posted February 19 Can someone please explain this in plain simple English? Are we now supposed to request the ground crew to configure the laser codes before takeoff, rather than rely on the default configured 1688? I have several custom loadouts developed in ME with default code 1688.. nullnull
Wyvern Posted February 20 Posted February 20 This should explain it! I have 600GB in skins in my Saved Games. 200GB of that is probably made by myself. Check out my DCS UserFiles section Join the Official Deka Ironwork Simulations discord server!
Gunz Posted February 20 Author Posted February 20 18 minutes ago, Wyvern said: This should explain it! Awesome.. Thanks a ton. That surely explained it a lot better
zetetic Posted March 8 Posted March 8 (edited) BRM laser guided rockets doesnt see a laser spot at all. Any info about fixing? Edited March 8 by zetetic HYPERPC LUMEN_MSI RTX 5070 Ti VENTUS_AMD Ryzen 7 9800X3D_MSI MAG X870 TOMAHAWK_DeepCool LE360 V2_G.SKILL TRIDENT Z5 DDR5 6400MHz, 2x32GB_2TB Samsung 9100 PRO_1000W DeepCool_Microsoft Windows 11 Home
whisky.actual Posted March 9 Posted March 9 6 hours ago, zetetic said: BRM laser guided rockets doesnt see a laser spot at all. Any info about fixing? You need to manually setup the code in the loadout page using the yellow tab in the top left corner
zetetic Posted March 9 Posted March 9 (edited) 4 часа назад, whisky.actual сказал: You need to manually setup the code in the loadout page using the yellow tab in the top left corner The codes are same in pod and BRM (1688). Your BRM rockets working properly? Edited March 9 by zetetic HYPERPC LUMEN_MSI RTX 5070 Ti VENTUS_AMD Ryzen 7 9800X3D_MSI MAG X870 TOMAHAWK_DeepCool LE360 V2_G.SKILL TRIDENT Z5 DDR5 6400MHz, 2x32GB_2TB Samsung 9100 PRO_1000W DeepCool_Microsoft Windows 11 Home
zetetic Posted March 9 Posted March 9 (edited) В 20.02.2025 в 01:20, Alpha_Mo66 сказал: Can someone please explain this in plain simple English? Are we now supposed to request the ground crew to configure the laser codes before takeoff, rather than rely on the default configured 1688? I have several custom loadouts developed in ME with default code 1688.. nullnull The reason of problem was because POD point must be changed in Configuration Panel from -1 to 1688 as well. Too strange and not friendly idea. What is -1 and for at all? But interesting that GBUs are working properly, when TPOD has -1 parameter! Edited March 9 by zetetic HYPERPC LUMEN_MSI RTX 5070 Ti VENTUS_AMD Ryzen 7 9800X3D_MSI MAG X870 TOMAHAWK_DeepCool LE360 V2_G.SKILL TRIDENT Z5 DDR5 6400MHz, 2x32GB_2TB Samsung 9100 PRO_1000W DeepCool_Microsoft Windows 11 Home
olistotch Posted April 27 Posted April 27 The laser code of a random hardpoint can change to -1 after pickle press, even if it was set correctly and checked at the ground. Some missions with start in the air (i.e. the quck mission for BRM's) have -1 code from the start, though it's correct in the mission editor.
Recommended Posts