Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - ProxyFuel

Pages: [1]
1
Thank you for the answers. As I expected, if there’s no explicit need for this feature, then it’s not necessary to use it.

My main concern is more about why this isn't an advanced option that can be enabled and configured by those who actually need it—instead of being a default setting applied to everyone out of the box.

I’ve been using Corona since the beta days and have always appreciated how easy it is to use while still delivering great results. But small things like this can be frustrating. I can imagine how many new users might struggle to understand why their renders look off or incorrect.

I realize this is more of a 3ds Max issue than a Corona one, but I still think it's worth bringing up

2
The plot thickens...

I’ve discovered something odd: if I add a JPG as a background using a Tonemap Control node, disable ACES in the tone mapping settings, and hit render — everything looks correct.

But here's the catch:
As soon as I hit Stop and render again, the image goes dark. It won’t return to the correct look until I restart 3ds Max. Then it behaves — but only for the first render. After that, same issue.

This happens consistently across multiple machines, all running the same version of Max and Corona. I’ve tried different scenes and different JPGs — same result every time.

Right now, I can’t get things to render correctly with the new color management system. Anyone else seeing this?

3
Is there an official or recommended workflow for using the new Color Management system in 3ds Max 2025+ with Corona Renderer 13? I've looked around and find answers that conflict.

So far, I’ve stuck with the legacy Gamma 2.2 setup because it gives me predictable results. But I know it's time to get familiar with the newer ACES/OCIO-based color management and how it integrates across the viewport, materials, rendering, and saving.

Out of the box, I often run into issues where what I see in the viewport doesn’t match the render, and both differ from the saved image. I’m trying to establish a consistent, predictable workflow—ideally where what I see is what I get when saving a standard JPG (let’s leave 32-bit linear workflows aside for now).

Example of the issue:
Using the legacy Gamma 2.2 workflow:

I import a JPG street photo—looks good in the viewport.

It renders correctly, matches the original.

Saved output is accurate.

Using the new Color Management workflow:

The same image looks washed out in the viewport.

The render comes out darker than the original.

If I tweak the color management settings to fix the background, then my 3D elements look wrong—as if they no longer match the photo.

This inconsistency is making it hard to transition. Has anyone found a solid setup or workflow to ensure predictable results from viewport → render → saved image, especially with standard 8-bit JPGs?

4
Same here—I just made a post about it. There’s definitely something off with version 12. It’s noticeably slower when we test it across our machines. As a school, we have several computer labs with completely different setups, so it's not a specific hardware issue. Scenes that ran quickly in version 11 are now sluggish, even when merged into empty scenes. This seems like a software issue that needs to be addressed ASAP.

5
[Max] Bug Reporting / Corona 12 feels sluggish?
« on: 2024-08-26, 09:09:47 »
Is anyone else noticing that the latest version of Corona 12 feels slower compared to previous versions? I've been using the same test scenes for years, running them on different machines with consistent software setups but varying hardware, and I've observed a significant drop in speed. Even my students have been complaining that it feels sluggish. Is anyone else experiencing this? I'm running Corona 12 with 3ds Max 2025 on Windows 11


6
Since Corona changed the setting where you chose to use Photographic exposure in camera to the Frame buffer itäs been acing strange. Has anyone else been having problems?

Allways had good resules with real world camera values, but since the change I often run into issues where I need to cranck it up to stupid values like ISO 6000, F-stop 2, shutter 50, and it¨s still rather dark?? And no it¨s not any rookies mistakes like bad lighting.





7
Yes it still happens. When it first happend I was sure it was an issue with google drive trying to backup somthing and that made Corona freak out so I told everyone when they doing overnight renders to place project on desktop and just render from there. Still happend.
Could it have anything to do with "relative to the project folder"

8
I have some 30+ students that use Corona render and we´ve been teaching and useing corona for many years. Suddenly my students started complaining that they got this error and ther render got abortet.

"Render had to be aborted because a bitmap on disk changed and is being reloaded. Continuing the render could cause crash or undefined behavior"

I found this info on the support page that "solves" the problem but I still don´t understand why everyone suddenly was getting this issue? Is it a corona 8 problem? Only other this that has changed is they use google drive to store files but in ofline mode. 

https://support.chaos.com/hc/en-us/articles/4528201114641-Render-had-to-be-aborted-because-a-bitmap-on-disk-changed-and-is-being-reloaded-Continuing-the-render-could-cause-crash-or-undefined-behavior-Bitmap-name-is-XXXX

9
I have a class with 30+ students that are using Corona 8 with 3ds max 2023. Several of them are getting the same problem. It crashes when they use Interactive Render.

We´ve updated drivers, reinstalled, Killed the ENU map. Smae thing on different specs of laptops.

Added the dump file 

10
If you have a scene that has been converted to physical materials can they be converted back to corona? I know corona can render physical but was hoping not to need to work with multiple material types.

11
I've seen renders that get strange effects that over time disappear. Both massive colored reflections that over time clean up and aren't visible in the end render and strange effects where you see massive pixels like if the bitmaps where super low rez.
I'm thinking that the scene might have non-corona lights? or some new progressive setting? The image looks right after rendering for a long time but it's irritating not knowing how the end result will be.

Pages: [1]