Monitor blinking and octane error 999

[rafaelcoppola]

Hello friends of the forum, I'm having an error that taking my sleep of (literally) ...
I start my render this scene, whether this in PMC, path tracing or direct light,
and at first all is well with no problems, however after a while when the yield reaches about 20 samples
the monitor flashes and appear some error messages (pictures attached) ...
I'm lost because I tested the same scene in 3 different computers and the same error occurred in the 3,
another thing I cannot understand is why it also begins to render normally and suddenly the error occurs.
The drive from my video card is update with the latest version (I tested on computers with Titan and Titan Black)
since already I appreciate the help

error 2

error 3

error 3

error 4

error 5

[rafaelcoppola]

I'm using 801 SP3
I tried to render into the octane plugin 2_21_1_53 and 2_23_2_78

[face_off]

Hi

Is it just that scene which is causing the error - or all scenes?
Are there any displacement maps in that scene?
What Nvidia driver version are you running?
What graphics card(s) do you have?
Are they overclocked?

Thanks

Paul

[rafaelcoppola]

Hello Paul
Thank you for the answer!
The error occurs in my last scenes, I'm testing this moment how many scenes have been affected by this error, so far it was the three last.
Last night I testing numerous times with different versions of the plugin (2_21_1_53 and 2_23_2_78) and 3 different machines, follow the specifications:
-1 Computer with 4 Titans
-1 Computer with 4 Titans Black
-1 Computer with 2 Titans Black
in all computers I used the last version of NVidea driver, the 353.30 driver
I test with daemon on and daemon off.
I'm using displacement on the ground.
The video cards are stock speed.
thanks

[face_off]

Thanks for sending through the scenes causing this issue. They both render fine on my PC. My guess is that maybe the displacement map is causing the problem. Would it be possible to send me the displacement map pls, and I will take a closer look.

Also - have you installed Octane Standalone via the .exe installer? (pls see question 5 at http://render.otoy.com/manuals/Modo/?page_id=416 for details).

Paul

[rafaelcoppola]

thanks for the reply, Paul
if I take a guess, I dont think is the displacement that causing the problem, I say this because the materials with displacement were already there before the problem started ....
Yes I installed my Octane via .exe.
Yesterday I talked to the people here in LightFarm studio about this crash (Rafael Vallaperde and Rafael Moco), we realize that this error usually happens when the daemon is connected, in my particular case, it happened when I started to render using the cards of other computers(network rendering). Its takes some time to happen, not right away, it renders some samples and then it crashes ... if you save the scene after the crash it becomes corrupted forever(like it saves the crash), at least on my computer. Yesterday I backtracked about 5 scenes behind and found a scene that was okay, reworked all materials using exactly the same parameters for material and light (including displacement) and so far I did not have this crash, thank God....
I will upload a scene with the textures and send you.
big hug
Rafael Coppola

[face_off]

Hi Rafael. We need to isolate if it is an issue with network rendering or that scene. I suggest disabling network rendering until you are comfortable that there are no issue with that scene, then enable it.

if you save the scene after the crash it becomes corrupted forever(like it saves the crash), at least on my computer.

I suspect if you get the crash, then reboot all PC's you should be able to render again. I wouldn't think it possible that a crash could effect the LXO.

I will take a look at the new scene you sent me and enable network rendering for it too.

Thanks

Paul

[rafaelcoppola]

hey Paul, thanks again

I am working since yesterday with the daemon off, and so far I did not have that problem anymore ...
I restarted all PCs after the crash and the error persisted in all files and PCs, at least on the computers here.
It really does not make sense the error corrupt file or something, put all files that have since come to the error display ever ....
big hug

[face_off]

Some more details on this issue...

1) Yes, your scene is causing an error 999. I believe this error is coming from the slave (you can see the cuda error on the slave PC terminal window). I appears to be related to a particular texture. If you export to ORBX, load into Standalone, and try to network render there, the upload process gets stuck at 147/746MB, so I think something in that scene (a texturemap?) is terminating the upload process, resulting in the error 999. I have uploaded the ORBX to the Otoy devs to determine the exact problem.

2) Yes, after this error, loading the scene into Octane only loads a partial scene. I have never seen this before, and have no explanation! Clicking the Refresh button seems to fix the issue.

Thank you for all the info you provided.

Paul

[face_off]

Hi Rafael - The Otoy devs believe that the error 999 is due to the slave PC Nvidia time-out settings. Pls see http://render.otoy.com/forum/viewtopic. ... 68#p214968 for details. Can you pls install Octane Standalone 2.23.2 via the installer EXE on all your slaves and try again?

Thanks

Paul