crash_continental

Okay, I've read that ASE has problems with non-FS9 waypoints and will give you an "incomplete weather synthesis" (unlike AS 6.5, which always did). Even when I go into FS9 and re-save the flightplan with the FS9 flight planner, it still doesn't work. So my question is; how can I get my head/tailwind component? On trans-oceanic flights this is a must. Or should I go back to AS 6.5? Thanks, Daniel

Yeah, tried this. Did not work, unfortunately. It's a really crazy issue. My controllers can't be configured (you tell it to do one thing, it does another. Links two controls together, etc) In FSUIPC when I look at Joystic calibration it clearly shows a huge lag behind the movement of the axis. My view hat is like it's permanently in the "up forward" position. It's like the .dll for the controllers has been erased, or changed somehow. Don't know. I read about another guy who had exactly the same issue, but just did a reinstall. Maybe that's all I can do? Any guides for reinstalling FS2004 out there? I have many modifications that I'd hate to lose. - Daniel

Thanks for the effort, though.

Nope, didn't seem to do anything at all. Thanks for the suggestion though. Any other ideas? Thanks - Daniel

Hi, Looks like my FS9 is messed up after a FSX unistall. Control assignments, views, at the very least. Anyone know what's happened? Any easy fixes? Thanks, -Daniel

Hi again,Yeah, even with these issues fixed, I still have autopilot disconnects. Actually, what seems to happen is I get an autothrottle disconnect, and have to re-engage the autothrottle.It often (but not always) corresponds to huge altitudes shofts while at cruise. I'll be flying along at 39000 ft, and suddenly the altimeter shows 37800 feet. The aircraft gives an alarm and struggles up to altitude and disconnects the autothrottle.Sometimes I just heard an alarm, see the engines almost flameout, the autothrottle disconnects and comes back to whatever RPM percent I happened to have my throttle unit set at.It also always disconnects whenever I go into the menu bar and chose the FSUIPC options tab. Even if I change nothing, the autothrottle disconnects.- daniel

Hi there,I have the Samsoft Taipei scenery (purchased, I believe, many years ago) and have noticed that some of the taxiways exhibit the behaviour of rough ground when you taxi over them (high thrust needed, and 'dust' clouds coming from the wheels). Also some of the runway textures disappear when rolling down them.I know this is some kind of flatter/elevation problem, but don't know how to fix it. I have a flatten program, but I don't think it will do the trick. As far as I know there is no Samsoft Scenery website or forum, but would not expect to get help there anyway after all this time.Anyone with a suggestion on how I might fix it? Thanks,- daniel

Okay, I will do this.One thing I just noticed was my FSUIPC.ini file has a lot of duplicate entries. Things like:WindTurbulence=NoWindTurbulence=YesCloudIcing=NoCloudingIcing=YesSome of these are repeated four or five times. Surely this must have something to do with it? I imagine I only want one entry per option, don't I? - daniel baker

Nah, even with it all turned off it still disconnects the autopilot. After checking in the PMDG forum it seems like no one can fix it. Bottom line - ASE and PMDG do not get along. (ASA 6.5 was fine)- daniel baker

Hi,Seems all weather smoothing must be turned off, both in ASE and FSUIPC. Turbulence does not seem to turn the A/P off on it's own. Tested 10-15 flights so far.- Daniel Baker

Hi there, SInce installing my GTX 480 on my computer I've always seemed to have one or two nagging problems. The one I've experience lately is the most frustrating, and I've run out of ideas as to how to isolate and deal with the problem. Problem:When changing view on the view hat (or even during taxi, when turning) my FPS will suddenly begin to drop rapidly, and become stuttery (from 60 to ~ 15 FPS). It clears when I hit the ALT key and bring up the menus, and FPS return to 60. It'll continue to happen every so often, until I hit ALT again. My set-up Q6600 (overclocked to 3.8MHz)EVGA GTX 480Windows XP, Service Pack 3nVidia driver Version: 6.14.11.9975 (newer drivers introduce all kind of strange effects and artifacts - it was my understanding that using older drivers for FS9 was the only way to go, and that has been the most stable driver I've found)FSUIPC registered versionFSPassengersFSCaptainDBS Walk and FollowHundreds of add-on airports and freeware AI traffic packages. I've disabled all my add-on scenery, and the problem still occurs. I've disabled all AI traffic and the problem still occurs. I've tried removing the .dll for FSPassengers, FSCaptain and Walk and Follow, and the problem still occurs. I would very much like to avoid doing a reinstall, as I've hundreds of add-ons that I've purchased at huge cost and many hours of installing and tweaking. If this is my final recourse, I would seek advice at how best to do it with an eye to getting everything up and running again. Anyone have any ideas at what I should do next? Thanks in advance for your help. - daniel

Okay, thanks for this! Although I'm using FS9.1, not FSX. Do I edit similar values in the FS9.cfg? - daniel

I know this has been raised before, but I've been unclear as to what I am doing wrong, so apologies if this has been answered and my search skills are at fault! I have never been able to get the PMDG and ASE to work properly in FS9.1. I regularly get disconnecting autopilot functions, and S-turn issues. I also have ASA and never get these issues. Windows XP, SP3FS9.1ASA build 647FSUIPC registered version.FSPassengersFSCaptainPMDG 747-400, latest updates. The issues are present in all parts of the world, although it seems to happen more regulalry over the large expanses of open ocean. Thank you very much for your help, - daniel

Very true, however the argument could be made that had Feelthere patched up their Airbus line (like many of us here believe they should have) there would have been no need for this upgrade at all. Rightly or wrongly, people here are mostly buying this 'upgrade' hoping that it will be in fact a 'patch' for all the systems. And to be fair Wilco is implying a patch of existing systems by showing a mapview of a holding pattern (on their purchase page), which they show to be stable. One would infer from this that the autopilot glitches had been addressed, extending hopefully to things like managed descent, etc.I glad you have experienced good customer service from Feelthere - many of us here have had the exact opposite experience. I personally found nagging deficiencies in the Embraer line (the first round, not the new ones - not going to chance another purchase regret) and the manuals (especially). Any request for updates on either were either met by stony silence, or outright disdain.- daniel

Wow,Shameful. Even worse than I expected, actually. I can only guess that Wilco knew there was trouble with the update, and kept delaying and delaying, trying to decide whether or not to put it out. Seems the lure of money won out.If it wasn't before, Wilco's name has been forever sullied by this event. Having no support forum makes them look like a shifty company - putting out a product (with no refund available) like this will only confirm that in everyone's mind.Even with an update to make this workable - something they are not known for - Wilco has cemented their reputation. Most FS users in the know (particularly here, in forums like these) will never do business with them again. My only fear is that new users, or those without knowledge of the forums like these, will still fall for the predations of a company like Wilco. Perhaps it's time for AVSIM to become involved? Just a suggestion - but removing their ads from the AVSIM website would be my humble suggestion.As for Wilco; a full refund should be offered to all those who were duped by this project. Nothing else is really ethical, is it?- daniel

Just be aware that some people (myself included) purchased the 'upgrade' from Eric Marciano, and never got it to work properly. There were several new bugs to go along with the fixes, but the most frustrating thing was that the throttle control seemed tied to the main panel window (or perhaps the VC). So when if you decided to fly the approach in the mini-panel (the "W" key on my set-up - I often do this to fly approaches as the viewpoint is skewed from a main-panel view in FS. I use the pop-up PFD for the approach - SHIFT-6) the throttle would surge unexpectedly, and uncontrollably.I was told by Eric that this was my problem alone, and after awhile he stopped responding to my emails, so I uninstalled it and went back to the old version; flawed, but at least useable. I later found out that I wasn't the only one with this issue.I was hoping he'd have fixed this for this update, but you can't fix an issue you won't admit to. For what it's worth, some people did not report this issue.- daniel

My experience with Wilco/Feelthere add-ons have been mostly disappointments. I find they either have critical omissions ("we never said it would"), system and FDE inaccuracies ("we're not sure it could") or outright bugs that they will not acknowledge or fix ("we have your cash, tell us why we should?!"). I also find their manuals vague and incomplete (particularly in regards to performance numbers).Having said that, I've always found the products to be "close" to being satisfactory. Just a tweak here and there and they would be satisfying enough that you could look past the odd foible/omission. I find their support to be unsatisfying (yes, there are many posts in the Feelthere forum, and they do get replies, but the answer is often unsatisfactory, and usually posted with the kind of brevity that borders on rudeness).I have tried many ways to get the Airbus Vol 1 to work, including purchasing the 'upgrade' from Eric Marciano (in NO WAY connected with Feelthere... I know, I know...). Nothing has worked properly for me.I do have a version that works most of the time (removed the 'upgrade'), although it occasionally causes CTDs. The descent management just doesn't work, and a few MCDU features are buggy. The flight model handles poorly, but not brutally.I'm dying for an Airbus A320 (I also bought the Airsimmer disaster) for FS9, and would even purchase this whole thing again if I had any faith in the company at all (being Wilco, Feelthere, Wilco/Feelthere or whatever the confusing relationship on this product is.) To regain that faith, I'd need to see satisfied customers. To see satisfied customers, I need a support forum that remains open indefinitely.Wilco has no forum, so the only thing left to do is watch here in the Avsim forums, and see what transpires...

You need to power up the electrics... either by battery, ground power or APU.On the overhead (left hand side of panel) hit the battery switch. That should power things up, but may drain the battery in time. By going to the "set-up" panel, under Ground Commands, you can choose to connect to ground power, which you then have to select on the overhead panel. You may also start the APU, which will do the same thing. In both cases the battery needs to be selected first.In real world ops the aircraft would be connected to ground power, until 5 - 15 minutes before pushback. Then the APU is started, ground power disconnected, and your electrics, hydraulics and air conditioning duties will be taken over by the APU. Once engines have been started, the APU is turned off and everything then is supplied by the engines.Hope this helps...- daniel

Hi mad dog,Hey thanks. I might just do that. It'll have to be in a little while (not only is flying expensive, but my girlfriend and I have just purchased a lakeside cottage, making the budget very tight). I recently spent my computer money on a new graphics card and heatsink - it'll be a while before anything else gets purchased. But the suggestion looks like the best option I may have. Thanks,- daniel

Thanks guys, I understand your point.My whole thing is, I just can't stand the thought of spending the countless hundreds of hours getting the program to run again with all my add-ons, like I did a few years ago when I changed my system. Complete nightmare - I just can't do it again. To be honest, with all the OOM errors I've gotten over the last few years (had it solved for the longest time... then for some reason, they cropped up again) the whole flight simulation thing has gotten less and less enjoyable. Seems like a lot of wasted money now, unfortunately. I can't unpgrade my op system because I write and record music on it, and with all the plug-ins I have for that (many of them no longer available) I would lose many of my projects.I was hoping for a tip that would allow me to fix the problems I have now, but it seems that that's not possible. I may one day get fired-up enough to undertake the whole disaster again (wipe and reinstall FS2004), or I might just wait to see what kind of effort Microsoft brings out in Flight! Who knows.Meanwhile, I'll just spend more time (and a hell of a lot more money) on my real world flying. Even if it does break the bank, the Cessna never gives a OOM error when I'm turning final!Hey altstiff, I see you're from Toronto as well, and from your avatar that you may have your PPL too. I fly from Buttonville - where do you fly from?- daniel

Ah,well... guess that's that then..

Can you install XP 64 over XP 32? Would I have to reinstall FS2004? Aren't I supposed to be free of OOM errors with the 3G switch? Thanks for the response...- daniel

Just wanted to know how you can get OOM errors on XP 32 bit with the 3G switch installed and FS9.exe as large address aware. What other things can trigger it despite these safeguards?I haven't been able to fix my OOM errors for the last 3 months, and facing the thought of reinstalling FS2004 with all my payware add-ons... must say, just doesn't feel worth it. Crazy, I know, with all the money invested, but the huge effort involved just makes me balk. I've done everything... even reinstalled original textures. Nothing works. It's so frustrating that I have almost no interest in simming anymore. Even with all my scenery disabled I'm still getting them! Completely out of ideas.... thanks for any last help.- daniel

@ John. Good to know, thanks. Hopefully we'll see an update for nHancer soon...@ jja. Thanks for your input; all good advice. However I'm pretty sure it's a driver or fs9.cfg (FS2004 btw, not FSX) or some other hardware related issue, as I had none of these issues with my old card and have changed nothing since. Also... the low FPS goes away as soon as I hit "ALT" or change out of the full screen menu. I removed all the ATI and nVidia driver prior to install, using Driver Sweeper in Safe mode. However, something called "ati2evxx.dll" hangs around and I can't seem to get rid of it. Anyone know what's up with this? I can't delete it - though, I'm going to try to in safe mode.

Hi,Hopefully I'm getting into the final leg of this graphic card change...Long story, short; had to change graphic card from nVidia 9800GX2. First got a ATI HD 5890, which was terrible. Now have a nVidia EVGA GTX 480 Superclocked edition. Running FS9.1, Windows XP SP3, Quad Q6600 o/c to 3.2. Latest graphic card drivers and motherboard drivers. Playing in full-screen mode. nHancer enabled.My problem: The FPS is great for a few minutes, then drops drastically (from 60 FPS to 11 FPS). If I "alt-tab" to the desktop and come back, it goes back up to 60 FPS, but only for a few minutes. The same happens when I hit "alt" to go to the menu. Is this some kind of texture load issue?After a week or two I feel like I'm in the home stretch... Any help would be greatly appreciated.- daniel