General Category > Unofficial F/A-18 Acceleration Pack board
vLSO Beta release
Paddles:
Thanks, K6952
Here's your locus (in bold colors) compared with the default locus (in faint colors). There were no exact numbers in the RHE_NAV_90_TR_1, so I just used 'rule of thumb' to specify the locus limits. Your numbers look good, I hope people will give it a go 8)
Paddles:
--- Quote from: Essex on November 07, 2011, 10:09:02 pm ---...I did manage to get the Ark Royal to 'work' with the beta...
...
Obviously the deck angle etc are wrong (but not deck height in this case).
Could it be possible in future to add custom carrier entries to the ini file ideally with parameters for its geometry as well?
...
Also ideally could we add custom aircraft entries with their optimum AOA?
--- End quote ---
Sounds good, but you are right - the AR's deck geometry is totally different, so the vLSO will not work properly with this carrier. Does this carrier have an OLS similar to FSX CVN68? I mean is that OLS as precise as FLOLS?
The vLSO currently supports following aircraft:
F/A-18A
F/A-18E
F-14D
T-45C
A-4K
And it's no problem to add support for any other carrier capable aircraft. I will add this feature to the next beta release.
Paddles:
Well guys,
The Beta 0.2 is here http://www.fsdreamteam.com/forum/index.php?topic=4915.msg45464#msg45464
Read, install and test...
Some more details on the program.
The correct abeam position now depends on aircraft type and follows its NATOPS numbers:
F/A-18A - 1.25-1.5 NM
F/A-18E - 1.10-1.3 NM
F-14D - 1.0-1.25 NM
T-45C - 0.9-1.1 NM
A-4K - 1.0-1.25 NM
Too close abeam and too wide abeam areas both are 0.5 NM wide (again I used the rule of thumb here), abeam altitude limited to 800' (we'll discuss CASE III ops later)
LSO levels currently implement voice levels only:
Nugget - all voice calls,
Fleet - advisory and imperative calls,
CAG - imperative calls.
Happy landings! ;)
GOONIE:
Thanks again Serge! Looking forward to the new release. Couple questions, is there anything one needs to do to have the vLSO adjust AoA values and abeam position for different aircraft or is it automatic? (e.g. T-45C vs F/A-18C). Did you mean F/A-18C 1.25-1.5NM, or F/A-18A?
Second, for the carrier mission you developed, can one add a support ship (destroyer, cruiser) 1NM behind the carrier by adding these lines of code to the .FLT file for the saved mission? Of course I would need to update the lat/long to match the carrier starting point with offset? I typically use the support ship to help fly the airplane from the 2D cockpit, as a visual reference for getting into the groove.
[Sim.245]
Sim=VEH_destroyer01
[SimVars.245]
Latitude=N36° 26' 27.60"
Longitude=W74° 30' 9.36"
Altitude=+000008.99
Pitch=0
Bank=2.5401646986622414e-027
Heading=79.075232246543749
PVelBodyAxis=0
BVelBodyAxis=-2.3020198699624645e-028
HVelBodyAxis=2.3773682295426338e-031
XVelBodyAxis=-3.2886623520653484e-027
YVelBodyAxis=7.4110606801254932e-020
ZVelBodyAxis=16.88761451793836
SimOnGround=True
OnPlatformHeight=-9999999999
[Slew.245]
Active=False
[Freeze.245]
Location=False
Altitude=False
Attitude=False
Paddles:
--- Quote from: capthaltli on November 08, 2011, 04:20:17 pm ---...is there anything one needs to do to have the vLSO adjust AoA values and abeam position for different aircraft or is it automatic? (e.g. T-45C vs F/A-18C). Did you mean F/A-18C 1.25-1.5NM, or F/A-18A?
--- End quote ---
The vLSO now automatically sets AoA and abeam values for the supported aircraft, which I listed previously.
Is there an FSX F/A-18C?.. Did I miss something? ;D
--- Quote from: capthaltli ---Second, for the carrier mission you developed, can one add a support ship (destroyer, cruiser) 1NM behind the carrier by adding these lines of code to the .FLT file for the saved mission?
--- End quote ---
Of course! You are free to modify this mission to your taste. But I think it's better to add ships to the mission's XML file, via Object Placement Tool, so the ships could move along with the carrier.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version