Messages

31

[Max] General Discussion / Re: What is the workflow with Corona image editor it does not have the new features

« on: 2024-12-02, 16:40:12 »

Hi, I don't understand at this point the point of saving a file in cxr. in our workflow we always save the cxr to possibly recover exposure or exclude some lights, but if it is not possible to manage the new features then we cannot use them. I read about the option to open the cxr in the new VFB, but I don't find in the new VFB an option to open the cxr file later, am I doing something wrong?
Thank you

Howdy! Hopefully I can be of help :)

For the "use the new VFB as CXR" setup we'd recommend watching our official tutorial on the topic -

(already linked to the correct timestamp).

In short, you drag your CXR image into the VFB, you go under the History list and hit the pencil button. At that point you should be able to the usual CIE things to the image :)

32

[C4D] I need help! / Re: Color Profile Issues with Cinema 4D R25 and Corona 12

« on: 2024-12-02, 13:11:59 »

Hi
1 i am using substance painter because i am more familiar with masking in photoshop and in substance

2 i will upload the project as soon as possibile but i cannot upload the box and the texture because of NDA
so i will create a new object with the same workflow as soon as possible

Thank you davetwo and burnin for helping here! I also think some sort of a scene file with the issues present would be great at this point - so we can all have a more in depth look at what is happening.

Thank you for your patience!

33

[C4D] General Discussion / Re: Team Render machine not reachable

« on: 2024-12-02, 12:28:02 »

hi Moritz, it says I am on port :5401, I reinstalled everything back to cinema v2024.1.0 and it worked until I shut the machine down, now it won't connect again. I think it's time to switch to Redshift

Not trying to be that guy but that sounds like a general Team Rendering issue that is probably related to your network setup / firewall. Given that you get the "red" icon there you'll have the same issue with Redshift :)

One thing that has tripped me up in the past was surprisingly the actual C4D versions themselves. IIRC I had something 2024.1.0 installed on most of my nodes but some apparently got updated with like 2024.1.02 which then prevented TR from working. Of course the error I was getting didn't mention that :)

34

Hardware / Re: Workstation Build Advice - 7985WX

« on: 2024-12-02, 12:20:44 »

Looks good to me although given the specs I'd definitely consider getting a Threadripper non-PRO system aka something based on the 7980x instead of the 7985wx.

I don't see you using any of the advanced features of the platform with that build - you have one GPU, 256GB of memory and a single SSD. So you don't really need the extra PCI-E lanes of the PRO platform.
Even if you need "PRO" features like IPMI I'd still go with a 7980x and just buy an ASUS IPMI card I guess?

Main reason is that you're really going to be overpaying for the PRO platform and won't be using it to its full extent. Instead what I think could be better is using up the saved money for more SSDs, high end GPU with more VRAM and things like that.

That is unless I am missing something :)

Oh and for the cooler I'd personally go with a Noctua u14s but just make sure you pick the correct one for the platform you have.

35

[C4D] I need help! / Re: Color Profile Issues with Cinema 4D R25 and Corona 12

« on: 2024-11-25, 17:48:10 »

Hm hm, that to me looks like the ACES color shift. Can you try disabling the ACES OT operator in the Tone mapping stack inside the Corona VFB?

ACES OT is very popular as it has a nice filmic curve to it and it also shifts the color a bit depending on how strong the lighting / bright the bitmap is. Our users typically find that to be desirable behavior because it mimics how film & cameras work in the real world - that said it can be less than ideal for whenever you need your colors to stay as close as they can to how the client specified them.

Please give it a try and report back.

36

[C4D] Daily Builds / Re: Who has the Mac M4 pro or max

« on: 2024-11-18, 11:47:18 »

The single core numbers for the M4 are really impressive, basically 1,5 times faster than anything released before. That must make a big difference in render to first pixel.
I also see that the M1 and M4 are faster than a 64T thread ripper. Makes me wonder what these numbers really mean.

I'm not sure whether I'm looking at the wrong M4 numbers but just to offer an observation... a last gen 5995wx (64c/128t) scores roughy 4300 points in CB2024, 7970x (32c/64t) isn't that far behind it either.

37

Hardware / Re: Phoenix fd

« on: 2024-11-07, 14:24:50 »

So I don't do too sim work often but we do have this link you can check out:
https://docs.chaos.com/display/PHX4MAX/Setup+and+Installation#SetupandInstallation-HardwareAdviceforFasterSimulating

I guess generally speaking individual core speed is more important than core count especially after a certain amount of cores. At some point simulations don't scale well with more cores / threads.

But then I'd say you need to consider how much time you're also rendering. So if you opt for say a 64 core 7980x then arguably the simulation speed won't be as fast as on the 9950x but the rendering (including the Interactive Renderer) will be in fact much faster.
So it kind of depends is what I would say :)

Oh and I've only listed AMD examples. You can pick a CPU from team blue (Intel) as well but the general consensus at the moment is that for the high end consumer stuff the 9950x type CPUs are more efficient than their Intel counterparts whereas Threadrippers pretty much seem to be the go to option for the prosumer stuff. That said, if you go with something below the 16 core range then from my understanding Intel's stuff might be the better option.

38

[Max] I need help! / Re: Volumetric grid: flicker in animation

« on: 2024-11-07, 13:30:30 »

Glad to hear you've resolved the issue and thank you for letting us know what went awry :)

39

[C4D] I need help! / Re: Win10/Win 11 Lag

« on: 2024-11-01, 15:16:40 »

Hey everybody, good news! The devs have been working on improving the way high core count machines work with Corona for C4D and, after daily driving this build for a couple of days, I can say it has solved these issues in its entirety for me on my 5995wx (with SMT enabled!).

So if you hop over to the daily build forum section (https://drive.google.com/drive/folders/1u3jdwa6h-in-DT-PcMEqTsvUkyZVjjPh) and download the latest build (posted on 31.10.2024) you can give the build a try yourself as well.

For me this build really works wonders as things work smoother than ever before but as always, we'd welcome your input as well to see if that is the case for your high core count configurations as well.

40

[C4D] Bug Reporting / Re: Interactive or Render with VFB opened on 9950x freeze system

« on: 2024-10-31, 15:44:10 »

Hm hm, that build I was mentioned earlier, it is ready and you can download it from here:
https://drive.google.com/drive/folders/1u3jdwa6h-in-DT-PcMEqTsvUkyZVjjPh

Would you mind giving it a try and reporting back if this in any way shape of form helps with your issue?

Thanks!

41

[C4D] Bug Reporting / Re: Interactive or Render with VFB opened on 9950x freeze system

« on: 2024-10-28, 17:53:34 »

Hm hm, the devs are working on fixing some of the threading issues with high core count CPUs and I'm wondering if that'll resolve some of the issues you're having. I'll update this topic once the build is ready.

42

[C4D] Bug Reporting / Re: Interactive or Render with VFB opened on 9950x freeze system

« on: 2024-10-24, 11:29:46 »

Howdy! Thank you for opening up a thread :) Does this apply to Interactive rendering or final render or both maybe?

43

Hardware / Re: AMD 9950x

« on: 2024-10-24, 11:26:41 »

Based on reviews available online you'll be getting ~10% faster rendering compared to the 7950x. Not as huge as of a leap as we typically get but it is indeed still faster :)

44

[C4D] General Discussion / Re: Match Corona colors in Davinci Resolve Fusion 19

« on: 2024-10-24, 11:24:57 »

Hmm hmm, fellow Resolve user here (use it daily) and I'm not really 100% sure what you're running into but things do work as expected on my end if I do the following:

- Make sure the tonemapping stack is disabled (including ACES OT)
- Save a 32 bit EXR
- Drag it into Resolve (Color science I'm on Davinci YRGB but without the color managing, Rec 709 (scene))

This will allow for a fully linear workflow aka you can do advanced compositing on with things then. If you'd like to get the ACES OT look back in directly in Resolve then you go to the Color page and throw the "ACES Transform" node in there. You'll probably want the sRGB (Linear) as input and sRGB as output.

Now if you'd like to use tonemapped images but still want some extra data by going EXR 16/32 bit then from what I recall you just export a tonemapped image and load it up in Resolve and it should all work automatically.

Let me know if the above helps, if not I'd be happy to dive deeper :)

45

Hardware / Re: Which Monitor is best?

« on: 2024-10-22, 09:36:58 »

There is indeed auto-color management with latest Windows 11 update, or it's been there since January if you're on fast-track. I haven't tested it as I don't run these builds with it yet.
It's called..."auto-color management". https://support.microsoft.com/en-us/windows/auto-color-management-in-windows-11-64a4de7f-9c93-43ec-bdf1-3b12ffa0870b

If not that, then there are few more things to consider:
- Do you have wide-gamut Display and are you running wide-gamut mode in OSD? (Native, or DCI-P3/AdobeRGB). Unless you have monitor that greatly exceeds sRGB color gamut, you will not see noticeable color shift. This shift would also be strongest in Red tones.
 ICC profile merely interprets color in OS, it runs on top of what the monitor's OSD is set to. That's why ICC is always paired to specific monitor mode, and if you switch it's not longer applicable. So for wide-gamut environment, you would run Native or specific wide-gamut mode in OSD, and then calibrate after that to ICC which matches the desired color-space. The possible working combination go from higher to lower (so Wide-Gamut to Low-gamut) or equal to equal (HG to HG or LG to LG).
- What do you mean "make sure the ICC profile is set", Working Space ? When you import file, you can convert to profile (which should be default settings if you don't get asked), or assign profile (which is meant to interpret colors when profile is missing). Since I am not on 2025 with OCIO, my 3dsMax (or Corona VFB for that matter) doesn't save with any color-profile attached to file formats.
- Your file (render) should be converted to space you intend to work in and the working space should like-wise be set to generic (non-device specific) color-space (sRGB or P3/AdobeRGB/.. for Wide-gamut. If you load your monitor ICC, you will disable color-management.


- If you want to be sure, set working environment in Photoshop to sRGB (that is default). On importing render, set the mode to "convert". On opening, convert the render to sRGB color-space. Make sure the auto-mode in Window is disabled if by any chance this latest update is on. And only after that, compare 3dsMax Corona VFB and your opened render.

I don't understand right now 100perc. which exact combination you're doing, but in my opinion you most probably negated color-management and are seeing incorrect (but identical) colors in both 3dsMax and PS. That's actually quite easy scenario to achieve. Seeing identical colors doesn't mean you have correct color-managed workflow pipeline.

It doesn't matter though, I can guarantee you 3dsMax until 2025 simply isn't color-managed, it can load Gamma 2.2 and that's about it. With the OLED I have right now, single-toggle of sRGB in NoVideo tool shows almost 20perc. perceptible difference in red saturation, matching the srgb coverage of WOLED panels (125perc. QD-OLED up to 150perc. even)

Yas so I'm definitely a newbie for when it comes to ICCs and managing this stuff (thank you for getting into it with me) but nonetheless - I do think it might work better in the latest W11 build across all apps?

I do have a wide-ish gamut display that covers 90% of the Adobe gamut and roughly 70% of Rec 2020 which naturally makes the everyday "web" colors quite saturated if I don't "clamp" it back to sRGB using the display's OSD. Suffice it to say though, for my line of work at least, I am predominantly concerned about the sRGB output so the display is set to hardware clamp to sRGB.

I'm trying to validate what kind of an effect the ICC profile has and with all of what you've mentioned above I'm not sure how it could be wrong.

- With the ICC profile loaded into Windows via Color Management, the 3ds Max / C4D VFB image looks the same (side by side) to the one in Photoshop where I can set the RGB working space to the ICC profile.
- If I have the ICC profile loaded in Windows and in Photoshop I select the standard sRGB profile (the one that comes with Windows by default) then the two images don't match.
- If I try to validate the colors the ICC profile produces with my xRite i1 Display Pro, then the average dE is 0.4 with the highest being 0.8 . I do this via Calibrite where I load the ICC profile into the app and have it do validation.

I could be missing something here though.