0002570: Configurable unsynced heightmap block size

ID	Project	Category	View Status	Date Submitted	Last Update
0002570	Spring engine	General	public	2011-07-23 08:37	2012-01-31 16:03

Reporter	Google_Frog	Assigned To
Priority	normal	Severity	feature	Reproducibility	always
Status	closed	Resolution	no change required
Product Version	0.82.7+git

Summary	0002570: Configurable unsynced heightmap block size
Description	I noticed the unsynced heightmap blocks have become far larger than they were originally. This size should be fine for the current games on the engine but with the ability to hide terraforming new game ideas become possible. Such games would benefit from a higher block resolution. So I would like a setting in modrules.lua that controls the size of these blocks.
Tags	No tags attached.

Checked infolog.txt for Errors

jK 2012-01-24 23:30 developer ~0008221	This is not a synced computation and so it should/will depend on the power of the client's CPU how fast the unsynced heightmap gets updated.

Google_Frog 2012-01-25 08:40 reporter ~0008223 Last edited: 2012-01-25 08:42	I think equal UHM block size should be enforced between clients because larger blocks increase the range at which you can see the real heightmap. Update frequency could be client configurable.

jK 2012-01-26 00:55 developer ~0008225 Last edited: 2012-01-26 00:55	There is no UHM blocksize, the UHM resolution is the same as the SHM one. If something limit it, it is the game's losMap resolution.

Date Modified	Username	Field	Change
2011-07-23 08:37	Google_Frog	New Issue
2011-07-23 08:37	Google_Frog	Graphics Card	=> unknown
2012-01-24 23:30	jK	Note Added: 0008221
2012-01-25 08:40	Google_Frog	Note Added: 0008223
2012-01-25 08:42	Google_Frog	Note Edited: 0008223
2012-01-26 00:55	jK	Note Added: 0008225
2012-01-26 00:55	jK	Note Edited: 0008225
2012-01-31 16:03	Kloot	Status	new => closed
2012-01-31 16:03	Kloot	Resolution	open => no change required
2012-01-31 16:20	Kloot	Relationship added	duplicate of 0002569