  Rank: Seasoned Forum Member Joined: 7/9/2015(UTC) Posts: 698 Medals:
|
Originally Posted by: SifuPeter  Matrix style building
There is a view horizon distance of 42300, a prop is not drawn even if it could be seen. As result a prop simply disappears.
We can use this engine optimization to our advantage by creating scenes at point within the zaby.
The first advantage of building in such scenes is raw speed. Many props together tend to clog the graphics engine to a standstill.
We instantly understand that props in the kitchen next door are invisible for us. The graphics engine only figures that out after working through all the props.
So by moving the room with all its content to a different cube or bubble we then can greatly reduce the lag.
The second biggest advantage is that builds can progress much quicker. Example a castle. You could start with just a single room. Then in another bubble build a dungeon. Add MTL scripts on the doors back and forward. Maybe later you add a corridor. Re-link the previous doors so they now connect to the corridor.
With each added space, the castle would grow and yet still be livable. A mono space castle would take a considerable amount of time to make before things start to look finished. You can also decide to redo your bedroom and making it a different shape room or different size without having to rebuild your entire castle.
A third advantage is that it allows for different times or events. One of the first places i made in this model was for a lady with a dangerous fetish in real life. She had this dream of being taken from parking lot, tossed in the back of a car, then escape, still be caught again and then violently sexual enjoyed on stage by a large group of strangers. After she would come close to her car in a simple parking lot with some shady dudes, a trigger would pull her inside the trunk of the car, (which was inside the bsp so she could not move and only escape by finding a tiny clickable trigger to arrive in a street, the only gate that would let her out led to a garden... a house etc... each stage there would be only one way out: the next scene.
There is an obvious disadvantage too, certain props will be repeated, like sky boxes, and certain 'cardboard' fronts might appear more than once. You might also have to make screen shots from say the front of the castle, then cut it out and shrink it to be displayed in a forest that leads to the castle. I have seen a place with 12000 !!! props which really did not have significant lag (despite the somewhat more intense initial load)
Another disadvantage is that when you fill all 26 spots then finding each other can become something of a puzzle.
The space of the zaby itself is best avoided. The city around the zaby has a fair amount of lag associated with it.
So to calculate where the centers of such bubbles can be:
Since the MoveToLocation(MTL) script only does allow number smaller than 100k we must use smaller numbers than that or use the MoveToOwnedStartPoint (MTOSP) script. The second requirement is that each bubble does not interfere with others. A Sky-10 with scale 22 xyz gives about 44000 diameter space. Standing at the edge you should just about see a hole in the other side. Since mostly people will not walk to the absolute edge this gives the largest amount of space. Standing at the edge we then should not see any other bubble. This suggest a distance of 1/2 + 1 + 1/2 of the viewhorizon or 2 x 42300. Rounding it off upward would be about 90k. So if the center of what we build is 90k away from any other part then we would indeed have the freedom to walk around in such space without interference.
Imagine a rubic cube or a matrix with 3 x 3 x 3 or 27 cubes. You could think of the default zaby as being the invisible center. Each bubble would be self-contained and not lag out other bubbles even if you would use extensive animations.
Original i did use +90000y for above the zaby. However a recent stair bug above the 64k has lowered the y number to 50k.
To start such building you might want to make a 'switchboard' inside the zaby. Best use simple props that symbolize which scenes to expect and place them around a center point. Then create a surfacewater02, make it scale 3xz 1y and put the location as per the following tables and make it collidable. You might also directly put a sky_10 scale 20xyz with an appropriate image. Then put the MTL script on the prop with the same xz numbers but the Y 571 higher ( so 50571y, 571y, -89429y). A great advantage of such switchboard is that it also keeps track of what spaces are used and which not yet.
---- Confirmed outside space in layouts -----
12 469 472 473 1058 1079 1139 1142 1143 1202 1203 1581 1584
boardwalk (do not know the layout number)
example 1142 = Basic Zaby Layout 1 with Kitchen V3
--- above the zaby
+90000x +50000y +90000z
+90000x +50000y 0z
+90000x +50000y -90000z
0x +50000y +90000z
0x +50000y 0z
0x +50000y -90000z
-90000x +50000y +90000z
-90000x +50000y 0z
-90000x +50000y -90000z
--- around the zaby
+90000x 0y +90000z
+90000x 0y 0z
+90000x 0y -90000z
0x 0y +90000z
0x 0y 0z This is inside the city itself, commonly in the second room
0x 0y -90000z
-90000x 0y +90000z
-90000x 0y 0z
-90000x 0y -90000z
--- below the zaby
+90000x -90000y +90000z
+90000x -90000y 0z
+90000x -90000y -90000z
0x -90000y +90000z
0x -90000y 0z
0x -90000y -90000z
-90000x -90000y +90000z
-90000x -90000y 0z
-90000x -90000y -90000z
---- Limited free space in layouts ----------
Basic Park 1155 1154
L shape
+90000x +50000y +90000z
+90000x +50000y 0z
+90000x +50000y -90000z
0x +50000y -90000z
-90000x +50000y -90000z
---- No space in layouts --------------------
1057 1060 1061 1083 and most of the ones not not mentioned above (regularly new layouts come out, i have not tried the cargo ship yet) 
"Friendship is like peeing on yourself: everyone can see it, but only you get the warm feeling that it brings."
By Someone Awesome My Social Center Profile
|
|
2 users thanked DurtyJay for this useful post.
|
|
