constant render server error across all files on 2018.1.2 Tweet

[b.o.p]

hey im getting constant render server errors when working, meaning im spending the weekend in my office having to manually render a frame and then save the image for every frame. blender/octane is becoming unbearable when rendering especially when the live viewer works flawlessly !?!?!

anyhow ..... the two files being worked on for clients are largely different.
one is a ten second animation with a memory size of around 75 Mb and the other is a full 3:30 animation with around a file size of 60-100Gb on disc but only 4-5Gb on rendering so i don't know why i can't get either file to render past the first frame unless im doing it manually and saving each file manually. i can send the files via mail but they cannot be shared on the forum due to not making them publically available, im sure you understand.

i desperately need a clear solution to why we have to use this overly complex middle man render server that is the week link in the whole chain, its what fails every single time. why you don't just get us to sign in once a day, when we open blender with our credentials and then allow it to stay open until we close?.

im so close to switching back to our studio's previous rendering solution as i spend more time trying to troubleshoot and try and figure out where octane is going wrong. im literally losing income due to having to make up extra time or not take on jobs because i can't trust octane is going to run or work with what we throw at it .

steps we have taken to try and resolve what's going on .
1 we removed every piece of software and plugin not needed for each project.
2 changed and reordered each GPU
3 bought new routers to see if the network was the issue
4 swapped out hdds
5 removed all O/Cs on pc
6 stopped all unneeded essential software at rendering
7 shut down all monitors bar one
8 updated all drivers
9 put down a salt circle and offered up old ram to the pc gods

errors for the small Vectron file

errors for the large file

a few side notes ....... for the Vectron file, the Vectron code always complies correctly

for the larger file, we don't need to use out of core , although we did try it , it made no difference as the size for the render was only 4-5Gb and all ai and denoise attributes were turned off


all and any help welcome if you work at otoy and what the files PM me and ill get you links via correct channels so you can test them if needs be.

best

B.o.p

[BK]

hey im getting constant render server errors when working, meaning im spending the weekend in my office having to manually render a frame and then save the image for every frame. blender/octane is becoming unbearable when rendering especially when the live viewer works flawlessly !?!?!

anyhow ..... the two files being worked on for clients are largely different.
one is a ten second animation with a memory size of around 75 Mb and the other is a full 3:30 animation with around a file size of 60-100Gb on disc but only 4-5Gb on rendering so i don't know why i can't get either file to render past the first frame unless im doing it manually and saving each file manually. i can send the files via mail but they cannot be shared on the forum due to not making them publically available, im sure you understand.

i desperately need a clear solution to why we have to use this overly complex middle man render server that is the week link in the whole chain, its what fails every single time. why you don't just get us to sign in once a day, when we open blender with our credentials and then allow it to stay open until we close?.

im so close to switching back to our studio's previous rendering solution as i spend more time trying to troubleshoot and try and figure out where octane is going wrong. im literally losing income due to having to make up extra time or not take on jobs because i can't trust octane is going to run or work with what we throw at it .

steps we have taken to try and resolve what's going on .
1 we removed every piece of software and plugin not needed for each project.
2 changed and reordered each GPU
3 bought new routers to see if the network was the issue
4 swapped out hdds
5 removed all O/Cs on pc
6 stopped all unneeded essential software at rendering
7 shut down all monitors bar one
8 updated all drivers
9 put down a salt circle and offered up old ram to the pc gods

Inkedror errors_LI.jpg

Inkedship errors_LI.jpg

a few side notes ....... for the Vectron file, the Vectron code always complies correctly

for the larger file, we don't need to use out of core , although we did try it , it made no difference as the size for the render was only 4-5Gb and all ai and denoise attributes were turned off


all and any help welcome if you work at otoy and what the files PM me and ill get you links via correct channels so you can test them if needs be.

best

B.o.p

Hi B.op,

Thank you for reporting this. We have sent an email via Zendesk support.
Looking forward to your reply.