FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: tango3000 on September 22, 2022, 01:27:25 am
-
even after re install, updates ...still crashing (LFPG/ captainsim 777)
couatl v4.8 (build 5023)
panic log started on Thu Sep 22 01:26:04 2022
problem raised by addon couatl-dev-64
Traceback (most recent call last):
File ".\GSX\aircraftDialog.py", line 454, in _setOpenCloseLabel
File "C:\umberto\umberto_svn\couatl-dev-64\wx\_core.py", line 16711, in __getattr__
wx._core.PyDeadObjectError: The C++ part of the DoorDialog object has been deleted, attribute access no longer allowed.
{'Airport': 'LFPG', 'User Pos': (49.00633608530086, 2.5858898103645416, 110.735 m, 5.59244 m, 265.7983928317204, 0.007891091518104076, -0.003490658476948738, 0.00027831389156651764, 5.669280116271973, 1.0)}
>:(
-
even after re install, updates ...still crashing (LFPG/ captainsim 777)
Please clarify if:
- it's crashing only when that airplane is edited on that airport
- when that airplane is edited on any any airport
- when any is edited on any any airport. If this is the case, could you please provide reproduction steps ?
-
Hello, it's crashing when: choose GSX ==> Customize airplane ==> choose a gate or cargo or other ==> press Customize in 3D editor ==> CARSH !!
Tried again with another aircarft and airport: default A320 at LIRF default airport
couatl v4.8 (build 5023)
panic log started on Thu Sep 22 10:56:27 2022
problem raised by addon couatl-dev-64
Traceback (most recent call last):
File ".\GSX\aircraftDialog.py", line 457, in _setOpenCloseLabel
File "C:\umberto\umberto_svn\couatl-dev-64\wx\_core.py", line 9207, in SetLabel
TypeError: in method 'Window_SetLabel', expected argument 1 of type 'wxWindow *'
{'Airport': 'LIRF', 'User Pos': (41.79953867198672, 12.252377840796141, 5.74023 m, 2.72698 m, 166.54729075548698, 0.011248570866882801, 0.003490658476948738, -0.00026694122866608274, 2.7096721046447754, 1.0)}
-
I can't reproduce the problem, have you installed today's update ?
-
last update yesterday, i will try an update now
-
I am using the default link for update: "C:\Program Files (x86)\Addon Manager\Couatl_Updater.exe"
Is it still ok ?
-
Yes, that's correct, and you should also have a Desktop icon for it, and another one in the Start programs.
-
the live update update files from c: and it close without warning so is it doing the job ?
-
the live update update files from c: and it close without warning so is it doing the job ?
If there's nothing to do, the updater will exit automatically at the end. You can also use it in installer mode ( from the installer icon ), to check what is doing. Or, you can also use the Offline installer.
-
ok, restarting MSFS 2020 and checking...
-
exactly the same problem
-
Have you tried the offline installer ? If you still have it after using that one, please provide precise, exact, reproduction steps.
-
same problem after using offline installer
choose GSX ==> Customize airplane ==> choose a gate or cargo or other ==> press Customize in 3D editor ==> CRASH !!
couatl v4.8 (build 5023)
panic log started on Thu Sep 22 11:44:13 2022
problem raised by addon couatl-dev-64
Traceback (most recent call last):
File ".\GSX\aircraftDialog.py", line 454, in _setOpenCloseLabel
File "C:\umberto\umberto_svn\couatl-dev-64\wx\_core.py", line 16711, in __getattr__
wx._core.PyDeadObjectError: The C++ part of the DoorDialog object has been deleted, attribute access no longer allowed.
{'Airport': 'LIRF', 'User Pos': (41.79833322163407, 12.246619456148355, 4.27232 m, 2.72393 m, 158.7075741245278, 0.0067627932876348495, 0.003490658476948738, -0.0006315104497566322, 2.7096721046447754, 1.0)}
-
choose GSX ==> Customize airplane ==> choose a gate or cargo or other ==> press Customize in 3D editor ==> CRASH !!
Please clarify better what you did, the "choose a gate or cargo or other" sentence is particularly unclear: how you choose a "gate" on an airplane editor ?
-
sorry i mean EXIT door au cargo door or service door....(not a gate)
-
Hello,
Any news ?
-
No, other than confirming what I already said that I cannot replicate it.
It would be helpful if you made a more precise report, like which airplane you used, if you started from an existing configuration or you edited it from scratch, etc. For example, if the airplane is already supported in GSX, try to RESET the configuration, so you start with a clean one.
-
i am sorry i have already ansered this, default airplane A320, default airport, same problem with 747 etc... edit from scratch even after configuration reset...
The logs are strange what is doing a message like : "C:\umberto\umberto_svn\couatl-dev-64\wx\_core.py", ? I don't have a directory named C:\umberto\umberto_svn\
-
There's no need to interpret the log your, if there was a clear problem in the log, I would have said that.
Since I said I can't replicate it, with the default A320 and starting from scratch, do you have other information about something specific to your system, like which other add-on that are running ? Something that might connect to the sim, or affect Simconnect.
-
Hello Umberto,
I use FSUIPC, RAAS pro, ...
But, I have tested (and had exactly the same problems) without thoses modules and with the community older empty (except 2 folders for gsx).
In my msfs2020 community folder there is 2 shortcuts (pointing to C:\Program Files (x86)\Addon Manager\MSFS\fsdreamteam-gsx-pro and fsdreamteam-gsx-world-of-jetways):
fsdreamteam-gsx-pro
and fsdreamteam-gsx-world-of-jetways
My MSFS 2020 is installed in a dedicated directory c:\simu (so outside c:\program files (x86) ).
GSX is installed in the default c:\program files (x86) (I have also tested an installation in c:\simu)
I have updated all .NET libraries, microsoft visual basis c++
Maybe is somewher a problem of rights management ? ?? I really don't understand where is the problem. :-\
-
Hello Umberto,
SU10
3D editor working if MSFS 2020 is in windowed mod ! It Crash again if I am in ful screen mod !
-
3D editor working if MSFS 2020 is in windowed mod ! It Crash again if I am in ful screen mod !
Just tried it now, works just fine in full screen mode too.
-
I think maybe there is conflict with arrow keys (in MSFS 2020 i have configured arroy keys to camera movement) / different behaviour between window and full screen ?
-
I think maybe there is conflict with arrow keys (in MSFS 2020 i have configured arroy keys to camera movement) / different behaviour between window and full screen ?
It's possible.
One of the biggest problems in MSFS Simconnect, is an application cannot momentarily take keys for itself and prevent the sim to get the key. This was possible since FSX and according to the official SDK documentation is still possible but...it just doesn't work, that's why we had to choose keys which won't otherwise being used in the default Showcase camera, or are used for minor features but, of course, when you customize keys, unexpected thigs will happen.
In your case, having assigned to the camera the same keys as they one GSX expected to use, might be exactly the problem.