I am trying to render a very simple PRT sequence and I keep getting an error msg at frame but the error msg is blank so I cant figure out whats going on.
Anyone experience this before?
Never seen this.
Does the PRT sequence show up in the viewports?
Does it show in the Particle Data Viewer?
How / where was the PRT sequence created?
Hello.
Does the PRT sequence show up in the viewports?
It does show up but at the frame i get the error there are no particles.
Does it show in the Particle Data Viewer?
After the error nothing shows before the error I can see the data.
How / where was the PRT sequence created?
It was with pflow a simple flow. I am using a PRT cloner but it dosent seem to make a difference whether i use it or not.
If you go to fram 478 , thats when the error happens.
Your archive does not contain the PRT files, only frame 0000 with 1 particle in it.
From the sound of it, the file is simply corrupted. You might have to resave it.
I thought that was the case as well, and I saved it a few times but I still get the same issue. I have added the PRTS to this msg.
v003.zip (4.75 MB)
Ok, I think I figured it out. I would consider this a bug, but thankfully there is a relatively easy workaround until it is fixed.
Here is what I did:
*First, I loaded the PRTs in an empty scene with only one PRT Loader, no Magma, no Cloning or Materials. Everything loads OK, so all frames are valid and not corrupted.
*Second, I tried to look at the data inside your scene. I noticed that the PRT Loader had a material assigned. I put the Krakatoa Material in the Compact Material Editor and then removed the material from the PRT Loader ($.material = undefined). Error was gone!
*Knowing that the material is related to the problem, I looked at the PRT data again - on the frame where the error appears, the PRT frame contains zero particles. It appears that having zero particles with a Krakatoa Material is a bad idea (and it seems to be a bug), so I set the Limit To Custom Range end frame to 98 (the last frame with any particles) and it stopped failing.
Now of course this is slightly bad because there are still a few particles visible, and setting the end condition to Blank does not fix the problem. But since the error seems to be in the Krakatoa Material itself, I decided to copy the GradientRamp map into the Diffuse slot of a Standard Matertial and… the error was gone even with zero particles!
So I am off to log the bug in our database, and you can just use a Standard Material in place of the Krakatoa Material, unless you need Raytraced Reflections which requires the Krakatoa Material. Pretty much everything else can be achieved using the Standard Material…
Thanks for your report!
Thanks Bobo!!.
That explains why it suddenly started doing that I wasn’t using a Krakatoa material before.