Version 2.12.2 - final (updated on 18.11.14)

[miohn]

Hi momade,

thanks for your explanations!
Anyway I'm not sure if I understand right.

First, if both cards are exactly the same model with same driver:
how can I find out, which card is which?
Is the first card in settings the card in the first pci-slot?

Second.
So assumed if the first card is the card where the monitor is plugged in (so also for OS),
Priority "Low" means that Octane uses this card less?

So I would think, that if I want to use the second card only for Octane,
I should set the priority for this 2. card to "maximum", not?

thanks
MIke

[aoktar]

LOW = low gpu usage. Why so hard to understand? Just change settings and compare gpu usage on LV.
How to find monitor gpu? Check only one and check free vram on LV. Which shows less free vram, that's the System's gpu.
Also if you use system gpu, you will see more lags. That's the second clue

[miohn]

sorry, I'm really too stupid to understand!

When the first titan is the one with the monitor plugged in:

This is, how I understand and would set this up, because I want
Octane to use full power of the second card.

Wouln't it be easier to understand, if each card has the option for
priority "low", "medium" or "high"?

Then I would check for the fist card --- "low"
and for the second card I would set it to -- "high"

sorry for this confusion!
Mike

[rodross]

Miohn, basically, if you uncheck "use Pri." on your card NOT running your OS and monitors, it will run at full, maximum speed in Octane. Check the "use Pri." for your other card and set the priority dropdown to low or medium so you can use other programs. If you have it setup that way and your OS is lagging horribly, then you need to reverse the settings in Octane and uncheck "Use Pri." for the other card and check it for the one that was running maximum. You're probably right, it may be useful to have priorities separated for both, but people who run multiple GPUs tend to not use priority for the secondary so that it is always running at maximum.

[aoktar]

Wouln't it be easier to understand, if each card has the option for
priority "low", "medium" or "high"?

you are asking about the things, which are not related with plugins. Not related with me.
All is same on standalone. That's the way how works on Octane.

Priority is common. When you activate priority, it uses what you selected on priority.
There maybe a confusing for gpu orders on some systems, i can't do anything. Displayed gpu order is different from gpu setting order.
This confusion is related with a Cuda sdk problem. But Gpu order is correct on devices section.

[miohn]

o.k. getting it clearer now!

Didn't know that this is SDK or standalone-thing and cannot be
influenced by plugin.


regards
MIke

[aoktar]

o.k. getting it clearer now!

Didn't know that this is SDK or standalone-thing and cannot be
influenced by plugin.


regards
MIke

if you see a feature which never changes since lot of version, bu sure it's not a plugin related.

[Iceman9]

I don't know if these are new/unique since I've not used Octane a lot. But I know displacement used to work and now it doesn't at all.

My guess is that these bugs are unique to R16. I am using Mac/Yosemite 10.10 OS/R16.027 Studio/Octane 2.12.2

Here are two brief videos which demonstrate significant bugs with the latest revision.

http://icecavetechnology.com/BugReportV ... entBug.mov
http://icecavetechnology.com/BugReportV ... werBug.mov

Thanks for all you ongoing hard work!
Cheers

[aoktar]

I don't know if these are new/unique since I've not used Octane a lot. But I know displacement used to work and now it doesn't at all.

My guess is that these bugs are unique to R16. I am using Mac/Yosemite 10.10 OS/R16.027 Studio/Octane 2.12.2

Here are two brief videos which demonstrate significant bugs with the latest revision.

http://icecavetechnology.com/BugReportV ... entBug.mov
http://icecavetechnology.com/BugReportV ... werBug.mov

Thanks for all you ongoing hard work!
Cheers

Thanks for report. But, neither is a bug. For displacement refer the attached image and help window.

if we talk about double geometry, when you send the tagless objects will be exported as a collected mesh. When you add a objecttag to a object, this object will be exported a single mesh under the different geo. group. But old data will be there. This is your scenerio. So you should resend this scene to generated clean export data. But if you add a object and put a objecttag, this will not generate double geometry. Because it would not be sended before.

Ok, why we don't send all data? Because sending is a slow process. Expecially for high poly counts. So we don't do it automatically. I hope this is clear for you.

EDIT: Forget to mention. Check second image to see a method. There is a "create objecttag" menu item. Which creates tag and resend the scene again. Worth to know.

[Yan]

I have installed 2.12.2 and I had some problems. I'll try to explain as short as I can.
I am using windows 8.1, C4d R16, latest nvidia driver, two 780 gtx, i7 Haswell, 16gb RAM.

The first problem:
When I start the live viewer, my computer freezes most of the time in a few seconds if I use both cards on high priority. I have to restart the system.

The second one:
When I render a range of frames in the picture viewer, the rendering stops after a number of frames (usually 2-3), the computer freezes, but c4d will save the remaining frames not rendered. Also using both cards on high priority.
Here is the log appearing before computer freezes:
---- FRAME 157 DOC:0x00000099ACCA1700 first:1 fullUpd:0 updMthd:0 nodes:38 links:0 ----
Tried to access null item
Tried to access null item
Tried to access null item
Tried to access null item
Tried to access null item
Tried to access null item
Tried to access null item
Tried to access null item
Tried to access null item
Tried to access null item
--------------------------- EXPORT LOG ---------------------------
Export materials time= 88.892 ms
Collect objects time= 0.085 ms
Meshes creation time = 44.073 ms
Octane voxelization time = 0 ms
Sending to Octane engine time = 0 ms
Total export Time = 935.879 ms
Can't Read Preset File: C:\Program Files\MAXON\CINEMA 4D R16\plugins\c4doctanepresets.dat
Can't Read Preset File: C:\Program Files\MAXON\CINEMA 4D R16\plugins\c4doctanepresets.dat

The third one:
I wanted to write about this one from the earlier version.
If I move the frame several times in live viewer or use the render region, sometimes c4d stops working and a notification with display driver stopped working and has recovered.
After this error it seems that one video card is no loger working so I have to restart.
This one is happening also in standalone.

I don't think this is a hardware issue because I have installed a few hours ago v2.06.1 (both standalone and plugin) and everything seem to work fine until now.

I hope you have time to read this. Thanks!