Page 2 of 3

Re: V3 and the mixed bag-of-bugs

Posted: Sat Jun 25, 2016 4:43 pm
by preciousillusion
aoktar wrote:
preciousillusion wrote:Then why are you charging full price for the plugin?
Are you joking? Plugin has lot of free add-ons which should be paid or individual plugins. As scatter/volume generator/node editor. And many video tutorials by inlifethrill. I don't spare it as V2/V3/etc.. and i'm trying to improve as much as possible. I see that's the fee of this continual improvements.
1. If the product doesn't even come with complete documentation, then I think it's a perfectly valid question.

2. "lots of free add-ons.." Oh, is that how it works? I have to try it on a client!
"Yea, the animation is missing a few frames, but I sent you a free picture of a really cute kitten! So we're cool, right?
Can't wait to see how that goes down..

3. What company does not provide free tutorials for their software? Also, see number 2.

4. If, as you say, certain parts of the plugin is considered "free add-ons" then why, like in "why dear god, why?" isn't the core of the plugin finished before any add-on?

5. Is it also the official position of Otoy that certain features of the plugin are "free add-ons which should be paid or individual plugins", and If so, can we get a clear statement which those features are?

Re: V3 and the mixed bag-of-bugs

Posted: Mon Jun 27, 2016 9:24 am
by bepeg4d
Hi preciousillusion,
please, could you try to follow the procedure described in this posts in order to get a log file from you?
viewtopic.php?p=234275#p234275
viewtopic.php?f=87&t=48125&start=20#p240111
viewtopic.php?f=23&t=54614#p278362
ciao beppe

Re: V3 and the mixed bag-of-bugs

Posted: Fri Jul 01, 2016 1:02 pm
by preciousillusion
bepeg4d wrote:Hi preciousillusion,
please, could you try to follow the procedure described in this posts in order to get a log file from you?
viewtopic.php?p=234275#p234275
viewtopic.php?f=87&t=48125&start=20#p240111
viewtopic.php?f=23&t=54614#p278362
ciao beppe
Here's some logs from both master and slaves

Re: V3 and the mixed bag-of-bugs

Posted: Sun Jul 03, 2016 1:43 pm
by preciousillusion
And there's more..

Here the slave somehow believes there's a master at 192.168.1.41
That address belongs to a disabled nic, and even if I change that ip and disables the nic again the slave still thinks there's a
master there.

Why doesn't the slave verify that there's actually something responding at the address it got from god knows where?

How does Octane handle multiple NiCs?

Re: V3 and the mixed bag-of-bugs

Posted: Sun Jul 03, 2016 10:02 pm
by Yan
I also get more crashes with V3.0.
I have even downgraded to V 2 to render a client project In time with no errors.
For me it seems that I am running out of VRAM but this only happens on V3. If I open the same scene in V2 it works great. I have 6GB of VRAM and the scenes are quite simple. Still testing what's happening.

A better help/tutorials for V3 new features are a must especially for options like "use for tonemapping" etc.

Log looks like this:
> failed to deallocate device memory
CUDA error 700 on device 1: Kernel tried to load or store to an invalid memory address. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> could not get memory info
CUDA error 700 on device 1: Kernel tried to load or store to an invalid memory address. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> failed to unload module

Re: V3 and the mixed bag-of-bugs

Posted: Sun Jul 03, 2016 10:14 pm
by aoktar
Yan wrote:I also get more crashes with V3.0.
I have even downgraded to V 2 to render a client project In time with no errors.
For me it seems that I am running out of VRAM but this only happens on V3. If I open the same scene in V2 it works great. I have 6GB of VRAM and the scenes are quite simple. Still testing what's happening.

A better help/tutorials for V3 new features are a must especially for options like "use for tonemapping" etc.

Log looks like this:
> failed to deallocate device memory
CUDA error 700 on device 1: Kernel tried to load or store to an invalid memory address. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> could not get memory info
CUDA error 700 on device 1: Kernel tried to load or store to an invalid memory address. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> failed to unload module
If you have render failures so make an orbx export and post in Standalone forum. Having render failures due low VRAM doesn't mean a crash.
Or if you have C4D/plugin crashes post in related topic or bug reports section with required steps and full details as we wished. In other cases i'll not count these as bug reports.

Re: V3 and the mixed bag-of-bugs

Posted: Mon Jul 04, 2016 4:09 am
by Terryvfx
I also have been getting crashes with the drap a drop functionality too, everything I drop a group of textures straight to the node editor C4D will froze up I notice that the crash doesn't happen if I drag only one image first then the rest.

Re: V3 and the mixed bag-of-bugs

Posted: Tue Jul 05, 2016 4:37 pm
by preciousillusion
Still no answers..

Especially this one is of great concearn.
5. Is it also the official position of Otoy that certain features of the plugin are "free add-ons which should be paid or individual plugins", and If so, can we get a clear statement which those features are?

Re: V3 and the mixed bag-of-bugs

Posted: Tue Jul 05, 2016 8:04 pm
by mojave
Hi preciousillusion,

Sorry for the delay on answering. I started investigating your issue but still could not find out what the problem is. I'll get in touch via PM in case I need more information and keep you posted.

Best,

Re: V3 and the mixed bag-of-bugs

Posted: Fri Jul 08, 2016 3:40 pm
by preciousillusion
And v3 has been out for almost 2 months, still waiting for the documentation..

Also "Save C4D scene with assets" is broken, if any textures used in an Octane material in your scene resides in a a path that's added to C4Ds preferences/files section they don't get copied, except when loaded in an environment tag.