general:playertips

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
general:playertips [2024/07/24 19:49] – [How to get your BAR stuck, and how to fix common issues] gurpadmingeneral:playertips [2024/09/03 17:21] (current) – [To Recap:] gurpadmin
Line 2: Line 2:
 ===== BuildAndRepair Issues and best practices===== ===== BuildAndRepair Issues and best practices=====
 Note: BuildAndRepair will henceforth be shortened to "BAR" Note: BuildAndRepair will henceforth be shortened to "BAR"
-==== General best practices ====+=== General best practices === 
 +This section describes general best practices to allow seamless BARing! 
 +  * Do not include limited blocks in the blueprint! Before you take the final version, remove any limited blocks (especially refineries, assemblers and H2/O2 Generators) from the grid. If structurally necessary, add a brightly colored light armor scaffolding to be ground off afterwards.  
 +  * Start your build as a separate grid! Best practice for this is to start from an existing connector, building a light armor block onto its side, adding a projector and placing another connector facing the existing one. Weld the projector and connector, connect the two connectors, grind down the light armor block and rename the grid to what you want it to be. Afterwards, load the projection in such a way, that the connector you already built aligns with one from the blueprint! This will allow you to refuel, power and arm the grid while it is being built while also completely avoiding any grid limit issues.  
 +  * Subgrids are best separated, connected to main grid via brightly colored sprues and then attached with a tug. The "Multigrid projector" plugin will not work on the server. 
  
- +=== How to get your BAR stuck, and how to fix common issues ===
- +
-==== How to get your BAR stuck, and how to fix common issues ====+
 Any of the following will prevent the BAR from working fully or will get it stuck. A good way to tell a BAR is stuck is when the main block plays the welding animation and sound, yet no blocks get added to the grid/welded up. Any of the following will prevent the BAR from working fully or will get it stuck. A good way to tell a BAR is stuck is when the main block plays the welding animation and sound, yet no blocks get added to the grid/welded up.
  
Line 21: Line 23:
       * Note: These last two bullet points will not be an issue if the owner is online at the time of welding.        * Note: These last two bullet points will not be an issue if the owner is online at the time of welding. 
   * Not supplying enough materials: Make sure the BAR or its connected inventories are well stocked! It greatly helps to use a plugin called "Projection to Assembler" or running a programmable block using the BARQueue script.    * Not supplying enough materials: Make sure the BAR or its connected inventories are well stocked! It greatly helps to use a plugin called "Projection to Assembler" or running a programmable block using the BARQueue script. 
 +  * Running "Multigrid Projector": While it looks like it will save you time, this is actually another great way to get a BAR stuck. This script will almost never work on the server!
  
-==== General fixing steps should none of the above work====+=== General fixing steps should none of the above work===
   Credit: @jonasfors on GURP Discord   Credit: @jonasfors on GURP Discord
  
Line 45: Line 48:
  
 ===== Plugin Launcher setup and getting it to launch from the steam game ===== ===== Plugin Launcher setup and getting it to launch from the steam game =====
 +=== Setup ===
 +[[https://github.com/sepluginloader/SpaceEngineersLauncher| Project Github Page with setup instructions]]
 +
 +=== Inject into steam launch ===
 +  Credit: @mommyraven on GURP Discord
 +Find Space Engineers in your steam library, and right click > properties.
 +In the "Launch Options" section, insert the following text:
 +  "D:\Program Files\Steam\steamapps\common\SpaceEngineers\Bin64\SpaceEngineersLauncher.exe" %COMMAND%
 +Replace the listed path above with your own launcher location. 
 +Do not forget the %COMMAND%.
 +
 +With this done, you can now launch Space Engineers through steam as you would any other game. 
 +Please note that shortcuts that directly connect to GURP will not work with this. 
  
-===== Whitelisted scripts ===== 
  
 ===== Grid optimization ===== ===== Grid optimization =====
 +  Credit: @toluenefennec on GURP Discord
  
-===== Helpful third party tools =====+  * Conveyor loops (even really long ones, which are worse) cause lag by the pathing algorithm used for conveyor systems getting confused and will drastically increase lag as more is added to the system. 
 +{{ :general:conveyorlooppng.png?400 |}} 
 +  * Cargo and Tank blobs cause the same issues as loops and lag from the pathing check looking into each connected cargo causing more calculations and lag. 
 +{{ :general:cargospampng.png?400 |}}{{ :general:tankspampng.png?400 |}} 
 +  * Refinery and assembler blobs are notably much worse, Due to their constant pulling and pushing of components it does hundreds of calculations a second and since it checks all things in the path to it, it will create exponentially more lag per machine in the path of the check. This applies to h2 gens as well. 
 +{{ :general:assemblerspam.png?400 |}}{{ :general:refineryspam.png?400 |}} 
 +  * Dry pulling when you run out of materials is in a similar vein as this, due to it checking every frame to check if it has more materials it causes a large amount of lag, try to turn off your assemblers when you run out of materials. 
 +  * Extremely long conveyor lines just increase the base calculations the check has to do, It's generally a bad idea to have a conveyor length of more than 75 or so blocks on a station due to how much it will be used. This isn't quite a problem on a lesser used ship like a fighting craft. 
 +{{ :general:longline.png?400 |}} 
 +  * A good setup would have nothing having to link through another machine nor any loops in the conveyor system (If you can go in a circle without going to the same place twice, you have a loop).
  
 +{{ :general:bestpracticepng.png?400 |}}
 +
 +=== To Recap: ===
 +  * Do not leave large ships connected for extended periods of time, it increases the size of your conveyor network and causes more checks and lag.
 +  * Do not have large spread out docking lines
 +  * Try to keep your Build and Repairs as close to your cargos as you can (do not place them directly on the side of cargo containers)
 +  * You can use Industrial cargo containers side by side if you rotate it so the side ports don't link
 +  * Try to avoid large pressurized environments, the code for airtightness is obnoxiously bad
 +  * Do not leave welders on unless being used (they have the same issue as assemblers)
 +  * Have a main conveyor line with your cargo near the central point of it
 +  * Mobile bases, while fun are a bad idea, moving heavy grids that are 5m kg+ cause permanent physics lag which is only fixed by a restart
 +  * If you have to path through a machine to get to a machine, you did something wrong 
 +
 +
 +===== Helpful third party tools =====
 +  * [[https://mxmbrook.co.uk/tools/SECircle|Marcy Brook's Circle Generator]] 
 +  * [[https://spaceengineerspraisal.net/|Space Engineers Blueprint Appraisal]]
 +  * [[https://steamcommunity.com/sharedfiles/filedetails/?id=2938853980|Chozabu's SeShipWrightTools]]
 +  * [[https://steamcommunity.com/sharedfiles/filedetails/?id=2129594594|Armor Replacer]]
  
 +===== How to get logs =====
 +-> Open Windows Run (Win+R)
  
 +-> Enter:
 +  %appdata%/SpaceEngineers
  
 +-> Search for the file called "SpaceEngineers_YYYYMMDD_xxxxxxxxx.log
 +(Replace YYYYMMDD with the date of when the event you get the log for happened, xxxxxxxxx will be a random string of numbers)
  
  • general/playertips.1721850558.txt.gz
  • Last modified: 2024/07/24 19:49
  • by gurpadmin