Products Support > GSX Support FSX/P3D
Crashing Still with Latest Update
B777ER:
Log attached. Crashed after setting up walking path. Tried deboarding and crashed. Restarted sim, tried again and still crashed.
couatl v4.0 (build 4612)
panic log started on Sun Feb 13 13:50:14 2022
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\common\fsm.py", line 73, in executeDoFuncToCompletion
File ".\GSX\assistanceServices\passengerStairs.py", line 248, in do
File ".\GSX\assistanceServices\passengerStairs.py", line 62, in setStairsVars
SystemError: error return without exception set
{'Airport': 'TBPB', 'Requested assistance services at': 'Parking 11', 'User Pos': (13.07888479613832, -59.48755740904926, 55.9916 m, 4.48157 m, 346.00000091026413, 0.0030766925774514675, -0.0, -0.0, 4.572, 1.0)}
Traceback (most recent call last):
File "<string>", line 22, in OnIdle
File ".\common\fsm.py", line 73, in executeDoFuncToCompletion
File ".\GSX\assistanceServices\passengerStairs.py", line 248, in do
File ".\GSX\assistanceServices\passengerStairs.py", line 62, in setStairsVars
SystemError: error return without exception set
Traceback (most recent call last):
File ".\common\fsm.py", line 73, in executeDoFuncToCompletion
File ".\GSX\assistanceServices\passengerStairs.py", line 248, in do
File ".\GSX\assistanceServices\passengerStairs.py", line 62, in setStairsVars
SystemError: error return without exception set
{'Airport': 'TBPB', 'Requested assistance services at': 'Parking 11', 'User Pos': (13.07888479613832, -59.48755740904926, 55.9916 m, 4.48157 m, 346.00000091026413, 0.0030766925774514675, -0.0, -0.0, 4.572, 1.0)}
flugmatz:
You make it a little easy on yourself, don't you? I'm pretty sure that lots of your customers use Win7 still. Its ok for the purpose. So I'm still convinced that your chief programmer will find the bug. Or you'll find a workaround, something like providing a step-back-solution. And I swear not to update from now on...
virtuali:
--- Quote from: flugmatz on February 13, 2022, 08:04:46 pm ---You make it a little easy on yourself, don't you? I'm pretty sure that lots of your customers use Win7 still. Its ok for the purpose. So I'm still convinced that your chief programmer will find the bug. Or you'll find a workaround, something like providing a step-back-solution. And I swear not to update from now on...
--- End quote ---
You are mixing up to completely different things. This crash problem when stairs start to move is completely unrelated to Windows 7. And yes, I'm quite sure we'll found have proper fix soon enough, it's just that everything is slower during weekends.
But again, it's completely unrelated to the fact we stopped supporting Windows 7 2 years ago, when it went completely out of support from Microsoft, and this won't change, regardless how many Windows 7 users are left, it's not really something we can control.
As explained so many times when Windows 7 support is discussed, once it went out of even extended support from Microsoft ( which happened on Jan. 2020 ), it means that ANY update that Microsoft releases, which will affect the libraries and compilers we use to keep the software working on currently SUPPORTED OS, which we obviously MUST do, might break backward compatibility with Windows 7 at any time.
It's nothing we have any control over or we do intentionally.
It's nothing we can test, nobody ever used Windows 7 here in years.
It's nothing we have any means to fix.
So, if it worked for you in Windows 7 until today, then good for you, but it can stop working at any time, and we can't simply do anything about it.
And again, it's TOTALLY unrelated to this crashing problem, which doesn't have anything to do with the OS used, you might still be able to use Windows 7 after the fix, but that's not guaranteed. What's more likely to stop working, it's the new updater, which is a .NET application, so it's more dependant on OS updates than the rest of the software so, it might be possible that, even after we'll fix the crash with stairs, you might not be able to download the update, because the new updater might not work on Windows 7 anymore. But again, it's nothing we have any control over, it's nothing we do intentionally, it's nothing we can test, and if it happens, we can't fix it.
B777ER:
I see my post got moved into here. I'm on W10 with latest updates. Just don't want my error message getting lost with this other user and W7.
virtuali:
--- Quote from: B777ER on February 13, 2022, 09:32:43 pm ---I see my post got moved into here. I'm on W10 with latest updates. Just don't want my error message getting lost with this other user and W7.
--- End quote ---
Sure, I merged all posts related to the same issue so, if you check other replies, you'll see we are aware of it, even if I'm not able to replicate it with the current version, but I know the fix made is not fixing the real underlying issue ( which I CAN replicate if I rollback the fix ), and to look at this, I need to discuss it with the main GSX programmer first, which will have to wait until we'll go back to normal business hours.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version