FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: DarrianCZE on February 11, 2022, 09:47:05 pm
-
Hi,
the new free update looks very nice, but whenever I try to create walk-in gates, I will place the door location, and when I hit F6 to add the waypoints where the people should walk, Couatl crashes.
Here is the log file. I have tried it on 2 sceneries. Freeware LKMT, and Aerosoft Brno. Basically the same error message, just different coordinates.
couatl v4.0 (build 4612)
panic log started on Fri Feb 11 21:45:05 2022
problem raised by engine or unspecified addon
{'Airport': 'LKMT', 'Requested parking services to': 'Gate C 2', 'User Pos': (49.696187262324045, 18.120550578040444, 259.711 m, 2.46093 m, 176.50874345445166, 0.014165906235575676, 0.011344640515744686, -0.0, 2.5511759651184085, 1.0)}
-
Same for me
-
Best to enable Logging in the Troubleshooting section of the GSX Settings, because the normal error log is not detailed enough to understand the problem.
-
couatl v4.0 (build 4612)
panic log started on Fri Feb 11 21:02:39 2022
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\GSX\__init__.py", line 627, in customizeAirport
File ".\GSX\__init__.py", line 688, in startParkingEditor
File ".\GSX\parkingEditor.py", line 1522, in activate
File ".\GSX\parkingEditor.py", line 1640, in selectVehicle
File ".\GSX\parkingEditor.py", line 284, in showEditorMark
AttributeError: 'PaxStopPositionMover' object has no attribute 'pushbackLabel'
{'Airport': 'KVPS', 'Requested parking services to': 'Parking 30', 'User Pos': (30.495083369326846, -86.54989689620456, 27.6394 m, 1.12238 m, 93.47318200861554, -0.017863525077700615, -0.0, -0.00016195590556069122, 1.1582399854660035, 1.0)}
-
Best to enable Logging in the Troubleshooting section of the GSX Settings, because the normal error log is not detailed enough to understand the problem.
Here you go :-)
I think this is the important part:
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Pax_barrier_5m_BLACK'
{'Airport': 'LKTB', 'Requested parking services to': 'Gate M 1', 'User Pos': (49.15401567278225, 16.689475649739823, 239.595 m, 2.46072 m, 189.46109234154565, 0.014202890917658806, 0.011344640515744686, 0.0, 2.5511759651184085, 1.0)}
-
Best to enable Logging in the Troubleshooting section of the GSX Settings, because the normal error log is not detailed enough to understand the problem.
Here you go :-)
I think this is the important part:
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Pax_barrier_5m_BLACK'
{'Airport': 'LKTB', 'Requested parking services to': 'Gate M 1', 'User Pos': (49.15401567278225, 16.689475649739823, 239.595 m, 2.46072 m, 189.46109234154565, 0.014202890917658806, 0.011344640515744686, 0.0, 2.5511759651184085, 1.0)}
I'm getting the same crash and same error
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Pax_barrier_5m_BLACK'
edit: no crash if I select to hide the stanchions, which makes sense
-
I get the same crash, i tried disable pax barrier but still crash
Traceback (most recent call last):
File ".\GSX\__init__.py", line 627, in customizeAirport
File ".\GSX\__init__.py", line 688, in startParkingEditor
File ".\GSX\parkingEditor.py", line 1522, in activate
File ".\GSX\parkingEditor.py", line 1640, in selectVehicle
File ".\GSX\parkingEditor.py", line 284, in showEditorMark
AttributeError: 'PaxStopPositionMover' object has no attribute 'pushbackLabel'
{'Airport': 'NZQN', 'Requested parking services to': 'Gate R 3', 'User Pos': (-45.021244054627765, 168.740087278336, 355.496 m, 3.49618 m, 205.89999574161575, 0.009476828388869762, 0.005580201745033264, 0.0, 3.5381520584106445, 1.0)}
Total payload:28666 lbs.
-
Just to chime in with the same error when trying barriers. I get no error when I select no barriers. Great addition though Umberto!
-
It's strange because, the updater SHOULD have added those objects. I even tried purposely removing the Addon Manager\Simobjects\PBR\Pax_Barrier folder, which is where they are located, and by running the FSDT Live Update again, the folder is restored!
So, basically, this simply cannot happen unless, as usual, your local Cloudflare node hasn't got the latest files yet.
Do you have that folder after running the update ?
-
I have the same issue. Have managed to get it working if I disable the barriers
-
Sadly not Umberto. Searching the PBR folder for PAX has some hits but none for pax_barrier
-
I have the same issue. Have managed to get it working if I disable the barriers
Of course it would work if you disable the barriers, but that's the point. I'm trying to understand why you don't have those objects, which surely are online and are downloaded by the updater, at least here.
Which is why, in my previous post, I asked to check if you have the Addon Manager\Simobjects\PBR\Pax_Barrier folder because, if you have don't have it, it's a network update problem, but if you have it, it's a completely different problem.
-
Sadly not Umberto. Searching the PBR folder for PAX has some hits but none for pax_barrier
Then it's clearly a problem of your local Cloudflare node still not getting the new files, because they are surely online, and I checked and double-checked, the updater downloads them, at least here.
Try to remove this folder:
%APPDATA%\Virtuali\UpdateCache
Then run the Live Update again, and pay attention if the Pax_Barrier objects and textures are being downloaded.
-
I've just run another live update and checked the PBR folder again. No change so certainly looking like an issue updating.
-
Sadly not Umberto. Searching the PBR folder for PAX has some hits but none for pax_barrier
Try to remove this folder:
%APPDATA%\Virtuali\UpdateCache
Done and checking
-
No joy. Attached the log too for you.
Checking if Visual Studio 2013 Runtimes x86 is required (don't worry, if it's already installed or you already have a new version, it won't be reinstalled or downgraded).
DOWNLOADING Visual Studio 2013 Runtimes x86 files
DOWNLOADING file C:\Users\norma\AppData\Local\Temp\vcredist_2013.zip.001
CREATING Visual Studio 2013 Runtimes x86 .ZIP archive
Removing temp file C:\Users\norma\AppData\Local\Temp\vcredist_2013.zip.001
EXTRACTING Visual Studio 2013 Runtimes x86 .ZIP archive
Removing temp file C:\Users\norma\AppData\Local\Temp\vcredist_2013.zip
Checking if Visual Studio 2015-2019 Universal Runtimes x86 is required (don't worry, if it's already installed or you already have a new version, it won't be reinstalled or downgraded).
Checking if Visual Studio 2008 Runtimes x64 is required (don't worry, if it's already installed or you already have a new version, it won't be reinstalled or downgraded).
DOWNLOADING Visual Studio 2008 Runtimes x64 files
DOWNLOADING file C:\Users\norma\AppData\Local\Temp\vcredist_x64_2008.zip.001
CREATING Visual Studio 2008 Runtimes x64 .ZIP archive
Removing temp file C:\Users\norma\AppData\Local\Temp\vcredist_x64_2008.zip.001
EXTRACTING Visual Studio 2008 Runtimes x64 .ZIP archive
Removing temp file C:\Users\norma\AppData\Local\Temp\vcredist_x64_2008.zip
Checking if Visual Studio 2015-2019 Universal Runtimes x64 is required (don't worry, if it's already installed or you already have a new version, it won't be reinstalled or downgraded).
DOWNLOADING Visual Studio 2015-2019 Universal Runtimes x64 files
DOWNLOADING file C:\Users\norma\AppData\Local\Temp\vc_redist.zip.001
CREATING Visual Studio 2015-2019 Universal Runtimes x64 .ZIP archive
Removing temp file C:\Users\norma\AppData\Local\Temp\vc_redist.zip.001
EXTRACTING Visual Studio 2015-2019 Universal Runtimes x64 .ZIP archive
Removing temp file C:\Users\norma\AppData\Local\Temp\vc_redist.zip
QlmLicenseLib.dll registered successfully
DOWNLOADING file C:\Program Files (x86)\Addon Manager\couatl\GSX\GSX Level 2 Control Panel.exe
DOWNLOADING PBR V5 Objects Multi-liveries Split Package files
DOWNLOADING file C:\Users\norma\AppData\Local\Temp\simobjects_pbr_p3d5_textures.zip.001
CREATING PBR V5 Objects Multi-liveries Split Package .ZIP archive
Removing temp file C:\Users\norma\AppData\Local\Temp\simobjects_pbr_p3d5_textures.zip.001
EXTRACTING PBR V5 Objects Multi-liveries Split Package .ZIP archive
Removing temp file C:\Users\norma\AppData\Local\Temp\simobjects_pbr_p3d5_textures.zip
DOWNLOADING file C:\Program Files (x86)\Addon Manager\Simobjects\PBR_P3D5\FSDT_SODE_jetway_logo\sim.cfg
DOWNLOADING Legacy Objects Multi-liveries Split Package files
DOWNLOADING file C:\Users\norma\AppData\Local\Temp\simobjects_legacy_textures.zip.001
CREATING Legacy Objects Multi-liveries Split Package .ZIP archive
Removing temp file C:\Users\norma\AppData\Local\Temp\simobjects_legacy_textures.zip.001
EXTRACTING Legacy Objects Multi-liveries Split Package .ZIP archive
Removing temp file C:\Users\norma\AppData\Local\Temp\simobjects_legacy_textures.zip
DOWNLOADING file C:\Program Files (x86)\Addon Manager\Simobjects\Legacy\FSDT_SODE_jetway_logo\sim.cfg
Completed
-
I removed %APPDATA%\Virtuali\UpdateCache ran update again and I still have no pax folder
-
Could you please tell me the exact filesize of this file ?
%APPDATA%\Virtuali\UpdateCache\GSX_Simobjects_pbr.md5
-
85 kb
-
Could you please tell me the exact filesize of this file ?
%APPDATA%\Virtuali\UpdateCache\GSX_Simobjects_pbr.md5
Size 225 KB (230,669 bytes)
Size on disk 228 KB (233,472 bytes)
-
85 kb
That's explains it, the correct one is 230k so, this is the file you are getting outdated, and the size looks far too small, try to ZIP it and attach it to a post, because even before this update, that file shouldn't be so small.
-
Size 225 KB (230,669 bytes)
That's the perfect size, which makes your problem completely different than the others who got the wrong file.
-
I believe the user told you the file size for GSX_Simobjects.md5 which is 85kb
-
Attatched
-
Size 225 KB (230,669 bytes)
That's the perfect size, which makes your problem completely different than the others who got the wrong file.
Absolutely sure Umberto, sorry!
-
my GSX_Simobjects_pbr.md5 is 226 Kb, and I also dont have Pax_Barrier folder after deleting the UpdateCache and rerun FSDT Update
-
Attatched
Thats not the file Umberto was asking about.
-
Yes its GSX_Simobjects.md5 but its zipped
-
Yes its GSX_Simobjects.md5 but its zipped
The one he asked originally for is a similar name - GSX_Simobjects_pbr.md5
-
Oh yes sorry my bad. I dont even have that file
-
You do - its listed in your screenshot :)
-
Size 225 KB (230,669 bytes)
That's the perfect size, which makes your problem completely different than the others who got the wrong file.
Looking at the contents of the md5 it has listed a bunch of FSDT_Pax_barrier entries including FSDT_Pax_barrier/model.4m/model.cfg 38 so that side of things is good. Just not downloading the files themselves.
-
Im confused The file was GSX_Simobjects.md5 and then you said no its GSX_Simobjects_pbr.md5.
so which file is it ??
-
Correct which shows in your screenshot. Anyway, re run live update. It will look different now and hopefully work.
-
I understand the issue, so I guess it's really time to put our next-gen Installer/Updater out of Beta.
The problem was the old updater, which doesn't download a new sub-folder in the GSX Simobjects, unless it has been updated as well to know of its existence.
We have been working on a completely rewritten version, which is far more efficient, has lots of new features and it's even able to reinstall products for MSFS you might have lost the installer, fixing the Digital River annoying 30 days redownload policy.
We have been sending it for testing to MSFS users that lost their installer and contacted support to get their download since several weeks, so it finally is quite reliable now, so we'll release the final version very soon, but in the meantime you can try it now:
http://www.virtualisoftware.com/update/FSDT_Universal_Installer.exe
This will work just like the old updater if you run it from the FSDT Live Update icon. However, if you run it from the "FSDT Installer icon", it will run in "INSTALLER" mode, which can also Update things, but can also do much more.
The new updater is online now, the installer is only required to create the "FSDT Installer" icon, and it will be used when you are reinstalling from scratch with nothing from FSDT installed. Right now, is only able to install from scratch MSFS products, which was really needed, FSX/P3D products installation will come later on but, the idea is that it will eventually replace all our installers.
-
Thanks Umberto. The files downloaded as expected using the new updater. Time to take a break whilst P3D starts.
-
Indeed, it is better now, with Pax_barrier being downloaded
-
The new V2 installer is crashing for me. It says "PHOG updated" then quits to desktop, no error message.
-
The new V2 installer is crashing for me. It says "PHOG updated" then quits to desktop, no error message.
- Configure the antivirus to be sure the whole Addon Manager folder is added to the antivirus Exclusions.
- Run the FSDT updater (or the installer) again.
- If that doesn't work, try doing it again after a Windows reboot. Be sure your Windows is fully updated as well, since it's a .NET application, it requires all system libraries to be current.
-
So i used the new installer and yay i now have the pax folder but it couati stil crashes when i try and make pass route.
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_GSX_Pointer_Pax_Gate_Orange_P3D4'
-
It was just a typo in the name of one of the P3D4-specific objects. It's should be fixed now, by running the Live update again.
-
The new V2 installer is crashing for me. It says "PHOG updated" then quits to desktop, no error message.
- Configure the antivirus to be sure the whole Addon Manager folder is added to the antivirus Exclusions.
- Run the FSDT updater (or the installer) again.
- If that doesn't work, try doing it again after a Windows reboot. Be sure your Windows is fully updated as well, since it's a .NET application, it requires all system libraries to be current.
Did all three and still crashes.
-
Mine now works. Thanks
-
Did all three and still crashes.
Are you SURE it "crashed" ? If PHOG was the last scenery (of the ones you have installed) which was supposed to be updated, it hasn't crashed, it simply quitted because there wasn't anything left to do.
If you want to "play" with the updater, run it in "Install mode", that is launch it from the "FSDT Installer" icon, which you will see if you installed the FSDT Universal Installer I posted before.
-
Ok So coualti doesnt crash like it did before i got the pax folder but now it just disappears from the drop down menu
edit so if i uncheck disable bus gsx runs perfectly, if i check disable bus and make a walking path gsx disappears from the menu
-
Ok So coualti doesnt crash like it did before i got the pax folder but now it just disappears from the drop down menu
What, exactly, crashes ? The installer, the updater, or GSX itself.
Doing what ? When customizing a gate ? When using GSX ? If using GSX, when, exactly ?
-
So, after updating through the beta installer you have provided, I now have the PAX barriers and was able to create their path. But now, when I want to try it out, when I click on Operate Stairs (during normal GSX operation), it crashes again... Entire log is in the attachment...
SystemError: error return without exception set
{'Airport': 'LKTB', 'Requested assistance services at': 'Gate M 1', 'Requested parking services to': 'Gate M 1', 'User Pos': (49.1540156727517, 16.689475649733136, 239.597 m, 2.46289 m, 189.46107915494207, 0.014963814057409763, 0.011344640515744686, -0.0, 2.5511759651184085, 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 241, in do
File ".\GSX\assistanceServices\passengerStairs.py", line 58, in setStairsVars
SystemError: error return without exception set
createCamera() PassengerStairsRear Behind
createCamera() PassengerStairsRear Front
createCamera() PassengerStairsRear Right
createCamera() PassengerStairsRear Left
createCamera() PassengerStairsRear Driver 1st Person
createCamera() PassengerStairsRear Driver Close-up
Total payload:28615 lbs.
Sorry Umberto, but this update is a mess...
-
The current Live Update should fix your crash when selecting Operate Stairs.
-
Hah... ok.... another issue. Everything was working correctly, and I have set to board the entire 737-800 (189 people) and P3Dv5 did not handle it, and ran out of VRAM :D I think this needs some optimization.
I have RTX 3070Ti with 8GB VRAM
https://i.imgur.com/64PwCFZ.png (https://i.imgur.com/64PwCFZ.png)
-
Hah... ok.... another issue. Everything was working correctly, and I have set to board the entire 737-800 (189 people) and P3Dv5 did not handle it, and ran out of VRAM :D I think this needs some optimization.
If you were already on the borderline of VRAM exhaustion, it's possible the added objects/textures of the visible passenger barriers might just be enough to cause a crash due to VRAM exhaustion.
This of course is not GSX's fault or something we could "fix", the point is you shouldn't place yourself in a situation which you are so close to exhaustion that just a few new extra objects couldn't fit in VRAM anymore.
What you can do from GSX's side, is not use a too high Passenger Density slider setting, which will lessen the VRAM requirements.
Or, you can use the option to Disable the visible Barriers at Walk-in gates: the Passengers will still use the path, but no extra objects will be added compared to the previous version, it will be just the passengers, which hasn't been changed.
-
And what will exactly the passenger density do, in this case? Extend the queue of the passengers over the longer distance?
-
And what will exactly the passenger density do, in this case? Extend the queue of the passengers over the longer distance?
There will be less passengers visible on screen at the same time, because the time between each generated passenger will be longer, which also means Boarding/Deboarding will take more time.
Of course, this is explained in the GSX manual, Page 27:
it’s possible to control the passenger Density, which will affect the number of animated passengers visible on screen at any given time. Setting the slider towards the highest density settings will shorten boarding and deboarding times, but with some cost in performances. Also, on 32 bit simulators ( FSX and P3D 1/2/3 ), there’s a risk that too many passengers visible at the same time might exhaust the limited memory available in 32 bit mode, especially when using GSX with complex airplanes and airport scenery. We suggest to start with the lowest density settings, and eventually rise them up if you are sure there’s enough memory available.
On a 64 bit simulator, like P3D4, the highest passenger density settings won’t risk memory exhaustion, so the GPU will probably be the only factor affecting performances.
This was written before P3D V5, because in V4 and DirectX 11, exhausting VRAM would usually just cause an fps drop, more likely because memory handling in DirectX 11 is made in the video driver itself, which is an highly optimized/tested code written by those who made the video card.
Instead, in DirectX 12, lots of memory handling responsibility is given to the application developer ( LM in this case ), which means if their memory handling code is not as robusts in dealing with VRAM exhaustion as nVidia/AMD code is, when you are close to VRAM exhaustion, the sim will usually crash.
That's the cost of getting usually better performances compared to DX11. DX12 is very unstable in MSFS 2020 too, but unfortunately in P3D V5 you don't have a choice to revert to DX11.
This is nothing new, it's very well know since P3D V5 came out, you must be more careful about VRAM exhaustion and keep your settings reasonable to not risk it.
-
So this video might explain my ongoing problem, https://youtu.be/-jLOPd9JeXM (https://youtu.be/-jLOPd9JeXM)
When i try and use walk to gate gsx crashes couoti crashes and it disappears from the menu bar. before i got a pop up saying couati had crashed and do i want to see the log, now that does not happen. what is not shown in the video is that i select f12, then select stiars and that's when gsx and couati stop working an di have to reboot my sim
-
i select f12, then select stiars and that's when gsx and couati stop working an di have to reboot my sim
As already discussed here:
http://www.fsdreamteam.com/forum/index.php/topic,25938.msg170204.html#msg170204
and here:
http://www.fsdreamteam.com/forum/index.php/topic,25933.msg170186.html#msg170186
The GSX disappearing when operating Stairs should be fixed now, try updating and see if it works for you.
-
Yes i read that and updated before i did that video. So the update did not work for me
-
Yes i read that and updated before i did that video. So the update did not work for me
Before the update, I could replicate the crash with the Operate Stairs, after the update, I couldn't so, be sure you update again, maybe you haven't got the latest files.
-
Ok updating again now using the new updater
-
Still happens, I hit f12 if i select stairs couati/gsx disappears from the menu. i tried asking for de boarding and same thing happens.
where will i find my logging file to attach here ??
Edit/update Ok after updating again rebooting pc and sim again and again its finally working
-
Edit/update Ok after updating again rebooting pc and sim again and again its finally working
I was quite sure of that, likely you were not getting the latest update from a few hours ago.
-
Ok spoke too soon stairs bug is still present. last time i used de boarding & boarding and it worked, i just asked for just stairs and it crashed again.
-
Ok spoke too soon stairs bug is still present. last time i used de boarding & boarding and it worked, i just asked for just stairs and it crashed again.
And I can only repeat and confirm I can't reproduce it anymore. It happened 100% of the times before the update, now it never happens, and I tried all kind of combination of calling Stairs, and with different airplanes too.
-
Mine crashes too.
Kind Regards
Patrick
-
Same happens here, couatl crashes when requesting boarding/deboarding but only at a walk in gate.
-
Can also confirm it happens for me at the walk-in gates.
-
And I can only repeat and confirm I can't reproduce it anymore. It happened 100% of the times before the update, now it never happens, and I tried all kind of combination of calling Stairs, and with different airplanes too.
However, as already repeated several times in other threads, the fix that has been posted already is only temporary, and it's likely not fixing every situation, because I suspect it's related to timing and system overload and, since I CAN replicate it if I remove the fix for testing, at least this can debugged and investigated.
And, as already explained in other posts, since it doesn't seem like an obvious mistake that can be fixed like all the other fixes that has already been posted minutes or hours at most after they have been first reported, I need to wait to discuss it with the other GSX programmer (who is the *main* GSX programmer), starting tomorrow.
So, no need to continue posting about it. Even if I cannot replicate it anymore after the latest fix, I KNOW what I can do to replicate it, so the issue it's confirmed, it will be worked on, and we'll obviously release a fix as soon as possible.