OTOY Forums

Mhm, then the Maxon Updater is playing games with me. Thank you. I am on it.

Works now!

bepeg4d wrote:Hi Turk,
latest R21 is R21.115.

@shine71:
please, remove the installed version, and download and install again v2019.1.5-R2.
Here it is working as expected with Image Tiles node.
ciao Beppe

Running few tests....

It's not crashing but freezing....

shine71 wrote:

bepeg4d wrote:Hi Turk,
latest R21 is R21.115.

@shine71:
please, remove the installed version, and download and install again v2019.1.5-R2.
Here it is working as expected with Image Tiles node.
ciao Beppe

Running few tests....

It's not crashing but freezing....

Provide us the scene again please. Also activate all log outputs and repeat freeze, then send c4doctanelog.txt from its location.

Ahmet, Beppe, thanks a lot for your help and support!
I was running some test and I noticed one thing, I hope can be helpful for future fixes.
Everything seems to work fine am starting from scratch (I ran tests on R21), but if for somehow reason there is one cinema 4D material in material editor (not applied to scenes items) C4D crashes or freezes...
In my scene there was a c4d native material with just a diffuse color, nothing complex and as mentioned not assigned.
Once I deleted it I didn’t meet any further crashes.
Is it normal? Anyway, I’m really happy that I found way to work with this shader...
Thanks again mates!

Cheers

shine71 wrote:Ahmet, Beppe, thanks a lot for your help and support!
I was running some test and I noticed one thing, I hope can be helpful for future fixes.
Everything seems to work fine am starting from scratch (I ran tests on R21), but if for somehow reason there is one cinema 4D material in material editor (not applied to scenes items) C4D crashes or freezes...
In my scene there was a c4d native material with just a diffuse color, nothing complex and as mentioned not assigned.
Once I deleted it I didn’t meet any further crashes.
Is it normal? Anyway, I’m really happy that I found way to work with this shader...
Thanks again mates!

Cheers

Don't know, baking/sampling the c4d shaders are always a problem in plugin. So I'll bring osl emulation for possible nodes, like tiles/gradient. Then we'll be happier.

@aoktar

Did you fix the problem with the "lost" or "error" texture? I is a huge problem....!

THX

rclassenphoto wrote:@aoktar

Did you fix the problem with the "lost" or "error" texture? I is a huge problem....!

THX

I don't see this problem, did you read my post? And giving a better data to understand what's the real issue?

Hello Ahmet
I have had also a strange issue with 2019.1.5 R2. I crontol clicked a more or less complex material to double it for doing some changes... Than an error message pop up that some octane resources could not be read in row 52, clicking ok three four times with error messages in different rows ... than crash. After restart this c4d file was useless, I was unable to open a material or render or anything else. Crashing all times ... Open a new scene no problem ... Hours before I rendered a 100 times this scene without any problem. Going back to 2019.1.5 solved this issue so far...

Kind regards Martin

martinzip wrote:Hello Ahmet
I have had also a strange issue with 2019.1.5 R2. I crontol clicked a more or less complex material to double it for doing some changes... Than an error message pop up that some octane resources could not be read in row 52, clicking ok three four times with error messages in different rows ... than crash. After restart this c4d file was useless, I was unable to open a material or render or anything else. Crashing all times ... Open a new scene no problem ... Hours before I rendered a 100 times this scene without any problem. Going back to 2019.1.5 solved this issue so far...

Kind regards Martin

Some screenshot would be great. Did you redowload this version? There was a problem with resources and refreshed the build.