YEEEEEEEEHAAAAAAWWW!!!!You've found a bug - if you set some emission on a volume with 1 grid, then it should have some proper emission. In this case there is none, even with scattering. This seems to only apply to volumes which have a single grid. I'll get it fixed, thanks for checking it out!
Hi Abstrax,augdalmo wrote:Hi Abstrax,
I have installed some weeks ago the Photoshop plugin OR Compositing. Every few days Creative Cluod warns me of a new version to install, but on the last two days I was solicited many times in a day even if I confirm the installation and it was successfully installed.
Do you have released so much updates on so few days and lately on few hours?
Manu
Unfortunately, I didn't have time to look into the issue further yet. It would be a big help, if you could send me an example scene (preferably exported as .orbx package) that causes these issues on your hardware. I will then try to set up my system to run through a 1x PCIe bus when I have got time.Notiusweb wrote:Marcus, just want to report on subject of PCI 1x / Baking Cam, I was running a render on Daz Studio plugin with a very high 'something' (I think displacement?), as there was a higher than normal hair definition of some sort that makes the render run much slower, and this presented the same freezing at higher resolutions. I could get through at low, but after 720p I was getting crashes. Also, when I ran, as alternate, only with my primary GPU Titan X (16x from motherboard), I was not getting any crashes. It was too similar to the baking cam experience, so I figure I'd bring it up. It may not be 'baking camera' per-say that is an issue, it may be a greater issue involving GPUs at PCI speed 1x with higher resolutions, kind of like the lag thing.
And here is the obligatory note, I am sure you guessed it already...it did not occur when rendered through the Version 2.x of plugin.
Here is image with hair texture that made V3 stop in its tracks with multi GPU at PCI 1x:
Thx
Hi Marcus,Postby abstrax » Thu Feb 04, 2016 7:39 pm
Unfortunately, I didn't have time to look into the issue further yet. It would be a big help, if you could send me an example scene (preferably exported as .orbx package) that causes these issues on your hardware. I will then try to set up my system to run through a 1x PCIe bus when I have got time.
Do you know by any chance a way to control the bus speeds via software?
Is it a bus speed issue? The bus-speed is influenced by many factors. Is it not rather an I/O time-out issue that could be handled by the cuda code on the Octane side...? It seems to be more of a problem in 3 than in previous versions.abstrax wrote:Do you know by any chance a way to control the bus speeds via software?
It shouldn't but who knows... My guess it's more likely a driver problem, but it could be a timing issue in Octane that only occurs in certain configurations.Seekerfinder wrote:Is it a bus speed issue? The bus-speed is influenced by many factors. Is it not rather an I/O time-out issue that could be handled by the cuda code on the Octane side...? It seems to be more of a problem in 3 than in previous versions.abstrax wrote:Do you know by any chance a way to control the bus speeds via software?
Seeker
Meshes are compiled multi-threaded, but there are various factors that may prohibit a good parallelization. Especially on OSX and Linux. We are currently looking into it.BorisGoreta wrote:Compilation of the scene is not very multi threaded. I am seeing 3,7% - 25% CPU usage while compiling where the most of the time is around 3,7 %.
This is in standalone.
In LW plugin it loads the mesh then compiles it, then loads the second mesh, then it compiles the second mesh.
Why wouldn't it load all meshes and assign 1 or 2 cores for compilation of each mesh and then hopefully we would see near 100% CPU usage.
Is compilation of different meshes interdependent ?
I have dual Xeon E5-2687W with 16 physical cores.
