FSDreamTeam forum
General Category => Unofficial F/A-18 Acceleration Pack board => Topic started by: Paddles on July 04, 2013, 04:52:06 am
-
Guys,
I opened this separate thread to gather bugreports and complaints relating to vLSO. If you or your friends have problems of any kind with this program, feel free to report. Please, be brief, concise and specific. I'd suggest this template form to fill:
- Operating system (WinXP 32, Win7 32 Home, Win7 64 Pro etc.)
- Addons installed/used
- What exactly doesn't work (no sounds, no logbook records etc.)
Thanks!
-
Hi Paddles,
Not a complaint - I am trying your Fentress NALF, got the scenery installed and everything. Is there a TCN value to program for runway 23 or 05? Or do you have to input the ILS (in which case what are the values?)?
Thanks for this new development.
Happy 4th!
Johan
-
Johan,
AFAIK, there's no working Tacan at Fentress, though a Tacan cabin with antenna is present in real, so I've added one just for authenticity sake. If you have any info on what Tacan channel they use at Fentress, I'll add that channel to my scenery. If I get it right, naval aviators use Tacans only for navigation to FCLP fileds, not for actual landing. That's because there's no ILS at my FCLP fileds. :)
-
Johan,
AFAIK, there's no working Tacan at Fentress, though a Tacan cabin with antenna is present in real, so I've added one just for authenticity sake. If you have any info on what Tacan channel they use at Fentress, I'll add that channel to my scenery. If I get it right, naval aviators use Tacans only for navigation to FCLP fileds, not for actual landing. That's because there's no ILS at my FCLP fileds. :)
Thanks Paddles, no, I have no knowledge of Tacan channel used at Fentress, but since you have one at NOLF Coupeville (TCN 72), I was wondering if this could be added to your Fentress scenery, just to guide the pilot. Also, the IFLOLS gauge is not working for me, I suppose it's normal, but not sure, just inquiring.
Thanks Serge, you have added a great dimension to my FSX experience.
Johan
-
AFAIK there isn't a TACAN at Fentress. Oceana TACAN is 116.60 which I believe is the closest navaid. Norfolk INTL also has a VORTAC at 116.90.
-
Hi Paddles,
Still testing your new development, tonight is KNFJ scenery.
Attached are a few pictures, and there seems to be an elevation adjustment issue...I don't have any other KNFJ AFCAD files that are competing with yours, unless it is the one embedded in FSX....?
Please let me know,
Thank you,
Johan
-
Yes, that's my fault, I'm sorry. Please visit my blog and re-download the scenery.
-
Thanks, it works very well now.
Johan
-
Hi Paddles,
It looks like vLSO faces collateral damage from VRS TacPack 1.4 release (at least on my box) :
- text/voice notifications of approach and final bearing are sent very far away from CVN airspace (more than 190NM)
- text/voice notifications of approach and final bearing are sent very frequently (up to 10 times per minute)
My thanks,
-
upilote,
Here's a TacPack developer's answer:
I'm not sure what would be causing this user's issue, but I'm fairly certain it's not the recent TacPack update as no fundamental changes to the way carriers are handled was made. Feel free to send the user to our forums for support, but the simple check would be to have them disable the TacPack via the TPM and see if the behavior they're reporting remains. My guess is that it will.
So first disable the TacPack and see what happens.
-
Thank you for your answer/info.
Without TacPack, situation returns to normal.
So I created a topic on VRS TacPack Support Forum.
-
Feedback from VRS topic :
"Well, I think I pointed it out.
I was proceeding step by step to send you more details and I realized that the problem is due to AS12 changing meteorological parameters very often. I changed AS12 settings 20 days ago to fly well synchronized MP session and it refreshes FSX weather much more frequently. I guess I'll have to revert to my previous settings (or smoother ones) for carrier based operations.
Thank you for your time.
"
So we can leave with this one ...
;)
-
FYI, I downgraded vLSO to 0710 and the behaviour is much better even w/ AS12 DWC.
-
Believe it or not, but all 0.7.* versions are the same in regard to how the program acquires current weather conditions and the coordinates of a carrier. :)
-
Okay, I got that.
It looks like it's just a matter of AS12 DWC then.
There must be too many frequent changes in the area where I fly.
AS12 might have difficulties to compute accurate weather oversea (far from a station).
-
I’m having the same issue that people running vLSO on P3D v3 are having with the program not recognizing FCLP sceneries. Only thing is, I’m running vLSO on FSX Gold Edition. I did make the switch from Windows 7 Home 64 bit to Windows 10 Pro 64 bit when I built my new machine this past April. No vLSO recognition of Lemoore, Oceana, or Meridian (IFLOLS not showing up at Meridian either). vLSO works as advertised with carriers. Any ideas or suggestions would really be appreciated. Thank you in advance.
vLSO ver. 0.8.2.11 beta
Flying the VRS Superbug (ver. 1.4.3.0) almost exclusively but having the same issue with all vLSO compatible aircraft.
TacPac ver. 1.4.3.0
TrackIR ver. 5.4.1.26786
FTX Global Base Pack
FTX Global Vector
FTX North America Freeware Packs
FTX Europe Freeware Packs
REX Essential Plus Overdrive ver. 3.8.2014.1126
FSX @ War ver. 1.0.1.0
FSX @ War Carrier and Convoy Planner ver. 1.3.3.0
Several MAIW packages
-
HornetMech,
The reason is simple - currently vLSO does not support Prepar3D v3, thus it does not read addon sceneries config files (where FCLP sceneries are defined). That's why no FCLP sceneries recognized under P3D v3...
FYI: I'm currently working on a new version which will support all present P3D versions.
-
I really appreciate the response Paddles. But I'm not running Prepar3D. I'm running vLSO on FSX.
-
HornetMech,
I apologize for my inattentiveness. Well, could you run my utility FSchecker 5 (https://drive.google.com/file/d/0B3pFCe8B4_FGbWlIZXNndmR3cE0/view?usp=sharing) to make sure it recognizes your sceneries? In the Summary window right click, select all, copy and then paste its output here in this thread or e-mail to me.
-
I am far far from being a vLSO expert (I don't mess with it much. The AI LSO's it uses have it in for me, I swear. Very often :( ), but is it possible your sceneries are not someplace vLSO "looks" for them? I know FSX lets you put sceneries almost anywhere, but does vLSO only look in specific places, maybe? Most people put their additional scenery into the Add-On Scenery folder in the main FSX folder. Could it be, perhaps, that vLSO looks there for it, only?
I don't know where you installed your sceneries, or the IFOLS Trailer add-on (if you use it). Maybe, also, the priority needs to be higher or lower? Maybe you don't have high enough (or low) in the Scenery.cfg. Again, I am guessing here. I don't have the faintest idea if these guesses have any validity at all.
I hope Paddles will weigh in on this. I am just throwing WAGs out there.
Pat☺
-
Let's see what FSchecker finds :)
-
I thank you both for taking the time to look at this for me. I love this program and really want to get it working properly. It may be Monday before I can get around to running FSchecker 5 as I'm earning my living this weekend, but I will certainly do that and send you the results Paddles.
-
Here are my FSChecker v5 results:
Local roaming path: C:\Users\Bl^ck$heep\AppData\Local
Roaming path: C:\ProgramData
=== Scanning HKCU root... ============================
Checking FSX...
------------------------------------------------------
Registry key SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 - OK
AppPath value - C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\
FSX.exe - OK
Now trying to read FSX scenery config file C:\ProgramData\Microsoft\FSX\Scenery.cfg...
OK, 144 scenery definitions read
Checking FSX Steam Edition...
------------------------------------------------------
Registry key SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0 - NOT FOUND
Checking P3D v.2 32 bit...
------------------------------------------------------
Registry key SOFTWARE\Lockheed Martin\Prepar3D v2 - NOT FOUND
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
-
HornetMech,
As you can see, no FCLP scenries found among 144 sceneries, defined in the C:\ProgramData\Microsoft\FSX\Scenery.cfg file.
Possible reasons:
- no FCLP areas installed (improperly installed)
- no FCLP areas are set as active in the Addon Scenery manager
- your FCLP sceneries are installed in a folder other than that listed in the Scenery.cfg
- some folder paths inconsistencies, specific to Win10
My guess is that's the reason #3. May I have a copy of your Scenery.cfg file?
-
Paddles,
File attached.
-
HornetMech,
Thanks! As I can see there are no custom sceneries in your .cfg file. This is strange...
Before investigating further please make sure the sceneries in question (Lemoore, Oceana, Meridian) are installed and active. You may attach a screenshot of the Addon Scenery manager.
-
I have a feeling he didn't show the right file. I suspect he showed the one in the main FSX folder, not the one that get's modified when adding scenery in the addon manager. That one is located in C:\Users\All Users\Microsoft\FSX, not the main FSX folder.
I may well be wrong, but I was looking for the "in-use" .cfg file. I had a heck of time, trying to figure out just where in FSX they had hidden it. Then I did a HD search, and lo and behold, thar she blew :)
Hope this is the case, anyway. May well be wrong, though, I usually am...
Pat☺
-
That's right, in the sent file there are 120 scenery definitions whereas FSchecker reports 144. This program scans the C:\ProgramData\Microsoft\FSX\Scenery.cfg
BTW, in Windows 7-10 the C:\Users\All Users\Microsoft\FSX is mapped to the C:\ProgramData\Microsoft\FSX (though this one is hidden) ;)
HornetMech, please send the Scenery.cfg from either folder.
-
PhantomTweak,
You're dead on correct. I did send the file from my main FSX directory. Thank you for pointing that out.
Paddles,
I'll post the file from the correct directory ASAP. Thanks again!
-
Scenery.cfg from C:\ProgramData\Microsoft\FSX attached.
-
PhantomTweak,
You're dead on correct. I did send the file from my main FSX directory. Thank you for pointing that out.
Glad I could help out :) It took me the longest time to figure out where it really was myself.
Don't get used to the "PT is correct" thing, though. It's such a sadly rare occurrence...
;D ;D :D
Good fortune and wonderful flights to all!
Pat☺
-
HornetMech, thanks for the file!
There are a number of FCLP sceneries defined in your .cfg and they all are set as active.
The fact that FSchecker didn't report them (as well as vLSO didn't recognize any of them) means that the sceneries were either incorrectly installed or some files within their folders were corrupted. The program looks for a .tag file in each FCLP folder. This file contains all the necessary data and must be present. Please double check again and make sure that each scenery has its own tag file, located in its scenery subfolder. Note: there are two subfolders in each scenery folder - scenery and texture.
-
Paddles,
I think we might be making some progress here. I checked the Scenery folders for Lemoore, Oceana, and Meridian and there are no files with the .tag extension in any of them. I then used the Windows search function to look for *.tag in the entire Addon Scenery folder and it gave me 3 results. It found .tag files for all 3 sceneries but they're not in the Scenery folder like you indicated they should be. Instead they are each located in their respective Mk14 subfolders. When I installed these sceneries I followed the instructions provided in their included .pdf documents exactly. Just as I did when I installed them on my old Windows 7 machine and everything worked perfectly. I'm not sure what's going on this time. Any guesses? And what should I do from here?
-
Ok, as I can see you have my FCLP packs for the three Uchi's sceneries. There are two .cmd files for each scenery - KN??_Mk14_Add.cmd and KN??_Mk14_Remove.cmd - and a readme file (in the KNMM pack there's no readme, that's my fault). Each readme describes how to add the trailer to a particular scenery, but basically the procedure is similar, the difference is in names of files and folders only. So, to add/remove the Mk14 IFLOLS to a scenery, just doubleclick releveant cmd files.
Hope this helps
-
I don't trust auto-installers at all. Old problem I have.
I looked through those .cmd files. All they do is add the files in the Mk.14 files, scenery and texture, into the appropriate folders. So I did that myself. Works great :)
All that's left is the FCLP light command files, which just turn a set of lights on for night ops. That one I use. Quicker and easier than doing it myself, and I'm lazy. ;D
Have fun! I know I do...
Pat☺
-
I apologize but now I'm getting a little confused on this. I was under the impression that vLSO worked with the Lemoore, Oceana, and Meridian sceneries from Uchi irregardless of whether one was utilizing your Mk14 trailers or not. Am I wrong on that? If you decide to use the Mk14 trailers does that change the way vLSO interacts with FSX and the addon sceneries? Are the .tag files specific to the Mk14 trailers or the sceneries? Or both? Are the .tag files on my system in the wrong location?
I had to run the KNLC_Mk14_Add.cmd 2 or 3 times before the trailers actually appeared next to the runways. I not sure why I had to do this. I ran the Remove.cmd before re-running the Add.cmd each time. I don't know if that was necessary but I just did it for good measure I guess. I still can't get them to show up at Oceana or Meridian and I've tried running the .cmd file as an administrator and normally. Still no vLSO recognition of Lemoore, Oceana, or Meridian.
I apologize for all the questions but I just want to understand what went wrong. I'm thinking it's related to Windows 10 since I installed everything (Uchi's sceneries and your Mk14 trailers, Paddles) in accordance with their respective instructions just as I did on my Windows 7 machine. Everything worked perfectly on the Windows 7 system.
-
Do you, by chance, have your FSX, sceneries, or vLSO installed in C:\Program Files or \Program Files (X86)? I understand a lot of people have problems with that situation, as Windows puts extra "user protections" in place in those folders.
Bear in mind, I am far, far from an expert with vLSO, or it's add-on sceneries and such. Having said that, I believe, and may well be wrong, that the Mk.14 add-ons to Uschi's scenery should be integrated into them. IE: take the files in the Mk.14's scenery folder, and put them into the existing scenery folder of Uschi's scenery. ALL the files, including the .tag file. Obviously, same for the Texture folder.
I believe, and may well be waaaay off-base here, that then vLSO will work with the sceneries you have. As far as I could tell, that's what the add.cmd file does. It just automates the process so you don't have to spend time cut-n-pasting files all over Yuma's half-acre. As soon as I can, I will try my method (again, I hate auto-installers of any kind), and let you know the result.
Hope this helps a little :)
Pat☺
-
PhantomTweak,
I do in fact have FSX installed in the C:\Program Files(x86)\Microsoft Games\Microsoft Flight Simulator X directory on my computer. Addon sceneries are also run from the C:\Program Files(x86) directory (either within FSX or from their own directory (ie. FSXatWar and AICarriers). vLSO, however, is located in C:\Users\*\Documents. And I have heard the same in so far as people having problems with games installed in the Program Files directory in Windows. However, That's the same place I had it installed on my windows 7 machine and I had no problems so I didn't feel there was a need to change anything when I moved to Windows 10 Pro. And just to be clear, in case it's relevant here, I'm using a completely new machine with a fresh install of Win 10. Not an upgrade from Win 7. Also, I thought I read at some point that the issue with installing games, or simulators, in the main Program Files directory was related to Windows User Account Control. I have always turned UAC off right after I install Windows due to it's intrusiveness and problems it can create while it's trying to "help you". For my parents, I would recommend they leave UAC on, but not for someone like us. I thought about trying to run FSX from another directory but I believe that would require a complete uninstall and reinstall of FSX and everything else. I don't believe you can just cut and paste the directory but I could very well be wrong about that. The thought of a complete reinstall of FSX and all the addons makes me feel sick. :( :(
-
It certainly appears that installing and running flight simulators differs in W7 and W10. I'd suggest you reading this THE FSX COMPUTER SYSTEM: THE BIBLE - BY: NickN (http://www.simforums.com/forums/the-fsx-computer-system-the-bible-by-nickn_topic46211.html)
Just a couple of Nick's advices on UAC:
UAC and WINDOWS DEFENDER: Shut these Windows features down immediately after Windows is installed and then reboot. This should be done before any drivers are installed.
Windows UAC (User Access Control) is useless to protecting a single user computer. It was designed to protect a office network from malware spreading across the network but will not protect the original computer system the malware was executed on, nor will it protect a single user system.
If you use FSX and 3rd party addons by now you are probably already aware that User Access Control can block proper function of addons and even FSX. UAC should be completely shut down for both system performance as well as stop issues with installing and running addons.
And about UAC in Windows 8 (UAC in Windows 10 is pretty much the same as in Windows 8 ):
Windows 8 users, you have my condolences. Properly shutting down UAC is completely different in Windows 8. Read this (http://www.simforums.com/forums/windows-7-and-windows-8-uac-blocks-gex-interface_topic45785.html)
And a very practical suggestion:
METHOD 1:
VERY IMPORTANT: For this method to work, FSX, FS2004, P3D or any add-on product MAY NOT be installed in a "windows protected area/folder/directory" such as
\Program Files
\Program Files (x86)
You MUST install FSX/P3D to a folder you create on your main (C:) drive or alternative separate drive.
EXAMPLE: C:\FSX or F:|Flightsim or install FSX/P3D any folder outside of the directories shown above
"The thought of a complete reinstall of FSX and all the addons makes me feel sick" - Which is better: spend a few hours more reinstalling all your stuff to a proper location or keep struggling with "Microsoft's infinite wisdom"? ;D
-
I believe I've read on another forum (AHEMflightsimAHEM...) that Win 10 "protects" \Program Files and \Program Files(x86) no matter how you set you UAC settings.
As a great man said, which is better, un-installing/re-installing FSX and all the wonderful add-ons, or keeping struggling with this day after day?
As to cut-n-pasting the game it's self, no that doesn't work. HOWEVER, except paywares, most freeware, FSXBA F/A-18c, just for a wild, top of my head example ;D , can be simply cut-n-pasted to the new installation, no problem. I had a lot of problems with having to reinstall FS9 before I got FSX-SE, and I just got into the habit of zipping up the various folders that have add-ons. Things like \Guages, \Effects, and so on. Then I could just unzip them into the new installation, and tell it not to over-write. Poof! Add-ons installed. Only lengthy process was rebuilding the add-on scenery library. Small price to pay, IMO.
By the way, when I get the sim installed, and before I add anything at all, I always (now, anyway, could have saved a lot of head-aches if I had earlier...) zip up the game folder, everything. That way, I have a back-up of the "virgin" install, in case something (like me) messes up badly. I keep all my zipped up backups, add-ons and so on, on an external HD I can plug in easily, in case I want something off it. And with 7Zip, which is what I use, selecting individual files to unzip, and where to unzip them and so on, is very simple and easy. A huge plus for my poor ol' brain :D
Payware is a horse of a different color, but really, and I hope this is the case, as long as you keep the confirmation e-mails, with the registration codes, pass-words, or whatever, you are golden.
Hope all my rambling is of some small benefit...
Pat☺
-
Why didn't you guys tell me all this before I reinstalled everything on my new machine? :) Ok. Well, I'm going to be out of town for about 2 weeks so I'll think about the joys of a fresh FSX install while I'm away. Once again, I can't tell you how much I appreciate both of you working with me on this. I will of course report back soon on my decision and how it turned out.
-
Why didn't you guys tell me all this before I reinstalled everything on my new machine? Smiley
I'm sorry. My mind reading has been a bit off of late. Not sure why... :P :D
Good luck!
Pat☺
-
It only took a little over a month, but I have finally reinstalled everything and have tested my new FSX install with vLSO at Lemoore and Oceana and on the Nimitz. I'm happy to report that vLSO is now working as advertised ;D ;D ;D My thanks again to both Paddles and PhantomTweak for their time working with me on this.
-
I'm glad you got it all up-n-runnin!
Now, go enjoy the heck out of it :D
Pat☺