mcarvela

FSX runs great for me. You just need enough computer for it to run properly. Take a look at the post just above this one with the screenshots from FS2, Tomahawk, etc. Then tell us again that FSX is disgusting.

Just a thought. You might try AISmooth which should vector traffic away from you, although I'm not certain that it would work for ground traffic. But it's freeware and worth a try.

Do you mean they won't start at all or that they start and then immediately die. If they start even a little and then die out, open your throttles a touch as pistons won't start if you don't give them a little gaas.

Have you tried simviation at http://simviation.com//fsnd/Downloads.htm They have a nice Citation X which is a true FSX model, not a portover. Quite nice and also freeware

I'm just wondering, why? Why would you buy a flight sim program and then just sit back and watch it? Isn't the whole idea to fly the airplane? If I just want to watch, I'll turn on the TV. Not trying to be rude, but just trying to understand the whole concept.

I've already posted this over at the other site and got no replies. So I thought, maybe someone over here at AVsim has some ideas. I have FSX installed to C:\FSX and FSUIPC 4 is installed correctly in the modules folder. FSUIPC works for everything else but when I start AirHauler, after the company loads successfully, I get an error message that FSUIPC cannot be found in the FSX installation. Within Airhauler, in the options menu, I've already checked and the path is shown correctly as C:\FSX. Does anyone have any ideas as to why AH cannot find FSUIPC and what I can do to correct this. I'm running an Alienware Aurora R3 with Win7 64 bit. BTW, I've already asked at JustFlight and they were absolutely no help.

Where I'm now confused is, at Microsoft.com, the updates talk about direct x 9.0c. But I already have direct x 10 installed. Wouldn't that upgrade actually take me backwards? BTW, the sounds all work when I fly the Tinmouse. I'm just wondering if the error message is itself an error.

I downloaded the Tinmouse 737-200ADV which is in today's new files. The plane works perfectly with 2 exceptions.1. On starting the file, I get an error message that FS2AUDIO.DLL failed to load with the error 0x7e. I've already put the dll file into my system 32 folder (Vista Home). I've also tried registering the dll but get an error message that the file can't be found at that location.2. Although I can see the flaps going down in the external view, in the cockpit view, the flap indicator doesn't move from the fully up indication.If anyone has downloaded this plane and has any answers for these two problems, I'd really appreciate some help. ThanksBTW, the plane looks outstanding.

Whatever the problem was, I solved it by uninstalling and then reinstalling xgauge. It now works perfectly.

I'm running FSX with ASEvolution. What is happening is that I can hit Shift-5 and bring up the X Gauge. But when I click the powwer button, I get message "New Imagery Downloading" on the X Gauge screen. The problem is that it never loads. I waited over 5 minutes and that message was still on the screen. Can anyone tell me why it won't load the images. BTW, recently, I did a complete reinstall of everything including FSX, FSUIPC, ASE, etc. Before the reinstall, I was running ASA and the X Guage worked perfectly. It's only since the reinstall and upgrade to ASE that the gauge stopped working.

Now I really feel dumb. The problem was that I was trying to run RC for FSX from the rcv4 folder instead of from the rcv4x folder. All is now working perfectly.

That's what I tried first and it wouldn't work. So I just removed makerwys.exe and all the things it created, re-downloaded makerwys.exe from Pete Dowson's site, put it in the FSX root directory and started RC4. I then clicked on the rebuild dcenery db, answered no to the widefs question, and RC is still telling me that makerwys.exe is not in my FS directory. So why can't RC find it? Thanks

I had to reinstall everything from scratch and have a problem. I installed all the dll files to not get the error reports. I also put makerwys.exe in the fsx root directory and ran to from there, generating all the files from makerwys. Still, when I start RC4, when I try to rebuild the database, it asks if this is a widefs configuration. I answer no and I get the error message "makerwys.exe is not in your fs path, which should be. I'm a bit confused. How can I make RC find the correct path as the file is definitely where it should be. thanks

I had everything working fine. Then I had to reinstall everything when I had a massive crash. Now, when I start FSX in windowed mode (which is the only way I can see my desktop to open anything else) and then start RC4, no matter what my location is, RC4 sends me to Lat 0 Long 0 and, of course, I crash into the water. I'm running everything as administrator. If I run FSX in full screen, then I can't see the icon for RC4 to start it. Any ideas why I'm being sent to the coast of Africa? Thanks. Oh yes, when I close FSX, there is a RC4 window in the background with a runtime error 9. The path to the .PLN, which FSX created, is correct.Mike

I wonder if anyone else is having this problem. I recently had to reinstall everything from Vista on down. I've got everything back, but with RC4.3, I'v had to enter the registration 3 times already. For whatever reason, everything will be fine and then I'll load RC and all I get is the registration screen. So, of course, I have to contact John again for a new unlock code. It's getting tedious. I'm wondering if maybe I should load RC as administrator. Would this keep the program from losing the registration code. Any help would be appreciated.Mike

I found nothing by searching so maybe someone knows. I've installed the software and drivers for the X52 on my system running Vista Home Premium 32 bit. When I try to run the program editor, the program closes with a message about SAI3DVIEWER.DLL. I see that dll in the Saitek\software folder. I've tried copying it to the system32 folder and registering it, all with no luck. Is there a way to run the program editor in Vista and get around this .dll error? Thanks

I had to do a complete reinstall of everything from Vista on down. When I got to reinstalling the FS things, I installed FSX, then FS9.1 (I still use both), then X-Graphics, ActiveSky X, and then ASA upgrade. the problem is that when I start ASA, I am no longer given the choice of which flight simulator I want to use. It automatically goes into FSX mode. How can I get ASA to give me the choice of which flight simulator I wish to use.

Hi JimAh, success. You were absolutely right, the problem was in the registry. For whatever reason, the registry entry for the FS9 path was pointing to the FSX directory. I'm at a loss how that could happen. Anyway, I edited it to read FS9 and the Start FS button now works correctly. Thanks a million for you help.Mike

Hi JimI ran the Flight 1 utility a few replies ago. FS9 was on my drive and deleted about a year ago. At that time, I removed all folders pertaining to FS9. I just recently re-installed it on my drive, but again to the default directory. But as I said, since the reinstall, I have run Flight 1 utility. So I'm wondering if the previous install and deletion could be affecting things, although I don't see how.Mike

Hi JimSorry for the delay. I was at the US Open today. Yes, if I start FS9 from its own icon, it runs OK both in windowed mode and in full screen. I have an nVidea GeForce 8800 GT with current drivers 185.85. Also I have a Dell XPS730 with a Core 2 Extreme X9650 at 3.67 gH, 4 gig ram. In other words, plenty of computer to run all this. Out of curiosity, where is the utility that ASA uses to look for FS9. I'm thinking that it might be looking somewhere else than where FS9 is. Perhaps, the location can be edited???Mike

Already tried that. But I just tried it again and no luck. When I click on "START FS" I get a small window that starts to appear and quickly disappears with nothing left in the tray. This is even when I run as administrator. BTW, yes, FS9 is in the directory that FS9 defaults it to. Hmmmm, puzzling.

Hi JimSorry to be a pain butI use an unregistered version of FSUIPC. I just ran the registry repair utility you sent and still no happiness. Oh well, ASA works for FSX so this won't be a total loss.Mike

Hi JimUnfortunately, I didn't get any e-mails.Mike

I've installed ASA and registered it. ASA starts normally and I select FS9 as the flight sim to look for. After ASA loads and is ready, I press the button to start FS, but nothing happens. I get a momentary window which disappears immediately leaving nothing in the tray. If I start FS9 manually, ASA doesn't find FS9. Changing my location in FS9 to KISP but ASA is still locked to KSEA. I have FSUIPC 3.90 in the modules folder. The odd thing is if I start ASA in FSX mode and hit the start FS button, it finds FSX with no problem (I have both FSX and FS9 on my computer. I'm at a loss as to why ASA cannot find FS9 even though I have the correct version of FSUIPC installed. I'd appreciate any ideas. BTW, running VISTA Home. Thanks for any help.

Oh, now don't I feel dumb. I reinstalled FSX and forgot about FSUIPC. Thanks JD. You must get really tired of dealing with the dummies. LOLMike