Nurgeldi Dovletov

Hi 安娜!

Cascade Margin is used only to get rid of artifacts (it happens mostly with objects with stretched or simply large polygons, for example in tall objects). If you set a large value, the speed and quality of the shadows will decrease a bit due to the accuracy of the depth buffer (floating-point precision) rather than the resolution of the shadow map itself.

If you increase the distance of the light source, it will not have much effect, because Verge3D in 3ds Max automatically calculates the optimal distance depending on the size of the scene when exporting (this was very convenient before the current cascaded shadow maps were introduced).

You may not notice the effects of adjusting the Cascade Margin because the optimal light distance is automatically calculated to minimize shadow issues. However, sometimes this can compromise shadow quality as a trade-off.

We will probably change this soon to give users more control over shadow optimization in 3ds Max.

• This reply was modified 2 months, 1 week ago by Nurgeldi Dovletov.
• This reply was modified 2 months, 1 week ago by Nurgeldi Dovletov.

Hello
It seems that the Margin is too large and/or ESM Bias is not configured correctly.
To better understand the problem, could you please provide a minimal version of the scene where the problem persists?

1. Set keyframe tangents to linear for all baked animations, it should solve the problem.

2.

When i tried to path contrain them (on 2 different paths), no animation was playing but the manual rotation keys i added. This is why i bake the animation from helper.

This issue occurs because the path constraint could not be exported (exporter cannot find the curve object). The messages in 3ds Max console:

V3D-WARNING: Can not export animation of Path Constraint for Point001
V3D-WARNING: Can not export animation of Path Constraint for Point002

To solve it – simply convert your Freehand to Spline curve:

The reason for this is the unusual structure of object. This is how it usually should look:

Hope this helps

• This reply was modified 11 months, 1 week ago by Nurgeldi Dovletov.
• This reply was modified 11 months, 1 week ago by Nurgeldi Dovletov.

Hi,

• try adjusting the bias parameter
• try decreasing the Falloff/Field parameter
• select a different shadow filtering type to check if the error persists

Also recommend checking out this section

Sorry, I got it wrong, it was indeed a bug with Vertical viewport fit, the fix will be available in the next pre-release.

Hello!
As said here, “The FOV value of physical cameras describes the horizontal opening.”, after checking it seems to be true, so for the physical cameras viewport fit should be set to “Horizontal”.
If that didn’t help in your case, could you please provide a minimal file that reproduces the problem?

Hello!
Unfortunately, it is unhandled case, internal bug for v3d.WebGLOITRenderer, it does not support changing pixel density on canvas, for now I recommend not changing screen resolution with OIT, I think it will be fixed soon.