Version 3.00 - Alpha10.1 (30.04.2016)
Moderators: ChrisHekman, aoktar
- fuchsundvogel
- Posts: 102
- Joined: Tue Jan 06, 2015 3:21 pm
yes, just install the standalone. you can have both (v2, and v3) installed.
Hi Aoktar,aoktar wrote:joecurrie,
Can you make a test with same very simple box scene to reproduce error? Here is a text file "octane_log_flags.txt". It will produce some log output for us. Please put it to folder where is the Cinema4D executable. And try to generate same errors. Then find the generated "octane_log.txt" file and post here please. It can give more idea.
Please see attached Log file after reproducing the simple scene render using the same steps as before.
1. Render to picture viewer - Fails
2. Render to live viewer - Ok
3. Render to picture viewer - Now hangs on 'updating....' for some reason?
If I try and stop the render whilst is is hanging on 'updating...' C4D freezes and I have to force quit.
- Attachments
-
- octane 3.00 alpha 6 160407 155429.log
- (4.58 KiB) Downloaded 208 times
Mac OS X 10.11.4 - Cinema 4D R17 | Geforce GTX980 + 980ti | 32GB
joecurrie,
i can't reproduce the problem on windows or osx. Can you save and send this scene? Also please try with latest A6.2
i can't reproduce the problem on windows or osx. Can you save and send this scene? Also please try with latest A6.2
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Hi Aoktar,aoktar wrote:joecurrie,
i can't reproduce the problem on windows or osx. Can you save and send this scene? Also please try with latest A6.2
Please see attached scene and log this is now using Alpha 6.2.
Thanks
- Attachments
-
- Simple cube scene.c4d.zip
- (66.34 KiB) Downloaded 228 times
-
- octane 3.00 alpha 6 160407 160516.log
- (2.97 KiB) Downloaded 235 times
Mac OS X 10.11.4 - Cinema 4D R17 | Geforce GTX980 + 980ti | 32GB
Thanks! Everythings look fine until error. We will check it. Maybe an issue about osx and driver version. I'm running on 10.8.3 and 10.9.5.joecurrie wrote: Hi Aoktar,
Please see attached scene and log this is now using Alpha 6.2.
Thanks
Are you deleting unrelated versions of plugin when you extract?
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Hi, I have cleaned old versions of the plugin. Will try with stable and see if the same happens.aoktar wrote:Thanks! Everythings look fine until error. We will check it. Maybe an issue about osx and driver version. I'm running on 10.8.3 and 10.9.5.joecurrie wrote: Hi Aoktar,
Please see attached scene and log this is now using Alpha 6.2.
Thanks
Are you deleting unrelated versions of plugin when you extract?
Mac OS X 10.11.4 - Cinema 4D R17 | Geforce GTX980 + 980ti | 32GB
Thanks for the logs. I had a look and everything looks fine and it's definitely not the race condition I thought it could be. Do you have the same issues with older version of the Octane plugin, too? Can you run Octane Standalone?joecurrie wrote:Hi Aoktar,aoktar wrote:joecurrie,
i can't reproduce the problem on windows or osx. Can you save and send this scene? Also please try with latest A6.2
Please see attached scene and log this is now using Alpha 6.2.
Thanks
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
abstrax wrote:Thanks for the logs. I had a look and everything looks fine and it's definitely not the race condition I thought it could be. Do you have the same issues with older version of the Octane plugin, too? Can you run Octane Standalone?joecurrie wrote:Hi Aoktar,aoktar wrote:joecurrie,
i can't reproduce the problem on windows or osx. Can you save and send this scene? Also please try with latest A6.2
Please see attached scene and log this is now using Alpha 6.2.
Thanks
Hey Abstrax & Aoktar,
Just tried reverting back to 2.25 R3 and everything is working fine - attached log.
Let me know if you would like me to try any tests/experiments. Would love to work out why it's doing this in V3, should I try experimenting with any kernel settings?
Thanks
- Attachments
-
- octane 2.25 160408 105527.log
- (666 Bytes) Downloaded 212 times
Mac OS X 10.11.4 - Cinema 4D R17 | Geforce GTX980 + 980ti | 32GB
Ok, thanks. I guess, I will have to make a special build with more logging to see what's going on. Can't figure it out just by looking at the code, since the reported behaviour doesn't make any sense to me... I will get in touch with you again next week.joecurrie wrote:Hey Abstrax & Aoktar,
Just tried reverting back to 2.25 R3 and everything is working fine - attached log.
Let me know if you would like me to try any tests/experiments. Would love to work out why it's doing this in V3, should I try experimenting with any kernel settings?
Thanks
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Hi Ahmet,
Awesome work on v3.
I just wanted to mention a few small niggles that have only come up with this version... and see if it was just me and if they are fixable.
Firstly. My material previews have a high level of black pixelation going on. was fine in 2.25 but noise is clear in v3. Doesn't seem to respond to preview samples under 'other'. And secondly this version of the plugin seems to have been placed alongside my enhance3d plugins... it puts all the shaders nested under a folder simply titled "." Both issues illustrated in the attached thumbs. Just wanted to flag them and make sure i wasn't doing something stupid to cause them.
They are nothing major of course.
I'm running OSX mavericks. gtx680 ti and 780ti. Cinema r17 up to date.
Big cheers
R
Awesome work on v3.
I just wanted to mention a few small niggles that have only come up with this version... and see if it was just me and if they are fixable.
Firstly. My material previews have a high level of black pixelation going on. was fine in 2.25 but noise is clear in v3. Doesn't seem to respond to preview samples under 'other'. And secondly this version of the plugin seems to have been placed alongside my enhance3d plugins... it puts all the shaders nested under a folder simply titled "." Both issues illustrated in the attached thumbs. Just wanted to flag them and make sure i wasn't doing something stupid to cause them.
They are nothing major of course.
I'm running OSX mavericks. gtx680 ti and 780ti. Cinema r17 up to date.
Big cheers
R