ZippinZim

Hello and forgive the ignorance! Must Linda be previously installed for this to work? I have followed the directions to the letter, but no LUA controls show up in FSUIPC. I have FSUIPC 4.30. Thanks for the advice in advance!Jeff

Well, I uninstalled PD and (without restarting) I tried to launch FS2004. Guess what? It worked just fine and launched. So I've proven again the problem is PD. That's about all I've proven though.

Bob,Event viewer doesn't seem to be logging a problem at the times that I've launched FS9. I'm not terribly familiar with the event viewer, but I've browsed through most of the logs and haven't noticed anything with a time stamp matching a launch attempt. The problem started as soon as I installed Power Director. I know I can fix the system by restoring to the point I set right before installation, but I'd REALLY like to have both programs available on the same computer. I have to believe there's a simple fix for it, but what do I know? Thanks for your help as well!

Thanks again, Feng. I did find a running process that was PD related, so I stopped it. It didn't correct the problem, though. I've exported and attached a list of my processes (quite lengthy, and tab delimited so use a spreadsheet program) in case you had a couple minutes to browse through. I already owe you big time, so thanks again.Jeff

Feng,Thank you for your post. Great ideas and I fully expected one of them to work, but no joy. I didn't find any new processes running, and even re-booted and checked again. I figured it was a video issue (codec?), but being unfamiliar with codecs, I downloaded and installed k-lite as suggested. Still no joy.I renamed my fs9.cfg and tried to start the sim. The screen resolution changed as it was trying to start, so it's at least getting that far. But then again the splash screen went away and I was back at my desktop. The FS9.cfg file, the weather.bin file, are all updated with the time stamp of when I attempted to start, so it's something deeper. REALLY suspecting a video issue. here.I haven't tried your experiment yet, but again thinking it's a video issue, I wonder if it gives you any better ideas.Again, thank you SO MUCH for your help. I wanted to edit videos on this PC because it's so beefy due to my FS requirements.Jeff

Is your answer based on either having or hearing of other issues such as this, or simply based on common sense? I'm not trying to be rude, but is there a known conflict between the two programs or are you simply suggesting another editing software MAY be more compatible? Thanks for the response.Jeff

Hi all. I've tried twice now, but it appears that installing Cyberlink Power Director 7 (video editing software) causes FS9 to refuse to start up. I get the FS9 splash screen, but then after a few seconde is disappears and the sim doesn't launch. I did a system restore and FS9 worked fine. So I created a system restore point and again installed Power Director. And again, I have the same problem right away. FS9 was the first thing I tried to run after installing Power Director, so I know it's not something other than Power Director conflicting. I am running:Vista 644GB RAMPentium E7400 on a Gigabyte MotherboardnVidia GeForce 8800 GT (two of them running three screens)Any ideas? Thanks for the help!Jeff

Problem solved!!I had already edited the permissions for the group "Everyone" to give full access. What I had to do was to add a group "Guest" and give it full access. That worked. It allowed me to access the FS9 folder from XP and thereby giving ASA access to the same folder. Vista is a strange animal!Jeff

Jim, that didn't quite do it. I have, however noticed that each time I start ASA, it tells me it cannot find the FS2004 location, so I have to point it out each time. Curiously, I do indeed see the installation folder on the network, but cannot access the files in that folder from the laptop.On the other hand, ASA no longer asks me for the FS9 Data file location (seems it's remembering that location just fine). However I am able to access the individual files via the laptop ( on network network), unlike the FS9 installation folder files.I have added the appropriate permissions to both folders, but for some reason I can see both, but only access files in the data folder. Certainly seems like a sharing issue, but I'm out of options at this point.Thanks once again.

Thank you. I will try that. To answer your question, yes when I installed to the laptop it did ask for the license key and it also registered itself.

I believe I am having a similar issue and you may have answered it here, but I'd like some clarification.I just upgraded my FS9 PC from XP to Vista-64. I have an XP laptop that has been running AS6 via WideFs perfectly for over a year.Now that I have upgraded to ASA, I can't get it to connect from the laptop to the Flight Sim PC.Here's what I have done so far (and in order):-Clean install of Vista 64 and subsequent install of FS9, patched-Downloaded and installed ASA on Flight Sim PC (everything worked just fine)-Uninstalled AS6 from Laptop (mistake??)-Installed ASA on laptop-Shared FS9 folder on Flight Sim PC -Shared FS9 Data folder on Flight Sim PC(Both folders can be seen remotely on the laptop, so I presume sharing is working correctly)-Start up FS9-Start up WideClient(connection between the two computers is made and Squawkbox even works through the connection just fine)-Start up ASA-Alert box pops up and I point ASA to the FS9 folder and the FS9 data folder-ASA initiates and looks to be running fine, but the nearest location shows as SEA when my aircraft is parked at DFW.It won't update the weather at DFW and I think it's due to a comm problem between the laptop and the Flight Sim PC. My suspicions are a sharing problem, but I have both folders shared and full authority given to "Everyone"Can you help me please? Thank you!

Okay, thanks. Now I understand that the "database" that drives their GPS is integrated in the trainer. And that it will drive an approach even if the FS9 scenery file doesn't have the appropriate fixes (FS9 nav data is irrelevant to the third party GPS). I have also found elsewhere that there is no upgrade to the trainer at this time...at least not public and for less than $12k!Thanks again for the responses.

Thank you for your reply. As I think back and as I read your post I presume you're talking about .bgl files that come with new scenery. If that's the case, I certainly understand. Now, let's say I download the latest and greatest RealityXP update which includes the new, updated approach procedures. Does the FS9 database/scenery have to have the new fixes in order to fly (and use) the correct fixes in the RealityXP GNS430/530? I presume it doesn't and that the RealityXP GNS430/530 will still show the new fixes. Am I correctly assuming?

Hi all. I've done multiple searches, but cannot find the answer to my question. Forgive me as I know the question had to have been asked before.I was flying an RNAV approach using third party RealityXP GNS 430 when it vectored me to a fix that was not part of the currently published real-world procedure. Apparently the real-world procedure have been re-written using new fixes. I opened up the stock FS9 GPS to see if the new fix was depicted, but as suspected the new fix did not show up at all.I know I need some sort of update so that the GNS430 displays and utilizes the new fixes, but what about FS9? Is there a way to update the navigation database to include all (or most) new fixes, ILS frequencies, etc?Thank you for your help!

Okay, I did search for the issue before posting, but I was searching "crackling" and not "distortion". I found another thread where the issue was described (more appropriately) as distortion rather than my un-scientific "crackling". Anyway, it seems there's a sound issue when you have your frame rate slider at unlimited (as mine was). I moved it down to 50 FPS and the distortion seemed to go away or to at least reduce in volume to where I cannot detect the "crackles" as easily. It still sounds a little funny to me, so please let me know if any of you have the same issues and a sure-fire way to correct the issue. Thanks again!Jeff Zimmerman