JDK-8099886 : Prism (es2 or d3d): Visually noticeable rendering techniques are used when shape switched from 2D to 3D transformation matrix.
  • Type: Sub-task
  • Component: javafx
  • Sub-Component: graphics
  • Affected Version: fx1.3
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2009-08-26
  • Updated: 2015-06-16
  • Resolved: 2010-11-04
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
fx2.0Resolved
Related Reports
Relates :  
JDK-8098881 - Support 3D perspective transforms for existing 2D JavaFX objects
Relates :  
JDK-8108358 - Prism: no antialiasing when rendering shapes with a 3D transform
Description
The use of visually noticeable rendering techniques (Shader vs. Tessellated shape) when shape switching from 2D to 3D transformation matrix can be an issue for application. This only true to Prism stack with es2 or d3d pipe. Shader is used to render shape with 2D transform, but it is replaced with tessellated shape rendering when the shape has a 3D transformation matrix applied to it. Shader produces better rendering quality than tessellated shape.
Comments
Solving RT-5534 would also fix this problem.
04-11-2010
Loop-Blinn's curve rendering technique is likely out of scope for Presidio. We may look into using multisampling support in the HW. Reduce Origial Estimate from 4w to 1w.
29-09-2010
This feature requires investigation on implementation technique. Depending on our approach, this can possibly be a research project. May need to consider Loop-Blinn's curve rendering technique.
05-02-2010
We may need to address this for soma, possibly by having a sticky flag in each node such that once it is rendered with a 3D transform, then it will always be rendered by tessellation even if the transform switched back to 2D temporarily. Better solutions should be explored.
09-09-2009