Octane slave Daemon stop logging ( help !!!)

[HHbomb]

Hi Azen,
To make simple ( someone make this for me ), I open my computer, one card was not enlighten, so it was the card which had a problem.
I tested each card, and all were ok.
I unpluged and plugg all the cards, then all is fine now. No more cuda error, and all cards are working fine.
So as I told you, I think Octane made a cuda error through deamond when I had not same octane version and not same driver version.
It is just what I think. If it is true, it would be cool from Otoy to give us a tool to manage GPU errors.

[azen]

It could be a feature request worth looking into. It would be worth raising this in the standalone forum. I can't give too firm an assurance, as this request getting picked up will depend on our existing, as well as the extent of demand from the user community for this request.

To engage both the Octane team as a whole, as well as the user community at large, it could be worth raising this request on the main forum. Hopefully this will prove fruitful. It could also be a great way of collecting viable non-technical suggestion/solutions to handling CUDA context management

[craterdust]

My daemon kept quitting when my other computer would go to sleep, so I made it stay awake... Not saying this is your issue, but it happened to me.