Andreas Hohl
Forum Replies Created
-
Ok I did that – getting very weird results. If the particle is bright enough – it does a horrible job, but at least puts more than just black out. I can send you a sample if you like. The result is different each and every time. Even on the same project. This is totally weird.. I won’t be back till Friday, so no rush on my part.
-
Yes – it is the version downloaded this morning 3.0.7.1 – and yes – auto load is unchecked and has always been unchecked.
-
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.
-
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?
-
I did a search – found one in the “virtual store” under AppData (created 090110) – deleted it – but no change.
-
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.
-
Yes – these are totally sweet! –
-
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
-
I am experiencing the same issues all of a sudden. My first assumption was that it may have to do with the new ATI drivers. They boogered up a lot of other software as well as plug-ins (Magic Bullet Quick Looks for example) – We got those working again by reverting back a few versions of the stupid video drivers, but that in itself is not a clean solution. So, what now? Red Giant released some new versions (patches) to handle the new driver pretty quickly. I don’t know what the heck ATI is doing at this point. Looking deeper – I reverted the driver back again for testing PI (rollback) – but it made no difference. However, if I use PIRender standalone and render uncompressed AVI (so that I can get an alpha channel) – it works. This is totally weird. I guess for now it just will be a two step process. I will keep experimenting and if I find a real good solution, I will certainly share it. – Just for some specs: software rendering only (using an ATI Radeon 4800 on Win7 64 bit 6GB ram) – follow up – I did move back to the latest driver – and it does work as the two step process – hence, it most likely is not a video driver issue. But rendering from within PI is simply no longer working. 🙁 – The only thing I can think of now is that the codecs have somehow been modified or updated.