Version 2.24.2-TEST6 - Test only

[FxDesign]

Hello Aoktar
It seems that C4d (r17) crashes when there are c4d materials with normalizer shader or a simple normal map inside.

I can't see any crashes like you say. Can you give me sample scene with textures which can reproduce crashes?

Sorry Aoktar, it seems that it's was a mistake in my scene. problem solved

[milanm]

I'm going to make this as stable. I think that's very stable for common usages else of brand new addons.

With every new test, this version seems to be less stable.
All old problems with node editor and time limit are still there in TEST6 unfortunately.

While finishing a project with 5.2 I went through a lot of problems like freezing and crashing with R17.
I had to keep another separate C4D install with stable version of plugin to be able to finish everything.

Most common problems are 'Octane generating materials' taking forever and C4D freeze/plugin crash when switching takes.
Scatter sometimes doesn't send objects in the first frame of animation and sometimes reports 'Render Failure' even with enough free VRAM.
I had a lot more problems but i need to check my scenes in standalone first.

Regards
Milan

[aoktar]

I'm going to make this as stable. I think that's very stable for common usages else of brand new addons.

With every new test, this version seems to be less stable.
All old problems with node editor and time limit are still there in TEST6 unfortunately.

While finishing a project with 5.2 I went through a lot of problems like freezing and crashing with R17.
I had to keep another separate C4D install with stable version of plugin to be able to finish everything.

Most common problems are 'Octane generating materials' taking forever and C4D freeze/plugin crash when switching takes.
Scatter sometimes doesn't send objects in the first frame of animation and sometimes reports 'Render Failure' even with enough free VRAM.
I had a lot more problems but i need to check my scenes in standalone first.

Regards
Milan

Interesting. Do you have any scenes to presentate what you mean? I cannot see any bug reports from you! Do you have?
Also "Render Failure errors" are not directly related with plugin. Occurs due a some limitations or crashes on the Renderer. Are you checking message details?

Anyone else has similar complaints? I'm using my plugin to make 3d jobs also and i don't see any critical problems. Maybe related to your plugin/hardware setups also.

[milanm]

Interesting. Do you have any scenes to presentate what you mean? I cannot see any bug reports from you! Do you have?

How can I send you a bugreport if a scene is causing C4D to freeze when opened and not crash? If I remove the plugin C4D doesn't freeze. I can't send you the scenes because of NDA.
Octane plugin did crash with one scene a few times so I will try to get a bugreport for you like i did before for node editor. I will do my best to find what is causing it and make simplified scenes if possible.

Also "Render Failure errors" are not directly related with plugin. Occurs due a some limitations or crashes on the Renderer. Are you checking message details?

Didn't check the details for that same reason and I also assumed it was related to scatter whitch is still WIP. It never happened with the latest stable version.

Anyone else has similar complaints? I'm using my plugin to make 3d jobs also and i don't see any critical problems. Maybe related to your plugin/hardware setups also.

You use Octane on Windows, right? I'm using OSX. Others have confirmed problems with node editor on OSX several times, time limit option too.
With my same hardware/software setup I didn't have any problems like this with current stable version.

Regards
Milan

[momade]

Hello Aoktar.

Happy new year man! All the best for you!

I was wondering if there is any roadmap for future V2 releases. I see C4D2.24 is still TEST and I remember, that 2.25 was announced with ORC somewhere.
Can you say how long you are going to develop V2 before ending and moving 100% to V3. Which production-ready versions can we expect in the last cycles.

br.
mo

[aoktar]

Hello Aoktar.

Happy new year man! All the best for you!

I was wondering if there is any roadmap for future V2 releases. I see C4D2.24 is still TEST and I remember, that 2.25 was announced with ORC somewhere.
Can you say how long you are going to develop V2 before ending and moving 100% to V3. Which production-ready versions can we expect in the last cycles.

br.
mo

Thanks. You too also.

For you question:
It's named as test because i wished to hear feedbacks and apply all new implementations. You can remember these from changes list. Actually 2.24.2 and 3.0 alpha is based on same plugin codes. So i was working for 3.0 also. I could kept both in same code bases until now. But i can have to stop the development of 2.24.2 and to make it STABLE. At the moment user's feedbacks are much important about stability. If you ask for my conclusion, It's product ready for me. I hope this is clear answer for you.

I don't know the ORC that will be a part of 2.x. But it's mostly ready to be activated.

[prehabitat]

Hello Aoktar,
How many of the WIP implementations from your first post will remain as part of the final stable release of Version 2.X?

What do you mean exactly? Are we talking to make a new stable release? I'm going to make this as stable. I think that's very stable for common usages else of brand new addons.

Thanks Aoktar,

That answers my question

Just got my C4D 2.x licence! yew!

[milanm]

Hi

As requested, here is the feedback on some of the problems i had with 2.24.2.
With bugreports, screencaptures and a sample scene this time.

Please test this on OSX and R17.

New problem: Switching between takes containing materials with large textures. (8k or higher and OOC)
Discovered in TEST52.

After crashing C4D for about 15-20 times i found one scene that could reproduce the crash/freeze EVERY time.
5-6 coffees and 5-10 more crashes later i managed to narrow down (and screencap) the problem to multiple large (16K) texture maps.
I used that scene to generate bugreports in the latest TEST6.
It took many takes because C4D would not generate bugreport and it would just freeze sometimes.
Original scene is of course using OOC feature and renders without problems with any tested version of plugin in LV and PV.

I can't send that scene because of the size of multiple 16k textures and other reasons i mentioned before. But i made a small example scene that reproduces the crash when switching between takes.

Example scene:
Please make sure that all textures are loaded.
https://drive.google.com/file/d/0B9R9pW ... sp=sharing

I almost gave up on Bugreports from example scene, it mostly freezes and crashed only one time:

_BugReport.txt.zip

(17.41 KiB) Downloaded 374 times

To reproduce the crash/freeze in my original scene i have to just click on one take that switches materials in the scene.

bugreport for original scene:

_BugReport2.txt.zip

(17.14 KiB) Downloaded 387 times

Screen captures:

Large Textures and Takes 2.24.2 TEST6 - Crashing (and Freezing)


Large Textures and Takes 2.24.2 TEST31 - No crashing or freezing!


Large Textures and Takes 2.24.1 R3 - No crashing or freezing!




Old problem: ( reporting for the third time ) Node Editor, disconnected nodes and crashing.
Others reported a lot more but I narrowed it down to something that can be reproduced.
Discovered in TEST31.

Same node editor problems as reported by others:
viewtopic.php?p=257217#p257217
viewtopic.php?p=259478#p259478

I can reproduce it with any scene.

Bugreport for latest TEST6:

_BugReport3.txt.zip

(16.71 KiB) Downloaded 379 times

Node Ed. 2.24.2 TEST6 - Problem exists


Node Ed. 2.24.2 TEST42 - Problem exists
viewtopic.php?p=255436#p255436

Node Ed. 2.24.2 TEST31 - Problem exists


Node Ed. 2.24.1 R3 - No problems here!


Edit: Disclaimer - I'm just reporting here and I am doing some tests. I don't need this fixed right now or anything like that. Please don't get the wrong impression here. This is all just to help troubleshoot problems and hopefully improve the plugin. Thank you all and happy new year.

Regards
Milan

[aoktar]

Node editor problems should be fixed on last version. I'll try to check your scene.

EDIT: I suppose that your crashes happened at same point. It occurs on file name functions in material previews when you used TAKE switching.

What's numbers of your R17?

BTW as a side note;
I hope that you're not using png as textures. Because it's small but worst idea to work fast on material editing. Especially when a render session is not active on Live Viewer. Because Octane can't use caching of textures and have to reload and uncompress these images. Best idea to tweak your materials with an render is online in Live Viewer. Also tiff,psd, etc.. formats are much faster while making material editings.


FINAL WORDS,
I have fixed the problem. It was around take system and document's path functions. Do you have any point which is generating crashes?
I suppose that on this week i'll make this version as STABLE. Small glitches about scatter, that's not a avoidance to do this.

[milanm]

Node editor problems should be fixed on last version. I'll try to check your scene.

EDIT: I suppose that your crashes happened at same point. It occurs on file name functions in material previews when you used TAKE switching.

What's numbers of your R17?

BTW as a side note;
I hope that you're not using png as textures. Because it's small but worst idea to work fast on material editing. Especially when a render session is not active on Live Viewer. Because Octane can't use caching of textures and have to reload and uncompress these images. Best idea to tweak your materials with an render is online in Live Viewer. Also tiff,psd, etc.. formats are much faster while making material editings.


FINAL WORDS,
I have fixed the problem. It was around take system and document's path functions. Do you have any point which is generating crashes?
I suppose that on this week i'll make this version as STABLE. Small glitches about scatter, that's not a avoidance to do this.

Ok, that's great news. Thank you Ahmet!

Regards
Milan