A36 Apache

No one at all?

Have you tried to taxi the Aerosoft F-16 at night with no airport lights and no moon? I would call the lack of a landing light that illuminates the ground a case of releasing an obvious bug, or worse, a defect they allowed to get by. I thought I was safe with Aerosoft, but after that experience I will wait for a long time before I purchase a new plane from anyone. I can also see, after that, the point the OP (PPSFA) is making.

Have you used the logbook checker to test for errors?

My favorite plane has always been the P51 with the four cannon (after the A36 of course), but I could make do with the Warbirdsim P51B & Cs if I knew they worked with FSX with only rudimentary modifications. Has any bought any of their packages and tried it yet?

The real secret to V64 is NOT using C:\Program Files (x86)\ for installing your app to. If you use something like C:\Program Folders\ instead UAC won't get in the way and none of your files get hidden in the virtual store. If you do install to C:\Program Files (x86)\ all you have to do is turn off UAC (which is a good idea anyway) and create a shortcut to the virtual store files, so that you can access files faster.

I can't wait to see the results of their efforts actually come to FS.

Aw man! I just bought the program like a month ago! :(

No big deal I just couldn't find a forum for direct contact.I noticed that the installer always puts the files into c:\Program Files\... which is no problem if you read the messages as you are installing, but there are (as we all know) people that just click and click ...On Vista 64 or XP 64 you don't want the files going there. Instead they should go to C:\Program Files (x86)\...I'm not sure if the installer you use can tell the difference and it's not hard to make the change manually, but it could be some people won't know/realize what happened.If you are aware of this already my apology for bringing it up and posting a new topic. I love what you are doing for FSX!

Falcon, where can I find this?

Make sure, at least, that the 'large water body feature' is enabled under UTX's 'Water Bodies' feature tree item. Same goes for the other water bodies if it's smaller lakes and ponds you're missing.

I'd guess you were running with drivers you got from the Nvidia website?

I'll bookmark their page for frequent visits then.The 400 is the only reason I play the lotto!

Wow! SR22? I really want to compare one with the 400 (w/ Garmin).

I was about to respond to your original posting...Yes, shouldn't be a problem with Vista, but just recently I saw a nasty conflict with a SB Live 5.1 card that brings shivers to my spine to think of the problems it presented.

I think you fail to consider shared IRQs. Sound and video will very commonly share IRQs and that in combination with CPU load can present difficult problems.

Sometimes we expect too much from these computers we play with and we have to be careful not to load them down with too much overhead. If we expect them to be 'do-everything' systems then they can't do any one thing well. So, we should decide if we want to use them for games, or multimedia, or programming, or whatever. You can still have all of them, but you are better off creating separate boot environments for each, so that you don't have conflicts. Just a thought.

I don't think that the audio stream is discernible with the process manager. I think something like RightMark ( http://audio.rightmark.org/products/rm3ds.shtml ) is what you want.I can tell you that I see an awful lot of things that are stealing memory and frames from you (Java Update Scheduler, Memeo, task scheduler...), which you can always shut down for the periods you are running FSX. Have you ever tried AlacrityPC? I used it for quite a while and then finally shut down what I never need and just start TrackIR and FRAPS myself before starting FSX, which works for me.

Not if the partition is on the same physical drive as the system files. If, you have more than a single hard drive (and a second drive is faster than your system drive), then it is better to place your page file upon the second hard drive (separate from the system files). Optimally, you could place the page file on a SSD, which would have the added benefit of being blazing fast.Otherwise, there is no benefit of creating a partition just for a page file.

If you're talking about the SupremeFX II sound system it puts 100% of its sound processing onto your CPU and no it's not that good either. I understand what you want to do and now you have me wanting a second BGears card myself. If you had this and a low end XiFi card then I understand what the problem was and yes this probably killed you due to CPU overload and shared IRQs (just a thought though without hands-on exposure).Still, I hope your flight works out well and you have good news.

I was waiting until I heard that your flights sans sound was a success. The card you chose is a great one. Choosing between Professional and Champion series is a personal preference. Personally, I don't care for Creative products, so I would have gone with BlueGears, or Xonar.I would go to Radio Shack and get a y-splitter so you can have two sound jacks to the single card, rather then run two cards. Any USB headphone is going to load drivers and/or programs into memory and run off the CPU. If, you know for sure this sound/audio/CPU load is what is causing you the lockup periods, then I would avoid USB like the plague. I would avoid USB anyway because of my experiences (frame rate stutters and lockups).However, if you already know that communications cover up aircraft/sim sounds then I guess you could run two sound cards at the same time. I haven't ever thought about that (if you do that let me know how it works out). I am gaining more and more interest in this online adventure you engage in.

The memory handler in Vista is a lot more efficient then it was with XP. Have you tried dropping services you don't need and slimming down the startup programs? You can also optimize things a bit more with your page file; minimum page file size should be 1.5 times your available RAM and maximum size 3 times available RAM (you can go higher but bear in mind you are using hard drive space).If you've turned off your page file you're killing yourself.

Nhancer is a really good way to learn what settings do when you make changes, but you are much better off using the NVidia Control panel and making the changes yourself, as well as creating your own profiles. Particularly, when dealing with Vista, Nhancer lags behind driver updates and it can cause bugs to appear (perhaps the very one you are experiencing). All that aside it's another application installed that you don't need since the Control Panel is already available to you.Also, when updating programs (FSX too) you are better off to completely remove your old profile and recreate another one once the update is completed, especially if you do not keep FSX (or whatever game) in its default location.

With Vista its best to go straight to the manufacturer of your video card (eVGA, PNY, BFG, etc.) for the latest driver and not the generic driver available from the Nvidia site (speaking specifically of Nvidia but likely the same for ATI). Also, with Vista it is very important to thoroughly clean the old drivers off your system before updating them (either sound or video).

Unfortunately, I have already run into the same problem with on board sound and USB myself. I'm totally against using both at the same time by the way. I had a similar issue myself. Not in FSX but another online game that hits the CPU just as hard. It's the very reason I went to a sound card that uses very little, if any, CPU. Network traffic is a lot heavier in that program, so perhaps it isn't your problem.Once again, page file initial size should be 1.5 times your RAM and maximum size 3 times your RAM (although for maximum you can go higher). You could also remove drivers for both sound systems, clean your system of sound drivers and turn off on board sound within the BIOS as a final test, but hopefully before you get to that point your data collection approach will reveal the problem nicely.