Page MenuHomeFeedback Tracker

Terrain boundary’s for terrain set to locked number / doesn’t change with terrain creation
Assigned, NormalPublic

Description

When creating a new world and making a new terrain plane, the boundary for the camera (black outline) is small and doesn’t reflect the size of the map created.

My current map I’ve been working on has had its boundary’s reset, and there is multiple reports of other map creators having this issue since newest update putting development of these maps effectively on halt.

Best reproducible on fresh terrain)

I also notice if you try and reset the value of world boundary’s it will not let you save the values and resets to the number randomly set.

Details

Severity
Major
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Category
Editor
Steps To Reproduce
  1. Create new project
  2. Enter world editor

3.Create world file
4 . Create terrain plane entity (any size)

  1. Notice that the black outline doest’t reflect the terrain limits (yellow outline )

Steps for existing terrain resetting boundary

  1. Load map that’s not affected.
  2. Place any object, spline, etc
  3. Save and reload world.
  4. Find black outline is now small and you can’t move editor camera past distance previously able to
Additional Information

Best reproducible on a fresh new created world.

Reddit link for someone else having issue on existing Terrian
https://www.reddit.com/r/ArmaReforger/s/ZsbBf9ZPdR

Event Timeline

Irko created this task.Jun 27 2024, 4:15 PM
Irko added a comment.Jun 27 2024, 4:17 PM
This comment was removed by Irko.
Geez changed the task status from New to Assigned.Jun 27 2024, 5:04 PM
Irko updated the task description. (Show Details)Jun 28 2024, 8:06 AM
Irko edited Steps To Reproduce. (Show Details)
Irko renamed this task from Terrain boundary’s for terrain set to arbitrary number, doesn’t change with terrain creation to Terrain boundary’s for terrain set to arbitrary number / doesn’t change with terrain creation.Jun 28 2024, 10:51 AM
Irko changed Category from General to Editor.
Irko renamed this task from Terrain boundary’s for terrain set to arbitrary number / doesn’t change with terrain creation to Terrain boundary’s for terrain set to locked number / doesn’t change with terrain creation.Jun 28 2024, 10:53 AM
Irko updated the task description. (Show Details)
TilW added a subscriber: TilW.EditedJul 1 2024, 5:18 PM

I looked into this issue, it appears that 1.2 broke the way terrain bounds are calculated.
Meaning when you create a new terrain or resave an existing world entity, the terrain bounds will break.
Reproduction is as simple as it sounds, just create a terrain larger than the default bounds (~3000m) and try to move the camera beyond it.

The issue can temporarily be fixed by opening the layer file with a text editor and increasing the boundMaxs vector.
However, as I said, every time you save the layer with the world entity in it, this will break again, so before you apply the fix I would recommend moving everything else away from your default layer and locking it so you don't make changes accidentally.

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.

EDIT: As of 1.2.0.98, you may also have to change boundMins back to -100 0 -100!

BigAndSloppy added a subscriber: BigAndSloppy.EditedJul 5 2024, 6:41 PM

If boundMins / boundMaxs are missing, add them.

I noticed when I opened my default file, the end } curly bracket for the

 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
}
Was missing and once I added that it worked for me too.

https://pastebin.com/y7f2kVK2 This is what I saw when I open that default file in notepad.

and after I fix it.

Emam added a subscriber: Emam.Jul 7 2024, 4:06 PM

Please fix this ;(

Irko added a comment.EditedSep 27 2024, 1:25 AM

please fix this issue asap!