FSDreamTeam forum
General Category => Unofficial F/A-18 Acceleration Pack board => Topic started by: Paddles on December 30, 2016, 05:40:16 am
-
Ok, guys
It's finally here (http://vlso.blogspot.com/). I named this version as Christmas edition.
So what's new? Everything!
new design with changeable skins
RFN support
new manual, now in CHM format
multiple flightsim configurations support
new INI file format to support multiple flightsims
practice carriers
user activated calls (ex.manual ball calls)
new debrief window
and lots of internal changes here and there
It took me over a year to assemble all those features in this new version, but it's still not a release, it's actually a transition version. It is still compatible with previous 0.8 betas but I'm going to make some more improvements, particularly to change the logbook format. And that hopefully should be a release...
So, that being said, be prepared for potential errors and glitches. I'm always open for your feedback and criticism.
I'd like to give special thanks to Michel Panattoni who provided invaluable assistance in debugging the RFN part of this release. Bravo, Michel!
PS. Some things to remeber:
- The manual is still WIP and some parts are missing or incompleted. Feel free to ask me.
- When switching to RFN mode and back, please restart vLSO. This will be corrected in the next version.
- I have removed downloads of all previous versions - no way back!
The download link is updated to 0.9.7.2 version.
I temporarily disabled the help button in the 0.9.7.1 version. Looks like I'll need to consider getting from the CHM help back to good old PDF format.
Happy New year and happy virtual langings!
-
Thank you so much!
Russ
-
The new version is most appreciated and reflects your dedication to reaching for a fully realistic LSO version.
Thank you for your Exceptional talent, Paddles.
-
Downloading now, THANK YOU for your continued support for all the naval aviation sim fans.
-
I would like to add a thank you to all the others! :)
I sure appreciate all the hard work you put into this little piece of software.
I still think those AI LSO's have it in for me though :D
Pat☺
-
Paddles-
Liking the new design, and especially the revamped ball calls. Got a couple of items though...
Starting the new version reliably gives me this error...the program appears to function as normal though.
(http://i.imgur.com/pM48LVX.png)
Also, did you change the reference points for the Javier carrier? I think I got tagged for LO AR on every single pass - and I even flew a pass 2 balls high just to check it.
-
ExNusquam,
Thanks for the feedback.
No changes made to the carrier data. That's really strange to have LO AR with 2 balls high...
When that 'List index out of bounds' appear? Does the splash go out when the program continues to work?
-
ExNusquam,
Thanks for the feedback.
No changes made to the carrier data. That's really strange to have LO AR with 2 balls high...
When that 'List index out of bounds' appear? Does the splash go out when the program continues to work?
I'll try and record a few passes today to see if I can get it to reproduce a LO AR call.
The "List index out of bounds" appears on the splash screen on start. Clicking OK, the splash remains momentarily then disappears and the program continues to work.
-
I just did a carrier operation off of Oceana using; the Nimitz carrier, P3D latest version, VRS Superbug and TacPack latest version, AS16 Weather latest version. The weather was terrible with low clouds under 600 ft, turbulence and lightening. vLSO was reporting Case I recoveries instead of Case III. When I tried a Case I pattern from the carrier I was in the clouds at 500 ft. Just a note for your information.
-
The help file contents were initially blank (in version 0.9.7.0) but it worked after unchecking the box "Always ask...when opening this file..." in the dialog box.
-
FYI: New version 0.9.7.2 is out.
-
FYI: New version 0.9.8.1 is out.
-
Wow!
The changes are coming in so hot, I barely have time to get one downloaded before the next one comes out! Not to mention trying to install and test them out :)
Great work, though, Paddles. Thank you very much for a wonderful freeware. Your work is truly impressive, and most appreciated.
Pat☺
-
Yep, keep working... ;D
New version 0.9.8.2 is out, by the way.
-
I was also having the problem with the "List index out of bounds" message on startup. The solution for me was to rename the vLSO_log.txt file and let the program create a new one. I haven't had the problem since.
Mike
-
Mike,
Thank you for reporting this bug.
When starting this new 0.9 family I thought that it would be convenient to limit the vLSO_log.txt size and not allow it to grow larger and larger... So, the program tries to trim this log to some reasonable 3000 lines. Obviously, this part of code is far from perfection. :-[
-
Mike,
Thank you for reporting this bug.
When starting this new 0.9 family I thought that it would be convenient to limit the vLSO_log.txt size and not allow it to grow larger and larger... So, the program tries to trim this log to some reasonable 3000 lines. Obviously, this part of code is far from perfection. :-[
Which means it is likely to mainly effect people who have been loving and using your program for a long time. ;D
Keep up the good work,
Mike
-
Thanks Paddles! Always appreciate your work and contributions to naval aviation simulation.
Installed yesterday and flew a couple of approaches using the latest P3D with VRS Bug, couple things:
First, I keep muting vLSO accidentally and not sure how I am doing this? I fly an approach and get vLSO calls, but then they stop, and when I look at vLSO it shows it is muted. I am not able to open the "help" file because of the doc format in Windows 10, so unable to check how to unmute. Also need a little help with the manual controller Ball Call setup, figure it is in the manual that I cannot open.
Second, on CASE III approaches, vLSO gives me two "paddles contact" calls and then one "call the ball" after passing 1.0NM. Is this happening to anyone else on CASE III?
Third, Wind over deck calls, I checked the box for winds in vLSO, but don't here them being called with the roger ball call. Am I missing something? Is there a wind limit (based on real wind calls available)?
GOONIE
-
New version 0.9.8.3 is out.
Back to the good old PDF format! ;D
-
New version 0.9.8.4 is out.
Wind over deck calls, I checked the box for winds in vLSO, but don't here them being called with the roger ball call. Am I missing something? Is there a wind limit (based on real wind calls available)?
Fixed. Please read the Practice carrier section of the manual.
-
New version 0.9.8.5 is out.
Fixed. On CASE III approaches, vLSO gives two "paddles contact" calls and then one "call the ball" after passing 1.0NM.
-
I'm just going to wait. I can't keep up with all these updates! :o
I sure appreciate all the hard work though. I am amazed by people who do this. I did some work in Visual Basic and C++ a LONG time ago, and those simple little things I did for practice gave me splitting headaches. I hate to think what it's like now! :P ::)
Thanks for all the effort. It makes a big difference :)
Pat☺
-
New version 0.9.8.7 is out
-
I just installed the latest version v 0.9.8.7 and the pilots log file was empty. I tried to import previous pilot records and they all come in as read-only files. When I close the program and reopen it again the records are gone. Is the import/export function working? If so how do I import?
-
Fryman,
That's strange - the 0.9.* version is fully compatible with 0.8.* and should open old LDF files without problems. Does old 0.8 version open the same LDF file ok?
-
Paddles
I get the following error when I startup vLSO.
"EStringListError error raised, with message: List Index out of bounds(127535)"
I am running version 0.9.8.7 as an administrator. Windows 10 Pro and the latest version of P3D.
Russ
-
Hi Russ,
Could you email me a copy of your Logbook.ldf file for detailed inspection?
Are you using RFN gauge?
-
Paddles
Not that I am aware of. Where should I look for it?
Russ
-
No, that was just a guess, using the RFN gauge is not mandatory. You can read about RFN in the manual, by the way.
Well, I'd suggest to run the latest 0.9.8.8 version, which should provide a bit more information on that error, so this could help me to spot which of two potential parts of the program caused this bug.
Thanks!
-
I installed 0.9.8.8 version. Still getting same message.
Suggestion: When on the Config screen and in the Flight Sim box and you choose the sim to use to set configuration have the chosen sim become the default instead of defaulting to FSX.
Russ
-
I installed 0.9.8.8 version. Still getting same message.
It's almost the same. I'd like to know what exactly says that message?
Suggestion: When on the Config screen and in the Flight Sim box and you choose the sim to use to set configuration have the chosen sim become the default instead of defaulting to FSX.
Do you mean when opening the Config once again it should default to the last chosen sim, right?
-
This is the error message.
"EStringListError error raised, with message: List Index out of bounds(127535)"
Do you mean when opening the Config once again it should default to the last chosen sim, right? Yes.
Russ
-
Russ,
Most likely the error occurred when the program tried to crop its log file. Try to delete the vLSO_log.txt file in the vLSO folder and start the program again.
-
Paddles
Deletion of the vLSO_log.txt eliminated the error.
Thanks
Russ
-
Thank you, Russ!
-
Two items:
1. On a previous post about Pilot files, I had installed vLSO under C:/Program files/vLSO. The new installer put vLSO under C:/vLSO and so the pilot log file was empty. For the latest version I browsed to C:/program files/vLSO and the last pilot log file came in.
2. I have been trying to get the RFN gauge to work and have not been successful. My system is P3D latest version, vLSO 0.9.8.8. I have RFN installed on a separate hard drive and vLSO shows a red light with no RFN. This last version is to support different directories for sim objects but was not tested in P3D. Is there something I can check to see why it is not showing up?
-
First and foremost, do NOT install things other than Windows file to c:\Program Files or \Program Files(X86).
It will give you nothing but trouble. Install things ANYwhere other than those two. It would have been much better to install to C:\vLSO, and copy or move the required files to there, not the other way 'round.
I don't know if that's any help...
Pat☺
-
2. I have been trying to get the RFN gauge to work and have not been successful. My system is P3D latest version, vLSO 0.9.8.8. I have RFN installed on a separate hard drive and vLSO shows a red light with no RFN. This last version is to support different directories for sim objects but was not tested in P3D. Is there something I can check to see why it is not showing up?
According to the RFN manual (ch. 2-4), the RFN gauge files have to be placed in the Gauge folder of a sim. That's the place where vLSO tries to look for required RFN files. If you've installed them in other folder, or even on a separate drive, then that's the reason why vLSO gives you a red light.
As for different SimObjects folders in P3D - do you practice placing you custom aircraft and boats outside of the main P3D folder? LM guys suggest doing this but it might be somewhat tricky, as you are allowed to use any of up to three simobjects.cfg, placed in different folders around your HDD... ::) That's why this feature still was not tested in P3D.
-
I just upgraded to the new vlso. Been making passes at coupville NOLF and having a blast. Great program Thanks. One question how do I get my landing bars at coupeville?
Les
-
Hi Les
You have two possibilities
1) Instal Nolf Coupeville vLSO compatible.
http://vlso.blogspot.fr/
or
https://docs.google.com/file/d/0B3pFCe8B4_FGUG85SE43QjNUeGc/edit?usp=sharing
In this situation RFN mode must be OFF.
2) Install RFN gauge 4.21 and RFN Scenery 4.2
http://royalefrenchnavy.restauravia.fr/RFN-Creations.htm#Gau
In this situation RFN mode must be ON.
Regards
Michel
-
Michel
1) I have Installed Nolf Coupeville and have the FLOLS. Am I missing something or should I have ILS bars. What is tacan for KNRA?
Working on RFN Gauges......
Regards
Les
P.S. Long day have it all working........
-
To look for the problem, when VLSO is running, you must have 4 greens when RFN mode is OFF:
SimConnect.dll, Flightsim connection, Aircraft selected, location selected.
If RFN mode is ON you must have RFN in green.
Michel
-
You can find TACAN frequencies in the pdf file.
With RFN gauge, KNRA is 122X (117.50) Rwy 32 and 122Y (117.55) Rwy 14
-
Paddles, love the software and sceneries. I am having trouble seeing the IFOL lights at many of the FCLP bases. KNTU (uchi's scenery with your mod) KNFE...etc. What I see is the IFOLS trailor but no lights. Is there a tweak I can do or is this a P3D v3 issue?
Thanks for the help.
Axe
-
Axe,
Yes, it's a P3D issue. Unfortunately there's no tweak...
The only viable solution is the RFN FLOLS, which will be fully supported in the upcoming vLSO release.
-
Picked up this book today on LSOs, thought others might be interested.
-
This is me right now LOL!!
Looks interesting though, I love reading about the origins of stuff like that. Let us know how it is.
-
Looks like this is the one? http://thanlont.blogspot.com.au/2017/03/the-complete-and-illustrated-lso-guide.html
(https://1.bp.blogspot.com/-mD706BOW_pc/WNPun36FiMI/AAAAAAAAKZ0/2pQKHS3zp4QzOFUPeIB9bx0XqOT0JjEeACLcB/s640/61MPeo18VZL._SX497_BO1%252C204%252C203%252C200_.jpeg)
-
Hello Paddles,
I tried the latest vLSO and I am still getting cases where I rollout on centerline but still get marked as _LUL_X. I attach a picture. I think that vLSO is taking the start just as a distance and is marking me as LUL in the middle of the turn and with the T-45C this seems not to work so well (this pass is even LIG)
(https://preview.ibb.co/c5OpCF/Untitled.png) (https://ibb.co/hNjJ6a)
what is image hosting (https://imgbb.com/)
-
syn,
Thank you for reporting this glitch. I'll try to fix it in the upcoming version.
Groove time. Currently the correct groove time is hardcoded as 16..19 sec, with up to 22 sec as little long in the groove or (LIG). I think that with the T45 and WOD > 30 kts it's impossible to land within 19 sec. And don't forget about that 4.12 glideslope, which adds more time to get to the ship... Perhaps we need to review the criteria of what is considered to be the correct groove time? In regard to this simulation, of course.
BTW, according to the chart attached, this pass was in manual ball mode, right?
-
Yes, manual ball call.
Regarding TIG with the T-45C I have no problem generally making it around 16-17 seg and get some NESA and LIG from time of course. The pass I chose to attach was because it depicted perfectly this bug of getting _LUL_X before the ball call/rollout.
-
And another one. Just wondering why is this pass given a pass even though there are no remarks listed. I noticed that with the T-45C es much more difficult to get an OK from vLSO than for example the F18. I have a few pases like this one, also case III and never manage to get an OK. Does it have to do with catching the 4th wire? The problem is that the FSX FLOLS does not take into account aircraft type and most T45 passes end up in a 4 wire.
(https://s13.postimg.org/7q9310own/Untitled.png) (https://postimages.org/)
-
I've noticed that in FSX, you can either fly a hair below the glideslope indication on the HUD, to get a 3-wire, or fly right on it, and get a 4-wire every time. If you fly the Ball, you will get a 3-wire, but the LSO's will call you a little low in the groove. You can do one or the other, depends on what you're trying to do. Hit the 3-wire with a slightly less than perfect grade by the vLSO's, or get a 4-wire with no vLSO comments. Assuming all other factors are correct, of course.
It may be that since the T-45C is a trainer, the LSO's are a little harder on you than for an F-18? That may be why it's harder to get an OK pass. Just a possibility. Or maybe the LSO program is optimized for the faster F-18, and the T-45C has to be flown slightly differently than it should be to get an OK.
Just a couple of my thoughts. I may be totally out in left field on all this, though...
Pat☺
-
The problem is that the hook-to-eye distance is different for the T45C and F-18 and FSX FLOLS seems to be optimized for the F-18, as shipped with the sim. That is why flying the ball on the T45 while normally end up in a 4 wire or bolter. There is not much we can do about it (unless somebody has the modelling skills (and time) to create a new carrier model with a new (I)FLOLS...) other than accepting it.
What I find a little bit odd is that I think I've never received an OK grade with the T45 in vLSO even on a clean pass, while I can get them with the F18. I am wondering if catching the 4 wire is "discounting" from the grading system.
-
Paddles will have to answer that, of course. Having said that, I think that a 4-wire trap does cause a slight down-grade by the vLSO's. They're looking for a 3-wire trap. But if you fly for a 3-wire, you'll get down-graded for flying below the glideslope. I think your two choices are to fly an incorrect pass in the T-45, or fly the F-18.
If you opt for the Hornet, may I suggest the v16.1 ? Great palne, flies like a dream, really does. And the team is making it even better as we speak, with a v17.XXX due for release here pretty soon, I hear. Well worth taking a look at.
Either that, or you annoyed the vLSO's. They're very easy to annoy, and will take it out on you from then on. They hold a grudge ::)
Have fun!
Pat☺
-
Guys,
Yes, a 4-wire trap does cause a slight down-grade by the vLSO. Only a 3-wire is a pass for an Ok ;)
You're definitely right when talking about different hook-to-eye distances. Both planes discussed here, the Goshawk and the Hornet, have different sizes and different geometry, thus different distances from the pilot's point of view to the tailhook's point, which 'grabs' virtual arresting wires. I agree with syn that FSX FLOLS is optimized for the Hornet. And we can do nothing about that.
But there IS a solution. The only [known to me] FLOLS, which takes into account aircraft's geometry, is the RFN gauge. And once mastered it, you can get consistent 3-wires with any airplane. The gauge also allows to adjust the glideslope angle... Of course, the upcomng vLSO will fully support the RFN gauge 8)