cant use whole terrain

[bytexf 0]

Hai ,

 

i do 1st steps in worldeditor .

made a terrain grid size 2048 x 2048 .

i can not move across the whole terrain . it stops when i reach 3000 ( x ) .

are there boundarys i can adjust ?

did not found anything .

 

thx

Step

 

ps.   in gamemode i can  pass this invisible border ...    its only in the world editor

 

[Casseburne 127]

Your heighmap is bigger than your normal map, generate it again

[--Michael-- 10]

Does the terrain creator have a limitation on size? 

[zeotrope 24]

I thought there was a world bounds option somewhere. I don't think 2048 x 2048 is too big

[stburr91 1009]

On 6/20/2022 at 2:51 PM, bytexf said:

Hai ,

 

i do 1st steps in worldeditor .

made a terrain grid size 2048 x 2048 .

i can not move across the whole terrain . it stops when i reach 3000 ( x ) .

are there boundarys i can adjust ?

did not found anything .

 

thx

Step

 

ps.   in gamemode i can  pass this invisible border ...    its only in the world editor

 

 

Your camera isn't set up correctly. 

Follow this guide.

https://docs.google.com/document/d/1viZSm7OquK8vhahskP0Bthy9uQufmz2PA01g1SHzFd0/edit

 

On 6/26/2022 at 9:46 AM, --Michael-- said:

Does the terrain creator have a limitation on size? 

 

I believe that there is some hardcoded limit, but you will run out of RAM long before you hit the limit. Your computer's RAM is going to be what limits your terrain size.

[CD8-T-LYMPHOCYTE 1]

/!\' EDIT : I found the solution : I just had to exit World Editor and load it back ! 

Hi all, I am having the same issue, but I can't find how to solve this. This issue occurs even before heighmap import. Seems like there is an invisible box preventing me to go over 3000. 

According to the above link, my camera is set up correctly.
I also tried to import height map and to generate normal map, but the issue is still present.

Any help ? Did I miss something important ? (EDIT : solved)

Thanks.

[BigAndSloppy 0]

I had this issue too, reloading world editor fixes it.   Only seems to happen at the very beginning.  hasn't happened since.

[john chaser 37]

Hello there. I am currently running into the magic 3000x3000 border issue with my free camera in the editor. However, the Reload-"Fix" doesn't seem to work for me - hence necro-ing this old threat. Any ideas on how to fix this? 

[Sly1 0]

On 7/28/2024 at 11:59 AM, john chaser said:

Hello there. I am currently running into the magic 3000x3000 border issue with my free camera in the editor. However, the Reload-"Fix" doesn't seem to work for me - hence necro-ing this old threat. Any ideas on how to fix this? 

Bumping, because I am also having the same issue

[Grimstar 0]

On 7/28/2024 at 4:59 PM, john chaser said:

Hello there. I am currently running into the magic 3000x3000 border issue with my free camera in the editor. However, the Reload-"Fix" doesn't seem to work for me - hence necro-ing this old threat. Any ideas on how to fix this? 

also getting this now. Used to be fine and a close and restart would fix. Trying to start a new map and it’s doing it, went back onto an old map and can also no longer access the majority of the map

[Norse Customs 2]

Having this same issue now when i first started it wasn't a issue before until recently, not sure if i has to do with the new update to the game or not if someone knows the fix i would like to finish my map.

[Norse Customs 2]

On 7/30/2024 at 2:31 PM, Sly1 said:

Bumping, because I am also having the same issue

i have been looking into this issue and have found this that has worked for me the original poster is  

@TilW since the 1.2 update has broke it again.

https://feedback.bistudio.com/T182440

"

Here's a detailed guide on how to fix it:

1. Make a backup of your terrain layers or project folder so you can revert any potential mistakes.
2. Open your world, check which layer contains your "world" entity (usually "default") and move all other entities from that layer to a new one. Lock the original layer with just the world entity, then save.
3. In the Workbench, browse to your world file, then to the _Layers subfolder. Open it, right click that layer and choose "Show in Explorer", showing the file in Windows.
4. Open the file with a text editor like Notepad. In there you should see something like this (I'm leaving out some parameters here):

 

GenericWorldEntity world { BSP 533 1 20 1 256 0 0 2 129 2 0 (and so on)

boundMins -100 0 -100

boundMaxs 100 20 100

}

 

If boundMins / boundMaxs are missing, add them.

1. Change the values after boundMaxs to something larger than your maximum terrain coordinates. For example, if your terrain is 8x8 km² large and the camera doesn't need to move higher than 2 kilometers, "boundMaxs 9000 2000 9000".
2. Make sure you entered everything correctly and did not break the formatting, then save the file and reload the world in the Workbench. If everything was done correctly, the bounds should have moved. If the world did not load correctly, the formatting was probably wrong.

Whenever you edit the world entity in the World Editor and save, you will have to repeat this process afterwards.

"

Hope this helps 

[Goodsir126 0]

works

[Adonaiis 10]

On 8/22/2024 at 10:10 AM, Norse Customs said:

i have been looking into this issue and have found this that has worked for me the original poster is  

@TilW since the 1.2 update has broke it again.

https://feedback.bistudio.com/T182440

"

Here's a detailed guide on how to fix it:

1. Make a backup of your terrain layers or project folder so you can revert any potential mistakes.
2. Open your world, check which layer contains your "world" entity (usually "default") and move all other entities from that layer to a new one. Lock the original layer with just the world entity, then save.
3. In the Workbench, browse to your world file, then to the _Layers subfolder. Open it, right click that layer and choose "Show in Explorer", showing the file in Windows.
4. Open the file with a text editor like Notepad. In there you should see something like this (I'm leaving out some parameters here):

 

GenericWorldEntity world { BSP 533 1 20 1 256 0 0 2 129 2 0 (and so on)

boundMins -100 0 -100

boundMaxs 100 20 100

}

 

If boundMins / boundMaxs are missing, add them.

1. Change the values after boundMaxs to something larger than your maximum terrain coordinates. For example, if your terrain is 8x8 km² large and the camera doesn't need to move higher than 2 kilometers, "boundMaxs 9000 2000 9000".
2. Make sure you entered everything correctly and did not break the formatting, then save the file and reload the world in the Workbench. If everything was done correctly, the bounds should have moved. If the world did not load correctly, the formatting was probably wrong.

Whenever you edit the world entity in the World Editor and save, you will have to repeat this process afterwards.

"

Hope this helps 

Another way without following these steps...

 

Simply select your "GenericWorldEntity" and go to object properties > Dimensions > Bound Mins & Bound Maxs.

 

For example, define:

Bound Mins x=0 y=0 z=0

Bound Maxs x=8000 y=4000 z=8000

[ShockaGang 0]

Check your layer file, isolate and open the world entity in notepad and see if the world dimensions are there above the block size. Looks like when you drag a fresh world entity it doesnt come with boundMins or boundMax in the file yet and we have to add it