Hi guys,
Congratulations! this is great plugin, like everything you do.
I have some wierd behavior. I’m using TP as source and enabled “use radius channel”, but when frost updates there is no mesh.
Also I set the same radius that is in tp, but with radius channel disabled and it works. Maybe I missed something?
Could you please send us a .max file which reproduces this problem, either through this forum or our ticket system? Also, please let us know which version of 3ds Max and TP you’re using.
3ds max 2011 sp1 and tp 4.0.6.4
Thank you for your report!
Edit: Removed incorrect workaround.
Huge thanks.
You’re welcome!
A correction for my original response: there is no need to apply a Scale operator. I misunderstood the scene setup.
Another note: Frost treats the thinkingParticles Size as diameter. If you want the Frost Radius to match the thinkingParticles Size, you must set the Size to 2 * the Radius. For example if the Radius is 3, you must set the Size to 6 to get the same result.
I’m having some weird behaviors with the radius channel. I put a prt volume object that has a float fed into the radius channel. I also put a default pflow file and TP just to show it happens with TP as well. I assumed that as long as Frost can read the radius channel from each then I could control each one separately, but somehow once a certain radius value is changed then the other sources are losing the resolution of their volume. That behaves the same in all modes.
Open the file I attached and change either the radius in the PRT, the size in TP and the size in the pflow shape op.
frostRadius_max2011.max (260 KB)
I don’t have TP at home so I cannot test the file, but are you using Relative Meshing? If you are, the meshing resolution will depend on the largest particle in the stream. So if you get one particle to be very large, very small particles could disappear if there is not enough resolution to accommodate them. Using Absolute Spacing fixes this, but now the meshing is not adaptive, so if you have varying sizes over time, the mesh won’t flicker, but it will also not adapt to the changes. In general, if you have two or more systems with vastly different radii, we recommend using the Absolute Spacing mode to ensure the smaller one is getting enough resolution.
If this is NOT your problem, please post some images.
In addition, when using Zhu/Bridson mode, the Blend value is dependent on the size of the largest particle. Thus, if your particles are changing size over time, the Blend value could be fluctuating, too. In that case, we recommend adding a Sphere Gizmo helper with the desired Max. Radius and putting it far away off screen to preserve a constant Blend factor.
Yes absolute spacing solves it. Can’t believe I missed it. Thanks a lot!
I’ll try the sphere gizmo trick too. 
The Gizmo trick turns the Relative Mode into kind of Absolute (or at least Constant) as long the the Gizmo is larger than any particles on any frame.
It should only be used if you are already using Absolute mode and you have flickering in the Zhu/Bridson blending due to new particles born with larger size than the previous frame - introducing the Gizmo defines a max. particle size throughout the whole animation.