Jump to content

Two issues with the Airbus X


specialist

Recommended Posts

I've tried to find the answer in the forum before posting, and tried the suggestions I've found, but I still can't change the heading, altitude, and speed on the FCU. The other problem I'm having is crash to desktop when I try to exist FSX after using the Airbus X. Please help, it doesn't happen with any other payware I have.

Link to comment
Share on other sites

Okay, I found out why I was having a problem setting the FCU. I have a full version of Pete Dowson FSUIPC4. If you have a check mark on using your mouse wheel for trimming, you have to uncheck it and save it. Go back to your cockpit and right click on the FCU knobs. Now use your mouse wheel and see the numbers change. As for my crash to desktop, I don't know what that is yet, but it seems that there is a conflict between the Airbus X and Pete Dowson FSUIPC4. I will play with it some more and see what gives.

Link to comment
Share on other sites

  • Deputy Sheriffs
As for my crash to desktop, I don't know what that is yet, but it seems that there is a conflict between the Airbus X and Pete Dowson FSUIPC4. I will play with it some more and see what gives.

Not necessarily. The CTD is extremly difficult to sort it out, as most of the users (like me) never had a CTD. I have the AirbusX from the beginning on Win7 64bit, also with the licensed version of FSUIPC, made about 50 flights with the Bus and had NO problems at all (except the TOC/TOD bug and other things I can live with).

So I guess, especially the CTD has a lot to do with each ones PC and FSX configuration (e.g. installation path of FSX,....). So it might be that the Bus interferes with another addon, but due to the high number of addons and their possible number of combinations, nobody can give you a 100% guarantee that it works in every combination.

Link to comment
Share on other sites

That's really interesting, and frustrating at the same time. I built my own computer a few months ago, these are the specs; "i7 930, HAF X, Noctua NH-D14, Palit GTX460, Corsair AX850, ASUS P6X58D, HD103SJ 2TB 7200 RPM, 6G Mushkin DDR3 @ 1600 (6-8-6-24), Win7 64bit Ultimate". I use my second drive dedicated solely to FSX which I call my "D" drive, and everything else stays in my "C" drive. I do have a ton of addons and never had a problem until I bought the Airbus X.

I have to say that despite the two problems I mentioned, and one I've resolved already, I am very please with the Airbus X. Extraordinary cockpit, very sharp looking, although would have loved to see a little more functionality like the PMDG or Level-D for the price. However, that said, I'm pleased with the purchase. I just want to get to the bottom of my CTD regardless of how many combinations of scenario there might be that may be causing this issue. If Aerosoft can't figure it out, I sure hope I can find out myself. Already, I'm very glad to find the culprit in the FCU issue, I hope I can do the same for the CTD.

Link to comment
Share on other sites

I have the crash to desktop when I exit after using the Airbus X... what you are saying mopperle is completely not true. I have seen alot of people on this forum talk about the CTD after exit. Most live with it, some of us have tried editing some files to fix the problem, and others have posted about just uninstalling the Airbus becuase of the bugs.

I just want to say, I have Windows 7 64bit, this computer is just over 1 month old. When I got this computer brand new with a clean install of FSX with Acceleration I installed the newest version of Airbus X (no other addons at the time) and I still got the CTD on exit. I also had fsx installed in its default location. I also tried the newest version of Airbus X on my older computer which ran Windows Vista 32bit, and the same problem occured. I have never had the Airbus crash at any other time, just on exit.

It really angers me when someone posts that not very many people are having the CTD on exit (so therefore its not an issue?) when actaully a good amount are having that problem and even more probably are who don't post. I read on another thread Shaun Fletcher said "Just to add to this the crashes are a hard one to solve as the majority of people dont get them." Thats not true! Every other day someone new is posting about some crash or problem with the Airbus. The sad part about this is, it obviously means nothing is being done about it. Payware software of any kind should not cause an application to crash. Out of a million computers, you might have one or two, but thats not the case in this situation. When something costs as much money as Airbus X does it should work, I now have several payware addons and not one problem with any of them but this one.

The topic I got the quote from above is this one: http://www.forum.aerosoft.com/index.php?showtopic=42248 scroll down to see where he said it.

specialist... please try something. Go to your fsx modules folder and move the gpsmodule.dll out of the folder and put it in a safe place like your "My Documents" folder and then try out the Airbus. You will not be able to use the MCDU scratchpad but can still fly with the default FSX flight planner. I just wanted you to test it, because I have the same problem as you, and when I did this, it worked, and the Airbus X did not crash on exit.

see this thread I started for more info: http://www.forum.aerosoft.com/index.php?showtopic=41602

PLEASE AREOSOFT, at least look into the problem further than just saying "it seems most people don't have that problem" that is not true!

Link to comment
Share on other sites

Thanks, I will try your suggestion of moving the gpsmodule.dll out of the folder and into "My Documents" and see how that works out. I'm a big fan of FMC and MCDU, but I rather not CTD any more until such time a better solution can be discovered.

Link to comment
Share on other sites

I have the crash to desktop when I exit after using the Airbus X... what you are saying mopperle is completely not true. I have seen alot of people on this forum talk about the CTD after exit. Most live with it, some of us have tried editing some files to fix the problem, and others have posted about just uninstalling the Airbus becuase of the bugs.

I just want to say, I have Windows 7 64bit, this computer is just over 1 month old. When I got this computer brand new with a clean install of FSX with Acceleration I installed the newest version of Airbus X (no other addons at the time) and I still got the CTD on exit. I also had fsx installed in its default location. I also tried the newest version of Airbus X on my older computer which ran Windows Vista 32bit, and the same problem occured. I have never had the Airbus crash at any other time, just on exit.

It really angers me when someone posts that not very many people are having the CTD on exit (so therefore its not an issue?) when actaully a good amount are having that problem and even more probably are who don't post. I read on another thread Shaun Fletcher said "Just to add to this the crashes are a hard one to solve as the majority of people dont get them." Thats not true! Every other day someone new is posting about some crash or problem with the Airbus. The sad part about this is, it obviously means nothing is being done about it. Payware software of any kind should not cause an application to crash. Out of a million computers, you might have one or two, but thats not the case in this situation. When something costs as much money as Airbus X does it should work, I now have several payware addons and not one problem with any of them but this one.

The topic I got the quote from above is this one: http://www.forum.aer...showtopic=42248 scroll down to see where he said it.

specialist... please try something. Go to your fsx modules folder and move the gpsmodule.dll out of the folder and put it in a safe place like your "My Documents" folder and then try out the Airbus. You will not be able to use the MCDU scratchpad but can still fly with the default FSX flight planner. I just wanted you to test it, because I have the same problem as you, and when I did this, it worked, and the Airbus X did not crash on exit.

see this thread I started for more info: http://www.forum.aer...showtopic=41602

PLEASE AREOSOFT, at least look into the problem further than just saying "it seems most people don't have that problem" that is not true!

Given the number of users there must be for this product and given that people are more likely to complain about a CTD than to state they don't have it, I think it's probably reasonable to assume that most people in fact don't have it.............otherwise the forums would have thousands of reports of this issue.

As for finding the cause (let alone fixing it), this is unbelievably difficult to do. As a beta tester, I can tell you that the CTD on exit has always been an issue for me and yet, for many beta testers it was never an issue. During the various beta releases, some of them were also prone to CTD's whilst flying as well, but this seemed to have been resolved quite some time before it was released.

So, I understand it's annoying, but, I really do think it affects the minority and as it only affects users on exiting FSX, I think you should accept it's not likely to be fixed. If it could be, it would have been done before release.

Link to comment
Share on other sites

I am one of those who have posted several times about the CTD on exit when using the Airbus X.

I don't think it is acceptable for Aerosoft to just keep ignoring this problem.

I have many other excellent Aerosoft aircraft, but I will certainly take my time before buying any others to ensure they do not have this problem.

The CTD only occurs on my system with the Airbus X, not with any other addons, so I would think there is something odd about the Airbus which causes this CTD but does not happen with other aircraft.

Maybe it is time to have a poll of forum readers to find the extent of the problem among users?

Paul

Link to comment
Share on other sites

I am one of those who have posted several times about the CTD on exit when using the Airbus X.

I don't think it is acceptable for Aerosoft to just keep ignoring this problem.

I have many other excellent Aerosoft aircraft, but I will certainly take my time before buying any others to ensure they do not have this problem.

The CTD only occurs on my system with the Airbus X, not with any other addons, so I would think there is something odd about the Airbus which causes this CTD but does not happen with other aircraft.

Maybe it is time to have a poll of forum readers to find the extent of the problem among users?

Paul

I imagine that because the CTD is on exit, there's a lesser need to look for a solution. Personally I find it a mild annoyance, but as I'm closing FSX when it happens, I don't take a lot of notice anymore.

The idea of a Poll is probably of little use. Even if 100 users said they experienced the CTD (and I actually doubt you would get that result), that's out of thousands of users.

I agree that the issue is caused by the AirbusX (I never have a CTD with anything else), but, if most beta testers didn't experience this and if nobody at Aerosoft ever experienced it, how on earth do they try and fix what for them isn't even broken? There has been no common link found to date i.e. it affects clean installs, different OS, different GPU, different install locations and different languages. You can bet there are 100 people with the same set-up as you that have no problem and this is what makes tracking issues like this such a pain.

Link to comment
Share on other sites

  • Deputy Sheriffs

Hi Paul (Gardner),

I understand your and others frustration when using a product and you get a CTD. But as Paul mentioned in most cases you only here from others when they have a problem. And I'm sure that aerosofts puts a lot of attention at this problem (altough we don't here too much from official side :rolleyes: ).

But as I wrote earlier: Due to the fact that .. (OK ;) ) not all users got a CTD, it depends not only on the Bus! Otherwise everybody would always have a CTD and the Bus would have never left the beta stage. But as this is not the fact, it must have something to do with the overall combination of OS (maybe hardware) + FSX + other addons + AirbusX and this gives you thousands of combinations to check. And even posts where people tell us they use the Bus on a new PC with nothing on it other then FSX and AirbusX (what I hardly can believe) it isn't helpfull, because why don't I have a CTD with tons of other software product + FSX + tons of addons on my PC?

Sometimes it takes a long time till you find a solution, because you just can't test it. You have to wait until you get that hint that solves it. This for example was the case, when we discussed over month the correct order of certain scenery products in the library.

Link to comment
Share on other sites

But as this is not the fact, it must have something to do with the overall combination of OS (maybe hardware) + FSX + other addons + AirbusX and this gives you thousands of combinations to check. And even posts where people tell us they use the Bus on a new PC with nothing on it other then FSX and AirbusX (what I hardly can believe) it isn't helpfull, because why don't I have a CTD with tons of other software product + FSX + tons of addons on my PC?

You hardly believe...

Look mopperle, when you get a brand new computer, fsx isn't already installed, and there are no addons on the computer at all. I knew about the problem already, so with a clean install on a BRAND NEW COMPUTER, I wanted to test it out, hopeing to find the problem for myself was casued by another addon. It did not help, the Airbus X still crashed on exit. As I have stated many times, the GPSmodule.dll has something to do with it, because when you move it out of the modules folder, the problem is no longer there. I close fsx after using the Airbus X, and there is no problem, no crash.

Given the number of users there must be for this product and given that people are more likely to complain about a CTD than to state they don't have it, I think it's probably reasonable to assume that most people in fact don't have it.............otherwise the forums would have thousands of reports of this issue.

lol, thousands of reports? well hypothetically speaky, being very generous, lets say 25% had the problem... I really doubt there would be thousands of reports. Its a good model and nice looking product but c'mon, I doubt there are thousands who even own it.

Also Paul, it wouldn't be a big deal to me either it crashing on exit, but when I start fsx up again after a CTD on exit, other addons then fail to load properly unless I restart my computer.

Again, its just my opinion that when you pay for addon software, you shouldn't have to reinstall Windows, and fsx just to get that one piece of software to work. I shouldn't have to restart my computer every time I use it, just so I can use it again with no other problems. I think this Airbus has the best modeling out there, and I enjoy flying it and learning the FBW, and I just would like to see Aerosoft look into this problem... and maybe we can get a fix when the advanced version comes. What ever happens, good luck to the development team.

Link to comment
Share on other sites

well year to be more specific it seems to be linked to the f-pln page as i in 1 of my fix (http://www.forum.aer...pic=41602&st=20) i delt that page from the MCDU and fs stopped the crash at max settings. so it seems the problem is located some where there or lead to a parameters.

And about other ad-ons it have no effect it seems, as i worked wiht fsx and airbus only instaled and crashed at fsx higest setting and by lowering 1 setting it stopped, but in fact it should not crash any way as othere payware could bee runed at max setting whit out crash fs.

so all in all find whats wrong whit f-pln page or what it leeds to, and the problem is solved.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use