Cinema4D version 2020.1.4 (Obsolete stable) 23.07.2020

[jayroth2020]

Hello thodosplay, can you send a test scene into help at otoy dot com so that we can take a look?

[thodosplay998]

Hello thodosplay, can you send a test scene into help at otoy dot com so that we can take a look?

It's in the mail.

[thanulee]

Hello,

I have no scene to attach it happens in ALL scenes, all projects so far: slaves randomly disconnect during rendering.
Is there some specific ip settings that I should do? Some network settings in windows?

If this is not octane's issue, please guide me step by step on how to setup the windows/networks locally.

This situation makes my work really hard cause i expect a render to finish in 3 hours and ends up doing 6.

[thanulee]

Also a lot of crashes with image sequences on materials. I dont know if they need to be only squre or something. Again no scene, it happens in all projects.
U really need to hire someone to help Ahmet, so that person can test everything before label something as stable and let Ahmet continue the development. In paper all is ok but in actual projects and not even heavy ones, I got lots of issues both 2019 and 2020.

Honest feedback cheers

[jayroth2020]

Hi Thanulee, I would respectfully ask that you send in any scene which causes the issue for you to -- help at otoy dot com -- as we cannot seem to reproduce your issue. We will take a look as soon as it comes in.

[jayroth2020]

Regarding the issue that thodosplay was having with shifting Material ID colors, whenever a new object is introduced into an animation in midstream, Cinema changes the Material ID indexes, causing the color shift (as Octane gets that information directly from Cinema). When exporting this file to standalone, the issue would be resolved by the baking process that occurs when saving to standalone from Cinema. In thodosplay's file, an object was animated from 0.0 to a target size, with said animation beginning right at the frame where the colors shifted. It was then a straightforward process to find that object and make adjustments to prevent the condition from occurring -- in this case, the initial scale key frame was set to be just a little larger than 0.0. This allowed the object to be present throughout the animation, though not visible until desired, thus never triggering the issue in the first place.

Those experiencing similar issues will hopefully benefit from this information.

[thanulee]

Hi Thanulee, I would respectfully ask that you send in any scene which causes the issue for you to -- help at otoy dot com -- as we cannot seem to reproduce your issue. We will take a look as soon as it comes in.

Hey mate, Its time consuming, lots of gb and as I understand a lot of users have similar issues with network. Idk how the team is not able to reproduce this, it practically happens at almost anything. To heavy scenes, to small scenes. Its random there is no pattern.

So in my case, besides render disruptions:
- 1080p render, use 2 slaves and max tile at 64
- Try resend the same scene to PV few times. Randomly 1/2 slaves do not connect. Without warning errors or anything.
- Same happens during rendering. Render may freeze at one frame no reason, other times a slave can just drop with no errors, other time with errors.

As i ve been using network non stop for 3 years, this situation here is first timer. I guess if someone does more experiments with production scenes, will reproduce all of the above.

More people needed to test those stuff.
Respectfully i been in close contact with OTOY dev team through the years and I am aware of the fact that not enough beta testers exist from ur side. Users are not the ones that should do this though.

Also i repeatedly asked for a guide in windows installation settings for network rendering: how to setup ips/firewalls etc. Maybe the error is on users sides, but if no official instructions about this, I have to throw the ball back at your team.

With no disrespect, my time is really valuable and is not my job to debug every scene.
Thanks.

ps. the fact that even texture displacement issue been missed in ur RC phase, means that nobody actually tests anything. How can someone miss a core feature like the above?
Dont label a version Stable and throw it out and wait for us.
This happens from v2019, I have lots of network issues for months now. Ever since I left v4, things are not going right and its not only me as I read.

[FullHPetroL]

Hi Aoktar!
Could you please check what could be done with the geometry area in the "particle rendering" section of the object tag - it doesn't expand. I have a hard time navigating all the geometry from this tiny window

[FullHPetroL]

Another strange behaviour with X-particles

It is impossible to enable particle or geometry rendernig on the generator (x-particles), but is you enable this option on the object and then drag to the generator - it works.

[jayroth2020]

Hi Thanulee, can you please open a ticket -- help at otoy dot com -- so we can get to you going as quickly as possible?

Thank you!