TheAviationFox Posted Wednesday at 10:22 PM Report Posted Wednesday at 10:22 PM Thanks for tidying my INI-file! And now we got to the even more interesting part: when I implemented the logging of the LVAR VC_POSITION_LIGHT_SW, the log came back with an error message, saying that this LVAR was unknown to it. Oh dear. I activated Developer mode again and checked the behaviour of the light switch and to my own surprise and shame I had provided you with an incomplete LVAR-name in my first post regarding this topic. It was late night and it slipped through me re-reading the post before submitting it. The correct LVAR is VC_POSITION_LIGHT_SW_VAL. I have now corrected the LVAR name in the INI-file and guess what: your preset code works exactly as advertised. Thank you so much and I apologize for wasting your time by providing an incomplete LVAR, I am embarrassed! Allow me to express my gratitude for your help and patience, top notch user support here!! Thanks John!
John Dowson Posted yesterday at 07:11 AM Report Posted yesterday at 07:11 AM Note that you can see available lvars by listing them (Add-ons=>WASM->List Lvars) - no need to use the MSFS behaviors dialog, except as a last resort (i.e. usually to discover b-vars or h-vars). No problem about the incorrect lvar name - these things happen...! Now you have the correct name, you should check if setting that directly works to control the switch. If so, the assignments can be simplified as you don't need the compound condition on the position of your switches, and you only need to send the one one command to change the lvar two positions instead of three (e.g. switch up, pause, switch up). Anyway, you should try and understand those assignments and try to assign yourself the next time you want to make a conditional assignment. I will help if you run into problems, but you should have enough info in this thread to make a start. Regards, John 1
TheAviationFox Posted 23 hours ago Report Posted 23 hours ago Yes, I have tested the correct LVAR VC_POSITION_LIGHT_SW_VAL in the WASM executor and in fact it only moved the switch, but did not change the lights status. I created that list of LVARs through the WASM-menu, but I personally find the Behaviour Tool better, because I can easier find the switch variables and actually test their functions/values. Obviously I am not proficient enough at actually connecting the dots of these variables, but eventually we will get there. I will keep the Preset that you have created for me, it does the job for me and I am happy!
John Dowson Posted 22 hours ago Report Posted 22 hours ago 50 minutes ago, TheAviationFox said: Yes, I have tested the correct LVAR VC_POSITION_LIGHT_SW_VAL in the WASM executor and in fact it only moved the switch, but did not change the lights status. Ok, that can happen. 51 minutes ago, TheAviationFox said: I created that list of LVARs through the WASM-menu, but I personally find the Behaviour Tool better, because I can easier find the switch variables and actually test their functions/values. Obviously I am not proficient enough at actually connecting the dots of these variables, but eventually we will get there. Thats fine - whatever works for you. Just pointing out that for most things, the various FSUIPC logging facilities should be proficient enough, but you do have to 'connect the dots; as you say. 53 minutes ago, TheAviationFox said: I will keep the Preset that you have created for me, it does the job for me and I am happy! Yes - you need to do it this way anyway if the position lvar only changes the position but not the actual function/lights.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now