I reckon it can be done, because someone has uploaded and is updating that 3rd party airfield on flightsim.to and is managing to do it. How, though, is baffling me!
I’ve asked them direct how they’re doing it so will post an answer here if I get one. If anyone has any suggestions in the meantime I’d appreciate it!
Using the 787 with Heavy Division Mod breaks GSX. using the stock 320 brakes GSX, using FBW A320 brakes Boarding.
Never ever made it to let people board the plane. Never saw luggage being loaded. Stairs and Gangways are connected to the plane, when hitting Boarding it brakes.
pushback works fine. Calling GPU brakes the Addon. Tryed it on many different airports.
No E-Mail reaction, no Forum approval. I have seen one of their posts, regaring to a customer, who complains why they didn’t make a proper Beta. They answered with: We had a Test with 25 people… rly… 25… for such a big plattform? Why… ^^
Just went over to the forums and the admin they have working it doesn’t have a clue about customer support… We’ve paid for this product and they constantly blame the users!
I can live with the hundreds of bugs this thing seems to have but if i can’t even takeoff before getting a CTD then whats the point!
That error has been in MSFS for some time now and is being suffered by people without GSX, myself included.
By its nature it is intermittent and can stop happening for quite a while, giving the false impression that something that the user might have done has cured the problem.
That’s the problem. The issue lies within MSFS and people have claimed success with all sorts of hardware and software tweaks, only to suffer the CTDs again, sometime later.
It might well be that the presence of addons, any addons, changes the likelihood of a CTD, but we won’t fully know until Asobo have completed their investigations and hopefully found a cure.
Don’t know, what is happening. I allways get a message like this in that GSX Debug Window, when I try to board a plane. Doesn’t matter, which plane and airport:
Traceback (most recent call last):
File “.\common\fsm.py”, line 73, in executeDoFuncToCompletion
File “.\GSX\assistanceServices_init_.py”, line 1833, in do
File “.\common_init_.py”, line 52, in playGSXWarning
UnicodeEncodeError: ‘ascii’ codec can’t encode character u’\xf6’ in position 25: ordinal not in range(128)
I even moved everything out of the community folder, except FBW and the GSX mod. This lines is from flight with the FBW plane in EDDH. But as I mentioned, I get such lines for every plane on any airport I try.
Traceback (most recent call last):
File “.\common\fsm.py”, line 73, in executeDoFuncToCompletion
File “.\GSX\assistanceServices_init_.py”, line 1833, in do
File “.\common_init_.py”, line 52, in playGSXWarning
UnicodeEncodeError: ‘ascii’ codec can’t encode character u’\xf6’ in position 25: ordinal not in range(128)
It sounds like you really need to get a forum approval for the FSDT Forums, or at least scan over them for people with similar problems. The error sounds like it’s related to a Unicode encoding issue with some of the text used somewhere.