I noticed that if one frost mesh is falling in another frost mesh , than unwanted results occur, not showing up in viewport and/or not rendering.
Restarting max or reloading the PRTs sometimes helps .
Also some comments:
In frost on the Meshing tab > Viewport > Enable in Viewport > Particle % … If we use less than 100% than it renders less than 100% too, that’s confusing because we expect only reduced display amount. Maybe another percentage spinner for rendering display would be useful to control the render amount separate.
Loaded PRT sequence throws and error message at render time if its offset and its missing frames, this is very annoying. In Krakatoa GUI there is an ignore missing frames button but if I use other render engine with Frost I get the same error. In PRT loader there is a “Dont render missing frames” button , its confusing , because I am not sure if I have to check that for all PRT loaders? I think it should be default OFF or should be on a more global place.
I have not seen this problem. Could you please send us a scene file that reproduces this problem using our ticket system, along with your 3ds Max version, Frost version, and a screenshot?
This is not intended – Frost should always use 100% of the particles when rendering. What renderer are you using? Again, could you please send us a scene file that reproduces this problem using our ticket system?
I’ll look into this.
The intended way to handle such problems is to enable “Limit To Custom Range”, and click the “Range” button to choose a valid range. You can find these controls in the “Particle File Loader” rollout in the PRT Loader, and in the “Particle Files” rollout in Frost. Is this reasonable in your case?
I’ve been tempted to change Frost so that, when you add a file, it will automatically enable “Limit to Custom Range” and choose a valid range. I think you almost always want “Limit to Custom Range” enabled, and it’s easy to miss.