That is pretty impressive. I am not sure if I've been too busy to see that, or went a different path due to a singular past experience... One issue I had once dealt with the time it took for the information to arrive (for example, my "Damage Report" command), being that it would update too late. I see you have a timer and a check to be sure the action occurs. Very sweet! Definitely going to revisit this for at least other functions I see that I was previously unable to create without live status variables.
I am always impressed with the different methods we all use, and I think I'll play around with the EDDI status variables some more now. I do keep things a certain way so that the base profile actually functions without EDDI, all the commands in the BASIC category function similarly, with a heavy focus on multiple syntax variation, so I can nearly forget how to specifically call a command and just speak conceptually, using every variation I can imagine and adding more when I say something that does NOT fire a command. haha! EDDI and VA have been a source of endless joy in that regard, so thanks a bunch to you all!
In VR, I hate alt-tabbing to VA, so my debug lets me record any errant command to a log that I can fix later, so that's the bit at the top, and plenty of standard commands work better with prefix/suffix sets, but here's how I do landing gear in a non-suffix version - again so fun to see how we all do things differently and reach similar functions:
I am always impressed with the different methods we all use, and I think I'll play around with the EDDI status variables some more now. I do keep things a certain way so that the base profile actually functions without EDDI, all the commands in the BASIC category function similarly, with a heavy focus on multiple syntax variation, so I can nearly forget how to specifically call a command and just speak conceptually, using every variation I can imagine and adding more when I say something that does NOT fire a command. haha! EDDI and VA have been a source of endless joy in that regard, so thanks a bunch to you all!
In VR, I hate alt-tabbing to VA, so my debug lets me record any errant command to a log that I can fix later, so that's the bit at the top, and plenty of standard commands work better with prefix/suffix sets, but here's how I do landing gear in a non-suffix version - again so fun to see how we all do things differently and reach similar functions:
Code:
//Command: "[deploy;extend;extent;lower;raise;retract;toggle;] [the;the landing;landing;] gear [down;up;]"
//Using bindED plugin for VA/ED
Begin Boolean Compare : [AVCS_Debug_ON] Equals True
Set Text [~AVCS_Script_Version] to '4.04'
Append, '{TIMESTAMP}v{TXT:AVCS_Version_Full}{TXT:AVCS_Version_Date} - {CMD} - sv{TXT:~AVCS_Script_Version}{NEWLINE}' to file '{VA_APPS}\AVCS\log.txt'
End Condition
//
Begin Text Compare : [{CMDSEGMENT:0}] Contains 'toggle'
Press variable key(s) [edLandingGearToggle] and hold for 0.05 seconds and release
Pause a variable number of seconds [AVCS_VP_Keystrokes]
Begin Boolean Compare : [AVCS_Macros_ON] Equals False
Say, '{TXT:TTS_COMMON_ActionDone}'
End Condition
End Condition - Exit when condition met
//
Set Text [~down] to 'deploy extend extent lower down'
Begin Condition : ([{CMDSEGMENT:0}] Does Not Equal '' AND [~down] Contains '{CMDSEGMENT:0}') OR ([{CMDSEGMENT:3}] Does Not Equal '' AND [~down] Contains '{CMDSEGMENT:3}')
Begin Boolean Compare : [AVCS_GearDown] Equals False
Press variable key(s) [edLandingGearToggle] and hold for 0.05 seconds and release
Pause a variable number of seconds [AVCS_VP_Keystrokes]
Set Boolean [AVCS_GearDown] to True (save value to profile)
Begin Boolean Compare : [AVCS_Macros_ON] Equals False
Say, '{TXT:TTS_COMMON_ActionDone}'
End Condition
End Condition - Exit when condition met
Begin Boolean Compare : [AVCS_Macros_ON] Equals False
Say, '{TXT:TTS_TOGGLES_Power_LandingGearAlreadyDown}'
End Condition
End Condition - Exit when condition met
//
Set Text [~up] to 'raise retract up'
Begin Condition : ([{CMDSEGMENT:0}] Does Not Equal '' AND [~up] Contains '{CMDSEGMENT:0}') OR ([{CMDSEGMENT:3}] Does Not Equal '' AND [~up] Contains '{CMDSEGMENT:3}')
Begin Boolean Compare : [AVCS_GearDown] Equals True
Press variable key(s) [edLandingGearToggle] and hold for 0.05 seconds and release
Pause a variable number of seconds [AVCS_VP_Keystrokes]
Set Boolean [AVCS_GearDown] to False (save value to profile)
Begin Boolean Compare : [AVCS_Macros_ON] Equals False
Say, '{TXT:TTS_COMMON_ActionDone}'
End Condition
End Condition - Exit when condition met
Begin Boolean Compare : [AVCS_Macros_ON] Equals False
Say, '{TXT:TTS_TOGGLES_Power_LandingGearAlreadyUp}'
End Condition
End Condition - Exit when condition met
//
Last edited: