-
Rendering black
-
I’m posting an update to pIRender on Windows (via AutoUpdate) that should fix this problem.
Alan.
-
Hi Alan,
Got the fix – downloaded and installed. But no luck. Still need to render as standalone. I verified that the fixes were installed.
Just as an FYi –
Trying to render to AVI uncompressed, Alpha, and remove black bg are checked.
Also tried without checking Alpha – still no luck.No worries though – I know these types of bugs are not easy. So for now I will simply do a two step process until we can help you figure out what’s at bay. 🙂
Thanks for your speedy support and replies in any case. – Andy
-
Thanks Alan!
I updated and it all seems to be working fine for me now.Andreas:
I have a similar set up. Windows 7 (32) Radion HD 4800 (1024mb) I am using the latest drivers – 10.11 though.
I am also rendering out as a png sequence and PI calls the stand alone renderer as my scene size is over 200 pix. That works fine. My actual sized rendering – so it fit on the screen always worked. (It still does with the update) I don’t know if this helps at all.Huge Regards
Dave -
Uncompressed AVI doesn’t work for some people with pI. I’ve never been able to figure out why. Try a different format and see if that helps.
Alan.
-
Yeah – I am on 10.11 (ATI Catalyst) as well – but still no luck.. I am on 64 bit. The weird thing is this all worked beautifully only a couple of weeks ago. So I have been reviewing what has changed. The only two things that I can imagine are the drivers (ATI) and Neoscene – but since I am not using the neoscene codecs ( They give erroneous errors, really.) for this, it should not impede this process. I have now tried to output a series of PNG with alpha – same results – all black. Same result with TIF sequence – all black. As said – if I do the renders separately using PIRender, no problems. This is totally weird.
-
When pI3 calls pIRender, it saves your project in a temporary project file called “pirender_project.ip3”. Why don’t you search for that file and delete it — perhaps it got set to read-only or something, so pIR is never getting the real project info.
Alan.
-
I did a search – found one in the “virtual store” under AppData (created 090110) – deleted it – but no change.
-
Ok, I just remembered something. Launch pIRender manually, then uncheck the “autoload” option, close pIRender, and try again from pI3.
If that doesn’t help try this:
1) Save your project file.
2) when pIRender is launched by pI3, if the render starts right away click the little “?” button to bring up the “about” window and pause the render. If it doesn’t start right away, don’t start it.
3) When pIR isn’t rendering (not yet started or paused with “about” box), search for “pirender_project.ip3” then compare its size to the project file you saved in step 1. If you can’t find the project file, or if the project files aren’t identical, let me know the details.
Alan.
-
Ok did what you asked – it created a pirender_project.ip3 file and yes, it is the same size as the project ip3 file. Just to make sure – searched the entire puter. 🙂 – Also checked to make sure that there was plenty of drive space on potentially used drives. And just to play it safe – I tried once more while running as “Administrator” – no change. Set compatibility up to WinXP SP 3 – no change. Also for the heck of it used a different drive – no change. I bet it will turn out to be something really silly. I am at a loss of any more ideas of things that could have changed. So logically thinking – if really all PI does when you ask for a render, it opens the PI Renderer. Maybe it is a memory issue or lack there of. But with 6 GB it should be fine. In any case – I proceeded to render a different file with a different size, and it still showed the original render file – so it is not creating a new file as it I suppose should. So I stopped the render altogether – deleted the pirender file and now I am totally locked out of the software with the sitecode MID screen. It now asks me for the activation code. –= Under application status it says it’s “locked” – now what? 🙁 scratching my head. I probably blew it up by deleting that file eh?
-
Ok, I verified that it is NOT consistently creating the pirender file, even when just using the render program as stand alone. It does create some weird shortcut files under my users dir and under the “AppData\roaming…. ” – but one thing that really sticks out is that video memory is being eaten up by PI. For example, while PI is running, and you have a window open and move it, it give that echo effect and it is really jumpy. Forget about trying to bring up the task bar. It is hidden behind PI if PI is maximized. Could be something, could be nothing. It is just acting very strangely now.
Reply to this Discussion! Login or Sign Up