Cinema4D version 2021.1.7 (Old stable) 16.12.2022
Moderators: ChrisHekman, aoktar
I had also issues with DWAB (thats how its called the smaller one?) that was producing big files instead of small, randomly. In c4d 2023 I noticed this behavior.
- blackcat321
- Posts: 18
- Joined: Fri Mar 06, 2020 3:08 am
Can you reproduce it? And describe what's the conditions to reproduce it hereblackcat321 wrote:c4d crashes when saving image in live viewer and selecting color space
octane 2021.1.6 r5
cinema 4d 2023
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
A small request for HSV sliders:
You cannot alter the H unless you play with the bottom sliders first. Which is weird a bit as its the first slider and our mind works from top to bottom hehe. Not a big thing, but it would definitely help on the UX side of things.
Thanks a lot!
You cannot alter the H unless you play with the bottom sliders first. Which is weird a bit as its the first slider and our mind works from top to bottom hehe. Not a big thing, but it would definitely help on the UX side of things.
Thanks a lot!
- SilentPartnersStudio
- Posts: 12
- Joined: Mon Feb 15, 2016 4:38 pm
So I have explored this a bit more, and I think it comes down to AE being case sensitive to the channel naming.aoktar wrote: The thing is working with any older version? I don't have AE to check but it looks like working with the other softwares
When I bring in the UV pass it is black...and when I add an extractor plugin it defaults to Capital letters for the channels. But when I manually assign a channel, the channels are labeled lowercase...but the manual assignment works. When I check another pass that was rendered the channels are labelled correctly with Capital letters
Checking in DJV I can see that the UV pass is indeed written with lower case letters for the channel names But when viewing a RLE encoded exr the UV layer has capital letters for the channel names Obviously it would be great if after effects was not case sensitive here...it seems like most apps are not case sensitive.
But also it would be wonderful if octane was using consistent channel naming conventions. Like ALL caps for channel names rather than switching between caps and lower case.
Hi,
I have a small problem with databases in asset browser c4d 2023.
If I drag any texture from my database to node editor, it creates a "tex" folder next to my project file and inside another "assetdb" folder and copies all the textures in the there. Is there a way to disable this behaviour?
I don't know if i should report to Maxon as well.
Thanks!
I have a small problem with databases in asset browser c4d 2023.
If I drag any texture from my database to node editor, it creates a "tex" folder next to my project file and inside another "assetdb" folder and copies all the textures in the there. Is there a way to disable this behaviour?
I don't know if i should report to Maxon as well.
Thanks!
- blackcat321
- Posts: 18
- Joined: Fri Mar 06, 2020 3:08 am
I tried to create a new project, open the live viewer and export the image, but it still crashes when I select the color space.aoktar wrote:Can you reproduce it? And describe what's the conditions to reproduce it hereblackcat321 wrote:c4d crashes when saving image in live viewer and selecting color space
octane 2021.1.6 r5
cinema 4d 2023
2021.1.6 r4 no problem
Yes this is weird. Probably because Octane doesn't have access to browser libraries.thanulee wrote:Hi,
I have a small problem with databases in asset browser c4d 2023.
Architectural Visualizations http://www.archviz-4d.studio
Files in database are not directly accessible by Octane so I have to duplicate it to hdd to use that from copy.thanulee wrote:Hi,
I have a small problem with databases in asset browser c4d 2023.
If I drag any texture from my database to node editor, it creates a "tex" folder next to my project file and inside another "assetdb" folder and copies all the textures in the there. Is there a way to disable this behaviour?
I don't know if i should report to Maxon as well.
Thanks!
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
I have a fairly large 3d scene kitbash3d Minerva kit https://kitbash3d.com/pages/minerva
When I try to copy an object I get an error;
Started logging on 24.10.22 18:25:55
OctaneRender Enterprise 2021.1.6 (11000600)
OCIO error: Error could not read 'H:\3d enviroment competetion 2022\OpenColorIO-Configs-master.zip' OCIO profile.
VRAM used/free/max:0Kb/23.999Gb/23.999Gb Out-of-core used:0Kb RAM used:16.432Gb total:127.893Gb OpenGL free/total:0/0
Scene created in plugin version 10021601
Scene plugin version is older than version:2021.1.6-(R5)
Plugin will convert the parameters of displacement texture.
Animated attributes should be changed by manually!
FumeFx library initialisation error!
--------------------------- EXPORT LOG ---------------------------
Export materials time= 32970.384 ms
Collect objects time= 20.382 ms
Mesh creation time = 6573.422 ms.
Api update time: 0.443 ms.
VRAM used/free/max:8.223Gb/12.337Gb/23.999Gb Out-of-core used:0Kb RAM used:45.7Gb total:127.893Gb OpenGL free/total:0/0
CUDA error 700 on device 0: an illegal memory access was encountered
-> failed to wait for event
device 0: direct light kernel failed
MB:0/0 ST/MOV:0/823 Nodes:1719 Tris:47.109m DispTris:0 Hairs:0 Meshes:823
Textures Grey8/16:0/0 Rgb32/64:272/6
When I try to copy an object I get an error;
Started logging on 24.10.22 18:25:55
OctaneRender Enterprise 2021.1.6 (11000600)
OCIO error: Error could not read 'H:\3d enviroment competetion 2022\OpenColorIO-Configs-master.zip' OCIO profile.
VRAM used/free/max:0Kb/23.999Gb/23.999Gb Out-of-core used:0Kb RAM used:16.432Gb total:127.893Gb OpenGL free/total:0/0
Scene created in plugin version 10021601
Scene plugin version is older than version:2021.1.6-(R5)
Plugin will convert the parameters of displacement texture.
Animated attributes should be changed by manually!
FumeFx library initialisation error!
--------------------------- EXPORT LOG ---------------------------
Export materials time= 32970.384 ms
Collect objects time= 20.382 ms
Mesh creation time = 6573.422 ms.
Api update time: 0.443 ms.
VRAM used/free/max:8.223Gb/12.337Gb/23.999Gb Out-of-core used:0Kb RAM used:45.7Gb total:127.893Gb OpenGL free/total:0/0
CUDA error 700 on device 0: an illegal memory access was encountered
-> failed to wait for event
device 0: direct light kernel failed
MB:0/0 ST/MOV:0/823 Nodes:1719 Tris:47.109m DispTris:0 Hairs:0 Meshes:823
Textures Grey8/16:0/0 Rgb32/64:272/6