[Solved] Terrain deformations

[noob]

does they leaks and does stop terrain deformation corrects the leak and also does stop all terrain deformations remove all terrain deformation leaks

 

[Zaio]

type terraindeformation extends handle

Seeing as they have their own handle i would presume so, just nulling it would probably sort any leaks out as i do not see any functions to remove said handles.

 

[Dr Super Good]

The main problem is that terrain deformations cause a split to occur between mac users and windows users playing in the same game session. I believe it even causes people to split who are not playing with maximum visuals.

 

[PurgeandFire]

terraindeformations leak and do not get destroyed when you stop them. They exist permanently in data, and can't be removed neither in GUI nor in JASS.

 

[noob]

I will not use them in my random dungeon generator if they leak permanantly and can cause split between pc and macs.
solved

 

[WaterKnight]

I doubt that they will desync in every case, so would request further information on that.

 

[Dr Super Good]

I doubt that they will desync in every case, so would request further information on that.

They will not as long as all clients to a game session are running the same OS at the same visual settings. Otherwise it is extreemly likly that it will cause a split every time a unit is exposed to the deformation. The reason why is because the height values on OSX are different from on windows after the deformation is applied which causes some functionality (Especially GetLocationZ) to cause an instant split.

 

[WaterKnight]

They will not as long as all clients to a game session are running the same OS at the same visual settings. Otherwise it is extreemly likly that it will cause a split every time a unit is exposed to the deformation. The reason why is because the height values on OSX are different from on windows after the deformation is applied which causes some functionality (Especially GetLocationZ) to cause an instant split.

The height itself, however, has no engine-dependent gameplay effects as I recall. GetLocationZ may be async through walkable, animated destructables too or it's also the case, even on the same OS, when player's have different sight of the point in question (which is being deformed). Either avoid this function there or, which I aimed at, maybe it is no problem for an instant deformation.