edineygomes Posted May 24, 2019 Posted May 24, 2019 RB-05A is not working in Luft mode Does not explode within 6 meters of target. Proximity sensor is not working from what I noticed.
theOden Posted May 24, 2019 Posted May 24, 2019 (edited) Worked fine last time I tried against an Antonov. Are you on open beta maybe? (or should I try again, was a while) Edit: Nope, you're correct. In the missile definition there is "KillDistance = 0.0," so if you switch that one to "6.0" it will work. I guess this is a design choice since the missile should use different values depending on your selection in cockpit but is probably out of scope for the DCS engine. Since LUFT and MARK detonates the fuse by proxy and only SJÖ is penetrating the target before going poff I personally choose to use "KillDistance = 6.0," in my updated version of "DCS World\CoreMods\aircraft\AJS37\Entry\Weapons.lua" (now at a total of 56 edits, many for looks only but a substational number of warhead/range/weights and other corrected values). If you choose to edit your copy too remember to keep the original to restore when going multiplayer - I've even created a csharp application to restore/update weapons.lua since over 50 values is a bit much to keep track off manually each DCS update. Edited May 24, 2019 by theOden tests done [sIGPIC][/sIGPIC]
edineygomes Posted May 24, 2019 Author Posted May 24, 2019 Worked fine last time I tried against an Antonov. Are you on open beta maybe? (or should I try again, was a while) Edit: Nope, you're correct. In the missile definition there is "KillDistance = 0.0," so if you switch that one to "6.0" it will work. I guess this is a design choice since the missile should use different values depending on your selection in cockpit but is probably out of scope for the DCS engine. Since LUFT and MARK detonates the fuse by proxy and only SJÖ is penetrating the target before going poff I personally choose to use "KillDistance = 6.0," in my updated version of "DCS World\CoreMods\aircraft\AJS37\Entry\Weapons.lua" (now at a total of 56 edits, many for looks only but a substational number of warhead/range/weights and other corrected values). If you choose to edit your copy too remember to keep the original to restore when going multiplayer - I've even created a csharp application to restore/update weapons.lua since over 50 values is a bit much to keep track off manually each DCS update. Hmmmm. I edited the file, however, it disappeared all the viggen's weapons in the selection screen of the mission editor
edineygomes Posted May 24, 2019 Author Posted May 24, 2019 try this one. It worked. Was it because I used the notepad that disconfigured the .lua file? I hope developers correct this problem with the proximity sensor in this missile. I'm doing a mission where you must take down the enemy transport with this weaponry, but without the correct adjustments, it will be difficult for anyone who enters the multiplayer to fly with the viggen. Thank you very much.
Holton181 Posted May 25, 2019 Posted May 25, 2019 Was it because I used the notepad that disconfigured the .lua file? Might have been. Use Notepad++ instead. Helicopters and Viggen DCS 1.5.7 and OpenBeta Win7 Pro 64bit i7-3820 3.60GHz P9X79 Pro 32GB GTX 670 2GB VG278H + a Dell PFT Lynx TrackIR 5
Recommended Posts