This is the right approach.
If you wait for something to be deprecated before you start working on it,
then you end up like most of the AWT features were broken on latest
operating systems.
Davide
On 15/10/2024 02:50, Marius Hanl wrote:
In my opinion this is a nice change.
Modernizing the Windows backend of JavaFX is a good idea and will also
enable us to use more modern features if needed.
There should be some performance improvements as well.
Even though Direct3d9 works and is not deprecated, I still think it is
good to move on with the technology.
I guess that at one point (when everything is more stable and tested),
the direct3d12 backend will be enabled as the default?
When I have some time, I will check it out as I'm curious myself about
this.
-- Marius
*Gesendet:* Montag, 14. Oktober 2024 um 17:24 Uhr
*Von:* "Lukasz Kostyra" <lukasz.kost...@oracle.com>
*An:* "openjfx-dev" <openjfx-dev@openjdk.org>
*Betreff:* JavaFX Direct3D 12 rendering pipeline for Windows
Hello openjfx-dev,
we just pushed a prototype of a new JavaFX Direct3D 12 rendering pipeline
for Windows to a new "direct3d12" branch on jfx-sandbox. It is more
than an
experiment branch - we intend to fully develop the D3D12 backend there.
We're not necessarily looking for contributions at this point, but if
anyone
has early feedback about it or wants to try it by building it themselves,
that would be fine. We also did not test it on a wider range of
hardware, so
your mileage may vary. While D3D12 pipeline will build by default, D3D9
pipeline is still the default pick at runtime. To run anything on D3D12
pipeline you need to force it with ex.:
java -Dprism.order=d3d12 ...
Backend supports 2D rendering (albeit with some graphical issues here
and there
that need to be ironed out) and basic 3D rendering. Expect not
everything fully
working yet (ex. some gradients on 2D controls are incorrect, or
3D-in-2D will
straight up not work) and the performance not matching D3D9 yet. Our
goal is to
first reach feature completion and then focus on performance.
Lukasz