JDK-8097158 : [Ensemble] Graphics3D Audio Visualizer showing lines instead of rect
  • Type: Bug
  • Component: javafx
  • Sub-Component: graphics
  • Affected Version: 8
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2013-07-23
  • Updated: 2015-06-12
  • Resolved: 2014-11-14
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.
JDK 8
8u40Resolved
Related Reports
Duplicate :  
JDK-8093566 - [3D] Shapes can be very blurry in 3D rotations if not started in the 2D plane
Relates :  
JDK-8108358 - Prism: no antialiasing when rendering shapes with a 3D transform
Relates :  
JDK-8089602 - Graphics3D Audio Visualizer is noticably slower compared to pre JavaFX 8.0
Relates :  
JDK-8088013 - Bleeding Edges - Background Bleeding on Shared Edges for 3D Multi-Polygon Configurations
Description
See attachment.
Comments
This bug was exposed (not introduced) by the removal of the tessellator but not because of the problems with antialising the edges. Rather, the problem is that when we started rendering the 2D shapes directly (without the tessellator), we ran into the same caching bug -- RT-39120 -- that was causing blurriness in some other cases. We verified that the fix for RT-39120 has fixed this bug.
14-11-2014
This should be retested once the fix for RT-38063 is ready. I think this bug can be closed as a duplicate of that one.
13-11-2014
The change for RT-5534 went into b100.
09-11-2013
This bug is the result of an intentional change in behavior to fix RT-5534. A solution to this will require new rendering algorithms for mixing 2D and 3D, which is new feature work that is out of scope for FX 8. Reverting the change to RT-5534 would not be feasible, even if we felt that was an acceptable solution.
09-11-2013
I can not understand. If it's a regression, than from what build, relaese?
01-11-2013
This will take additional rendering work to resolve which is out of scope for FX 8.
30-10-2013
This is probably due to the fix for RT-5534 which has changed the rendering of 2D primitives with a 3D transform so that it renders using antialiasing. Assign to Chien to verify.
05-08-2013