Comments on Profile Post by EruptionTyphlosion

4096 objects including the player, the camera, the terrain, and anything else you can see in the object editor mode (f1). Forest objects - all of them total - count as *ONE* object total, so forest your heart out, just watch RAM usage for forest physics model (1000 trees&houses = still 1 object).

Anything past 4096 objects will not get loaded. So put everything you can (that has collision or doesn't NEED it) into the forest.
Houses, Trees, pillars, pipes, jumps, stores, bridges, other map furniture, etc.

Thanks! :)

No problem, and your welcome. Always here to help fellow mappers, whether 'it won't load' or 'i keep crashing the editor' or 'my terrain is black, help!' or other questions. This game can do many strange things, and being alpha, it's not well documented, so bugs can be quite menacing and infuriating at times. --Best of luck!

One other thing, if my map is on the edge of the limit, what happens if a player spawns in vehicles over that limit?

Anything past 4096 object on the map (every vehicle is one object), will not work. Keep the hard limit at 4000~4032 objects at most, to allow for many vehicles in the future, and allow the player to spawn jumps, blocks, hay bales, couches etc, and for race checkpoints and such. Use forest object to cut down on object count.

The only restrictions to forest objects vs regular map objects, is they must have built-in collision data (colmesh-1 i believe), and you can't stretch x-y-or-z axis individually, it's all or nothing there. Watch your memory footprint on loading the map when heavily foresting, and keep an eye on FPS. --Good luck!

Ok, thanks!

Also, would a 36 x 36 mile map be feasible? If so, how would I avoid shaking near the world borders.

I would not recommend anyone trying to make anything but a slowly rolling desert any larger than So-Cal which uses a 2.5 or 2.6 meter square size. The higher you go, the less flexible the terrain becomes, you lose detail, etc. You need to use tiled terrain support & it's not in yet. You will shake no matter what past 3 miles from 0,0,0 center.

Also, you can make whatever you want with lots of large Collada (DAE) files (models), but you will still have the shake, but you'll have to know 3d modeling. I would recommend sticking to a MAX of 2.5 square size which is the size of So-Cal, which is manageable otherwise you need 1000's of hours of time... best of luck & use 4k x 4k terrain.

FPU is Floating Point Unit, processor in the CPU, does physics math for Beamng.drive, it's slightly rounded but still very accurate and is very fast compared to not using FPU processing. The small bit of rounding it does will result in discrepancies, which is the shake, it's merely visual and does not affect game-play.

The further out you go, the bigger the number, the more rounding will be done, so the more the shake. It's akin to many games like Minecraft where going too far results in oddly configured worlds. So a millimeter of shake @ 2 miles becomes obvious at 4 miles. At 20 miles from center, it's a small/moderate earthquake for the car.

Know exactly what you want to make, from the start. Base your map on one of the game levels to save time, and use trial of L3DT to put out a 4k terrain of choice, to have a fresh terrain. Use google street view and pictures on the net to get inspiration. Again, best of luck - if any more questions post here or private message me.