Strange thing happening, I've been rendering passes the last few weeks without issue but in one particular project (LW scene) it's not rendering out the passes. I've checked all the usual settings to make sure things are rendering, but nothing is any different than the scenes I've been working with except the location of the files (and even then it's only a different sub-directory on the same drive.
It seems like it's just a setting I'm missing, but can't seem to find it. Any thoughts?
thanks!
bruce
F10 render passes not saving
Moderator: juanjgon
okay, so I had a thought. I tried a different directory and realized the image being saved didn't have a frame number (it was saving the first frame). So I loaded up the image in irfanview and waited until LW had "rendered" a few frames then loaded that image in a separate irfanview window. I AB'd the two images and noticed that LW was saving each rendered image with the same name. Auto Frame Advance is checked, but it keeps rendering over the top of the same image (without number the frames)
Anyone else run into this?
thanks,
bruce
Anyone else run into this?
thanks,
bruce
The problem are the dot characters in the filename. If you replace your "ww.turtle.01.v001." base name for something like "ww-turtle-01-v001", the plugin works fine.
I can't see any problem in my code, so this could be a limitation of the Octane save functions. Do you know if the passes are working in other early plugin versions (saved as discrete PNG files) with dots in the file name?
-Juanjo
I can't see any problem in my code, so this could be a limitation of the Octane save functions. Do you know if the passes are working in other early plugin versions (saved as discrete PNG files) with dots in the file name?
-Juanjo
hmmm...really strange.
I changed the filename to underscores "ww_turtle_01_v001" and it did the same thing. REALLY weird. Also, just for kicks, I selected a bunch of passes to render as well (I was only rendering a Main pass) and it doesn't save ANY of those files.
bruce
edit:
I used to use "dot" names a while back (previous to Octane) and had only decided to try it again on this particular scene. The other scenes I have did use underscores. I was hoping that would fix it, but it's still the same problem as noted above.
I changed the filename to underscores "ww_turtle_01_v001" and it did the same thing. REALLY weird. Also, just for kicks, I selected a bunch of passes to render as well (I was only rendering a Main pass) and it doesn't save ANY of those files.
bruce
edit:
I used to use "dot" names a while back (previous to Octane) and had only decided to try it again on this particular scene. The other scenes I have did use underscores. I was hoping that would fix it, but it's still the same problem as noted above.
yowza! nice catch on that! It was still in there, sneaky little bugger...that seemed to do it. So is this the normal way it handles the dots? Seems like back in the day they were all dots before we started using underscores...
thanks, juanjo, once again you saved my bacon!
bruce
thanks, juanjo, once again you saved my bacon!
bruce
One other crazy thing that hasn't really bothered me (I just work around it) is the naming of the render passes. I have it set to:
Name_pass_0001
but it renders out:
ww_turtle_01_v001_Main-0000
where right after the pass name (in this case "Main") is puts a minus sign as opposed to an underscore.
would this be an Octane thing, or part of the plugin?
thanks,
bruce
Name_pass_0001
but it renders out:
ww_turtle_01_v001_Main-0000
where right after the pass name (in this case "Main") is puts a minus sign as opposed to an underscore.
would this be an Octane thing, or part of the plugin?
thanks,
bruce