vLSO Beta release

[discoferret]

discoferret,

Can you post a screen shot of the vLSO debrief when this happens? Is it an On/On pass, with a random WO in the wires? Or is it a dive "spotting the wires" pass, which deserves a late WO? Could also be a delay in the program due to many calls being triggered, are you getting a lot of calls prior to the WO call?

Here's the debrief pics. I'm hardly getting any calls prior to the WO just a few like "dont settle"

[Paddles]

vLSO is not able to recognized and identified  FCLP airbases,but all carriers are identified and with them vLSO works correctly
I have NAS Meridian KNMM and Fentress KNFE sceneries, all installed properly, according the install instructions (in add-on scenery folder there are the appropriate "tag" files in each of the scenery folders)

Taras,
Do I get it right, that when approaching a FCLP area you don't see any text messages stating that you're in that area (as in case with carriers)?
Try to run the program with the log option, you should have in the vLSO_log.txt file something like this:

6/19/2013 4:00:42 PM Program started
6/19/2013 4:00:42 PM FSX connection established
6/19/2013 4:00:42 PM User aircraft detected (F18)
6/19/2013 4:00:48 PM FCLP location NALF Fentress (runway 23) set as current

[Paddles]

Here's the debrief pics. I'm hardly getting any calls prior to the WO just a few like "dont settle"

discoferret,
That is a nice solid pass, so it's my program's fault, not yours.
This AR/IW waveoffs glitch will be fixed in the next vLSO release.

[discoferret]

Here's the debrief pics. I'm hardly getting any calls prior to the WO just a few like "dont settle"

discoferret,
That is a nice solid pass, so it's my program's fault, not yours.
This AR/IW waveoffs glitch will be fixed in the next vLSO release.

Ok thanks. Looking forward to the update.

[Taras]

vLSO is not able to recognized and identified  FCLP airbases,but all carriers are identified and with them vLSO works correctly
I have NAS Meridian KNMM and Fentress KNFE sceneries, all installed properly, according the install instructions (in add-on scenery folder there are the appropriate "tag" files in each of the scenery folders)

Taras,
Do I get it right, that when approaching a FCLP area you don't see any text messages stating that you're in that area (as in case with carriers)?
Try to run the program with the log option, you should have in the vLSO_log.txt file something like this:

6/19/2013 4:00:42 PM Program started
6/19/2013 4:00:42 PM FSX connection established
6/19/2013 4:00:42 PM User aircraft detected (F18)
6/19/2013 4:00:48 PM FCLP location NALF Fentress (runway 23) set as current

Paddles,

that is correct, I can't see any text messages stating that I'm in FCLP area.

I took off from KNFE, made one cirquit, TGL and then created with TacPack one carrier and did several approaches. As you can see in log file everything with carrier worked fine.
As you requested I attached log file from vLSO and image from FSX addon scenery folder

[Paddles]

Well... I'd suggest first run my program FSchecker (found on the vLSO blog) and then see what it finds.

[Taras]

Here is the result from FSchecker

[Paddles]

taras24,
As I can see, none of your FCLP sceneries is ENABLED in Scenery Library. Can you give me a screenshot of your Scenery Library screen?

[Taras]

Here is the screenshot from my Scenery Lib and I attached Scenery.cfg too

[Paddles]

taras24,
Now I know what's the problem. When installing FCLP sceneries (and a few other sceneries, according to your Scenery.cfg file) you double-clicked on them, so FSX stored their paths with this additional part \scenery, whereas any scenery already has two folders (scenery and texture) inside its main folder and there's no need to specify them additionally.

I'd suggest you first uninstall them and then install again clicking their folders once. That's it! 

[Taras]

Paddles
Thank you very much for your help, every FCLP was recognized, now it's working fine    

[Paddles]

Happy bouncing! 

[Archi]

I have also problems with P3D v2.4 (win7x64)

I get following error message when launching vLso.exe:

FSX Acceleration not found!

The vLSO program may not work properly.



Flight sim checker gives me this:

Roaming path: C:\ProgramData

Checking FSX...
------------------------------------------------------

Registry key SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 - NOT FOUND



Checking P3D v.2 32 bit...
------------------------------------------------------

Registry key SOFTWARE\Lockheed Martin\Prepar3D v2 - OK
SetupPath value - E:\Lockheed Martin\Prepar3D v2\
Prepar3D.exe - OK
Now trying to read P3D scenery config file C:\ProgramData\Lockheed Martin\Prepar3D v2\Scenery.cfg...

OK, 180 scenery definitions read



Checking P3D v.2 64 bit...
------------------------------------------------------

Registry key SOFTWARE\Wow6432Node\Lockheed Martin\Prepar3D v2 - NOT FOUND


Checking P3D v.1 32 bit...
------------------------------------------------------

Registry key SOFTWARE\LockheedMartin\Prepar3D - NOT FOUND


Checking P3D v.1 64 bit...
------------------------------------------------------

Registry key SOFTWARE\Wow6432Node\LockheedMartin\Prepar3D - NOT FOUND

[Archi]

I got vLso running on P3D 2.4!!  After few landings it seems to work fine and no more error messages on startup. I installed the Migration Tool from Flightsim Estonia and I think that program did the magic to get it working!

[GOONIE]

Not sure if folks are aware of Aerosoft's F-14 to be released tomorrow, but it will include a new carrier, the Kitty Hawk.

They reworked the FLOLS in FSX, and we now will have 3.5 degree glideslope  , more details here;  http://forum.aerosoft.com/index.php?/topic/88861-pre-release-f-14-topic/

You can also download the manuals (pre release), for more gouge on the FLOLS.

Hope vLSO will support this new carrier when released!