to call APIs that it
exposes. But, all that is still not a priority for this backend right now - we
might take a look at it later down the line.
Lukasz
From: Nir Lisker
Sent: Thursday, 17 October 2024 18:33
To: Lukasz Kostyra
Cc: openjfx-dev
Subject: Re: [External] : Re: JavaFX Direct
d be to access a D3D12 backend
> DLL we create (so basically accessing current prism_d3d12.dll but with FFM
> and not JNI). But it is something that we can explore in the future, for
> now I think there are more higher-priority tasks related to this backend.
>
>
>
> Lukasz
>
can explore in the future, for now I think
there are more higher-priority tasks related to this backend.
Lukasz
From: Nir Lisker
Sent: Tuesday, 15 October 2024 14:28
To: Lukasz Kostyra
Cc: openjfx-dev
Subject: [External] : Re: JavaFX Direct3D 12 rendering pipeline for Windows
This is exciti
This is exciting news!
I looked at the code quickly. Here are my thoughts.
My biggest remark is that JNI is still being used, which is being more and
more restricted. Recently, Kevin announced that we will be FFM-ready,
surely by the time this pipeline is released. I would like to see (and can
he
D3D9 is 20 years old (even if it's still getting updated) and graphic cards
aren't optimized for it. Computer Graphics is an area where the coupling of
hardware and software is much stronger than what Java developers are used
to with its abstractions over hardware, and modern graphics hardware
assu
support-for-directx-9-from-arc-and-xe-graphics/
[3] - https://www.microsoft.com/en-ie/download/details.aspx?id=8109
-Original Message-
From: openjfx-dev On Behalf Of Michael Strauß
Sent: Monday, 14 October 2024 18:50
Cc: openjfx-dev
Subject: Re: JavaFX Direct3D 12 rendering pipeline
Hi Lukasz!
What is the reason for doing this? Direct3D 9 is not going away on
Windows. Are there any new features that will be enabled by the
Direct3D 12 backend? Having two backends for Windows seems to be twice
the maintenance burden.
On Mon, Oct 14, 2024 at 6:10 PM Lukasz Kostyra
wrote:
>
> H
