General Category > Unofficial F/A-18 Acceleration Pack board
vLSO Alpha Release
sonofabeech:
Hey Sludge
Don't want to start any false rumours around here as far as the time in groove is concerned ...the reason I said it had possibly been fixed was because of the photo above showing the vLSO glideslope page shows his pass as being 12,7 seconds in the groove. I guess only Serge can answer that question.
Is there any way of getting the vLSO to work in a multiplayer setup? Im guessing if it can be done that someone will have to write another multiplayer mission? Or do we go back to LSO Sludge with his dreaded log book ;D You guys think the vLSO is tough ....LSO Sludge will make grown men cry ;D
Whenever you guys are ready for a session drop me a message ..it's been far too long since I last saw your ugly mugs :P
Sonofabeech is in the slot LOL
Sludge:
Beech...
No worries, I think Serge took our criticisms and is working with them. Thats all we can ask. I'm gonna do some more passes tonight and see how I stack-up in the pattern and try to get my FRAPS running to record it.
--- Quote ---You guys think the vLSO is tough ....LSO Sludge will make grown men cry
--- End quote ---
Man, now I feel like the LSO version of the "wicked witch of the West". Haha. I think the good news is that once people get comfortable with the vLSO and can bring that to the multiplayer sessions, they should be just fine with my grading. Of course ALL BETS ARE OFF once you get NEUTRINO'd, but its all good if we can get some sessions started again and get people out there.
Later
Sludge
Paddles:
Guys,
These pictures were taken not during actual approaches but in the OPT mode. I use this OPT (Object Placement Tool) when working on the vLSO project and missions. This powerful tool allows me to place and move the plane around the scene as I want it, so I don't need to fly the pattern every time I need to check something. I just move the plane into required position and see how the vLSO registers and evaluates its position... So what you see is not exactly what you think :)
However I do fly my missions. But I still can't reproduce the groove time issue, I constantly get 18..26 sec. Will keep working on this issue...
sonofabeech:
Sludge!! ...wicked "witch" of the west you cross dressing these days ? thats a scary thought ... I remember the multi sessions..
Sonofabeech : "Abeam ..hook down"
Sludge: "Do you want the friendly LSO or the real deal"
Sonofabeech " the real deal"
Sludge" Right then ...."
Sonofabeech" OH CRAP!! :o
Sludge .... WAVE OFF WAVE OFF ... ;D
Serge thanks for the feedback ..appreciate all the time you have put into this project!
Paddles:
--- Quote from: Sludge on September 28, 2011, 08:32:54 pm ---Also, are you gonna have "launch/activations zones" for the other cats as well? So we can do launches from CATS 1/2 while doing sustained carrier patterns. Its my opinion that the boat was "stopping" cause the Hornets werent starting and using CAT 4. Hopefully, we can get this fixed, so we can CAT anywhere and the boat will keep going...
--- End quote ---
Sludge,
looks like the problem caused by this xml tag set to True:
<YieldToUser>True</YieldToUser>
Just open in an editor each mission's xml file, find and set the tag to False (easy to find, it's the only <YieldToUser> tag within the xml code) and re-fly the two missions again. There should be no more stopping.
Here's my new question.
Currently my missions are set for the F18, and ideal abeam position is 1.3 nm from the touchdown point and abeam area margin is 0.4 nm, so that when the plane is 1.7 nm or farther from the ship, it gets TWA; when the plane is 0.9 nm or closer, it gets TCA. But what if you fly the T45 or F14 or any other carrier capable plane? Will this 'hardcoded' into missions abeam position be suitable for them? NAVAIR 00-80T-105 specifies abeam numbers without referencing to any particular aircraft (see the attached picture). On the other hand I recall that abeam position for the T45 is 0.9-1.1 nm (don't have any Goshawk NATOPS in handy to check that). So, flying correct T45 pattern would result in wrong LSO reaction, right? :)
What I want to do is to get rid of these areas and let the vLSO judge an approach according to aircraft type. This will a) give the program more flexibility and b) allow the user to fly ANY carrier mission with ANY carrier capable planes...
Here's the list of such planes - F/A-18A (Acceleration), F/A-18D (Captain Sim), T-45C and F-14D (both Dino's). Are there any other flyable planes? What are their VFR approach numbers?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version