some small bugs/wishes

Bugs:
[]Viewport update checkbox isn’t working for me (beta3).
[
]There is no any check if distribution obj is proper. As example if I picked particle flow which is turned off, Stoke is trying to evaluate in every frame (with nothing happening of course).

Missing Features:
[]I really don’t like how velocity sources is listen. Long pflow names isn’t easy to see. Maybe it is better to split them to separate list?
[
]Viewport Display is great, but where turn off Rendering? :slight_smile: One button to not render all Stokes in Krakatoa isn’t enough.

[*]It will be super cool to have Stoke Follow operator for PFlow. Or at least support Stoke in Ember Follow operator.

Overall Stoke experience is awesome, you guys rock in all vfx directions. Keep it up!

You mean the Viewport Display > “On” checkbox?
I just reinstalled Beta 3 and it works for me (Max 2013, 64 bit).
What Max version are you using?

Thanks for the report.

I agree, but we cannot make the UI wider than 160 pixels, that’s the limitation of the Max Command Panel.
You have two options - drag the name column wider to see more of the name (but have to scroll to see the Scale value), or hover over the name with the mouse to read the tooltip.

Hide the object? :wink:
I am sure we could squeeze in a “Render On” checkbox somewhere…

I also feel Stoke should be a valid source anywhere SIM Ember is accepted (including Ember Force and Ember Follow).

I believe marking a node as non-renderable via the node properties page is the definitive 3ds Max way of doing this.

The dialog for that is modal and nobody likes going there. So when you set an object as “non-renderable”, there is no indication why the object does not render, while hiding the object obviously removes it from view, and a checkbox in its UI is in your face…

I only set object to non-renderable when I know I will NEVER want them renderable again in that scene. E.g. source meshes of PRT Volumes etc.

I mean checkbox and value for the viewport refresh when simulating. I’m using max2012 x64.

I know that this is max limitation, but maybe to split PF sources and Events to separate lists? Anyway, this isn’t very important, just my impressions when I picked pflow which have more than 15 events :slight_smile:

I absolutely agree. Marking at object level isn’t a comfortable solution, especially while working on several Stoke/PRT Loaders switching from one to another. Simple checkbox will be enough.

While I completely agree with this sentiment, accessing non-renderable is a PITA either threw Props or the lacking in love Layer Manager. Using the non-render hidden objects method has made this somewhat cumbersome work-around that is now regarded as a psuedo-standard operating procedure, one that really should be addressed at a core level, ie max itself. Kinda drives me a little batty.