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 - Julieta

Pages: [1] 2
1
[Max] I need help! / Re: Chaos corona livense not found
« on: 2025-03-10, 14:16:48 »
In Autodesk for example whenever there's a connectivity issue or whenever it can't retrieve the license you don't lose access to the products, you get to use it offline for 24 hours.
Couldn't that be applied here?

2
[Max] I need help! / Re: Chaos corona livense not found
« on: 2025-03-10, 13:55:12 »
Working here as well Tom! Thanks for taking care of it!

3
[Max] I need help! / Re: Chaos corona livense not found
« on: 2025-03-10, 13:11:15 »
All our render nodes are failing as well. Is Corona down everywhere? Pls, we really need to deliver a job today

4
[Max] I need help! / Re: Chaos corona livense not found
« on: 2025-03-10, 13:09:21 »
We are having the same issue over here, the license server says there are no licenses available when we should have at least 8.

5
Dear Corona team,

In the meantime we started checking our nodes when they were rendering and we realized that, somehow, the Physical Camera exposure control was overriding the Post-production settings in the VFB, we don't know how and why, because this was not happening locally. We are re-installing 3ds max in all our nodes. We never use physical cameras (Only Corona Cams), this project was an exception, so we had no idea this could happen.
I apologize for wasting your time and I thank you for your assistance.


6
the same "black overlay" look on each of the frames

7
We've only got 5 nodes with 24/7 availability and I tried rendering on each of them (by setting exclusive nodes in Render Manager), the result was always the same.
At night our workstations work as render nodes, and they had the same result. It's an animation of <100 frames and each frame had these "black overlay" look.
Unfortunately I can't render locally in our nodes because they are just render nodes, we can't use them as Workstations, I don't have Railclone or Forest Pack licenses on these nodes (and our iToo licenses are not of the floating type) so I can't open the files correctly in these.

8
Hi Maru,

thanks for your answer. No, we are not using distributed rendering. We are using only 1 node per frame.

9
Dear Corona team,

We are having issues with a project of ours. Locally it renders fine, but when we send it to our render farm the visuals are dark (although you can see that it's not 100% black, there's light information in there)
We've searched the forum to see if there could be anyone else with this strange issue, but we couldn't find anything.
We've deleted mental ray legacy assets, we've cleaned the scene with Corona Power tools and Prune Scene but nothing seems to work.
I attach a picture of how it's looking vs how it's supposed to look.
We have an urgent deadline and we are driving ourselves crazy trying to figure it out. Would you please help us with this?

USEFUL INFO:
Corona 12 HF1
3DS max 2025
Color management: Gamma Workflow 2.2
Rendered in our farm using Pulze Render Manager 2.2.15
Set Ups through Pulze Scene Manager 2.5.10 (BETA)

Kind regards :)


10
Next time I'll take it into account!

11
No, would have this changed something?

12

After lots of trial and error, I managed to solve it. The issue apparently came from one of the many Forests I had in my scene. It's quite weird because there were no issues when rendering the other cameras, and it was not even visible in the camera that was causing Max to shut down. Even when it was hidden, it was causing trouble. Solution was to delete this specific forest, and now everything works as it should. There was definitely something corrupt in this forest, unfortunately, I've got no more time to keep doing research on what. Deleting was the easiest path.


13
Did you try to just recreate the camera?
With Cam...008 chosen, press 'P' to switch to perspective view, then deselect all, use the 'Create CoronaCam from Viewport' button in the Corona toolbar, this will create a new CoronaCam which should match all parameters of the old camera.
Does this still crash Max?

Hi! Thanks for your reply! Yes, I also forgot to mention that I tried creating the camera multiple times as well.

14
Dear Corona team,

I've been encountering problems with a file I'm working on. Whenever I try to do an interactive render of "CoronaCamera008" my 3ds Max crashes ("An error has occurred and the application will now close..."). The VFB continues to work though, but naturally I can't keep working with it because I have to let 3ds max shut down.


I've tried different alternatives: material overrides, changing sky, changing sun, hiding forests packs, rail clones, etc. But it doesn't matter what I try it keeps crashing.
The file was originally created in Max 2021 (corona 8-9), then edited in Max 2023 (corona 10) and never had any issues with it. Now I have to create new visuals, and I opened it in 2025 and I've been having these errors. I tried merging all the assets into a new file. However this file also crashed. It's always with this camera.
I also tried it on another PC (same software version, better hardware specs) and the error occurred again.
I tried rendering the camera with nothing on it (I hid all the elements)  and even though it managed to start rendering without crashing, it took <2 minutes for scene parsing (for an "empty" scene!)
EDIT: I also tried re-creating the camera more than two times.
I've came to the conclusion that there's clearly something wrong with the file, but I can't point my finger towards the error. That's why I'm recurring to you for help.
I've just attached the files via the "Chaos Drop Zone" they should be sent any minute now. Submission ID# T7T9-CZF6


Thanks in advance for your help! it'll be greatly appreciated


EDIT: After lots of trial and error, I managed to solve it. The issue apparently came from one of the many Forests I had in my scene. It's quite weird because there were no issues on the other cameras, and it was not even visible in the camera I was rendering. Even when it was hidden, it was causing trouble. Solution was to delete it, and now it works as it should.

15
Thank you all for your answers, I'll try the release candidate.

Pages: [1] 2