Saving bricks' relative positions yielding incorrect results?

[otto-san]

I decided to remake saveDup in a way that makes certain tasks easier for me since it's broken, but I ran into the same issue. (probably was a good idea to do the exact same thing as something known to be broken to achieve the same goal)

I'm just looping through a given brick's upBricks and saving them to a .bls file using their positions relative to it (using VectorSub(%upBrick.getPosition(), %brick.getPosition());).

However, when doing so with this:



I get this result:



Is there a solution to this or should I go with another method?

edit:
'incorrect' may be a bad word to use for this. i guess some bricks determine position oddly?

[Ad Bot]

[otto-san]

ugh i solved this by subtracting 0 0 0.1 from the base position

the reason i wasn't seeing this change is because i didn't save the set of bricks so i kept loading an old broken one hahaha gg

this probably isn't a good solution though, so i'll look into it further when issues arise

[Treynolds416]

Yea, upbricks is generally not useful for duplication, even if it's not the source of your problem. I have some (very slow-computing, because it's unoptomized) logic code that gets bricks that a brick is independently supporting. I'll post it if you guys would like to have a look

[Zeblote]

Yea, upbricks is generally not useful for duplication, even if it's not the source of your problem. I have some (very slow-computing, because it's unoptomized) logic code that gets bricks that a brick is independently supporting. I'll post it if you guys would like to have a look

I think that's not what he wants to do but post it anyways!