Hello all,
I've been investigating the reason behind some rendering issues in LDCad.
Very noticeable in e.g 2345p04.dat
renderIssue.png (Size: 22.51 KB / Downloads: 26)
I'm suspecting it comes from the single type 2 lines overlapping multiple triangle/quad edges.
I know this is more of a rendering engine problem then an authoring problem, but I would like to make a case for dividing such edges into segments so they connect with each polygon on the edge.
This because it makes smoothing easier as you can then use edge lines to determine when to average a group of normals.
This is demonstrated in the rendering issue of LDCad as its smoothing algorithm will break normals into groups based up on the fact a point is also used for a type 2 line
A condition which fails for all polygons touching the side or part 2345p04, hence the 'crumbled' paper look.
I could probably fix it, but it would take a whole lot op processing power and administration to try and find all points touching a type 2 line.
Any thoughts on this?
I've been investigating the reason behind some rendering issues in LDCad.
Very noticeable in e.g 2345p04.dat
renderIssue.png (Size: 22.51 KB / Downloads: 26)
I'm suspecting it comes from the single type 2 lines overlapping multiple triangle/quad edges.
I know this is more of a rendering engine problem then an authoring problem, but I would like to make a case for dividing such edges into segments so they connect with each polygon on the edge.
This because it makes smoothing easier as you can then use edge lines to determine when to average a group of normals.
This is demonstrated in the rendering issue of LDCad as its smoothing algorithm will break normals into groups based up on the fact a point is also used for a type 2 line
A condition which fails for all polygons touching the side or part 2345p04, hence the 'crumbled' paper look.
I could probably fix it, but it would take a whole lot op processing power and administration to try and find all points touching a type 2 line.
Any thoughts on this?