Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><em>I am not a mathematician, so I'm going to use the most basic terminology I know how to explain the procedure. You may even find the simplicity of the terminology I use easier to understand than mathematic "jargon"</em></p> <p>You need to use the nominal centre points of all objects in the formation to determine the exact <em>Formation Centre</em> (this will be, of course, a 3D Vector consisting of an X, Y and Z value)...</p> <p><strong>Object Total</strong> = The total number of objects within your "formation"</p> <ul> <li>Cycle through all objects in your formation <ul> <li>For each <strong>object</strong> (to calculate <em>Axis Total</em>) <ul> <li>Add the X co-ordinates together (gives us <strong>Axis Total X</strong>)</li> <li>Add the Y co-ordinates together (gives us <strong>Axis Total Y</strong>)</li> <li>Add the Z co-ordinates together (gives us <strong>Axis Total Z</strong>)</li> </ul></li> <li>For each <strong>Axis Total</strong> <em>axis</em> (to calculate <strong>Formation Centre</strong>) <ul> <li><strong>Formation Centre X</strong> = <strong>Axis Total X</strong> divided by <strong>Object Total</strong></li> <li><strong>Formation Centre Y</strong> = <strong>Axis Total Y</strong> divided by <strong>Object Total</strong></li> <li><strong>Formation Centre Z</strong> = <strong>Axis Total Z</strong> divided by <strong>Object Total</strong></li> </ul></li> </ul></li> </ul> <p>The three values you now have constitute the <strong>Formation Centre</strong> (as a 3D vector).</p> <p><strong>NOTE</strong>: <em>If you are arranging your objects based on a pre-defined fixed point in 3D space (0, 0, 0 for example) you don't need to do the above calculation, as your <strong>Formation Centre</strong> will be that fixed point.</em></p> <ul> <li>for each object <ul> <li>Calculate the <em>Distance</em> of each axis (<strong>Distance X</strong>, <strong>Distance Y</strong> and <strong>Distance Z</strong>) of the <em>Object Centre</em> from the according axis of <em>Formation Centre</em>... <ul> <li><strong>Distance X</strong> = <strong>Formation Centre X</strong> - <strong>Object Position X</strong></li> <li><strong>Distance Y</strong> = <strong>Formation Centre Y</strong> - <strong>Object Position Y</strong></li> <li><strong>Distance Z</strong> = <strong>Formation Centre Z</strong> - <strong>Object Position Z</strong></li> </ul></li> <li>Scale the object by your desired <strong>Scale Factor</strong></li> <li>Set the X, Y and Z <em>Position</em> values to their current value plus the distance value of the same axis multiplied by the scale... <ul> <li><strong>Position X</strong> = <strong>Position X</strong> + (<strong>Distance X</strong> * <strong>Scale Factor</strong>)</li> <li><strong>Position Y</strong> = <strong>Position Y</strong> + (<strong>Distance Y</strong> * <strong>Scale Factor</strong>)</li> <li><strong>Position Z</strong> = <strong>Position Z</strong> + (<strong>Distance Z</strong> * <strong>Scale Factor</strong>)</li> </ul></li> </ul></li> </ul> <p>If you've done this correctly, your objects have now been scaled, still retain their formation, but have moved relative to the <strong>Formation Centre</strong> and <strong>Scale Factor</strong>. Simply put: occlusion between these objects can no longer occur as their <em>Positions</em> have scaled along with their <em>Dimensions</em>.</p>
    singulars
    1. This table or related slice is empty.
    1. PORelatively scale an object collection in 3D space
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USLaKraven
    1. USLaKraven
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORelatively scale an object collection in 3D space
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIt's also worth pointing out that this is pretty-much exactly how the objects themselves are scaled individually! The verticies are just repositioned relative to their central point!
      singulars
      1. PO
      1. USLaKraven
    2. COThat did the trick :) Many thanks for the detailed explanation.
      singulars
      1. PO
      1. USshadeMe
    3. CO@shadeMe You're very welcome! This is the sort of thing best demonstrated with a video, though, and your question has inspired me to put together a full video demonstration of this process (step-by-step)
      singulars
      1. PO
      1. USLaKraven
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload