Hello,
What happens when it reaches the limit of 64 textures. It is the latter that is invisible?
Thank you.
Niuq
Maximum textures in Octane
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
In RC1 all textures that go over this limit render black. The GPU status will turn yellow and you can check which texture type has reached the limit by hovering over it the GPU status.niuq.cam wrote:Hello,
What happens when it reaches the limit of 64 textures. It is the latter that is invisible?
Thank you.
Niuq
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Thank you Marcus,
Have you seen my cubes scene file ? The same problem of slowness with the new RC1 compared to the beta3.03
http://render.otoy.com/forum/viewtopic. ... 9&start=70
There is a latency problem when moving nodes. This problem can be solved?
Thank you.
Niuq
Have you seen my cubes scene file ? The same problem of slowness with the new RC1 compared to the beta3.03
http://render.otoy.com/forum/viewtopic. ... 9&start=70
There is a latency problem when moving nodes. This problem can be solved?
Thank you.
Niuq
Roeland has fixed the slow down for the cubes scene. It will be available with the next release.niuq.cam wrote:Thank you Marcus,
Have you seen my cubes scene file ? The same problem of slowness with the new RC1 compared to the beta3.03
http://render.otoy.com/forum/viewtopic. ... 9&start=70
There is a latency problem when moving nodes. This problem can be solved?
Thank you.
Niuq
What do you mean with "latency problem"? Do you mean moving nodes in the node graph editor lags? That's probably because you are using the display card for rendering and there is nothing we can do without a further drop in performance. The only way you can solve it is by rendering smaller images while you make changes in your scene or by having a dedicated graphics card for display only.
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Hello Marcus,abstrax wrote:Roeland has fixed the slow down for the cubes scene. It will be available with the next release.niuq.cam wrote:Thank you Marcus,
Have you seen my cubes scene file ? The same problem of slowness with the new RC1 compared to the beta3.03
http://render.otoy.com/forum/viewtopic. ... 9&start=70
There is a latency problem when moving nodes. This problem can be solved?
Thank you.
Niuq
What do you mean with "latency problem"? Do you mean moving nodes in the node graph editor lags? That's probably because you are using the display card for rendering and there is nothing we can do without a further drop in performance. The only way you can solve it is by rendering smaller images while you make changes in your scene or by having a dedicated graphics card for display only.
Cheers,
Marcus
Thx for the Roeland's solution about the GTX580.
Exactly, there is 3 seconds lag when moving nodes and i have a dedicated card for display. A 8800 gt 512Mo.
Perhaps for the 200 nodes i have in this window...
I think someone has the same problem, I can not find the message.
His avatar has a tattoo on the back of the head I think.
EDIT :
When i move nodes in a macro material, everything result ok.
So it seems to be the big amount of nodes.
Tank you.
Niuq