Sorry to read that, I had not that much problem here with a 10 years old 2-core desktop CPU running at 3,3GHz, I'm not sure map generation is spread across all cores. This mod indeed adds various amount of stress upon map generation, mostly with a lot of players exploring simultaneously, moving fast or when a new world is created. The default settings should work fine with rather few players and should stabilyze once exploration becomes less frequent.
Still, if you are experiencing performances issues, there are a some settings to reduce the effects of the mod to be able to run on various machine and world profiles and tweak the effect/lag ratio.
The progressive generation mode is the most noticeable and mandatory for single-core processors which doesn't benefit from the map generation dedicated thread. It is recommended if the default mapgen mode doesn't run fast enough and you don't mind the landscape being unprocessed during a few (or even tenths) seconds by automatically adjusting to the performance of the server to slow down. But it globally takes a lot more time.
Skipping nodes upon generation creates less slopes, but runs faster (by default all nodes are processed).
Increasing the map generation factor will have almost the same effect, but distributed more randomly (pick a value closer to 1.0 or even above). This controls the age of the landscape with more or less sharp edges.
I would recommend disabling shape update on generation completely only if the other settings are not enough. At that point it turns off almost all effects of this mod, because the landscape is almost not automatically updated. You'll have to basically do everything by yourself, turning off the "natural" feature of this mod. And because once a map block is generated, there is no way to to run the automatic update on it after that if you changed your mind.
I'm not sure map generation is spread across all cores.
I am unsure too – I actually suspect it may not be spread.
The progressive generation mode is the most noticeable and mandatory for single-core processors which doesn't benefit from the map generation dedicated thread. It is recommended if the default mapgen mode doesn't run fast enough and you don't mind the landscape being unprocessed during a few (or even tenths) seconds by automatically adjusting to the performance of the server to slow down. But it globally takes a lot more time.
Interactivity in gameplay is much more important for me than speed of map generation. Invisible walls for not-yet-generated parts of the world can be okay if I am not exploring too much – but the kind of server lag I experienced without “progressive generation” was so bad that nodes took tens of seconds to appear in or disappear from my inventory and falling nodes hovered for quite a time.
Thank you for taking the time to write a detailed reply!
This mod created server lag with default naturalslopeslib settings, on an 8-core machine. IMO these should be adjusted accordingly.
If interacting with the world in singleplayer mode becomes extremely laggy with this mod active, change the naturalslopeslib settings:
Changing “Generation Method” to “Progressive” lead to a non-laggy game. You can also disable “Shape update on generation” to fix this.
Sorry to read that, I had not that much problem here with a 10 years old 2-core desktop CPU running at 3,3GHz, I'm not sure map generation is spread across all cores. This mod indeed adds various amount of stress upon map generation, mostly with a lot of players exploring simultaneously, moving fast or when a new world is created. The default settings should work fine with rather few players and should stabilyze once exploration becomes less frequent.
Still, if you are experiencing performances issues, there are a some settings to reduce the effects of the mod to be able to run on various machine and world profiles and tweak the effect/lag ratio.
The progressive generation mode is the most noticeable and mandatory for single-core processors which doesn't benefit from the map generation dedicated thread. It is recommended if the default mapgen mode doesn't run fast enough and you don't mind the landscape being unprocessed during a few (or even tenths) seconds by automatically adjusting to the performance of the server to slow down. But it globally takes a lot more time.
Skipping nodes upon generation creates less slopes, but runs faster (by default all nodes are processed).
Increasing the map generation factor will have almost the same effect, but distributed more randomly (pick a value closer to 1.0 or even above). This controls the age of the landscape with more or less sharp edges.
I would recommend disabling shape update on generation completely only if the other settings are not enough. At that point it turns off almost all effects of this mod, because the landscape is almost not automatically updated. You'll have to basically do everything by yourself, turning off the "natural" feature of this mod. And because once a map block is generated, there is no way to to run the automatic update on it after that if you changed your mind.
I am unsure too – I actually suspect it may not be spread.
Interactivity in gameplay is much more important for me than speed of map generation. Invisible walls for not-yet-generated parts of the world can be okay if I am not exploring too much – but the kind of server lag I experienced without “progressive generation” was so bad that nodes took tens of seconds to appear in or disappear from my inventory and falling nodes hovered for quite a time.
Thank you for taking the time to write a detailed reply!