I know braniac was considering the feature to call mesh build for a zone that was missing via MQ2
My concern is it would be inefficient if MQ2 was doing it, but if that is not the case than it makes sense
Regardless if it is initated by MQ2 or by the thick client....
A possible idea is if you had a json/xml/ini file of sorts that specified
- default mesh build settings
- each zone
- zone-specific-mesh-build-settings
If this was the case then the community could update git to specify the zone-specific-mesh-build-settings.
Example
I have found changing Rasterization_Cell_Height, Agent_Radius and Agent_Max_Climb fixed the pathing in oldkaesorab for me
Rich (BB code):
[defaults]
Tiling_TileSize=128
Rasterization_Cell_Size=0.6
Rasterization_Cell_Height=0.3
Agent_Height=6.0
Agent_Radius=2.0
Agent_Max_Climb=6.0
Agent_Max_Slope=60
Region_Min_Region_Size=8
Region_Merged_Region=20
[poknowledge]
[oldkaesorab]
Rasterization_Cell_Height=0.6
Agent_Radius=3.0
Agent_Max_Climb=2.0