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

Pages: [1] 2 3 ... 7
1
[Max] Daily Builds / Re: New VFB Skin and functionality
« on: 2024-03-17, 15:56:51 »
It would also be nice to have an option to change the VFB background color in Corona Renderer.
This was discussed previously here: https://forum.corona-renderer.com/index.php?topic=28172.0

It really helps a lot when you need to adjust the overall brightness level of the rendering, because with the current linear RGB 4/4/4 background color, it is easy to miss it.

2
Hardware / Re: Which Monitor is best?
« on: 2024-03-15, 22:23:48 »
I am using an 27 inch Dell U2723QE with 125% scaling since one year and find it great.
There is also bigger one U3223QE avaliable:  https://tftcentral.co.uk/reviews/dell-ultrasharp-u3223qe

also, some great articles:
Monitor selection guide: https://docs.google.com/document/d/1illeNLsUfZ4KuJ9cIWKwTDUEXUVpplhUYHAiom-FaDo
Jonny Elwyn reviews and main concepts of choosing right display: https://jonnyelwyn.co.uk/film-and-video-editing/affordable-colour-grading-monitors-2/

just 2 cent. who knows, maybe it helps :)


3
[Max] Daily Builds / Re: Corona Curvature Map playground!
« on: 2024-03-09, 12:26:36 »
Depends what exactly you mean. :)
We have "ignore bump" option in the newest daily: https://forum.corona-renderer.com/index.php?topic=41598.0


Hello Maru,

The "Ignore bump" option is a must-have, for sure.
I am also referring to my post at https://forum.corona-renderer.com/index.php?topic=35473.msg222493#msg211123 , where we get not only the "real" edges of the objects, but also unwanted edges such as backside with a curvature map.

Hope you can fix this as well.

4
[Max] Daily Builds / Re: Corona Curvature Map playground!
« on: 2024-03-01, 21:35:41 »
Hello Corona-Team,

Are there any potential plans for v12 to fix curvature-related issues?


Best regards

5
Now that almost 80perc. of my materials feature Randomizer and Triplanar, often both in row, that is not nice news. I did want better representation in viewport (just by taking any bitmap in chain), but if it's causing  performance issues now : /

Please check my reply here: https://forum.corona-renderer.com/index.php?topic=41834.msg221045#msg221045

I am sure it was scene/object/material specific, so no worries.
I have bunch of scenes and in 99.9% of them all material are set with Triplanar, MappingRandomizer combination, many of them with CoronaColorCorrect. The mentioned combination is preset for sure. None of them has ever caused slowdowns.

I even, just to be sure, dared to open one of the current production scenes of mine and applied to all objects the mentioned material with bad combination. Guess what - the viewport 40-50fps (heavy scene), with bad combination material is became faster.

So really nothing to worry about. I really believe this was scene specific, as tested and confirmed.

Glad to hear that this is a specific case. At the same time, I feel "lucky" because this scene was a part of my work project that I created in Corona 9. Then, I installed Corona 11 and immediately hit this bug.  :-/
Anyway, I hope you can resolve it.

6
Was this addressed in the recent hotfix? If not, are likely to get a second hotfix?  I'd say a large portion of us are using mapping randomizer.  Removing it just from the BaseColour isn't really a valid option.  I'd say that's the most important map slot for it to be used in.
Yes, it is Corona 11 and Corona 11 HF1 problem.

@Aram Avetisyan
Thanks for creating this thread !

7
Hello Corona team!

Sorry for the delay on my side. I just tested Corona 11 HF1, and the issue I described in Reply #5 is still present.
I have uploaded my scene with a recorded video and created a ticket with ID #197426.

Best Regards

8
Hello Simon Bourgeois,
Thanks for the script!

A small suggestion from me:
Is it possible to add an additional checkbox for selections?
Right now, it works on selected objects and material ID's, which cause limited functionality, especially if some material ID has CoronaLayeredMaterial. If the model is collapsed and consists of many materials in multisub mat- the user need to select id's first.
It would be much more flexible if we had an additional option to choose between selected objects, ID's and selected materials in slate material editor.

Please look at the attachment.

Best regards.

9
@brr @John.McWaters could you guys please contact us about this at https://support.chaos.com/hc/en-us/requests/new and ideally attach a sample scene (with all textures and assets) where this can be reproduced?

Also, if you have Scatter in your scene, it may be the culprit. There was a bug where isolating a Scatter object would cause a massive slowdown. You are describing something a bit different, but maybe it is related to Scatter as well? Just guessing for now.
That issue is fixed in the newest daily, so if you have the time you can test it out: https://forum.corona-renderer.com/index.php?topic=41598.0

Thanks in advance and if we get a sample scene we should be able to fix it or at least find out what is causing the slowdown.

Hello Maru,
I can provide only a stripped-down version of the scene and need to ensure first that the bug will be there. I think I can check it at the end of the week. Regarding the scatter- I have scatterring in the scene, in latest scatter version(from corona 11) - I have uninstalled Corona 11 but left the latest scatter version and have no performance issues with Corona 10 HF3.

Best Rergards


10
[Max] Feature Requests / Re: Tone mapping - Grouping
« on: 2023-12-16, 16:46:40 »
+1.

As an option, it would be great to have the chance to save VFB settings directly in the current presets menu. Of course, with the possibility to change the order, delete, and modify them.

11
UPD: installed Corona 10 HF3:
- when performing alt+W to see all my viewports, max freezes for 1-2 sec (as usual) and overall viewport performance does not drop. So I can continue to work with ~50 FPS[/b]

So the issue would be related to Corona 11? I don't have any particular problem when I display all viewports with Alt+W under Corona 10HF2.

Hi,

I have corrected my original message to be more clear.
With relatively large scenes, it is common to experience a one-time 1-2 second freeze when performing ALT+W, so I described this as normal behavior. With Corona 10HF3, I have no problems with viewport performance at all. After one-time 1-2 second freeze I have my 50 FPS again. With Corona 11 I have 1-3 FPS.

Best Regards

12
I've had 3dsMax get sluggish on me after I do an alt+W to see all my viewports. Before I do that, 3dsMax operates smoothly, even with a complex file. But after I do that, anything I do leads to a 1-2 second lag.

Same here!

I experience an instant and significant performance drop when using "show all viewports." I mainly skipped Corona 10 and installed Corona 11 a few days ago. Yesterday, I opened a relatively simple scene created with Corona 9, then pressed ALT+W (show all viewports). The viewport performance dropped dramatically, in my case, from 50 to 1-3 FPS (CPU usage when rotating viewport goes up to 28%). I tested this on 3ds Max 2022 and 2024 with fresh ENU folders and default viewport texture resolutions.

I took some actions to understand where the problem lies:
-Changing the viewport from perspective to other views in a single window (left top corner) does not result in a performance drop.
-Changing viewport settings and texture resolutions does not help. Even with bounding box mode, I still experience 1-3 FPS.
-Importing the scene into a new one doesn't change the result. The scene is laggy from the beginning.

Currently, I don't have time for further investigations and tests, so I need to revert to the previous version (I will try Corona 10HF3 first) and finish the project.

Best Regards

UPD: installed Corona 10 HF3:
- when performing alt+W to see all my viewports, max freezes for 1-2 sec for one time (as usual) but overall viewport performance does not drop as in Corona 11. So I can continue to work with ~50 FPS





13
[Max] Bug Reporting / Re: Memory leak (Phoenix + Corona)
« on: 2023-12-09, 13:42:04 »
Hi,

This issue is fixed in the latest Phoenix nightly.

You can grab the latest nightly from here: https://nightlies.chaos.com/ If you have trouble accessing this page you can submit a support ticket and they'll give you access.

Cheers,

Rowan

Hello, Rowmanns,

Thank you for the updated information. I have installed Phoenix nightly build (2023-12-08) and started the scene, tested it on the first 60 frames:

- There are no issues with RAM anymore.
- At frame 25, I got Corona NAN error (Corona 11 Final), but the rendering continued fine.
- I rendered until frame 60, closed and reopened the scene to check if the NAN error would appear again.
- There were no more NANs.
- I finished testing up to 60 frames without issues with RAM and NANs.

What do you think? Should I test it a bit more because of the NAN in the first launch?

Best Regards

14
Is it only useful for Animation or does it benefits Single frame images. And which scenario is it much better than Uhd Big windows interior scene vs Standard window interior scene?

I personally use it always: for single images and animations.

15
Hi devs, struggled to find news on this but what's the latest on the 4k Cache? Is it still undergoing development? Is it recommended for use in any particular scenarios over standard UHD Cache?

Cheers,

Hi Alex,

4K Cache has been my default secondary solver since its release in Corona Renderer 6. I remember that, at that time, I was working on a retail store with UHD cache, and the results were good. However, I then experimented and tried 4K on the same camera. I was really impressed by how many "splotches" UHD cache produced in comparison with 4K cache. It was almost invisible if you looked only at the UHD cache result, but very noticeable when you compared them both via VFB history.

In my experience, 4K Cache is also about 10-20% faster in rendering, and it precomputes really fast, which is especially good for animations and gave me trouble only once—I got around 5 frames of my 300-frame animation corrupted. The frames were rendered only partially and had analog film defects..I had to re-render 5 frames with the same settings individually, and the problem was resolved. 4K Cache also works well with the Intel AI Denoiser.

One significant issue with 4K Cache is that you can not get proper results when baking the textures with explicit normals. I have described this issue here:
https://forum.corona-renderer.com/index.php?topic=27953.msg210801#msg210801

Best regards

Pages: [1] 2 3 ... 7