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

Pages: 1 [2] 3 4 ... 14
16
I think it would make most sense to load B&G calculations on GPU, leaving CPU all available for rendering.

+1 I think it's very slow in most of our scenes even though we have 3990X cpu in the workstations. Often I click it off to compare, but feel it doesn't react, then click again and apparently there was just a lag, so I ended up turning it on again ;)

So having the GPU do this would maybe make it snappier also just the calculation?

Or maybe a setting to only recalculate bloom+glare pr X pass rendered so it will be easier/snappier to turn on/off and compare. Now it needs to calculate everytime you turn it off/on.

A bonus thing to this we would love was for corona to be able to keep the bloom and glare on the entire image after we have done a region render on an already completed render. I.e. "clear VFB" is turned off, we see a small thing that needs to be rerendered. We do a region and then cry that bloom and glare is now only on that region and we have to rerender entire image once again :)

17
[Max] Feature Requests / Re: Region improvements
« on: 2022-11-23, 16:15:39 »
i just want some sort of lasso tool to draw my own regions to render instead of having to try and block out with square regions ;)

18
Place a slicer object around the camera, linked to the camera so it moves with it. That way the camera will always be "outside" the volume object (as there will be a sliced away external face the camera is looking at), and that way you can fly through a volume object.

Is there a guide to this? Found an old link to freshdesk from Maru way back, but I can not access that page? Our login only seem to work to the Chaos support login and I can't find any article regarding that there?

Hi, if you're referring to the slicer article, it has been moved here: https://support.chaos.com/hc/en-us/articles/4956761514897-How-to-use-the-Corona-Slicer-Material-3ds-Max

I can't get the slicer material to work with the camera being inside corona vol grid object (cloud). It works (slices the vol grid) if camera is outside the grid, but that is not the point at all - am I doing something wrong?

Just made a sphere, applied slicermtl to the sphere and placed it on camera pivot point. Tried to have the sphere in different sizes without any effect (when the camera is inside the cloud).

19
Place a slicer object around the camera, linked to the camera so it moves with it. That way the camera will always be "outside" the volume object (as there will be a sliced away external face the camera is looking at), and that way you can fly through a volume object.

Is there a guide to this? Found an old link to freshdesk from Maru way back, but I can not access that page? Our login only seem to work to the Chaos support login and I can't find any article regarding that there?

20
Hi guys

I'm currently experimenting with corona vol objects (cloud vdb's scaled up many times) to get to a specific mood/look with great effect, but scene performance and scene parsing quickly becomes horrible (even on a threadripper 3990X). While increasing step size of the volumes and overall tweaking help on render performance, I still get 30-50sec of scene parsing per frame. Is it still only the saving of 4k/uhd cache that can speed this up for the final animation?

Also, is there anything in the works that would allow cameras to be placed in or pass through vol objects? It's very limiting doing animations and not have the camera touch the vol objects as it will then just disappear + i still see some "boxing/edges" of volumes overlapping (daily v9 RC2).

21
Hi,

To everyone experiencing the issue with corrupted textures, could you send me the following to https://upload.chaos.com/u/manns@corona-renderer.com

  • The name of the map which has the problem
  • The texture stats file which is located here: "C:\Users\USERNAME\AppData\Local\CoronaRenderer\textureStats.csv"
  • If possible the texture cache itself: "C:\Users\USERNAME\AppData\Local\Temp\CoronaRenderer\ImageTextureCache"
  • And lastly the scene if possible.

Thanks for your patience and help with diagnosing this issue :)

Rowan

Will do this next time the bug happens :)

22
Noticed that the Tone Mapping in the framebuffer seems to reset in my scene. Has happened a couple of times now when I open the scene, start the interactive render and wonder why it just renders white - then notice Tone mapping settings has reset to the default ones and all values to default too - any one else?
RC2 build, max 2023.

23
haven't altered that location no, didn't even know that option excisted :) Just checked, it's same as yours with users/appdata etc

Seems to happen after working in the max file for a couple of hours. Attached is the result. Some bitmaps seem to still read okay, but most of them load black. Restarting max resolves the problem.

Seems to only happen to CoronaBitmap nodes. Not the standard max ones.

24
hello i had a similar issue but when I opened the effects tab I found a tremendous amount of "brightness & contrast" added and i cant seem to know how to delete them all at once there's no option of selecting multiple by pressing shift or cntrl

Just had same issue, you can delete them all with the fee Sini Forensics plugin :)

25
Hi,

Is everyone experiencing this using dropbox to store their maps?

Thanks,

Rowan

No, but maps are on network drive. (Can't send you scene as it's under a heavy NDA). It's hard to recreate as it seems to happen randomly.

26
I've found a very weird problem in Corona R3. Some images are loaded totally off when using Corona Bitmap. They look Ok when loaded using Max standard bitmap though. Any idea what's going on?

I'm having issues with this too in RC1. So far it's only happened with Forestpack objects. I.e. loaded in trees. Turned them to proxies. Scatter with FP. Initially all renders fine. But later on it seems to "corrupt" the coronabitmap nodes. So They only load black bitmaps. I tried "reload" bitmap, remove and make new corona bitmap, but still black. Also tried to merge in the same tree and tell it to "use merged material", but still black corona bitmap.

The scene was sent to a render node that rendered it fine, and the problem seems to go away after restarting 3ds max and reopening the scene. So to it looks to be something corrupting going on in the single 3ds max instance.

27
Have you tried Collect Assets 2.0?

Wanted to give it a try, but doesn't seem to support max 2022/23.

28
Hi guys

Anyone else having issues when archiving projects and the scene has corona proxies?

I've tried both the Sini tools archive function and with 3ds max native one. More often than not, it will either completely skip some of the corona proxies in the scene or it will keep the position and just leave an empty corona proxy that we then have to relink manually - not always easy because of the auto naming when making a proxy and we don't rename then ;)

This happens to us in different projects, different proxies (max 2020, max 2022, max 2023, corona 8 and corona 9 dailies). Mostly it's proxies that are linked locally on the workstation.

29
ha! Was about to post this as a bug too. Happens to me too in max 2023 with corona 9 daily. Box, wireframe and point cloud works fine, but trying to show mesh while autokey is on, just shows a wireframe box.

Can we look into this behaviour? It's quite annoying when trying to animate polygon heavy objects made to proxies as point clouds most of the time, but then to control it rotates or lands/don't hit anything, I want to switch to full mesh preview real quick and it doesn't work and interrupts the workflow having to switch back to pointcloud, turn off autokey, show full mesh, then autokey again etc.

30

Hi,

If you have a repro scene, I'd appreciate it. I will PM you a link to upload the files to me.

Cheers,

Rowan

I tried to recreate this in a new scene with exactly the same setup of proxies etc, but IR works fine here. It's only in the other max file the issues persist, so I will just continue work in the new file. Very odd.

*UPDATE* So just working for half an hour or so on the scene suddenly the IR performance went laggy again. But only with the simple FP object visible. I haven't added or changed anything, just moved camera around to find views. If I keep orbiting around with the camera (or just in perspective view) with FP visible, it freezes exactly every 3 seconds for exactly 3 seconds, then continues to orbit/move whatever I do for 3 seconds, freezes for 3 seconds. Repeat.

**UPDATE 2**
Disabling the "Limit to visibility" under Camera in the FP object fixed the IR issue - isn't this an old issue now I come to think of it?

Pages: 1 [2] 3 4 ... 14