Project

General

Profile

Actions

Support Request #10171

closed

Missing disable GPU hardware acceleration

Added by hidden about 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Customer:
BOSCH
Department:
CC-DA/ETV
Requester's Priority:
Normal
Support Level:
3rd Level
Resolution:
Solved Issue
Product Issue Numbers:
Affected Products:
Platform:
Windows 7 64bit
Topic:
ADTF::Common
FAQ Links:

Description

Supportanfrage

The feature is missing in ADTF3. This was possible and required (remote desktop support) in ADTF2.

Lösung

We are not using any accelerated graphics on our own, but rely on Qt to select the proper backend.
In ADTF2 this setting only changed the behavior of the Video Display Filter to not use OpenGL directly but to use the Qt painter API. It had no effect on the Qt (QtWidgets) based ADTF GUI.
In ADTF3 we heavily rely on Qts QML technology, which uses accelerated graphics by default.
I tested right now using remote (Win10-Win10), starting CE, launching a session, attaching with GUI Control and some basic stuff, no problems using UI, no additional settings made.
As already mention, we occuring some trouble in virtualization regarding graphic devices, but then changing the software rendering as described works perfect.
But for remote access I can't figure out any problems so far.

Actions #1

Updated by hidden about 4 years ago

  • Status changed from New to Customer Feedback Required
  • Topic set to ADTF::Common
  • Support Level changed from 2nd Level to 3rd Level

Hi Bane,

this is currently neither a feature nor required... so far.

We did not run in any trouble for remote setups, do you encounter any problems ?
In my VERY humble option regarding this feature, I think in Windows 10 it is not required and can be handled by OS settings.
Another thing is that you do not have to work remote, because whole ADTF 3.x toolset works remote.
So there is no need to virtualize on a far host, you can attach there.

@Martin/Sebastian: Any information for this option ?

Actions #2

Updated by hidden about 4 years ago

By default, Windows Server 2016 and Windows 10 do not enable the GPU for rendering over Remote Desktop. If I have to support remotely I'll get black screen.
Please note we can not change OS settings in our Bosch environment. This is a blocker for support use case.

Please note a standard Bosch user can not change the registry settings:
https://community.esri.com/thread/225251-enabling-gpu-rendering-on-windows-server-2016-windows-10-rdp

Actions #3

Updated by hidden about 4 years ago

OK, we will check for the topic...

Does it work, to configure Qt rendering before, by setting environment variable QT_QUICK_BACKEND=software before starting CE ?

Actions #4

Updated by hidden about 4 years ago

Hi Bane,

we are not using any accelerated graphics on our own, but rely on Qt to select the proper backend.

In ADTF2 this setting only changed the behavior of the Video Display Filter to not use OpenGL directly but to use the Qt painter API. It had no effect on the Qt (QtWidgets) based ADTF GUI.

In ADTF3 we heavily rely on Qts QML technology, which uses accelerated graphics by default. As Florian pointed out there is a software render as fallback, so please give this a try.

Regards,

Maritn

Actions #5

Updated by hidden about 4 years ago

Hi Martin,

that means remote desktop support shall work w/o problems? I mean did you test this?
if so please close this ticket.

Thanks, Bane

Actions #6

Updated by hidden about 4 years ago

@Bane, I think there has been a misunderstanding. We thought you already encountered problems running ADTF3 (Launcher or CE) on a remote desktop, but if I do understand you correctly now, you have not tried to run it in your remote environment yet?

@Flo Can you please elaborate on what remote setups we have tested so far?

Actions #7

Updated by hidden about 4 years ago

I tested right now using remote (Win10-Win10), starting CE, launching a session, attaching with GUI Control and some basic stuff, no problems using UI, no additional settings made.
As already mention, we occuring some trouble in virtualization regarding graphic devices, but then changing the software rendering as described works perfect.
But for remote access I can't figure out any problems so far.

Actions #8

Updated by hidden about 4 years ago

if the basic watch example works, you can close this. Thanks

Actions #9

Updated by hidden about 4 years ago

  • Project changed from 5 to Public Support
  • Subject changed from disable GPU hardware acceleration to Missing disable GPU hardware acceleration
  • Description updated (diff)
  • Status changed from Customer Feedback Required to To Be Closed
  • Private changed from Yes to No
  • Resolution set to Solved Issue
Actions #11

Updated by hidden almost 4 years ago

  • Status changed from To Be Closed to Closed
Actions

Also available in: Atom PDF