G4 11.2.2 Qt6 problems on Windows

Recording, Visualizing and Persisting Data
1

Dear All,

As pointed out here: [Installation Error] Install with Qt6 in Windows
and here: https://bugzilla-geant4.kek.jp/show_bug.cgi?id=2599#c6
there were compiling errors when compiling G411.2.1 with Qt6 on windows.
I’ve tried to compile the new version G411.2.2 (with the fixing) and similar errors still occur on other files, as I already reported in the bugzilla post.

After my patch, G4 compiles correctly.

Now, my problem is that when I run my application, the following graphics systems are available:
ASCIITree (ATree)

  • DAWNFILE (DAWNFILE)*
  • G4HepRepFile (HepRepFile)*
  • RayTracer (RayTracer)*
  • VRML2FILE (VRML2FILE)*
  • gMocrenFile (gMocrenFile)*
  • TOOLSSG_OFFSCREEN (TSG_OFFSCREEN)*
  • TOOLSSG_OFFSCREEN (TSG_OFFSCREEN, TSG_FILE)*
  • OpenGLImmediateWin32 (OGLIWin32, OGLIQt_FALLBACK)*
  • OpenGLStoredWin32 (OGLSWin32, OGLSQt_FALLBACK)*
  • Qt3D (Qt3D)*
  • TOOLSSG_QT_GLES (TSG_QT_GLES, TSGQt, TSG, OGL)*
  • TOOLSSG_QT_ZB (TSG_QT_ZB, TSGQtZB)*
  • TOOLSSG_WINDOWS_GLES (TSG_WINDOWS_GLES)*
  • TOOLSSG_WINDOWS_ZB (TSG_WINDOWS_ZB)*

While when compiling G4.11.2.2 with Qt5 the following graphic systems are available:

  • ASCIITree (ATree)*
  • DAWNFILE (DAWNFILE)*
  • G4HepRepFile (HepRepFile)*
  • RayTracer (RayTracer)*
  • VRML2FILE (VRML2FILE)*
  • gMocrenFile (gMocrenFile)*
  • TOOLSSG_OFFSCREEN (TSG_OFFSCREEN)*
  • TOOLSSG_OFFSCREEN (TSG_OFFSCREEN, TSG_FILE)*
  • OpenGLImmediateQt (OGLIQt, OGLI)*
  • OpenGLStoredQt (OGLSQt, OGL, OGLS)*
  • OpenGLImmediateWin32 (OGLIWin32, OGLIQt_FALLBACK)*
  • OpenGLStoredWin32 (OGLSWin32, OGLSQt_FALLBACK)*
  • Qt3D (Qt3D)*
  • TOOLSSG_QT_GLES (TSG_QT_GLES, TSGQt, TSG)*
  • TOOLSSG_QT_ZB (TSG_QT_ZB, TSGQtZB)*
  • TOOLSSG_WINDOWS_GLES (TSG_WINDOWS_GLES)*
  • TOOLSSG_WINDOWS_ZB (TSG_WINDOWS_ZB)*

As you can see the OpenGLImmediateQt and OpenGLStoredQt are missing with Qt6.

It seems that Qt is found correctly but I cannot understand why these graphics systems are not available.
Do you have any suggestion?

Moreover:
With Qt6, by deafult the command /vis/open runs OGL, the TOOLSSG_QT_GLES is used and it works
By running the command /vis/open Qt3D, the application crashes → am I doing someting wrong?

Andrea

_Geant4 Version:_11.2.2
_Operating System:_Windows 11
_Compiler/Version:_VS2022 17.9
_CMake Version:_3.22.2

2

Hi Andrea

Moving to Qt6 has been a problem for the OpenGLQt drivers, and for Geant4 11.2 we adopted an interim solution whereby /vis/open OGL (or just /vis/open) opens a ToolsSG window instead. Somewhere in your output you should see “Qt6: Asking ToolsSG to stand in for OpenGL”. This has been all been corrected in the new 11.3-beta, released yesterday, although we are still finding some issues, for example, an intermittent crash with Qt3D. I would be very interested in your experience as a Windows user.

As for your fixes proposed in the bug report, I believe they are also included in the new 11.3-beta. We are grateful for your help with this. Your posts here and in bugzilla are always clear and meticulous - it is much appreciated.

John

3

Hi John,

Thank you for quick renspose!
I’ve compiled the 11.3.0-beta and I can confirm the OGLQt works and there are no compiling errors.

I instead was not able not run the Qt3D. It opens a window but does not draw anything. I’ve never used the Qt3D driver, so maybe I’m doing something wrong (I simply tried with: /vis/open Qt3D and then /vis/drawVolume).

Just a curiosity: Have you made any changes in the OpenGL rendering of coincident surfaces? Because in the 11.3.0 they look different from previous versions.

If I can, I’m happy to test and give you feedback!

Andrea

4

Hi Andrea

Thanks for confirming OGLQt works for you with 11.3. Great!

As for Qt3D, please consider this “under development”. I think we have broken it for both Qt5 and Qt6 at the moment.

Re rendering of coincident surfaces, I’m not aware of any changes. In any case, the result is not well defined, I believe, if, for example, the surfaces have different colours. I will look out for this behaviour change.

And…great…really appreciate your offer of testing. This is all under intense scrutiny at the moment and I may well send you a patch for testing before the next release.

John