Paddles,
Very nice work as usual!
Can I add additional "Marshall" sound files using the same file naming structure? For example would it be 1mile_.wav, or 1mile_1.wav or 1mile1.wav? If I wanted different calls at 1 mile.
No, the program currently uses only 1mile.wav. All others are just renamed alternatives. Should I use the same technique as with LSO calls, i.e. random selection?
Not critical, I was just thinking if you used the same technique as the LSO calls, I could add some "discontinue approach take angles 1.2" calls from the recent PLAT cam footage I have. I could add these files to the Marshall calls folder, and they would be randomly called.
Did a test flight last night in the VRS F/A-18E, couple things to report:
- I mainly use the manual ball and clara call feature, and when I hit the manual ball trigger now I hear the "ball" audio play, and then immediately get a the "roger ball". In the old vLSO implementation you didn't hear the virtual pilot call "ball", and the timing delay allowed for you to say "Rhino ball, 6.9" before vLSO called "roger ball". Is there a way to go back to the old manual ball call feature and timing? I deleted the "ball" calls from the LSO sound folder which solved the audio piece, but the timing is too fast following the manual trigger to make a normal ball call.
- The manual ball call works (vLSO recognizes the trigger) on the first pass, but on every other pass when I hit the manual ball call trigger I get no joy from vLSO. If I hit the manual Clara call on the second or third pass, vLSO recognizes it and then I can hit the manual ball and it works. Not sure what is going on here, but I tried this a few times and had similar results, first pass works on manual ball call, subsequent passes do not work with manual ball call unless clara is hit first.
- Does vLSO give you a WO call if you don't call the ball (when in Manual mode)? Got a WO call and was not sure why, could have been a bad trend in my approach or linked to the manual ball call issue I am having.
- Auto ball calls work fine with the program so far.
- Got a lot of "don't settle" calls, but see that you are working this based on your latest post, thanks!
- Got a WOP call with a bad approach, very cool!
- After a bolter the vLSO doesn't select random new audio files from the LSO sound folder, is that hard to change?
- If you get the ATC monitor feature to work, another cool feature would be to monitor the state of the aircraft external lights. After you trap at night, if you do not turn off the lights within 3-4 seconds, vLSO could call "lights" or "lights on deck". I have both of these LSO calls.
GOONIE