[BUG] Pavement Plus Mortar Bug (Staff: Confirmed)

Mortar Width 0..99 OK,
Mortar Width 100: Rendering is all wrong

I bet you can find a division by zero somewhere in a dark corner

Pavement Plus Bug.ffxml

it is not a "bug"!
It is "Optimization"!

Yep, that was a decade-old optimization that bit us in the arse when we introduced slave components. Another optimization like this is the sample cache: we're currently rewriting it completely.

Vlad, is the caching mechanism active even if there is just one outbound connection?

If so, there is a pretty significant performance improvement: remove caching mechanism in components that will only deliver a sample once per final sample.

Quote
Sphinx. wrote: Cool. I really hope you will consider the index/channel idea I presented here then. It may be useful with the slave situation too, as you can increase the index as needed.

if I understood that correctly, you're suggesting caching samples per outbound connection, not per component. Am I correct?

Quote
Vladimir Golovin wrote: if I understood that correctly, you're suggesting caching samples per outbound connection, not per component. Am I correct?

No, it is a little more sophisticated than that. Even though there is just one connection, any component up the flow may branch out to other components. As long as x,y stays the same it is all good, but if one is a distorter which modifies x or y it will miss the cache, force rendering of a new value and ruin the cache for any subsequent original x,y calls.

Quote
Sphinx. wrote: Vlad, is the caching mechanism active even if there is just one outbound connection?

Sorry, that was really not what I meant to ask. I was thinking about the sampling calls: if a component is only called once, do you still check and/or set up cache?

(I was thinking about a trivial filter with an Add connected to result and nothing else, and got all focused on that one connection.. forget about the number of outbound connections... its all about the coordinate flow and branchings/iterations)

What I proposed back then was this:

Quote
Any component that changes coordinates, should attach an index/ID number to its sources, making the sources spawn a new sample cache reserved for incoming requests with that ID

Basically any distorter up the flow will change the cache channel index/ID and thereby establish a new isolated cache for anything subsequent to that distorter.. and thereby not ruin the original x,y cache.. follow?