Hi,
I use octane render 2.13 with 2.24.2,
I get the window attached.
Any idea ?
(i'm in the hurry)
Octane slave Daemon stop logging ( help !!!)
Forum rules
Please post only in English in this subforum. For alternate language discussion please go here http://render.otoy.com/forum/viewforum.php?f=18
Please post only in English in this subforum. For alternate language discussion please go here http://render.otoy.com/forum/viewforum.php?f=18
- Attachments
-
YOKO Studio | win 10 64 | i7 5930K GTX 3090 | 3dsmax 2022.3 |
Hi,
Some primary culprits, from what I understand:
- Driver Issue: This is the most likely. Make sure that all machines are updated to the latest drivers (could you possibly be running the latest on your master, but still be on older versions with yours slaves?)
- Overheating: This error has been known to occur in this situation as well. If driver-based issues are eliminated and the problem persists, this would be worth a look. I recommend "MSI Afterburner" for help with this.
- Faulty Card: Probably unlikely, but this is also a common cause. Running some benchmark tests would be worth a shot if the first two issues are not the cause of your problem
How complex are your scenes? Does this happen when handling a simple scene? You are currently using 2.13 - does this issue persist on 2.14 or later (assuming you do not have a specific reason for sticking with 2.14 or course). Cuda 719 errors can be quite vague, so any further information would be appreciated.
Cheers,
Azen
Some primary culprits, from what I understand:
- Driver Issue: This is the most likely. Make sure that all machines are updated to the latest drivers (could you possibly be running the latest on your master, but still be on older versions with yours slaves?)
- Overheating: This error has been known to occur in this situation as well. If driver-based issues are eliminated and the problem persists, this would be worth a look. I recommend "MSI Afterburner" for help with this.
- Faulty Card: Probably unlikely, but this is also a common cause. Running some benchmark tests would be worth a shot if the first two issues are not the cause of your problem
How complex are your scenes? Does this happen when handling a simple scene? You are currently using 2.13 - does this issue persist on 2.14 or later (assuming you do not have a specific reason for sticking with 2.14 or course). Cuda 719 errors can be quite vague, so any further information would be appreciated.
Cheers,
Azen
Hi, thanks for answer,
the scene have 30 different octane proxies (plant) and now the slave seems to render (samp/s is as expected) but I get the linked message in deamon.
Cheers
edit : I have not same nvidia driver on the two computer, I will update and check...
the scene have 30 different octane proxies (plant) and now the slave seems to render (samp/s is as expected) but I get the linked message in deamon.
Cheers
edit : I have not same nvidia driver on the two computer, I will update and check...
- Attachments
-
YOKO Studio | win 10 64 | i7 5930K GTX 3090 | 3dsmax 2022.3 |
OKaayy
Thank you azen : old driver on slave, and older on the other slave...
When I am in hurry, my brain stop working...
Thank you azen : old driver on slave, and older on the other slave...
When I am in hurry, my brain stop working...
YOKO Studio | win 10 64 | i7 5930K GTX 3090 | 3dsmax 2022.3 |
Hi azen,
I have still an issue on a slave (see capture)
It seems that other people have problems ( viewtopic.php?f=101&t=52528&start=10 )
I use 2.25 engine now with 2.19 max version.
A card seems to have a problem to load textures... I read on some cuda forums that we can use driver API functions to explicitly manage and destroy any CUDA contexts.
But I'm definitly not a programmer...
Any idea ?
I have still an issue on a slave (see capture)
It seems that other people have problems ( viewtopic.php?f=101&t=52528&start=10 )
I use 2.25 engine now with 2.19 max version.
A card seems to have a problem to load textures... I read on some cuda forums that we can use driver API functions to explicitly manage and destroy any CUDA contexts.
But I'm definitly not a programmer...
Any idea ?
- Attachments
-
YOKO Studio | win 10 64 | i7 5930K GTX 3090 | 3dsmax 2022.3 |
Hi,
It seems that the issue is in the standalone, rather than the plugin. If you revert to an older standalone, does this issue still occur? Be sure to revert the plugin to an earlier version
If this issue is directly related to the latest standalone version, the query will need to be directed to the "General Support" forum. If this does not occur in the Standalone, but still happens through the plugin, then the troubleshooting will be refocused resolving plugin issues if any.
Cheers,
Azen
It seems that the issue is in the standalone, rather than the plugin. If you revert to an older standalone, does this issue still occur? Be sure to revert the plugin to an earlier version
If this issue is directly related to the latest standalone version, the query will need to be directed to the "General Support" forum. If this does not occur in the Standalone, but still happens through the plugin, then the troubleshooting will be refocused resolving plugin issues if any.
Cheers,
Azen
Hi,
I tested scenes with 3dsmax octane render 2.13 (2.24 engine) and I have same problem.
"device 0: failed to upload data texture 4 of context 0"
and the card seems not working as its temperature don't change during rendering.
even on a simple scene : (2 boxes no texture and a sun)
"device 0: direct lightning failed"
What I think : octane produced an error and now the card is enable to load render. This is why I asked if there is a solution to "reset" context of a card.
It would be a good tool for a renderer which relies on gpu.
I tested scenes with 3dsmax octane render 2.13 (2.24 engine) and I have same problem.
"device 0: failed to upload data texture 4 of context 0"
and the card seems not working as its temperature don't change during rendering.
even on a simple scene : (2 boxes no texture and a sun)
"device 0: direct lightning failed"
What I think : octane produced an error and now the card is enable to load render. This is why I asked if there is a solution to "reset" context of a card.
It would be a good tool for a renderer which relies on gpu.
YOKO Studio | win 10 64 | i7 5930K GTX 3090 | 3dsmax 2022.3 |
bump !
YOKO Studio | win 10 64 | i7 5930K GTX 3090 | 3dsmax 2022.3 |
Apologies for the belated reply.
Any context management is in the standalone. To get a better idea of what could be causing this, would you be open to sending your scene? I could run tests and get a more specific grasp on the issue. I initially thought that there was something about your textures that was overloading the CUDA cores, but that may not necessarily be the case. The issue you had with the relatively barren scene is what makes this perplexing - if the drivers are all in order, I'm inclined to think that you may be having a hardware issue. The only way to confirm would be to run against our in-house hardware to confirm.
Any context management is in the standalone. To get a better idea of what could be causing this, would you be open to sending your scene? I could run tests and get a more specific grasp on the issue. I initially thought that there was something about your textures that was overloading the CUDA cores, but that may not necessarily be the case. The issue you had with the relatively barren scene is what makes this perplexing - if the drivers are all in order, I'm inclined to think that you may be having a hardware issue. The only way to confirm would be to run against our in-house hardware to confirm.