So, to be clear, you have a PSCN at (x, y) and a CONV at (x, y+1), and when you stack them, the CONV comes out on top?
If so, that's intended behavior. The stack order should be the original subframe order of the particles before stacking. If you want the CONV to come out at the bottom, you should put the CONV above the PSCN.
why is scale 2 = scale 3?
edit: also scale 3 is scale 4 wich i dont tink even is a scale also more specifically i manually set the scale with notepad and im mean 2 = 3 = 4 as in the windo size is that big
A small update for 96.0 96.1 has been released. This is an ALPHA release, not everything has been tested yet. Expect a cleaner release soon.
v1.10a:
@thepowderkeg There was no changes made to the scaling code. Do you see it perform differently from the unmodded version?
The full release is out, with a handful of bugfixes and features! You're probably most interested in the stack edit feature, which allows you to edit particles in the middle of stacks without unstacking and restacking them.
v1.10a → v1.10:
Just a bunch of minor tweaks and bugfixes.
v1.11:
I have these problems with the new actualization v1.11 (2/8/2021),
I love how the debug bar displays the current particle in ejecution in shift + space.
Thanks, good work!!
Thanks for the feedback! I'll look into providing a shortcut to escape out of stack mode, probably Shift-T. As noted in the README, creating particles in stack edit mode necessarily reloads particle order; I might shift things around so that particle creation is disabled when autoreload is not enabled. Shift + D toggle stack mode, which reloads particle order for similar reasons; that includes completing particle updates to the end of frame, so that observation isn't surprising.
"unrecoverable fault : bad allocation" is definitely a bad bug, though. Do you remember anything about what you were doing or trying to do when it happened?
I was copying and pasting a DRAY element that contained a 3-layer stack into the simulation map tpt.autoreload_enable(1). That was enough at that time for it to fail in this way, when I tried again and the program works correctly.