GPU Rendering | PC | Rounded Edges Stop Rendering at Distance

#1

Hello!

I have an odd issue where rounded edges stop rendering at a certain distance (depends on camera FOV and focal length settings). Since I am animating in this case, I can’t avoid that critical distance and the effect of seeing the rounded edges disappear during a camera move is jarring (at least to me).

I’ve attached a static image that shows this happening mid-frame - you can actually see the hard line between rendered rounded edges and unrendered.

This does not happen in CPU mode, and this issue (perhaps a bug?) is really making life difficult for me as I try to complete some animations under deadline.

I have done a search for related topics, but have not found this issue posted here (the closest was the rounded edges option simply not presenting itself as available). Any ideas?

Here are some important details:
Keyshot v12.2.2 (Build 4) [4.9.2]
Velocity-built ProMagix HD80A
Processor AMD Ryzen Threadripper 2990WX
RAM 64 GB
GPU RTX 3090 Ti (latest Studio Driver installed: v546.33)

83
Spike Series Enclosures.83.jpg1920×1080 279 KB

#2

Here is a version of the scene with all NDA stuff removed. I’ve saved the camera at the exact distance where the rounded edges stop rendering on the subwoofer grille.

GPU Rounded Edge.ksp

Here is what the scene should look like upon opening (if you have the same issue I do)…

84
GPU Rounded Edges.84.jpg1920×1080 147 KB

#3

@dan.spore that’s really odd. It’s almost like some moiré kind of thing. I noticed that if I made the round corners 0.025 inch instead of 0.02 inch it doesn’t appear in your animation anymore. Bit of a non-solution maybe.

I also tried to give the mesh different/new normals on a 25 degree angle and do a round corners afterwards again but that didn’t help. When I used 0.021 as round corner value it seemed solved but the issue just appeared a bot later in the time line.

I didn’t saw the issue on opening the file but for those who want to try, it appears from 6.5s - 7s in the timeline of the animation.

#4

Hi, @oscar.rottink - thank you for digging into this - I know you enjoy puzzles. It is odd indeed. I’ll play around with different corner radii and see if I can come to a workable comprimise.

#5

I might try a bit more tomorrow. I didn’t actually checked if the scale/size of the object is correct but I would say so since 0.02 is not a really weird value to have for such surfaces.

I’m actually at the same drivers as you but since the 2024 beta gives issues I will revert to drivers from October tomorrow morning and see if that will make a difference. But I don’t think this is a driver thing.

Like you say, it’s like it stops at a certain distance. I did used rounded corners on meshes like this in the past and never noticed something like this but have some things I can still try after some sleep that is.

#6

I’ve tried a few more things but without result

  • Reverted Studio Drivers to 537.58
  • Re-tesselated the object to ± 10% of the original triangles
  • Actually scaled the item outside KeyShot in 3D software so it wasn’t used on such a small scale inide KeyShot (0.0394) I thought that might give issues as well.
  • Loading scene in the 2024.1 Beta gives the same result

I’m not sure what’s going on here, I’ll report it as bug but maybe it helps if you open a support ticket as well. @philip.rasmussen do you know what can cause this?

#7

@oscar.rottink -

I really appreciate you exploring this further. You’ve gone down some paths I suspected as well and I am grateful you have made time to do so - this is so helpful. I have indeed opened a ticket and cross-referenced it with this thread.

Thanks, again!

1 Like
#8

Just an update for anyone following this thread. Luxion support have escalated this issue to the devs. I’ll post any updates as they come along.

1 Like
#9

That’s good to hear Dan! Helps a lot if people who’ve issues are able to provide a sample scene. I know that’s not always easy because of NDAs but big help for the devs and makes KS better every time.

#10

A brief update for anyone following this thread. Luxion support have come back and reported that the devs have indeed replicated this issue and identified it as a bug. I shall be resolved in an upcoming release (hopefully soon).

Thank you again, @oscar.rottink, for your thorough investigation and interest. You make communities like this a joy to engage with.