V3 and the mixed bag-of-bugs

Tue May 31, 2016 3:42 pm

I’m sorry to say, but version 3 does not feel like a thoroughly tested release that went through proper QA. It feels like a beta, mainly for the following reasons:

It Crashes

Crashing/freezing a couple of times a day in a seemingly random fashion. It can happen when I open Live DB, change voxel size, changing a texture etc.

Network rendering

It mostly works in Live View, but as soon as I render to picture viewer, almost every time at least one slave crashes immediately.

Drag & drop textures in the node editor does not work.

Manual/Help

When clicking “Octane help” it fires up help for version 2.24

When opening the pdf help a lot is missing. To name a few:

Post
“Spectral_intensity”
Spectral_shift”

Devices
“Use for tonemap”

Other
“LV refresh time(ms)”
“Performance timer”
“Overlay power”
“Use viewport solo”
“Synchronize on geo. Updates”
“Experimental”

Env
The whole tab is missing..

Nodes
The whole tab is missing..

Tue May 31, 2016 3:49 pm

Hi,
What kind of crash are you talking? Version, os? What's content of your scenes? Any better information about to reproduce a crash?

-You may have c4d type materials/textures.
-You may have some old scenes which can cause problems.
-You may force voxels too much to cause render failures.
-Render failure is not upto me. It's about renderer.
-Drag/drop works on NE.

I can't agree with that about being at beta. At least on plugin side. It has same core as 2.25-R4. Also more features. We made a open beta period at very long period and didn't get much issue feedbacks.

Tue May 31, 2016 9:41 pm

preciousillusion wrote: Crashing/freezing a couple of times a day in a seemingly random fashion. It can happen when I open Live DB, change voxel size, changing a texture etc.

If this happens again could you please check your log window and other things such as device memory usage to include them in a bug report?

preciousillusion wrote: Drag & drop textures in the node editor does not work.

This has already been reported to not to work when a window is undocked and it is currently being investigated.

Wed Jun 01, 2016 9:16 pm

aoktar wrote: What kind of crash are you talking? Version, os? What's content of your scenes? Any better information about to reproduce a crash?

Most of the times C4D stops responding and have to be killed via task manager. There doesn't seem to be a way to reproduce any crash since they happen somewhat random, but maybe 75% occurs when working with materials (not node editor)
I have no problem with any other gpu-intense workload.

Windows 8.1 - All updates
C4D R17.048
Nvidia 368.22 driver

"-You may have c4d type materials/textures."
Nope
"-You may have some old scenes which can cause problems."
Nope
"-You may force voxels too much to cause render failures."
When that crash occured I made them one step larger than default
"-Render failure is not upto me. It's about renderer."
But it specifically happens only when rendering to picture viewer with octane
"-Drag/drop works on NE"
Not for me

mojave wrote: If this happens again could you please check your log window and other things such as device memory usage to include them in a bug report?

Does the log get stored in a text file somewhere?

Wed Jun 22, 2016 12:46 pm

And then there were silence from Otoy... For 3 weeks

Well here's a picture of some of the slave-issues.
Most of the times when rendering to picture viewer (attached image) one of the following occurs
(1) one of the slaves unchecks itself
(2) one of the slaves crash

On the issue regarding the manual I noticed it now says v3, but still far from complete. In addition to missing information stated earlier, there's also missing information on most Octane shaders.

Wed Jun 22, 2016 10:13 pm

preciousillusion wrote:And then there were silence from Otoy... For 3 weeks

Well here's a picture of some of the slave-issues.
Most of the times when rendering to picture viewer (attached image) one of the following occurs
(1) one of the slaves unchecks itself
(2) one of the slaves crash

On the issue regarding the manual I noticed it now says v3, but still far from complete. In addition to missing information stated earlier, there's also missing information on most Octane shaders.

So the crash you are experiencing happens usually when editing materials and using network rendering?

Have you experienced it without network render enabled?

Please note that we need a detailed description of your environment and the steps to be able to reproduce this issue in order to help you.

Regarding to the documentation, it is still work in progress but close to being completed.

Thu Jun 23, 2016 1:45 am

Some crashes are completely random. Regarding the crashing slaves, I've stated quite clearly when they occur. Stop live view, start "render to picture viewer", that's when slaves crash. Or uncheck themselves.

Regarding to the documentation, it is still work in progress but close to being complete.

Then why are you charging full price for the plugin?

Thu Jun 23, 2016 2:08 am

There were a couple of issues solved related to network rendering since you first posted your issue. Can you still reproduce it with the latest C4D release?

viewtopic.php?f=85&t=54672

Thu Jun 23, 2016 9:28 am

mojave wrote:There were a couple of issues solved related to network rendering since you first posted your issue. Can you still reproduce it with the latest C4D release?

viewtopic.php?f=85&t=54672

Yes

Thu Jun 23, 2016 10:59 am

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.