<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
This is the right approach. <br>
If you wait for something to be deprecated before you start working
on it, <br>
then you end up like most of the AWT features were broken on latest
operating systems.<br>
<br>
Davide<br>
<br>
<div class="moz-cite-prefix">On 15/10/2024 02:50, Marius Hanl wrote:<br>
</div>
<blockquote type="cite"
cite="mid:trinity-1f2bee30-eaa4-4da0-bcad-d0fffd02ce2b-1728953411069@3c-app-webde-bap23">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div style="font-family: Verdana;font-size: 12.0px;">
<div>In my opinion this is a nice change.</div>
<div>Modernizing the Windows backend of JavaFX is a good idea
and will also enable us to use more modern features if needed.</div>
<div>There should be some performance improvements as well.</div>
<div><br>
Even though Direct3d9 works and is not deprecated, I still
think it is good to move on with the technology.</div>
<div>I guess that at one point (when everything is more stable
and tested), the direct3d12 backend will be enabled as the
default?</div>
<div>When I have some time, I will check it out as I'm curious
myself about this.</div>
<div> </div>
<div>-- Marius</div>
<div>
<div>
<div name="quote"
style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b> Montag,
14. Oktober 2024 um 17:24 Uhr<br>
<b>Von:</b> "Lukasz Kostyra"
<a class="moz-txt-link-rfc2396E" href="mailto:lukasz.kostyra@oracle.com"><lukasz.kostyra@oracle.com></a><br>
<b>An:</b> "openjfx-dev" <a class="moz-txt-link-rfc2396E" href="mailto:openjfx-dev@openjdk.org"><openjfx-dev@openjdk.org></a><br>
<b>Betreff:</b> JavaFX Direct3D 12 rendering pipeline
for Windows</div>
<div name="quoted-content"><!--p.MsoNormal, li.MsoNormal, div.MsoNormal {
margin: 0.0cm;
font-size: 11.0pt;
font-family: Calibri , sans-serif;
}
span.EmailStyle17 {
font-family: Calibri , sans-serif;
color: windowtext;
}
*.MsoChpDefault {
font-family: Calibri , sans-serif;
}
div.WordSection1 {
page: WordSection1;
}
-->
<div>
<div class="WordSection1">
<p class="MsoNormal">Hello openjfx-dev,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">we just pushed a prototype of a
new JavaFX Direct3D 12 rendering pipeline</p>
<p class="MsoNormal">for Windows to a new
"direct3d12" branch on jfx-sandbox. It is more
than an</p>
<p class="MsoNormal">experiment branch - we intend
to fully develop the D3D12 backend there.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">We're not necessarily looking
for contributions at this point, but if anyone</p>
<p class="MsoNormal">has early feedback about it or
wants to try it by building it themselves,</p>
<p class="MsoNormal">that would be fine. We also did
not test it on a wider range of hardware, so</p>
<p class="MsoNormal">your mileage may vary. While
D3D12 pipeline will build by default, D3D9</p>
<p class="MsoNormal">pipeline is still the default
pick at runtime. To run anything on D3D12</p>
<p class="MsoNormal">pipeline you need to force it
with ex.:</p>
<p class="MsoNormal"> java -Dprism.order=d3d12 ...</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Backend supports 2D rendering
(albeit with some graphical issues here and there</p>
<p class="MsoNormal">that need to be ironed out) and
basic 3D rendering. Expect not everything fully</p>
<p class="MsoNormal">working yet (ex. some gradients
on 2D controls are incorrect, or 3D-in-2D will</p>
<p class="MsoNormal">straight up not work) and the
performance not matching D3D9 yet. Our goal is to</p>
<p class="MsoNormal">first reach feature completion
and then focus on performance.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Lukasz</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>