While gm_boreas is larger and heavier than the average GMod map, it should run smoothly and crash-free even on low-end PCs and laptops. The map was created and tested using an i5-2500K[www.cpubenchmark.net] and GTX 770,[www.videocardbenchmark.net] which are both over ten years old and significantly weaker than the majority of hardware that's available today. If your CPU and GPU score better than these in benchmarks (they probably do) but you're still experiencing crashes or poor performance, the instructions below will fix them in almost all cases.

If GMod crashes when loading the map, when entering specific areas or when noclipping/flying through walls, it usually indicates that the game is running out of memory. Using the 64-bit version of GMod will likely fix this. It allows the game to use more memory, which may improve performance and stability when you have a lot of addons installed. However, this is technically still in beta, so use it at your own risk: https://steamproxy-script.pipiskins.com/sharedfiles/filedetails/?id=2725447709
If this isn't an option for you or if it doesn't help, you'll probably have to remove or disable a bunch of other addons.

If you're getting significantly worse frame rates and/or very high CPU usage compared to other maps, you're probably using one or more script addons that have not been designed or optimized for a map of this size. Depending on what a script is doing and how it's programmed, it's easy for something to run fine in some maps but completely tank performance in others, and the developer might not even be aware of it. Unfortunately, there's nothing that I can do as a map creator to prevent this.

The only solution is to remove or disable such addons. See the next post in this thread for an incomplete list of addons that are known to perform poorly in this map. For everything else, follow these steps:

1. Subscribe to the Addon Hooks Lag Finder addon
   
2. Play the map (singleplayer mode is probably easiest if the issue occurs there too)
   
3. Press Shift+Esc to open the console, then enter the following command to start measuring: find_laggy_hooks_sv
   
4. Close the console, unpause the game and do something that causes the game to lag (or just wait 10 seconds or so if the lag is always present)
   
5. Press Shift+Esc to open the console again, then enter the following command to stop measuring: find_laggy_hooks_sv 0
   
6. Copy or write down the names of any addons that appear in the results (look for lines that say "found in Workshop addon « xxxxx »")
   
7. Return to the main menu, then disable or remove one or more of these addons (start with the first ones in the list, as these have the largest performance impact)
   
8. Quit GMod to ensure that nothing of the addon(s) remains in memory
   
9. Start GMod and play the map again, and see if performance has improved

Repeat these steps as necessary in case there are even more addons impacting performance. Alternatively, try repeating the steps using the command find_laggy_hooks_cl instead of find_laggy_hooks_sv.

1. Enabling multicore rendering greatly improves performance in this map and others, with little to no drawbacks: https://steamproxy-script.pipiskins.com/sharedfiles/filedetails/?id=718934470
   
2. Disabling detail props may improve rendering performance somewhat, but you'll lose out on some visual details (in this case, bushes on the ground). You can do this by opening the spawn/context menu (Q or C by default, if available) and toggling the option under the Drawing dropdown menu in the top-left corner. Alternatively, open the console (Shift+Esc) and enter the following command: r_drawdetailprops 0

If you're having trouble with these instructions or if they don't help, please leave a message below with the following information:

• What's happening and when it happens
  
• Which of the above steps you've followed, and what happened when you did that
  
• Your PC/laptop model or its specifications (CPU, GPU, memory, operating system)
  
• Which beta/branch of GMod you're using (none/default, 64-bit, other)
  
• Which addons you're subscribed to (ideally, create a collection of everything you're subscribed to and share the link)