Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
This adds limiting the ghost data to a specific area around the client. #908
By default it is not included in the build, you must #define GHOSTSCOPING in the torqueConfig.h to enable it.
visibleGhostDistance = "1000";
Or if it is not set in the mission file it will default to what is defined in torqueConfig.h #defined as GHOSTSCOPING_DEFAULT_DISTANCE_IF_NOT_IN_MISSION
The mission default distance can be overridden on a per connection basis by using gameconnection:setVisibleGhostDistance and gameconnection:getVisibleGhostDistance
The logic for setting the scoping distance was moved from shapebase in the original design to SceneObject so that it will affect cameras, players, etc.
Thanks for revising it to be a property of the
I'd much prefer to lose both the
Ooh, I see, this may interfere with the current behaviour with defaults of 0. But I'd really prefer to not have features barred out using
EDIT: So currently, you can set the visible ghost distance in the connection, and if that's zero, it can be overridden by the distance in the level info. Maybe we need one additional step - if that's also zero, use the visible distance.