General Category > Unofficial F/A-18 Acceleration Pack board
vLSO Beta release
pyroperson87:
Hey Paddles, I've been dying to test this all week, only to find that no matter what I do I can't connect vLSO to FSX. SimConnect light is green but FSX light is always red. I tried starting vLSO before FSX and after FSX, but no joy. Anyone else having any problems?
EDIT: I reverted to 0.7.1.2 and it also is unable to connect to FSX, so I'm pretty sure it is something local to my system. Time to start uninstalling things one by one I guess to see what the problem is ???
ExNusquam:
If you need to test the simconnect interface, there's a quick program you can use in the SimConnect SDK called "AI Traffic.exe". If it displays "connected to flight simulator" your simconnect is working, and the problem is something else, if it displays otherwise, somethings wrong with your simconnect config.
--- Quote ---A yellow 1 on black? Or just a solid black square, w/o CASE number?
--- End quote ---
A black square with a yellow 1 would be great, I think.
pyroperson87:
So here is my dilemma. I do not have the FSX SDK installed because I purchased a digital version of FSX acceleration through the "Games for Windows Live" marketplace. I have tried everything I can think of, including uninstalling the addons that I have installed since last using 0.7.1.2. Still the same problem, no matter what the FSX light on VLSO stays red. While I technically could GET the SDK by completely uninstalling, and reinstalling FSX from the GFWL marketplace, I really would rather NOT have to do that, as it must first download the 10GB installation files, and then install it which takes about 5-6 hours total to download and install, not to mention the hours spent reinstalling my various ORBX sceneries and REX textures. Any chance I could get someone to send me their three simconnect.dll files JUST TO TEST THEM and see if I'm having issues with simconnect? It would really suck to reinstall ALL of FSX and then still have the same issue. :'(
GOONIE:
Thanks Paddles, look forward to the updates! ;)
--- Quote from: Paddles on February 23, 2014, 06:18:05 pm ---...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.
Please more info on why and when do they call those "discontinue approach..." ?
--- End quote ---
I noticed on the PLAT cam footage when the Hornet got wrapped up in the wires for ~10 minutes, several aircraft on final, <3NM, were told to discontinue approach and take angles 1.2 straight ahead. I know it must be frustrating for the pilots coming down the chute to get this call, but you can't control when the deck is fouled. I thought a good way to simulate this would be to add one or two of these discontinue calls to the Marshall sound folder, and if vLSO randomly selects it, it would simulate a random fouled deck. Not sure if it would work with vLSO, or if you would keep getting the same discontinue call from vLSO if the folder is not randomized for each approach. I also have a couple other sound clips for the mile callouts, which I could add to the folder if it was randomized like the main sound folder.
--- Quote from: Paddles on February 23, 2014, 06:18:05 pm ---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.
ATC problem still unsolved. I believe it's ok to monitor the AC lights state, but I don't have any info. Could you be more specific on this?..
--- End quote ---
I think Jeff64 answered this well. I saw this happen on the PLAT cam footage twice, both times the pilot got a little low at the ramp. I presume the pilots were a little shaken up after the low approach and forgot to turn off all lights after trapping, resulting in the "lights" call. I've also done this in FSX, but didn't realize it until I was on the catapult and ready to go. When I went to switch on all lights (pinky switch) to signal ready on the CAT, my lights were already on, :-[. I thought it would be cool for vLSO to make the "lights" call during night approaches if you don't turn your lights off after trapping. Basically you would get a friendly reminder as they do in real life. The call should be delayed ~5 seconds, to give the pilot a chance to catch up to the aircraft after trapping.
Spaz,
Thanks for the LSO shorthand, understand the . and - mean something different then what I was thinking. Does it make sense to you what "on" or "to" means? The example the give was "slow on line up in close". Does that mean they took too much time (e.g. slow) to line up the aircraft in close? Or their airspeed was too slow when they were lining up the aircraft in close? Same question for the "to" or -. Thanks.
GOONIE
SpazSinbad:
I'm not trained as an LSO 'Goonie'. My guess would be the aircraft is slow (not slow to line up) in the example given. Why? Because it is important compared to how fast/slow one might be to line up - which gets to be irrelevant in close considering the lack of time available to do anything about it - power is more or less instant though to get back on speed. If bad line up further out then probably a wave off is called for, however anyone can get slow all of a sudden - anywhere - by taking off too much power or whatever for too long. Just my guess though.
"High in middle to in close" would mean IMHO that the aircraft is high during that part of the approach as defined (between middle and in close).
This is LSO shorthand which may not obey ordinary rules of English grammar. Not that youse Americans do that much anyway. ;D So the mixture of shorthand when put 'into a sentence' may appear odd to those wanting to see 'proper Engrish'. ::) ;D
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version