AndyHill Posted January 31, 2005 Posted January 31, 2005 Since version 1.1 is almost available I think it's about time to start whining and asking for features. I've got a few Lua export requests that would be useful (for me at least) and relatively simple to implement: -Gear up -Gear down -indicator for gear up/down -Autopilot on -Autopilot off -Hook in -Hook out -Radar on -Radar off -EOS on -EOS off -Active jamming on -Active jamming off There are other commands as well, but the general idea is that there should be separate on/off options to make using toggle switches easier. Furthermore I would like to have at least three different levels of RWR info available: radar signal detected, lock detected and launch detected. RWR is one of the systems I'd like to have in peripheral vision all the time and with this data I could build a simple light system for the most important data. My blog full of incoherent ramblings on random subjects: https://anttiilomaki.wordpress.com/
504MrWolf Posted January 31, 2005 Posted January 31, 2005 -PadLock this is spoiling my AirWars online campaign and needed to be adjustable server side. www.VVS504.co.uk www.lockonskins.co.uk
AndyHill Posted January 31, 2005 Author Posted January 31, 2005 Re: Lua export requests for 1.1 Hmm this is not Lua-related, but does Lock on support pedals with toe brakes? I didn't see any options regarding that in the options menu. I'm interested in getting Simped-pedals with brakes and I'd very much like to use them in LO. Is it possible? My blog full of incoherent ramblings on random subjects: https://anttiilomaki.wordpress.com/
chp Posted January 31, 2005 Posted January 31, 2005 2 AndyHill: It's a programming language (yes, yes lua ;) and with help of basic logic and knowleage you can "create" your own "commands" that will turn "a variable" only ON or OFF based on its state (which you can check or track). No toe-brakes mentioned in docs.
AndyHill Posted January 31, 2005 Author Posted January 31, 2005 How exactly do I track the state? This would be very interesting indeed. Autopilot I can get from MCPstate, but how do I get for example radar, ECM, gear or EOS status? To ED: ME WANT TOE BRAKE AXIS FUNCTIONALITY VERY MUCHLY. My blog full of incoherent ramblings on random subjects: https://anttiilomaki.wordpress.com/
chp Posted February 1, 2005 Posted February 1, 2005 On mission start everything (except undercarriage) is in OFF stated. So create your own variables and track ON/OFF/Failure changes ;) Airborne, saved missions (tracks) are rare and unimportant cases.
AndyHill Posted February 1, 2005 Author Posted February 1, 2005 Actually I play a lot of air-start mission in quick battle builder. Tracking the state with my own variables will work ok, but it's only a partial solution. Flaps and gear for example won't lower at too high a speed and I don't know if they're automatically raised if left down until certain speeds are reached. For ECM, EOS, radar and other such devices it should work, I'll just poll every input at startup and ignore those that are set "on" when their state first changes to "off". I would still prefer separate on/off functions as they would be a lot simpler. I want toe brake functionality in Lo! My blog full of incoherent ramblings on random subjects: https://anttiilomaki.wordpress.com/
Dmut Posted February 1, 2005 Posted February 1, 2005 agreed, AndyHill. We need separate functions for every state (SetOn, SetOFF), plus function to get a state. for every device\block. "There are five dangerous faults which may affect a general: recklessness, which leads to destruction; cowardice, which leads to capture; a hasty temper, which can be provoked by insults; a delicacy of honor which is sensitive to shame; over-solicitude for his men, which exposes him to worry and trouble." Sun Tzu [sigpic]http://forums.eagle.ru/signaturepics/sigpic2354_5.gif[/sigpic]
chp Posted February 2, 2005 Posted February 2, 2005 Sure, there is an endless space for wishes and ideas. But unfortunately there is no time to fulfill even 1/3 of them. Developers (PDM at first place) should concentrate on most important things from start to the finish. I dont wanna to say making these export thingies will slow everything down. However a better "productivity" is made from such small things. So, do you really need them or it's just nice to "have them all"? Most likely it's all will be there, but if it woudn't you still can make it (if you reeally want it.. Check alt/speed to set gear on/off, check speed you use gears/flaps, etc.) Have fun
MBot Posted February 2, 2005 Posted February 2, 2005 I want toe brake functionality in Lo! Agree. Best would be with differential braking.
AndyHill Posted February 2, 2005 Author Posted February 2, 2005 Practically yes, I need those functions. If I for example build a warning light for ECM on I either need some way to know when my active jammer is transmitting or I need to connect the light to the switch position. In latter case I really need to make sure the switch works the same way every time. I don't remember if I can get ECM on/off, information, that was just an example. I'm working on switches for many functions and ECM is just one of them. The laser range finder is an interesting system and will require extra care as the system automatically shuts it down when it overheats. Any addition or request is ultimately for ED to consider, we just let them know of nice features we'd like to see. They've already done fantastic job with the export feature and I think they could improve its usefulness a lot with the simple improvements I proposed. I want toe brake functionality with differential braking in Lock on! My blog full of incoherent ramblings on random subjects: https://anttiilomaki.wordpress.com/
Recommended Posts