Hi all,
I'm posting a bit of my life story here for context.
------
I'm having a bit of a nightmare with a job.
As far as I understand it's gone pretty smoothly - high res statics went to the client, every 25th tests were done for the animation.
Then, when trying to render it with our render manager it wouldn't render.
I then took over to fix the issue - Currently I wish I hadn't offered.
Sooooooo, I recreated the shots (all I really did was load the save and resave the scene) and they were rendering fine
However, they were taking too long to parse the scene.
Yesterday I spent most of the day optimising the scene
It then wouldn't render again
After a lot of testing (I was up until about 1am) I realised that it was one of the proxy trees
I turned them into a mesh, put a cube below it & attached it to the tree (this is what we've done in the past to fix dodgy objects (it seems to work)) - I then re-proxied and replaced.
IT WAS RENDERING - WHOOOOP
I left a system rendering the cache and went to bed.
This morning - 5 of the 9 systems are rendering the animation.
The others are giving this error - Does anyone know what the hell this means and what's going on?
15/03/2024 05:27:14: 15/03/2024 5:27:12 AM; Error rendering frame 358: <string>:8: DeprecationWarning: the imp module is deprecated in favour of importlib and slated for removal in Python 3.12; see the module's documentation for alternative uses
Let me know if you need any more information but we're using Max 2024 - Corona 10 (hotfix 1) - We have no issues with animations normally so I don't see why the Max version & Corona
Thanks
