1
[Max] Resolved Bugs / object transform bug during IR
« on: 2025-05-04, 11:27:39 »
Hi, check video. I encountered that few times already, seems like few last versions affected.
2025-07-06, 16:34:48
News:
Having trouble verifying your license? If you are seeing a license verification message or are unable to access your Chaos products, please follow these simple steps to fix sign-in issues. If you have already tried this and are still unable to access your Chaos products, please contact Support.
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.
Pages: [1] 2
2
[Max] Bug Reporting / corona slicer bug
« on: 2025-02-11, 21:51:05 »
Hi, an old problem, I encountered it for the first time quite a while ago, but this time I managed to isolate it
screenshot 1 - geometry
screenshot 2 - bug, slicer object is a single mesh combined from 1972 cylinders
screenshot 3 - the correct result, 1972 cylinders as separate objects
I had such problems with different scenes with different geometry, one of the cases - terrain exported from gaea. I used a box to cut a "tunnel" inside and it was visible through all scene geometry. I believe the core of the problem is the same.
Scene attached.
And by the way is it possible to add a mode change to the slicer? Subtraction/intersection
screenshot 1 - geometry
screenshot 2 - bug, slicer object is a single mesh combined from 1972 cylinders
screenshot 3 - the correct result, 1972 cylinders as separate objects
I had such problems with different scenes with different geometry, one of the cases - terrain exported from gaea. I used a box to cut a "tunnel" inside and it was visible through all scene geometry. I believe the core of the problem is the same.
Scene attached.
And by the way is it possible to add a mode change to the slicer? Subtraction/intersection
3
[Max] Bug Reporting / refractive+round edges+curtter = huge slowdown
« on: 2024-11-09, 22:45:57 »
Hi,
setup - "glass" object (green on screenshot), "liquid" object intersecting "glass" with round edge map in bump slot (blue) to add capillarity effect, copy of "glass" with push modifier with a small negative value and a cutter material applied to match glass walls, included "liquid" only (red).
Render time to 1% noise
1. glass+liquid - 21s
2. glass+liquid+round - 36s, 1.7 times slower
3. glass+liquid+cutter - 49s, 2,33 times slower. This is a question by itself - using cutter material gives a significant slowdown.
4. glass+liquid+round+cutter - 249s, 11,8 times slower???
3 - is it expected behavior with cutter and such slowdown? I encountered a noticeable slowdown many times in absolutely different scenes + a bug when a cut object was visible through all scene geometry despite obstacles between it and the camera (but that's another story and I'll report it next time when/if I catch it).
4 looks like a bug.
setup - "glass" object (green on screenshot), "liquid" object intersecting "glass" with round edge map in bump slot (blue) to add capillarity effect, copy of "glass" with push modifier with a small negative value and a cutter material applied to match glass walls, included "liquid" only (red).
Render time to 1% noise
1. glass+liquid - 21s
2. glass+liquid+round - 36s, 1.7 times slower
3. glass+liquid+cutter - 49s, 2,33 times slower. This is a question by itself - using cutter material gives a significant slowdown.
4. glass+liquid+round+cutter - 249s, 11,8 times slower???
3 - is it expected behavior with cutter and such slowdown? I encountered a noticeable slowdown many times in absolutely different scenes + a bug when a cut object was visible through all scene geometry despite obstacles between it and the camera (but that's another story and I'll report it next time when/if I catch it).
4 looks like a bug.
4
[Max] Bug Reporting / Hidden tyFlow object perfrom simulation on render stop with Corona only
« on: 2024-10-29, 22:06:20 »
Hi,
problem - clean scene, simple tyFlow object is hidden (as simple as birth operator only, so it won't render anyway), changing frame to let's say 50 doesn't perform simulation, starting render (interactive or production) as well doesn't perform simulation, but when I stop or cancel render, tyFlow start simulation up to current frame (50).
Tyson said
I tried Arnold and Scanline - no sim on render end, so probably some problem with Corona?
problem - clean scene, simple tyFlow object is hidden (as simple as birth operator only, so it won't render anyway), changing frame to let's say 50 doesn't perform simulation, starting render (interactive or production) as well doesn't perform simulation, but when I stop or cancel render, tyFlow start simulation up to current frame (50).
Tyson said
Quote
tyFlow objects simulate their result when Max queries their base object for a result...
Quote
hiding a tyFlow object does not guarantee Max will never query it.
I tried Arnold and Scanline - no sim on render end, so probably some problem with Corona?
5
[Max] Bug Reporting / refractive/non-refractive intersection (contact line) bug
« on: 2024-08-28, 11:44:37 »
It's an old problem, I reported it years ago, but it is still not fixed - black contact line between "water" and "ground"
render and scene attached
render and scene attached
6
[Max] Bug Reporting / Corona 13 Color management problem
« on: 2024-08-23, 11:09:07 »
Hi, the image saved from a VFB looks different when color management is set to OCIO.
Display/View-Transform is enabled (obviously without it images are dark).
So, if max saves images or from native max VFB - all ok, but if I save it from VFB 2.0 or 1.0 - looks wrong. It seems like a few months ago all worked fine - I worked on a project in March and everything was fine (or I didn't notice the difference that time...)
The next one is probably max problem, but just to ask. Same settings:
2024 renderoutput - save png and exr exactly as in VFB.
2025 renderoutput - save png but not exr, exr is dark, it seems like it skips conversion.
Is it max problem or can be something you can fix?
Latest Corona daily.
Display/View-Transform is enabled (obviously without it images are dark).
So, if max saves images or from native max VFB - all ok, but if I save it from VFB 2.0 or 1.0 - looks wrong. It seems like a few months ago all worked fine - I worked on a project in March and everything was fine (or I didn't notice the difference that time...)
The next one is probably max problem, but just to ask. Same settings:
2024 renderoutput - save png and exr exactly as in VFB.
2025 renderoutput - save png but not exr, exr is dark, it seems like it skips conversion.
Is it max problem or can be something you can fix?
Latest Corona daily.
7
[Max] Bug Reporting / single object multi/sub-obect absorpiton (refraction) problem
« on: 2024-02-19, 14:23:13 »
Hi,
looks like it's a very old problem but I thought it was fixed?
"liquid" inside "glass" works fine if it's 2 separate objects, but as soon as I attach them into a single - I'm getting result as on the screenshot.
Same materials, left side is separate objects, right side single object.
Top 4 - "liquid" without absorption
Bottom 4 - "glass" without absorption
looks like it's a very old problem but I thought it was fixed?
"liquid" inside "glass" works fine if it's 2 separate objects, but as soon as I attach them into a single - I'm getting result as on the screenshot.
Same materials, left side is separate objects, right side single object.
Top 4 - "liquid" without absorption
Bottom 4 - "glass" without absorption
8
[Max] Bug Reporting / Corona Bitmap Color space/RGB primaries not working properly
« on: 2024-02-12, 13:53:04 »
Or maybe I'm doing something wrong?
Screenshot is attached
Changing RGB primaries in corona bitmap has a subtle, almost unnoticeable effect. 3dsmax bitmap working as expected by selecting color space during load (those settings not affecting corona bitmap).
Latest daily build
Screenshot is attached
Changing RGB primaries in corona bitmap has a subtle, almost unnoticeable effect. 3dsmax bitmap working as expected by selecting color space during load (those settings not affecting corona bitmap).
Latest daily build
9
[Max] Resolved Bugs / CoronaPattern not receiving caustics
« on: 2023-02-06, 13:39:17 »
Nothing to explain - seems like caustics don't see the pattern.
10
[Max] Resolved Bugs / Corona slicer not working with single-sided geometry
« on: 2022-01-24, 17:33:14 »
Check images, same scene, just different camera rotation. Such behavior was in all previous versions.
11
[Max] I need help! / PhoenixFD Ocean texture + Corona decal
« on: 2021-12-16, 23:28:25 »
The height parameter in ocean texture set to vector mode is ignored if corona decals are added to this object.
12
[Max] Bug Reporting / Aerial perspective produces the wrong result in some situations
« on: 2021-12-14, 19:24:31 »
All simple, check the images.
Top view, corona camera, not orthographic. Render with default corona material as override and volume effect 10 - increased to see result better.
The second image with greatly increased contrast in PS to see where that volume effect produces the strongest result.
Additionally - not sure but seems like in some situations it produces the wrong color, like in a clean scene with sun and default corona material as override - adding volume effect gives some red/purple tint to the scene.
The above is true for at least a few latest DB.
And few questions:
1. aerial perspective still not working with volumetrics, will that be fixed in some nearby future?
2. is it possible to make it true volumetric (checkbox to switch between shader and volumetric)? Or maybe it'll be even if we can plug some map into volumetric material scattering/absorption.
Top view, corona camera, not orthographic. Render with default corona material as override and volume effect 10 - increased to see result better.
The second image with greatly increased contrast in PS to see where that volume effect produces the strongest result.
Additionally - not sure but seems like in some situations it produces the wrong color, like in a clean scene with sun and default corona material as override - adding volume effect gives some red/purple tint to the scene.
The above is true for at least a few latest DB.
And few questions:
1. aerial perspective still not working with volumetrics, will that be fixed in some nearby future?
2. is it possible to make it true volumetric (checkbox to switch between shader and volumetric)? Or maybe it'll be even if we can plug some map into volumetric material scattering/absorption.
13
[Max] Resolved Bugs / black edge + opacity bug in refractive material
« on: 2021-07-22, 21:08:38 »
1. Black edge where object with refractive material contacts other geometry - image attached.
2. Setting opacity to 0 makes fog like material.
On the second image water material have opacity 0, but underneath surface have blue color.
The third image is a preview but the sphere is still barely visible.
Both problems appear on physical and legacy materials.
Corona V7.
2. Setting opacity to 0 makes fog like material.
On the second image water material have opacity 0, but underneath surface have blue color.
The third image is a preview but the sphere is still barely visible.
Both problems appear on physical and legacy materials.
Corona V7.
14
[Max] Resolved Bugs / Huge slowdown when using corona distance
« on: 2021-02-09, 13:26:31 »
I have few materials. When applied to object separately speed ranging 7-14M. When mixed in multilayer material with corona distance - speed is 700k +/-
Same problem with opacity. I have a landscape model + a lot of buildings with pools. Bottom of pools below ground level - instead of cutting geometry I used corona distance to cut it during render - speed dropped twice.
Maybe that's correct behavior with opacity, but 10 times slowdown with mixing materials looks strange.
Same problem with opacity. I have a landscape model + a lot of buildings with pools. Bottom of pools below ground level - instead of cutting geometry I used corona distance to cut it during render - speed dropped twice.
Maybe that's correct behavior with opacity, but 10 times slowdown with mixing materials looks strange.
15
[Max] Resolved Bugs / Moving VDB volume in interactive very slow + bounding box visible
« on: 2021-02-09, 13:16:36 »
Nothing to explain here - moving vdb or changing settings very slow, looks like reload each time
And the problem with the visible bounding box still here - with global volume or inside/intersecting with another object with volume mtl.
And the problem with the visible bounding box still here - with global volume or inside/intersecting with another object with volume mtl.
Pages: [1] 2