Visible Worlds V1.26
==================
Well, it's been a long night here but work continues weeding out all the abnormal behavior in the app. If you are having problems compiling your own worlds/VWmap with V1.20, and you think there's a bug or you get crashes, please make sure you send any possible bug information to me. it's vitally important so I squash them ASAP...
Through the addition of Parent Regions, I've been able to discover a few rather subtle but deadly bugs in v1.20 also, so this hunting has occupied me for the bulk of the night/morning. As a result i'm yet to update the DB re-player libraries and document them. Understanding parent regions and their usefulness is quite a conceptual hurdle to overcome for the user..
Pictured bellow is a compiled map using a Parent Region definition. The region bound are shown as the RED alphaed box. The mini map shows what objects are clearly visible to the vis camera (top right hand corner)
Shot 1, You can see the camera is beyond the parent regions clipping distance to the camera, so thus the VIS returns a Parent Region event to the user (me in this case). In this case I've just displayed the regions box object... You could display whatever you like
Shot 2. The Camera is within a transitional range of the Parent Region in question, so thus it's contents (child objects) have vis calc'd upon them (the little table object) and the region is also returned as an event..
Shot 3. The Camera is now completely within the parent regions clipping distance. So the parent region is not needed to be returned.. It's just normal vis scene.
Here's what the Map actually looks like, the parent region can have any other region contained with it. Although you can't nest them...
[World_Definition]
{
Static_Box: 1000,1,0,0,0,3000,1500,100
Static_Box: 1001,1,3000,0,0,6000,1500,100
Static_Box: 1002,1,0,0,6000,3000,1500,6100
Static_Box: 1003,1,3000,0,6000,6000,1500,6100
Static_Box: 1004,1,0,0,0,100,1500,3000
Static_Box: 1005,1,0,0,3000,100,1500,6000
Static_Box: 1006,1,6000,0,0,6100,1500,3000
Static_Box: 1007,1,6000,0,3000,6100,1500,6000
Static_Box: 1008,1,3000,0,3000,4500,1500,4500
Static_Box: 1009,1,1200,0,1000,2700,1500,2500
Static_Box: 1010,1,950,500,150,1050,1000,250
Static_Box: 1011,1,950,500,350,1050,1000,450
Static_Box: 1012,1,950,500,550,1050,1000,650
Static_Box: 1013,1,950,500,750,1050,1000,850
Static_Box: 1014,1,950,500,950,1050,1000,1050
Parent_Region: 5000,50,63,8000,0,5000,-750,-350,-750,750,350,750,0,0,0
{
Static_Box: 1030,1,7850,225,4850,8150,250,5150
Static_Box: 1031,1,7850,0,4850,7872.5,225,4872.5
Static_Box: 1032,1,8127.5,0,4850,8150,225,4872.5
Static_Box: 1033,1,7850,0,5127.5,7872.5,225,5150
Static_Box: 1034,1,8127.5,0,5127.5,8150,225,5150
}
}
Now, while is really not a very practical test, as the room housing the parent region has no front wall to obstruct most of the visibility. You be able to see how the previous house example would work. You would place all the objects you wish in the house. then place a Parent Region around this collection. If you set the regions clipping range really close, it's lower the object count dramatically. So when the vis returns the a list of Parent regions that are too far from the camera but are visible. You can place a black plains in the windows/door ways to help create the illusion of even higher details in your scenes..
Visible Worlds
(old dead RTG link removed)
