[T3D1.0.1 Bug] Terrain block editing with blocks of different sizes.
by Jeff Raab · in Torque 3D Professional · 03/10/2010 (2:29 am) · 0 replies
As I only have binary, I can't say if this is happening in the 1.1 betas, but it's pretty obvious in 1.0.1.
I'm overlaying the 'game' terrain to a 'background' terrain to give the impression of a much larger game world/visibility, without needing to sacrifice the terrain resolution for the play area.
So I place a larger terrain block underneath the game area terrain block, the block sizes being 16 and 1 respectively.
Editing of the BG terrain block works perfectly fine, but once editing is completed, it completely breaks the game-area terrain block in the editor.
Flat areas on the game block shows as 16 block size in the editor tool, while previously edited areas still yield the block size of 1. The other artifact is that at every corner on the 16 block size spacing is spiked massively.
As I've only got binary currently, I can't look into this, and as said, no idea if it's still in the betas, but if it is, just a heads up, as I hadn't seen this bug posted prior. If it was posted prior and I missed it, my apologies.
Pic of it post-bug: img39.imageshack.us/img39/8172/terraineditorsplosion.jpg
I'm overlaying the 'game' terrain to a 'background' terrain to give the impression of a much larger game world/visibility, without needing to sacrifice the terrain resolution for the play area.
So I place a larger terrain block underneath the game area terrain block, the block sizes being 16 and 1 respectively.
Editing of the BG terrain block works perfectly fine, but once editing is completed, it completely breaks the game-area terrain block in the editor.
Flat areas on the game block shows as 16 block size in the editor tool, while previously edited areas still yield the block size of 1. The other artifact is that at every corner on the 16 block size spacing is spiked massively.
As I've only got binary currently, I can't look into this, and as said, no idea if it's still in the betas, but if it is, just a heads up, as I hadn't seen this bug posted prior. If it was posted prior and I missed it, my apologies.
Pic of it post-bug: img39.imageshack.us/img39/8172/terraineditorsplosion.jpg
