General Category > Unofficial F/A-18 Acceleration Pack board
vLSO Alpha Release
SpazSinbad:
Last font - third - one in that lot of three looks best IMHO.
Paddles:
--- Quote from: capthaltli on August 30, 2011, 04:43:31 pm ---One idea I had was to have a trigger or button in FSX that acts as a cue for calling the ball. This would replace the vLSO saying call the ball, which is not NATOPS case 1 ops. Once you see the ball in fsx press some TBD button, call your side number, ac, fuel state, and the program would recognize the trigger (FSX button) and respond roger ball. If you didn't make the call inside .6 miles you would get a wave off, or we could have a Clara call button, but that is probably overkill. Anyways just thought to make the calls more realistic, see the ball and the make the call, not wait for the auto trigger "call the ball".
--- End quote ---
Capt,
What we really miss in FSX is the player-game interaction. Unfortunately all that we can use are few free FSX functions. But as I have already mentioned, the need to assign a (joystick or keyboard?) button to an FSX command/function would significantly limit the player and/or FSX. What if that FSX command is already assigned and used by the player's aircraft?.. So, all we can do is to simulate or mimic real life interaction to a certain extent.
Currently there's a trigger area in my test mission(s) which is located in front of 'the start' position. When you fly through this 'window', the program starts recording your approach data. Then it issues 'call the ball', after that it shows your 'ball call' with your side number, ball and fuel state. Sure, it always says BALL, never CLARA, because the program has no idea whether you actually see the ball or not. :) Finally, the program says 'roger ball' and shows a message with this text and current WOD.
It is possible to programmatically determine Case 1-3 conditions, thus disable 'call the ball' if it is Case 1. Additionally, the program could show appropriate 'CASE I(II) Approach' text message to inform the pilot when he starts another approach.
GOONIE:
Serge,
Looking good. I personally like the third text format "Sean", IMHO. Maybe use this text to only fill in the cells (where the LSO writes), and change the coloumn headers (titles) to normal text.
As for the FSX "call the ball" trigger I agree it would be great to make this manual (through an assigned button) and not automatic for Case I Ops, but understand it would take away a FSX command and a joystick allocation. Although, I would be willing to give up one or two buttons to call the ball or CLARA at 3/4 of a mile to trigger the vLSO "roger ball" and scoring program, and this would include the risk being waved off if I did not make this call before passing 3/4 mile. I could see the trigger working two ways; one you see the ball, hit the button on your controller (trigger's virtual ball call) then the vLSO says "roger ball" and then works as normal. The second scenario, is you hit another button for CLARA, and the vLSO would not respond roger ball, but instead give you a glideslope call (e.g. on glideslope, your high, your low, etc.).
Sometimes in the 2D HUD mode when I am rolling into the groove, the LSO says call the ball before I can actually see it (still in the turn). Does this happen to anyone? Any tips? Not a big issue, but it would be cool to control calling the ball to when I actually see it and have good info for glideslope control.
Anyways I like the way the program works for CASE I, much better than anything out there, just wanted to share this idea.
As for CASE III, I think the scoring program could remaining the same (LSO scores inside 3/4 mile), but the mission could start by sending you to a marshall stack for holding, then clear you for the approach. The pilot would be responsible for holding in marshall, then hitting the platform altitude at various stages (see attached graphic) while getting setup for the approach. Triggers could be setup in the mission for calls like "say needles, concur mode x", "dirty up", etc. Also when you get to 3/4 of mile the vLSO could work as it does now, since you normally get the "call the ball" for CASE III (I think).
-CAPT
Paddles:
Guys,
just curious what's the size of your Logbook.dat file (placed along with the vLSO.exe in the same folder) and how many attempts are registered in the logbook?
Thanks
GOONIE:
428kb, and about 40-50 traps (hard to count,maybe a #column would help)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version