i think the game-play wise optimum solution would be, to have one synced heightmap per ally-team. but as you mention... that would likely be too performance heavy :/.
Maybe a blended height-map would make sense?
As in, blended between the original height-map and the real/current one, so that one sees the real one for in-LOS only, and everything out-of-LOS is always the original one, even if changes have been spotted already. This would likely have to be an optional system (mod setting). This solution would not need any additional ram (to speak of).
Pxtl wrote:How to handle the tearing as you reveal terrain?
heightmap is stored by point so you would just draw the polygon based on the points seen and not seen... this would make for a few "strange shear cliff" formations at the boundary, but there would be no more then you'd get with some maps (haven't played in a while so the "speed****" is the only example I can think of)
this would be a massive boon to my project (the bit about not revealing terraformed terrain until you are in LOS of it)
synced/unsynced wouldn't matter for me i dont think as all players will be allied
this would also improve the quality of ZK in particular, as they tend to have a fair amount of terraform going on...
from the "deforming under factories" i would blame the quality of maps more than i would a engine problem; always annoys me to see those "99% flat areas" where the deform takes place. were the map correct in the first place, it would cease to be an issue (that particular aspect at least)