Maxscript bug

[AlexMcLeod]

Hi!

After using a_setsystem() on a PhoenixFD object to set its coordinate system, it becomes unreadable with commands like a_getv(), producing an access violation error.

It works in grid space but not in world or object space. That's with version 3.10.01

I have this workaround that seems to produce the right coordinate system for a_getv etc.
inverse (matrix3 ($.transform.row1 * $.cellsz) ($.transform.row2 * $.cellsz) ($.transform.row3 * $.cellsz) ($.transform.row4 - ([0.5 * $.xc, 0.5 * $.yc, 0] * $.cellsz)))
...but am I missing anything?

[Svetlin.Nikolov]

Ouch, thanks! Will be fixed for tomorrow's nightly - the crash happens with object and world coordinates but not with grid coordinates, and in case you are accessing the cache data while the simulation is stopped and not during sim.

This is indeed the correct formula for converting world to voxel coordinates