OTOY Forums

UPD: Seems that issue is gone when I use my SSD drive instead of Hard Drive for TFD cache.
UPD 2: Issue is back, can't find any workarounds. Constant freezes, display driver errors.

I've got an issue. When I use low "Volume step length" settings, like 0.05-0.3, and try to render TFD simulations (14-18 Gb size) the render stops at some point in Picture viewer (with Display driver error popping from Windows) . Seems that when I set "Volume step length" to a higher value, it will stop a little bit later in animation (when there is more smoke to render). Seem to have some connection between "Volume step length" and simulation size to load on rendered frame. Tried to switch on and off different settings, updated display driver to latest version, nothing helped. It renders all samples only in "Live viewer" . The Issue is on both R15 and R16.

My system:
Windows 10 64-bit
32 gb ram
2x780ti, no OC
i7 4930k
Cinema 4D r16, r15
Octane Alpha 3.1(15.01.2016)

Some settings:




Windows Error message:

Hi,

I thought, that the triangle-limit is gone in V3.
regards
Mike

@Nullifier:
I think you don't mind what happens to render speeds on smaller Step Lenghts. It makes smaller volume steps for dividing volumes and causes higher calculations. After some value your driver and Octane becomes unresponsive due high calculation. There is a TDR topic how to increase this unresponsiveness times.

miohn wrote:Hi,

I thought, that the triangle-limit is gone in V3.

polylimit.JPG

regards
Mike

Gone i suppose. But i haven't updated plugin for this warning. But there is a Render Failure anyway.

Hey Ahmet, BEAUTIFUL release. Very very little crashing.

2 Things: 1. The info for scenes seems wonky. I hit render and the time starts at 30 minutes and there are 200 hours left, but the render only takes 3 minutes haha! Not that big of a deal.

2. My materials(not in render) show up glitchy if they have glossiness to them in the material manager and object manager.

http://imgur.com/MLXOgct

http://imgur.com/5NRn5XD

http://imgur.com/g3QnVol

jeffbriant wrote:Hey Ahmet, BEAUTIFUL release. Very very little crashing.

2 Things: 1. The info for scenes seems wonky. I hit render and the time starts at 30 minutes and there are 200 hours left, but the render only takes 3 minutes haha! Not that big of a deal.

2. My materials(not in render) show up glitchy if they have glossiness to them in the material manager and object manager.

http://imgur.com/MLXOgct

http://imgur.com/5NRn5XD

http://imgur.com/g3QnVol

1- Very well. I know that and fixed.
2- Don't know it why happens.

aoktar wrote:@Nullifier:
I think you don't mind what happens to render speeds on smaller Step Lenghts. It makes smaller volume steps for dividing volumes and causes higher calculations. After some value your driver and Octane becomes unresponsive due high calculation. There is a TDR topic how to increase this unresponsiveness times.

Thanks for reply, aoktar. I did all that posts were suggesting (change TDR value, update/downgrade drivers, with reboots as well), but unfortunately nothing helped, can't find any solution.
Octane log always returns "CUDA error 719" with heavy scenes. Just want to know if this is something fixable in future releases, or am I the only one having these issue?

Octane log file attached for more details.

not working camera visibility, when considered turbulencefd. I want to receive only the light from the fire, not the fire itself!

bepeg4d wrote:Hi,
PyroCluster is a CPU shader that has nothing to do with Octane and it's damned slow. You can obtain a much better result and in a fraction of time with the internal octane medium node... as an example, have you seen the medium node in action with TurbulenceFD inside C4D-Octane made by aoktar?
ciao beppe

Thanks for the answer
I have seen this. But because I dont own TurbulenceFD, I ask at pyrocluster.

JackMcRip wrote: Thanks for the answer
I have seen this. But because I dont own TurbulenceFD, I ask at pyrocluster.

Have you checked volume object?