OTOY Forums

Master and slave are the same version, only the plugin isn't.

Augustronic wrote:Master and slave are the same version, only the plugin isn't.

The plugin or to be more precise, the octane.dll used by the plugin is the master.

abstrax wrote:

Rico_uk wrote:Abstrax, just sent the PM with the log file.

Thank you very much for the log. Interestingly, the slave rendered all samples it was asked to render, so the problem doesn't seem to be on the slave side.

How many slaves are you using? What was the kernel you were using and can you remember how many samples were missing?

The next step would be to log the slave and the master. The procedure would be the same as before, but now you would place the octane_log_flags.txt also into the directory with the octane.dll. The write permission problem is the same. Can you run 3ds max as administrator to make sure that the plugin can write the octane_log.txt?

Anyway thank you very much for your help so far.

So the log text file should be copied into the Max plugins folder with the Octane.dll? I'm using two slave machines, but I've tried using only one at a time and it still does it. I'm also pretty sure I've had the problem without using any slaves and just the local machine. I'm rendering 8,000 samples, and I've tried 16,000 with a similar result. I can't see how many samples are left as it of course uses the Max frame buffer which doesn't display any useful information. The only thing I can see is that the progress bar is always fully to the right, looks like 99.99% complete.

I'll render a sequence now with the log on the master and one of the slaves and I'll send both txt files via PM when it freezes.

I'm not having much luck with the Log file on the master machine, I run Max as Admin and it does create a Log file but it is 0kb and doesn't have any info in there. I've also attached a screengrab of how the rendering progress looks when the problem occurs.

Rico_uk wrote:I'm not having much luck with the Log file on the master machine, I run Max as Admin and it does create a Log file but it is 0kb and doesn't have any info in there. I've also attached a screengrab of how the rendering progress looks when the problem occurs.

I placed a large fan blowing at 4 cards and especially PSU rendering does not stoop anymore! If I turn fan off it will stop in about 10 minutes. I think cards get hot but the main reason PSU gets overheated supplying cards with less power. Try it it might help

coilbook wrote:

Rico_uk wrote:I'm not having much luck with the Log file on the master machine, I run Max as Admin and it does create a Log file but it is 0kb and doesn't have any info in there. I've also attached a screengrab of how the rendering progress looks when the problem occurs.

I placed a large fan blowing at 4 cards and especially PSU rendering does not stoop anymore! If I turn fan off it will stop in about 10 minutes. I think cards get hot but the main reason PSU gets overheated supplying cards with less power. Try it it might help

so Coilbook is that now consistently working? I hope it's not just a temperature thing, I run gpu-z and the temperatures are ok, and I really don't want to have to have fans running pointing at my machines, it doesn't look terribly professional in the office! I've sent Abstrax a couple more log files, one from the slave and one from the master, hopefully he can find something in there that points to the problem.

Rico_uk wrote:

coilbook wrote:

Rico_uk wrote:I'm not having much luck with the Log file on the master machine, I run Max as Admin and it does create a Log file but it is 0kb and doesn't have any info in there. I've also attached a screengrab of how the rendering progress looks when the problem occurs.

I placed a large fan blowing at 4 cards and especially PSU rendering does not stoop anymore! If I turn fan off it will stop in about 10 minutes. I think cards get hot but the main reason PSU gets overheated supplying cards with less power. Try it it might help

so Coilbook is that now consistently working? I hope it's not just a temperature thing, I run gpu-z and the temperatures are ok, and I really don't want to have to have fans running pointing at my machines, it doesn't look terribly professional in the office! I've sent Abstrax a couple more log files, one from the slave and one from the master, hopefully he can find something in there that points to the problem.

i know, all these fans are loud and it looks bad. but it still works fine. Mine was PSU getting too hot and too weak not actual cards. cards always run around 65-70

We've got a 1500w psu in each of the machines, if these aren't up to the task then I'm not sure who Otoy are making this renderer for? There aren't really any powerful supplies that are more power. It's frustrating that this is called a 'hardware issue' when we've just spent a load of money on top end gpus, psu, etc. and then told that it isn't enough for Octane.

and now all of a sudden getting this problem (see attachment), this has suddenly happened on 3 separate machines, not using network rendering, tried opening a few different scenes, nothing is rendering. This is getting ridiculous.

it seems to be caused by some materials, mostly mix materials. if I change those materials the render starts. This has only happened since 2.04.

further investigation seems to show that it is emission textures. If I tweak the value ever so slightly suddenly the render will start... what is this all about?
and using the material editor crashes the scene a lot.

A few more tests and I'm even more confused. Seems to just be one scene in particular, and this scene has been working ok. I've gone and loaded previous iterations of the same scene that definitely worked, and they're all coming up with this same error. Sometimes I can trick it into rendering by swapping the material, or changing a value, but it doesn't always work, and there's no way I can actually render this scene. And it seems to kind of 'infect' 3Ds Max; once I've tried to render this scene and had the orangey pinkish square, if I open another scene that would otherwise work it will still just show the orangey pink square and refuse to render until I restart Max.

ok so here's the scene, I went through doing a lot of tests, it would seem that the material applied is somehow causing the problem, but I have no idea why? If someone could take a look at think it might highlight an issue with Octane. If you clear the material's emission value it seems to work, but this is an extremely simple scene and I can't see any reason why it doesn't render?

And been getting a lot of bits of text in the log file along the lines of:
error 719 on device 0: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
[11:12:02.414] ERROR : -> could not get memory info
[11:12:02.414] ERROR :

'must be destroyed' lol, but seriously, any ideas?