GlitchGans Member

Post Rank

Lost Soul

Posted 2/7/2026, 3:45:00 AM #

Analyzing the performance of custom world-gen scripts. It seems like using Sync functions for large-scale biome placements causes a massive tick spike. Is there a way to offload custom terrain noise calculations to a separate worker thread?

Analyzing the performance of custom world-gen scripts. It seems like using Sync functions for large-scale biome placements causes a massive tick spike. Is there a way to offload custom terrain noise calculations to a separate worker thread?

0 coins rewarded

B I U Code Quote Link Img Spoiler

Analyzing the performance of custom world-gen scripts. It seems like using Sync functions for large-scale biome placements causes a massive tick spike. Is there a way to offload custom terrain noise calculations to a separate worker thread?

Save Cancel

DataDrache Member

Post Rank

Wanderer

Posted 2/7/2026, 4:04:00 AM #

Always go Async for world gen. If you don't, your players will feel that 'stutter' every time they cross a chunk boundary.

Always go Async for world gen. If you don't, your players will feel that 'stutter' every time they cross a chunk boundary.

0 coins rewarded

B I U Code Quote Link Img Spoiler

Always go Async for world gen. If you don't, your players will feel that 'stutter' every time they cross a chunk boundary.

Save Cancel

A

AlphaAdler Member

Post Rank

Wanderer

Posted 2/7/2026, 4:22:00 AM #

The API documentation mentions 'GeneratorTasks'. You should be able to push your noise functions into a task queue that the engine processes in the background.

The API documentation mentions 'GeneratorTasks'. You should be able to push your noise functions into a task queue that the engine processes in the background.

0 coins rewarded

B I U Code Quote Link Img Spoiler

The API documentation mentions 'GeneratorTasks'. You should be able to push your noise functions into a task queue that the engine processes in the background.

Save Cancel