Version 3.00 - Alpha10.1 (30.04.2016)

Sub forum for plugin releases

Moderators: ChrisHekman, aoktar

Nullifier
Licensed Customer
Posts: 10
Joined: Wed Dec 24, 2014 4:06 pm

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:
Image
Image
Image

Windows Error message:
Image
miohn
Licensed Customer
Posts: 749
Joined: Sun Jun 06, 2010 3:00 pm

Hi,

I thought, that the triangle-limit is gone in V3.
polylimit.JPG
regards
Mike
User avatar
aoktar
Octane Plugin Developer
Posts: 16063
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye
Contact:

@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.
Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
User avatar
aoktar
Octane Plugin Developer
Posts: 16063
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye
Contact:

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.
Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
jeffbriant
Licensed Customer
Posts: 43
Joined: Thu Dec 25, 2014 4:21 pm
Location: Toronto, Canada
Contact:

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
2x1080's network rendering to 4x980Ti's
User avatar
aoktar
Octane Plugin Developer
Posts: 16063
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye
Contact:

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.
Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Nullifier
Licensed Customer
Posts: 10
Joined: Wed Dec 24, 2014 4:06 pm

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.
Attachments
octane 3.00 alpha 3 160121 214229.log
(1.99 KiB) Downloaded 199 times
borzoff
Licensed Customer
Posts: 16
Joined: Sun May 24, 2015 12:41 am

not working camera visibility, when considered turbulencefd. I want to receive only the light from the fire, not the fire itself!
JackMcRip
Licensed Customer
Posts: 96
Joined: Thu Jun 03, 2010 1:33 pm
Contact:

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.
C4D + ZBrush User
Use AMD Phenom 9850, GeForce 8600 256MB, 8GB
User avatar
aoktar
Octane Plugin Developer
Posts: 16063
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye
Contact:

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?
Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Post Reply

Return to “Releases”