Jump to content

simssmith

Business class
  • Posts

    19
  • Joined

  • Last visited

Everything posted by simssmith

  1. @Marten@Stairport Much better. I was able to load in ZGGG with Zibo 738 without crash. I was able to fly into ZGGG from VHHH in Cessna. Even 500 might be a bit high but a good direction to mitigate these types of airport.
  2. 2.2.6 significantly reduced crashes even in larger airports. Thank you very much. However, I just had a crash with default airport ZGGG when I was on ILS approach to runway 19. It was loading 1049 objects when I reached final! Like loader, cart, truck, tug. If the plugin has any control over loading then a slider for user to set max objects will be welcome. We can't control how some of these artist are creating these airports with so many Ground Service Equipment vehicles. Start: Log line number 3405 : 3:54:47.753 E/PLG: Actor created for C:\X-Plane 11/Resources/plugins/SAM/temp/obj/227208186972292686/loader.obj during render. End : Log line number 4454 33:54:47.753 E/PLG: Actor created for C:\X-Plane 11/Resources/plugins/SAM/temp/obj/227208186972292686/loader.obj during render.
  3. I had similar issue and I found the reason. I was using the option "manually copy SAM to Custom Scenery" folder, so that xOrganizer will be able to detect and track SAM (instead of SAM coming up with a random folder name). The problem is when this option is enable, SAM updater will update the "plugin" folder but "Custom Scenery" folder will have outdate version. The two being different version will collide and cause CTD. The fix I did was create a shortcut/symlink from plugin folder and place it in Custom Scenery instead of copying. This fixed CTD issue. @Marten@Stairport if you need beta tester for new version of SAM, let me know. I can sign NDA, etc.
  4. Hello, I found more custom airports that causes sim to crash. Trying to get hold of those author is not possible as many no longer develop scenery anymore. The reliable work around I am using is turning off AoS through plugin admin. If you want to debug this, you will be able to reproduce this using default airport. For me the sim will crash to desktop when fly between default KJFK and default KLGA. Is it possible for keep track of the nodes SAM is controlling and if it exceed certain amount then SAM stops controlling anymore jetway/GSE/etc?
  5. Good news. I was able to communicate with the author of KDFW Omar Masroor and he supplied me with a special apt.dat with much reduced number of GSE in the terminal area. After installing the modified version, sim didn't crash anymore with full SAM Suite. This is with the low res version of Airport Vehicle. This is already good enough for me in terms of visual quality so I didn't try the default version.
  6. I am still having crash to desktop even with lowres version. I took additional action like deleting Vulkan shader cache, the temp dir in SAM, etc . I just disabled KDFW and using default one to able to fly in the area. I notice some of the files in low res .zip seems big like 6 ~ 7 mb for example, cart_dolly_ALB, cart_tug_ALB, fuel_truck_large_NML, etc . I have a 2080TI card with 11 GB memory. I sent a message to the airport author Omar Masroor, and he is aware of it and will look into it as well.
  7. Here is my log file. It just crashed as soon as I went near KDFW Aerosoft "The DFW - Dallas Fort-Worth". I was on default Cessna 172 with REP. 2021.02.27-22.48.11-log.txt
  8. I have SAM (Jetway, FollowMe, Airport Vehicle) working very well in almost every airport except one. In Aerosoft "The DFW - Dallas Fort-Worth" the sim crashes to Desktop. My guess is due to the extreme size/complexity of this airport. If I start my flight in KDFW then no issue but if I start somewhere and as soon as I reach near the airport the sim crashes. If I remove SAM then KDFW approaches remains stable. There is nothing in the log file that indicates the cause of the crash. This is the reason I am looking for a way to disable SAM plugin on the fly in the sim when I am near certain exceptional airport.
  9. What causes this error? Is this error due to bad file in plugin or airport is bad?
  10. Marten, I was not able to replicate this bug after doing a clean install using the latest SAM Suite + all latest plugin. You can close this bug. Installer issues probably known: Removing SAM/lib/SAM_Library still showed all sub plugin installed. I had to do "reset" + Windows uninstall and then was able to install plugin again. Off topic: Please consolidate/remove some of the stickies in this forum. Thanks
  11. What is the proper way to uninstall first so I can reinstall? The reason I am asking is, I had no success of uninstalling. When I try to uninstall through SAM2 Suite, it closes and never uninstall anything regardless of if I choose "Yes" or "No". A "repair/reinstall" button will be very useful in SAM2 Suite.
  12. This is a very annoying problem. I have my monitor set to use full screen mode. During my VR session if I access SAM AOS and later switch to 2D the AoS window automatically maximizes. It covers up the whole XP and I can't select the edges to make it smaller. Here is a 19 sec video.
  13. I been using Sam WorldJetways with 3.15 (not 3.16) and I didn't experience any issue. However if I add other plugins like SAM Airport Vehicles/FollowMe, I start experiencing crashes. I will hold on moving to the new 3.16.
  14. Would like to have the ability to disable certain SAM plugins from the standalone SAM2 Suite. When I click on "More Details", I only see following option "Installed", "Uninstalled", "Get Help", "Manuel". Not knowing any better, I been uninstall and reinstall the plugin and this is not intuitive. I would love to disable certain plugin before I start X-Plane (mainly for performance reason when flying Orbx and other resource intensive scenery)
  15. Edit: Never mind I found support location where issue can be reported. https://stairportscenerieshelp.freshdesk.com/support/solutions/77000001349 /ignore below Picked up all SAMs plugin this holiday. Very happy with them. However, I am seeing a lot of crashes with --=={This application has crashed because of the plugin: AOS}==-- Where to whom do we file a bug report? Do you have a dedicated site / discord etc?
  16. Version 2.0.0

    54 downloads

    This plugin will display vital information like Heading, Airspeed, Altitude, and Vertical Speed. Great plugin for those new to Flight Sim and want to display vital information at finger tip. Here is my video preview. This plugin requires latest version of FlyWithLua 2.7.9. Simply copy the script "Accurate Vital Display.lua" it to the your X-Plane 11\Resources\plugins\FlyWithLua\Scripts folder. This script is open source and is maintained through GitHub https://github.com/Simssmith/xplane-accurate-vital-display Future version will include more customization and a key binding to make this windows visible/hide. Feedback appreciated. Special thanks to developer sparker for code contribution. Older version of this plugin can be download from https://github.com/Simssmith/xplane-accurate-vital-display/releases
×
×
  • Create New...

Important Information

Please read the Terms of Use