PTE build 85104-pte is now live!

cola_colin · August 4, 2015

pinbender said: ↑

cola_colin said: ↑

cola_colin said: ↑

pinbender said: ↑

Funny story here. Turns out that if you put in a value that is too far below the planet's surface, it won't actually snap to the surface. So aim for the planet radius. (I've added normalizing to the planet radius first to my to-do list...)
Click to expand...

Hmm, I can't get any values out of it that seem to snap.
Again on forge, I've used the raytrace API to get the location
-370.6982421875/-27.386085510253906/-164.40219116210938

world.fixupBuildLocations("/pa/units/land/energy_plant/energy_plant.json", 0, [{pos: [-371, -27, -164]}]).then(function(data) {console.log(data);});

does not snap. I'd say that is pretty close. Forge has a radius of 400, my input position has a distance to 0 of ~406

Another test with all positive values did not work as well.

EDIT:
Another greedy request that goes beyond fixing it: Return the snapped position even in case the build placement test failed.
Click to expand...

@pinbender
okay it does snap when I test a position close to the planet surface. However there is a second bug that prevents the snapped location from being returned, I always get the position back I put in. So I can see the result of the test changes, but the returned position is always just the position I put in.
Click to expand...

I found a bug that would cause this. It should be fixed in an upcoming update.
Click to expand...

I assume the normalized vectors are also not hard to fix? I would've assumed the puppets snapping and the placement snapping use the same snap function. The puppet snapping with snap: 0 is perfectional.
Sounds greats, this API is basically exactly what I need for the most part in this area.

PTE build 85104-pte is now live!

cola_colin Moderator Alumni

Share This Page

PTE build 85104-pte is now live!

cola_colin Moderator Alumni

Share This Page

Useful Searches