Auto Support by Kyle Albert - question
I have been using this mod that is very useful for me. I have noticed I get crashed when I had multiple Auto Supports boxes that I have not click "build" yet.
The question is: how many boxes limit that I can lay around before clicking "Build"?
11 Replies
How many boxes do you have placed approximately? I don't think I enabled lightweight management on the cube itself (it counts as a UObject)
Also whats the crash stack trace?
I know satisfactory 1.1 has a UObject leak on the blueprint designer, and sometimes selecting a blueprint in the UI anywhere in the world causes the blueprint to be built in some designer any distance away.
I'm not sure how many exactly - about 40 - 45.
I did not copy crash report but noticed when I made a box placement and then it crashed twice in row. On third attempt, I just deleted all boxes I placed on and did the manual adding pillars (no crash).

Any chance you have the logs still? Can't think of what would cause that off the top of my head
>debug
We need more information to help you. Before launching the game again, open the Mod Manager and use the "Generate debug info" option, then send the zip file produced in #help-using-mods. This ensures that your help request won't get buried and forgotten in other, non-help channels!
If you need to access older log files, see https://docs.ficsit.app/satisfactory-modding/latest/faq.html#Files_Logs
Or can you easily reproduce the crash?
Also you can auto build cubes you place by holding down an auto build button that can be bound in the keybinds menu. That way you don't have to click through each one.
When placed, it will default to the last used setup, so to prime it, place a cube, configure it, destroy it, then build cube(s) with the auto build button held when building
I tried to reproduce the crash, but it did not crash when I placed over 50 boxes. (shrug) I guess it may depended on where I placed it and caused some sort of conflict in certain spot. I placed those boxes under the foundation upside down as shown in the picture.
I tried to check my previous auto save and it did not save where I get crashed. And I was able to create Generate Debug Info - should I put in here? I'm not 100% familiar with Discord.
yeah, it should be fine, but if you'd prefer, try to find the crash stack trace in the logs and copy paste that here
From the "FactoryGame" debug:Line 284: LogPluginManager: Mounting Mod plugin AutoSupport
Line 285: LogIoDispatcher: Display: Reading toc: ../../../FactoryGame/Mods/AutoSupport/Content/Paks/Windows/AutoSupportFactoryGame-Windows.utoc
Line 287: LogIoDispatcher: Display: Mounting container '../../../FactoryGame/Mods/AutoSupport/Content/Paks/Windows/AutoSupportFactoryGame-Windows.utoc' in location slot 1
Line 288: LogPakFile: Display: Mounted IoStore container "../../../FactoryGame/Mods/AutoSupport/Content/Paks/Windows/AutoSupportFactoryGame-Windows.utoc"
Line 289: LogPakFile: Display: Mounted Pak file '../../../FactoryGame/Mods/AutoSupport/Content/Paks/Windows/AutoSupportFactoryGame-Windows.pak', mount point: '../../../FactoryGame/Mods/AutoSupport/'
Line 290: LogPakFile: Display: Mount point: '../../../FactoryGame/Mods/AutoSupport/' is not mounted to a valid Root Path yet, assets in this pak file may not be accessible until a corresponding UFS Mount Point is added through FPackageName::RegisterMountPoint.
Line 1353: LogPackageName: Display: FPackageName: Mount point added: '../../../FactoryGame/Mods/AutoSupport/Content/' mounted to '/AutoSupport/'
Line 1804: [2025.08.19-17.52.03:757][ 0]LogShaderLibrary: Display: Tried to open shader library 'AutoSupport', but could not find it neither as a monolithic library nor as a chunked one.
Part 2:Line 2642: [2025.08.19-17.52.05:807][ 0]LogAutoSupport: Verbose: FAutoSupportModule::RegisterHooks] Registering native hooks.
Line 3048: [2025.08.19-17.52.05:976][ 0]LogSatisfactoryModLoader: Display: AutoSupport: 1.2.1
Line 4501: [2025.08.19-17.52.08:705][ 0]LogContentLib: Warning: ContentLib Loading Assets of Mod: /AutoSupport
Line 7000: [2025.08.19-17.52.09:145][ 0]LogSatisfactoryModLoader: Registering configuration /AutoSupport/Config/BP_ModConfig_AutoSupport.BP_ModConfig_AutoSupport_C
Line 7001: [2025.08.19-17.52.09:145][ 0]LogConfigManager: Display: Successfully loaded configuration from ../../../FactoryGame/Configs/AutoSupport.cfg
Line 8051: [2025.08.19-17.52.09:333][ 0]AssetDataSubsystemLog: Load Mod: AutoSupport
Line 8703: [2025.08.19-17.52.13:767][ 0]AssetDataSubsystemLog: Load Mod: AutoSupport
Line 8843: [2025.08.19-17.52.15:324][ 0]LogAutoSupport: Verbose: UAutoSupportModLocalPlayerSubsystem::PlayerControllerChanged] Player controller changed to [FGPlayerControllerBase_2147481548]
Line 8844: [2025.08.19-17.52.15:325][ 0]LogAutoSupport: Warning: UAutoSupportModLocalPlayerSubsystem::GetPlayerCharacter] No player controller!
Line 8921: [2025.08.19-17.52.15:568][ 0]LogModUpdateNotifier: Verbose: Detected mod: AutoSupport.
Line 8922: [2025.08.19-17.52.15:568][ 0]LogModUpdateNotifier: Verbose: Could not find Support_URL field for mod: AutoSupport
Line 9162: [2025.08.19-17.52.16:717][ 4]LogModUpdateNotifier: Verbose: AutoSupport: 1.2.1
Line 9456: [2025.08.19-17.52.19:932][382]LogModUpdateNotifier: Verbose: The installed mod is up to date or newer than the available versions on SMR. AutoSupport
Line 9700: [2025.08.19-17.52.50:160][829]LogModuleManager: Shutting down and abandoning module AutoSupport (471)
Nothing jumps out at me here. I don't think I can help further without some crash dump. If you can reproduce it, screenshot the error details in the crash dialog and post it here.
I agreed. But thank you for responding. If I happened to get a crash, I will come back here along with a crash report.