General Category > Unofficial F/A-18 Acceleration Pack board
vLSO Beta release
pyroperson87:
Not necessarily. Grading a pass at the boat involves a plethora of factors and an OK 1 while it would be rare, is not impossible to achieve. Same for the 4 wire.
At the boat they aren't always targeting the 3rd wire. The air boss and mini boss determine what wire they will be targeting based on a number of factors as well. If you watch the PBS mini-series "Carrier" you will see the boss call out that for that recovery cycle they are targeting the 2 wire for traps.
AndiGelaendi:
Thanks - yes, the approaches looked OK but I was just wondering because of the 1-wire-grading. But in that case this grading from the vLSO should be okay - it's just the Case 3-issue then, that needs to be fixed.
AndiGelaendi:
Another update: I've flown some night-passes and called the Ball a little bit later than I normally do at Case 3 (normally I call the ball directly after the command "Call the ball"). By that way I was able to get several OKs and I got even an OK-underlined for a perfect pass (is night-time a complicating factor or why did I get this OK-underlined?). If using auto-ball-call then the ball-call is done directly after the command "Call the ball" (which should be the right way to do this at Case 3 I would assume) which seems to lead to this Long-in-Grove-Error although there is no LIG-comment in the Logbook at Case 3. So this is a workaround that is acceptable for the moment but it only works with manual-ball-call (but I always use manual-ball-call so for me that is not a problem but maybe for other pilots) and it needs some waiting-time between the command "Call the ball" and pressing the ball-button, which seems to be unrealistic, so I would still appreciate if that could be fixed soon.
Habu:
Using vLSO 8.2.4, I consistently get Access Violation vLSO.exe 004BB023. Read of Address 00000008. Might be related to loss of certain calls like "Very nice."
Fryman:
Since the update I have been getting errors where Vlos stops responding and has to be shut down. On the runway it happens all of the time and in the air it will happen several times and may stay on for the mission. The details of the error are as follows:
Problem signature:
Problem Event Name: APPCRASH
Application Name: vLSO.exe
Application Version: 0.8.2.4
Application Timestamp: 2a425e19
Fault Module Name: USP10.dll
Fault Module Version: 1.626.7601.18454
Fault Module Timestamp: 5359c2c9
Exception Code: c0000005
Exception Offset: 0004e645
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 4105
Additional Information 1: 01e8
Additional Information 2: 01e8c40125f18bf12356daad7553b21b
Additional Information 3: 4a53
Additional Information 4: 4a53587b17e8cfc6dc3585bc40c02869
Any ideas on what is causing this?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version