Activity Feed

Hey Jiri!

• The idea behind find_first_points() was to evaluate the function only at "lattice points" to cache them in the hash table. The function evaluation (bvh traversal and actual densfunc()) take 95% of the time in polygonization, so any gain made in this area contributes a lot to speed. But, to be honest, I just coded it this way out of laziness temporarily :-) I could make a version with 26 directions and check how it behaves. If all values will be cached, the speed shouldn't be much worse, and surface accuracy is number 1 priority after all.
• I don't exactly know what you mean by caching the surface? Updating only the part of the surface that was influenced by a moving metaball or something else? This could be a serious improvement, but not in the case when all metaballs are moving (eg. a fluid simulation). Could you explain it more?
• Sorry, but I don't have the energy to look at these papers right now (very tiring day at uni, a lot of science done :-)). They look very interesting at first glance. Will check them out in detail later.

Replace i by cam_idx in loop.

can we raise this back to normal because it will take a some time for us to test

i am sorry i had to do something and thought this was all that was needed

Closed by commit rBA514c08f839d5.

Wow, that is a huge scene !

So now we could set proxies for selected strips? Awesome! But could you please change the name of this operator to something like: "Proxy Sizes" — simple and comprehensive, and there could be more extensive information in the tooltip.

Oki, need a fresh mind for this which I don't have atm ;P Will reopen as design task and assign to me so I won't forget it

Com on, you should know that this isn't enough information. What happens, what do you expect to happen, steps to reproduce, ...

Initially we had both, then we agreed that having two ways to set the proxies was confusing too. The advantage of having an operator is that it allows us to set proxy settings for all selected strips, something which would otherwise require a script. I don't mind reorganizing the panel as you show (though I'd like to keep the organization and labels ("Enabled Proxies", Overwrite under the proxies). Probably the information can go just below the buttons to keep all proxy settings together.

If even the debug options don't show anything, this really looks like the event is swallowed from the driver. We could do some more in-depth debugging on event system/GHOST level, but I'm afraid that'd just be wasted time as I'm pretty sure we have a driver issue here. So, .... I'll close the report for now, but will keep my eyes open for similar issues. If others are affected as well, we can go back to it. Hope that's fine with you?

I know you don't like having to spend time on particle bugs, but this looks like a rather easy thing... So if you wouldn't mind? :)

Ah I think I can see what you mean. @sindra1961, you mean the render type always assumes a non-Hexagonal grid until you turn on and off Hexagonal grid, right?