SAM77 Posted April 20, 2014 Posted April 20, 2014 (edited) Using auto start UV26 Test switch is unlocked The UV26 switch is unlocked but not turned on. Edited April 20, 2014 by SAM77 Spoiler Intel i7 14700F | 64GB G.Skill Trident Z5 RGB | MSI RTX 4060 Gaming X 8G | WD Black SN770 2TB | Sound Blaster Audigy RX | MSI B760 Tomahawk WIFI | Thrustmaster T.16000M FCS Flight Pack | TrackIR 5 | Windows 11 Home |
flanker0ne Posted April 20, 2014 Posted April 20, 2014 Yes, the Autostart macro is not updated. SCOPRI DI PIU': https://www.amvi.it/joinus.php DISCORD COMBINEDOPS The Battle Planning Tool
tsumikae Posted April 20, 2014 Posted April 20, 2014 In DCS World\Mods\aircrafts\Ka-50\Cockpit\Scripts, you'll find a LUA file called Macro_sequencies. I think it is the one that drives the auto-start proc. If you are comfortable anough with that, you can edit it and solve the problem. You can even do your own start-up proc.
arkroyale048 Posted April 20, 2014 Posted April 20, 2014 Will this also allow me to set the warning tone on the radar altimeter from 100m to 30m ? Irregular streamer: http://www.twitch.tv/arkroyale048/profile
ajax Posted April 20, 2014 Posted April 20, 2014 It's fairly simple to fix. Make the following changes to {DCSW}\mods\aircrafts\Ka-50\cockpits\scripts\macro_sequences.lua : Original Line 62: {time = 17.828000,device = 22,action = 3011,value = 1.000000}, Line 70: {time = 18.984000,device = 22,action = 3011,value = 0.000000}, Modified Line 62: {time = 17.828000,device = 22,action = 3012,value = 1.000000}, Line 70: {time = 18.984000,device = 22,action = 3012,value = 0.000000},
Flagrum Posted April 20, 2014 Posted April 20, 2014 It's fairly simple to fix. Make the following changes to {DCSW}\mods\aircrafts\Ka-50\cockpits\scripts\macro_sequences.lua : Original Line 62: {time = 17.828000,device = 22,action = 3011,value = 1.000000}, Line 70: {time = 18.984000,device = 22,action = 3011,value = 0.000000}, Modified Line 62: {time = 17.828000,device = 22,action = 3012,value = 1.000000}, Line 70: {time = 18.984000,device = 22,action = 3012,value = 0.000000}, btw, this will be fixed with 1.2.8 1
tsumikae Posted April 20, 2014 Posted April 20, 2014 Will this also allow me to set the warning tone on the radar altimeter from 100m to 30m ? Yes, you should be able to add that as well. It's really a macro, ergo a sequence of commands, so as long as you know how to write the right command you should be fine. I don't, for the record.
SAM77 Posted April 21, 2014 Author Posted April 21, 2014 Cool Its only a tiny issue anyway but its been around for a while Spoiler Intel i7 14700F | 64GB G.Skill Trident Z5 RGB | MSI RTX 4060 Gaming X 8G | WD Black SN770 2TB | Sound Blaster Audigy RX | MSI B760 Tomahawk WIFI | Thrustmaster T.16000M FCS Flight Pack | TrackIR 5 | Windows 11 Home |
Recommended Posts