General Category > Unofficial F/A-18 Acceleration Pack board

vLSO Beta release

<< < (28/282) > >>

Paddles:

--- Quote from: WilliamCall on November 18, 2011, 03:22:04 am ---...  I've installed "carriertracks1and2", which have several compiled traffic .bgl files.  Two files of interest are: trafficNASeast.bgl and trafficNASeast2.bgl ...

--- End quote ---
Ok, I'll d/l this pack and see how my program handles these traffic carriers. Will report ASAP  :)

Edit.
Looks like you are using Javier's Nimitz_Ike_version2 carriers pack, right?  ;) Well, the program currently 'knows' only CVN68 carrier, whereas your traffic .BGLs use both CVN68 and CVN69. When starting the Pensacola saved flight, for example, take a look at the superstructure and you will see the number 69. That's why my program doesn't work with this carrier. The beta 0.3 will work with both CVN68 and CVN69 carriers.
BTW, the well known AICarriers2 utility allows you to use in free flight other Nimitz-class carriers, namely CVN71, 72, 73 and 76. They are all variations of the Acceleration carrier, not Javier's. Should I add support for these too?

SandPro:
Thanks for the info.  Yes, the file structures are correct.

I know there is a separate Simconnect build tool that uses Visual Studio 2005 or Visual C++. I assume that is how you are making that connection.

That leaves me a little confused on trying to isolate the issue, due to the fact that in the case of AICarrier2... the program uses the simconnect function provided via JAVA. As an example...If, you try to run AiCarrier2 without FSX running.... you will get about 9 Java errors... ie.. java.net.blindException:Cannot assign reqested address:connect and flightsim.simconnect.SimConnect.openNetworkConnection(simConnect.java:283), etc.
That is why I was questioning a possible Java conflict ?

WilliamCall:

[/quote]
Looks like you are using Javier's Nimitz_Ike_version2 carriers pack, right?  ;) Well, the program currently 'knows' only CVN68 carrier, whereas your traffic .BGLs use both CVN68 and CVN69. When starting the Pensacola saved flight, for example, take a look at the superstructure and you will see the number 69. That's why my program doesn't work with this carrier. The beta 0.3 will work with both CVN68 and CVN69 carriers.
BTW, the well known AICarriers2 utility allows you to use in free flight other Nimitz-class carriers, namely CVN71, 72, 73 and 76. They are all variations of the Acceleration carrier, not Javier's. Should I add support for these too?
[/quote]

Serge,
Thanks so much for looking into this!  Yes, when I start my flights from Oceana, Pensacola, or Key West and land on the carrier, the carrier is indeed the USS Eisenhower (CVN69).  If it's not too much trouble, I'd like to see support for CVN71, 72, 73, and 76.  Thanks again!

K6952:
Serge,

Thanks for your detailed input!

Oh, no. Thank *you* for all your hard work!


How do you autostart the vLSO? In a .CMD file or what?

It's an XML file called "Exe.Xml". I don't really understand how all that works, but the computer geek who walked me through it says it's detailed in the SDK.

Right now the abeam altitude is limited by 800'. I agree that this is probably incorrect, but what the upper margin should be? 650' or even more? And, what should be the vLSO's reaction when you fly above that level?..

I would say +/- 100' is easily doable by most pilots if they're paying attention to their scan. Generally the LSO will inform the pilot if he's a little off at the abeam if the pattern's not loaded. "Bullets 203 paddles contact, slightly high and close aboard", that sorta thing.


No problem, what parameters?

 I would say any parameters that would be useful to tweak for different aircraft (AoA, abeam distance, eye-to-hook, etc), but others have suggested that *all* variables should be external to the .exe in order to make it more adaptable.

 FWIW, I have another idea for the OK trigger: If you get an OK 3 pass with absolutely no additional comments, it upgrades it to OK 3.

Orion:

--- Quote from: K6952 on November 19, 2011, 01:37:34 am ---It's an XML file called "Exe.Xml". I don't really understand how all that works, but the computer geek who walked me through it says it's detailed in the SDK.

--- End quote ---
Actually, it's not detailed in the SDK at all (that I recall, anyways).  Fortunately, it's not hard to understand, either.  Whatever you put in a Launch.Addon node (with its appropriate sub-nodes) gets launched when FSX is loading.  Simple as that.

Navigation

[0] Message Index

[#] Next page

[*] Previous page