On 5/18/2018 10:45 AM, Matthew Elliot wrote:
Hey Anirvan,
Thanks for the info - guess it’s not such a promising route either then.
As these Jira for Matrox cards in JavaFX were from 2013 is it possible that
later Matrox cards / drivers would now work if this global disablement was not
present. I.e is forceGpu enough to test such scenarios?
Trying newer cards with forceGPU would be a good first step.
Or would I need to create another bug report for investigation at Oracle?
If you find that this works consistently on newer Matrox cards, then you
can raise a new bug for this, although it isn't something we are likely
to work on ourselves. The challenge would be in testing this, since
Matrox cards are not readily available.
To the wider group, has anyone else outside Oracle contributed code dealing
with supporting graphics cards?
Would something like implementing a workaround for whatever deficiency is
present (pixel shaders?! from comments in Bug reports) even be possible /
practical?
We've done this is a very limited way in the past for issues that
affected all Intel HD cards, for example.
Good luck with your investigation.
-- Kevin
Theoretically this could become an interesting topic for my company if a few
percent of our users have these types of cards (which is possible) and it could
be useful to the wider community.
Kind regards,
Matt
Sent from my phone.
On 18/05/2018, at 7:09 PM, Anirvan Sarkar <powers.anir...@gmail.com> wrote:
Hi Matthew,
OpenGL pipeline on Windows is not a supported configuration and so it is not
present in JavaFX for Windows[1][2].
You would have to build JavaFX yourself to include this pipeline and "use it at your
own risk". It may or may not work.
Also it looks like the card should support OpenGL 2.1 or later[3].
[1]:
http://hg.openjdk.java.net/openjfx/jfx-dev/rt/file/071b040b8736/build.gradle#l478
[2]: http://mail.openjdk.java.net/pipermail/openjfx-dev/2014-July/014936.html
[3]:
http://hg.openjdk.java.net/openjfx/jfx-dev/rt/file/071b040b8736/modules/javafx.graphics/src/main/native-prism-es2/windows/WinGLFactory.c#l252
On 18 May 2018 at 04:32, Matthew Elliot <matthew.james.ell...@gmail.com> wrote:
Hey, thanks for the second link, exactly what I needed just not the best news.
I see all Matrox cards are disabled which is a bit tricky for us when many of
our customers are have 4+ monitors and some have chosen those cards.
I then managed to find this - https://bugs.openjdk.java.net/browse/JDK-8103350
I assume this means there will never be support of these cards or is there a
work around? I.e. I see they support OpenGL so could I install OpenGL on a
windows machine and try that pipeline?
Is this exclusion of all Matrox cards still valid?
Thanks in advance,
Matt
Sent from my phone.
On 17/05/2018, at 5:15 PM, Anirvan Sarkar <powers.anir...@gmail.com> wrote:
Hi Matthew,
Please see the below file for blaclisted hardware on D3D.
http://hg.openjdk.java.net/openjfx/jfx-dev/rt/file/9e0e0e65e642/modules/javafx.graphics/src/main/native-prism-d3d/D3DBadHardware.h
Regards,
Anirvan
On Thu, 17 May 2018 at 11:04 PM, Matthew Elliot
<matthew.james.ell...@gmail.com> wrote:
Hi all,
we have some customers in the wild who use Matrox 9148LP (9100 series)
graphics cards because they drive more than 2 monitors and JavaFX always
reports an error initializing HW pipeline and forcing gpu results in system
instability.
I checked the bug reports but couldn't see anything about JavaFX and Matrox
cards.
Questions
Is anyone aware of an existing issue?
Is there a way to get more details on why JavaFx fails to enable the D3D
pipeline?
Is there a list of known problematic graphics cards or a black list of
graphics cards where JavaFX falls back?
Thanks in advance,
Matt
--
Sent from Gmail Mobile
--
Anirvan
