On Linux, the relevant file isgrimm wrote:Thanks Thomas for looking into the issue. Yeah I suspect that most of my problems are caused by the "focus follows mouse" which most windowing systems do not do correctly. I'm stuck with it as I will not drop that option unless it's crowbarred out of my cold dead fingers.
On redocking the render viewport, it's reproducible every time, that is to say that I can't get the redock to survive an application restart. I'm thinking that it's an issue with an older version of the default project file that is conflicting somehow with the new version of Octane? Is there a file I can blow away to reset things back to factory settings?
~/.OctaneRender/default.ocl which has the layout in xml. Before you bomb that one away, can you pass me that file so I can have a look?I wish this too!!!!kevinshane wrote:can we have a auto save render stats option?(for example, 2-3mins will auto save the current render stats to disk)
I wish this too!!!!kevinshane wrote:hi, have u guys consider adding an autosave render state for let's say every 500 samples reached??
Hi Shane,kevinshane wrote:hi admin, I use batchrender script to test deep images output but never success, is it a bug or I done something wrong? I define a frame range and check on Save deep image, but what I've got is the beauty pass only(missing the deep one), however if I manualy hit the save deep button in the viewport, everything works.. also please consider adding autosave render state, it's really important to me and anyone else, I think everyone would be happy if there is an autosave the render result when the hardware goes high temp and cause shotdown, in this case we can resume the last autosave state to continue..
Shane
There are usually two reasons why a slave may be unavailable: It has the incorrect version or it's being used by some other net render master.SVITAdmin wrote:I'm showing all my slaves in the network rendering list, but for some reason, only 1 of the 4 slaves is showing as available now. Restarts don't help. They are all running the same version (3.02_test_win. Not sure of the main file on the front page was been updated with the 3.7 compute model). All seemed to be just fine last week.
What makes the other slaves unavailable? The daemons seem to be functioning properly on the slave end.
Thanks
We will change the default from %f to %F in the next release.
