Unable to connect: Flame application not launching using PCoIP

In some cases, Flame may show various issues when accessing the application through a PCoIP session.

Possible Issues:

• Flame 2023 fails to launch.
• After the Flame 2023 launch attempt, mouse & keyboard input stops responding over PCoIP session.
• PCoIP session launches successfully but locks up when launching Flame 2023
• Launching Flame produced strange discoloration from purple to orange after selecting Enter while being able to "blindly right-click around with mouse to get a menu pop-up to quit Flame, at which point the display over a PCoIP session returned to normal.
• Fatal error seen when trying to load Flame

Scenario 1

Flame application is unable to load with the following fatal error displayed.

"Fatal: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem."

Cause:
This has to do with Flame having its own display configuration that is identified during installation which in this case was a physical machine with a physical display attached.
Once a PCoIP capable agent is installed and a PCoIP session established, the agent injects the virtual display which then breaks the Flame display configuration.

Solution

Replace the contents of the env.cfg file with the results displayed from executing the echo $DISPLAY command from withing a PCoIP session.

1. Establish a PCoIP session.
2. Open a terminal.
3. Execute the following command and save the results to use in the next step.
   echo $DISPLAY
4. Replace the contents of the env.cfg file with the results from step 3 using your favorite editor.
   Example: sudo nano /opt/Autodesk/cfg/env.cfg
5. Click Ctrl+X and exit saving the file.
6. Start the Flame application.

Platform:

• HP Z8 G4 Workstation
• Dual Intel Xeon Gold 6136 CPUs
• 384GB RAM (24x16GB) DDR4 2933 ECC REG 2CPU
• Two Nvidia Quadro RTX 6000 GPUs (driver v450.102.04)
• CentOS Linux 7.6.1810/64bit with kernel 3.10.0-957.27.2.el7.x86_64 (enabled for KDE Plasma)
• Eizo CG319X display
• AJA Kona 4 PCIe video I/O
• Intel X550T dual-port 10GbE
• 512GB boot disk
• 23TB usable (XFS formatted) of internal LSI SATA SSD RAID-6 (for Flame's media volume)
• Autodesk DKU v16.0.0 + Flame v2022.2
• PCoIP-agent-graphics 21.07.6

Scenario 2

Flame is not responding correctly and the following error messages are found.

/opt/Autodesk/io/bin/vref: symbol lookup error: /lib64/libGL.so.1: undefined symbol: _glapi_tls_Current
/opt/Autodesk/flame_2023/bin/flame: symbol lookup error: /lib64/libGL.so.1: undefined symbol: _glapi_tls_Current
Application exited abnormally.
press ENTER to continue

Cause

The GPU was in an incorrect slot for the platform to work with Flame in a PCoIP session.

Solution

Use the BIOS to set the GPU in slot 4 as primary which allows Flame 2023 to display & function normally in a PCoIP session after a computer restart.

Platform

• Z8 G4 Workstation
• Linux Operating System
• Dual NVIDIA RTX A5000 GPUs
• Imaged the Z8 with Autodesk custom ISO for Rocky Linux 8.5
• NVIDIA drivers were sourced from Autodesk DKU which provides NVIDIA driver version 460.91.03.
• PCoIP Graphics Agent 23.01
• Autodesk Flame 2023