31 replies to this topic

[Shaun Fletcher]

Please do the following.

1) De-install the product using the windows control panel software applet
2) check the FSXMainFolder\SimObjects\Airplanes\ folder and delete any remaining folder that starts with Aerosoft Airbus*
3) check the FSXMainFolder\modules folder and remove the GPSModule.dll if it still there
4) check the dll.xml that you will find here
Windows7: C:\Users\username\AppData\Roaming\Microsoft\FSX
Vista:xxxxxxxxxxxxxx
XP:xxxxxxxxxxxxxxxxxxxxxx
and remove the following lines if they are still there
<Launch.Addon>
<Name>GPS Module</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Modules\GPSModule.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>

Once done then re-install V1.20

[Damocles]

Hi Shaun,

Just to let you know I still have 30/40% decrease in frames using this method....I'm using SP2 not Accelerator. V1.11 is good with 28-35fps at add-on airports and 50-78fps up in the air.

[KAPTEJNLN]

well let me add some thing that also have to be removed, mabee. at step 4 you was in the Windows7: C:\Users\username\AppData\Roaming\Microsoft\FSX to delt the lines in the dll. but you see an folder named SimObjects in there you have to delt the folders to as the airbus x stil in that folder. hope that works :-)

[Bert Pieke]

Please do the following.

3) check the FSXMainFolder\modules folder and remove the GPSModule.dll if it still there

Once done then re-install V1.20

Just a question, rather than re-installing V1.20, is the GPSModule.dll dated Sep/2/2010
still the latest or do I have a backlevel module?

WinXP

[KAPTEJNLN]

Just a question, rather than re-installing V1.20, is the GPSModule.dll dated Sep/2/2010
still the latest or do I have a backlevel module?

WinXP

well i think but always the best way is to clean all before reinstall like the steps from shaun and my littel hint then you should be up to date

[Travis]

Hey Shaun, still no luck. Getting the same FPS, tops out at about 20 thanks for trying though

-Travis

[Dan Moorehouse]

Hello

Please don't take this as a complaint. It is not, but I am searching for advice to make my Airbus x fly with decent FPS.

I get 20-30+ fps on the default fsx airbus (great) with sparse autogen and sliders set in the middle.

For the Aerosoft Airbus X (with autogen turned off sliders low) I get 20-30+ just after loading up sitting on the ground but

after takeoff it drops to 12 - 15fps. After I turn fps drops down to 8 – 12 fps.

During approach I get 5 - 8 fps compaired to the default FSX airbus I get 20 - 25fps. This low FPS makes it very hard to land

well.

All of this is at rural (small) airports with standard fsx scenery.



I own both the aerosoft F-16 and the Twotter and both are wonderful with no FPS issues. I also own the boxed PMDG 747X and get

a bit better FPS with this than the Airbus x.

I have an E6850 core two duo 3.00 GHz with 2gigs of memory and an Nvdia 8800 with 512m ram 1920/1200 resolution. I run vista

and have tweaked my settings for many hours with the advice I have found here and other places trying many to make this and

enjoyable experience. I have flown V1.0 and V2 and to me there is no difference for me in FPS. So far I have not found

success.

Some of my settings include: unlimited fps, no water effects, <20% airplane traffic, no road or boat traffic, detailed clouds

60mi distance, no shadows.

I have tried reinstalling it using Shaun’s suggestions, tried the suggestions in the manual, have an updated video driver, shut

down unnecessary programs, tweaking the video anti-aliasing ect.

Also I can’t exit the airbus x without FSX hard crashing. A smaller problem.

I want to like this plane a lot. It has my level of systems detail and it looks cool but I don't want to expend a lot more time

tweaking and not get the FPS up to where it is flyable. I would be happy if I had 15fps during approach in low scenery

environments but I cannot seem to get that.

Should I consider more ram or a quad core processor?

Any suggestion would be nice.

Best wishes

Dan

[duckbilled]

Shouldn't the uninstaller take care of these issues? Seems like something that should be included with 1.21.

[frederic29]

hello,

Since i follow this topic and reinstall the 1.20, when i take off, speedbrakes on the left wing are "open" at 100 knots...any idea about this problem?

[vali]

Honestly speaking I have now around 7fps at FRA, with 100% AI, ASE, and in the same conditions I have 6.4 fps with Airbus X.
I used to got more for both but that's another story with my PC. So for loss of fps, at the moment I don't see a big difference.
If you see a difference at 40fps or more, then I don't know if that is really relevant for FSX.

late edit: I suggest you to not check this option: "Aircraft cast shadows on itself" (for Airbus X fps are really decreased, in my case with 50%). Now I have at FRA 15-16fps (lowest 13fps).　

[Tomaz]

I also own the boxed PMDG 747X and get

a bit better FPS with this than the Airbus x.

You get better FPS in PMDG 747x? Really? For sure?

[KAPTEJNLN]

mabee this would help to get a bit higer FPS: http://www.forum.aer...pic=39243&st=20

Best regards LN

[Mik75]

@ Dan:
I have the E6850 too. I'd suggest that you put 2 more GB of RAM into your machine. Mine is running with 4 GB of RAM @ 3.6 GHz and the Airbus X performs very well on that system. I recognised a loss of FPS compared to V 1.11 but that was due to the improved refreshrate of the F/O ND and PFD. I changed these back to the values of V 1.11 and now the Airbus flies like charm. My settings within FSX are all pretty much on the right side, except traffic and cloud density. On Mega Airport Amsterdam I get stable 20-25 frames. Once airborne they increase to 30-50 FPS.
So, get yourself som more RAM and overclock your E6850 to 3.6 GHz, you will be amazed what this "old" system is able to do! ;-)
Greets,
Michael

[Dan Moorehouse]

Michael

Thanks for your suggestion. I will give it a try.

Best wishes

Dan

@ Dan:
I have the E6850 too. I'd suggest that you put 2 more GB of RAM into your machine. Mine is running with 4 GB of RAM @ 3.6 GHz and the Airbus X performs very well on that system. I recognised a loss of FPS compared to V 1.11 but that was due to the improved refreshrate of the F/O ND and PFD. I changed these back to the values of V 1.11 and now the Airbus flies like charm. My settings within FSX are all pretty much on the right side, except traffic and cloud density. On Mega Airport Amsterdam I get stable 20-25 frames. Once airborne they increase to 30-50 FPS.
So, get yourself som more RAM and overclock your E6850 to 3.6 GHz, you will be amazed what this "old" system is able to do! ;-)
Greets,
Michael

[Shaun Fletcher]

Hello Folks,

As mentioned the refresh rate was changed and this causing a change in fps when turning etc as the gauge then needs to update.
Also as mentioned changing them back to pre V1.20 values may help.

[Wiseblood]

Hello Folks,

As mentioned the refresh rate was changed and this causing a change in fps when turning etc as the gauge then needs to update.
Also as mentioned changing them back to pre V1.20 values may help.

Would you mind telling us what they were exactly?  I've got Andy B's mod for the FO's displays (great work by the way), but what were the original settings for the default pilot displays?


Cheers

[Swen]

Problem is not solved with V1.21 extremly short bad frames on turning on taxiway. I dont have this problem before V1.20. On standard aiports i have 50 fps or more, if i taxi with this bird and turn the bird in other directions its stucking extremly... Frames go down to 15fps or less so i dont have this problem with other addons.

[Swen]

Again, i reinstalled all and make a fresh new install. I use SP2 no Acc-pack so if ND is refresh frames go down.

[Shaun Fletcher]

Hello Swen,

Did you try changing the values back as suggested by another user in the gauges.

[Swen]

No, i dont know about this feature. How can i do it?

[pauldgardner]

I also get a CTD every time I end a flight and then exit FSX. This only happens when flying the Airbus X and I can find no help on this matter.

Other forum menbers have suggested flying in full screen or windowed mode but this seems to make no difference.

I run Windows 7 Home with 4 Gb RAM and a decently specified machine.

Any help would be appreciated.

Paul

[Capt Martinle]

I never get a CTD when closing FSX with Airbus X.....but, I close FSX with that Airbus always in spotview, maybe this is the point.
Couldn't imagine that this solves the problem because I never tested this in cockpit view but you can give it a try.

Regards Martin

[skycoach]

Paul, it's the same here, too, with all versions up to and including 1.21. And It's not my rig. I have an 6600 with 4gigs, and 1024 vram, on XP64 Sp2. It's a rock solid machine, which runs just about every major FSX airliner add-on -- LDS, Captain Sim, PMDG, Coolsky, and all the Wilco AIrbuses -- without a CTD . But the fact is, but this piece of software is very fragile; one of the least stable add-ons I've experienced since some of those those built for FS2002 (e.g. SSW A310) Even now, after four builds since its release, I still get sporadic CTD's at take off, as the plane accelerate through v2, frequently during cruise, and every single time I exit a flight. (And the excuses that Aerosoft have come up with for that CTD on exit are lame, to say the least: even a ''Basic ''piece of software should be sufficnetly debugged not to cause a crash every time a flight is terminated.These are not rare) And then there are the FPS swings and stutters, the incoherent FADEC logic, and the supposed custom FBW which is a reverse engineered piece of FSX code. After trying this for over a month now, and spending lots of time trying to coax it into working -- reinstalling FSX, rebuilding cfg files, etc. -- I'm just about to give up on it, and head back to Wilco. However flawed that may be, it's reliable, and doesn't fall out of the sky on approach. Aerosoft needs to face the truth: this is still beta, and there;s some way to go before Airbus X can be boxed and sold.

'David

I also get a CTD every time I end a flight and then exit FSX. This only happens when flying the Airbus X and I can find no help on this matter.

Other forum menbers have suggested flying in full screen or windowed mode but this seems to make no difference.

I run Windows 7 Home with 4 Gb RAM and a decently specified machine.

Any help would be appreciated.

Paul

[KAPTEJNLN]

Paul, it's the same here, too, with all versions up to and including 1.21. And It's not my rig. I have an 6600 with 4gigs, and 1024 vram, on XP64 Sp2. It's a rock solid machine, which runs just about every major FSX airliner add-on -- LDS, Captain Sim, PMDG, Coolsky, and all the Wilco AIrbuses -- without a CTD . But the fact is, but this piece of software is very fragile; one of the least stable add-ons I've experienced since some of those those built for FS2002 (e.g. SSW A310) Even now, after four builds since its release, I still get sporadic CTD's at take off, as the plane accelerate through v2, frequently during cruise, and every single time I exit a flight. (And the excuses that Aerosoft have come up with for that CTD on exit are lame, to say the least: even a ''Basic ''piece of software should be sufficnetly debugged not to cause a crash every time a flight is terminated.These are not rare) And then there are the FPS swings and stutters, the incoherent FADEC logic, and the supposed custom FBW which is a reverse engineered piece of FSX code. After trying this for over a month now, and spending lots of time trying to coax it into working -- reinstalling FSX, rebuilding cfg files, etc. -- I'm just about to give up on it, and head back to Wilco. However flawed that may be, it's reliable, and doesn't fall out of the sky on approach. Aerosoft needs to face the truth: this is still beta, and there;s some way to go before Airbus X can be boxed and sold.

'David

well year there shuld much to get fsx crash. but an final thing i would like you to test as in some way i use MultiCore Environment to get my processer use all its power. and when that is running i can fly whit out problems also FPS are better. But MultiCore Environment is pay ware but try there demo of FSPS - FSX BOOSTER as the MultiCore Environment sadly have no demo. And i know much have been said about FSPS - FSX BOOSTER, i also dident get any thing in the demo first time but since they corected a fault it works. as tested it yesterday as demo for 1 day go try that and get back and tell if that also dident work or did. hope i had an beter option but cant find or mabee try set in fsx display settings the global texture resolution to the very low that gives you lower cpu load i think. it gives beter FPS. and you tont have to wory the texture in the Airbus X dosent changes as far as i remember.

[Tomaz]

Or try "prio", it's free and it does the same (it says it's for setting priority but you can set affinity also).

[pauldgardner]

Paul, it's the same here, too, with all versions up to and including 1.21. And It's not my rig. I have an 6600 with 4gigs, and 1024 vram, on XP64 Sp2. It's a rock solid machine, which runs just about every major FSX airliner add-on -- LDS, Captain Sim, PMDG, Coolsky, and all the Wilco AIrbuses -- without a CTD . But the fact is, but this piece of software is very fragile; one of the least stable add-ons I've experienced since some of those those built for FS2002 (e.g. SSW A310) Even now, after four builds since its release, I still get sporadic CTD's at take off, as the plane accelerate through v2, frequently during cruise, and every single time I exit a flight. (And the excuses that Aerosoft have come up with for that CTD on exit are lame, to say the least: even a ''Basic ''piece of software should be sufficnetly debugged not to cause a crash every time a flight is terminated.These are not rare) And then there are the FPS swings and stutters, the incoherent FADEC logic, and the supposed custom FBW which is a reverse engineered piece of FSX code. After trying this for over a month now, and spending lots of time trying to coax it into working -- reinstalling FSX, rebuilding cfg files, etc. -- I'm just about to give up on it, and head back to Wilco. However flawed that may be, it's reliable, and doesn't fall out of the sky on approach. Aerosoft needs to face the truth: this is still beta, and there;s some way to go before Airbus X can be boxed and sold.

'David

Thanks for the information as I thought it was just me having these problems of CTD on exit. A shame really as I love this aircraft and V1.21 seems pretty good otherwise.

Let's hope the developers have this in hand.

Paul

[Swen]

This Thread is for low FPS...

So i have change in ND.xml the frequenzy to 6. Its now more better. ND is not so smooth but i can life with it.

[bailout3]

Hello

Please don't take this as a complaint. It is not, but I am searching for advice to make my Airbus x fly with decent FPS.

I get 20-30+ fps on the default fsx airbus (great) with sparse autogen and sliders set in the middle.

For the Aerosoft Airbus X (with autogen turned off sliders low) I get 20-30+ just after loading up sitting on the ground but

after takeoff it drops to 12 - 15fps. After I turn fps drops down to 8 – 12 fps.

During approach I get 5 - 8 fps compaired to the default FSX airbus I get 20 - 25fps. This low FPS makes it very hard to land

well.

All of this is at rural (small) airports with standard fsx scenery.



I own both the aerosoft F-16 and the Twotter and both are wonderful with no FPS issues. I also own the boxed PMDG 747X and get

a bit better FPS with this than the Airbus x.

I have an E6850 core two duo 3.00 GHz with 2gigs of memory and an Nvdia 8800 with 512m ram 1920/1200 resolution. I run vista

and have tweaked my settings for many hours with the advice I have found here and other places trying many to make this and

enjoyable experience. I have flown V1.0 and V2 and to me there is no difference for me in FPS. So far I have not found

success.

Some of my settings include: unlimited fps, no water effects, <20% airplane traffic, no road or boat traffic, detailed clouds

60mi distance, no shadows.

I have tried reinstalling it using Shaun’s suggestions, tried the suggestions in the manual, have an updated video driver, shut

down unnecessary programs, tweaking the video anti-aliasing ect.

Also I can’t exit the airbus x without FSX hard crashing. A smaller problem.

I want to like this plane a lot. It has my level of systems detail and it looks cool but I don't want to expend a lot more time

tweaking and not get the FPS up to where it is flyable. I would be happy if I had 15fps during approach in low scenery

environments but I cannot seem to get that.

Should I consider more ram or a quad core processor?

Any suggestion would be nice.

Best wishes

Dan

[bailout3]

I have the same problems & think the only resolution is to uninstall AirbusX & move on to something else.

[CRM320]

For those having FPS issue, make sure you do not have any windows open behind FSX or even touching the FSX window while in window mode. It might sound funny but you'll notice a big difference.

Regards

[JasonQL56]

Hi, im having this same problem with FPS and I was wondering if it was fixed in 1.22? I'll try running it without windows open behind FSX, but I always use squawkbox and ezca cam so is there a fix for this?

Thanks

[Shaun Fletcher]

Hi, im having this same problem with FPS and I was wondering if it was fixed in 1.22? I'll try running it without windows open behind FSX, but I always use squawkbox and ezca cam so is there a fix for this?

Thanks

Have you checked Mathijs post in the OS and Hardware Forum maybe you can try his settings and see what happens.