ered completely white after update

[ubas]

I am having a problem with the display of 3D PDF files containing U3D models in PDF-XChange Editor.

Until a few months ago, these 3D models were displayed correctly on my laptop. After installing a PDF-XChange Editor update, the problem appeared: the 3D components are now rendered completely white, so surface details, contours and geometry are no longer properly visible.

The 3D model itself is loaded and interactive. I can rotate, pan and zoom it, the 3D Model Tree is available, and PDF-XChange identifies the model as U3D. However, the component itself remains essentially a solid white shape without proper surface shading.

We have already made a direct comparison with a colleague's computer:

We are using the same PDF-XChange Editor version/build.
We opened the exact same 3D PDF file.
We compared the PDF-XChange settings point by point, including the Multimedia 3D settings, and they appear to be identical.
On my colleague's computer, the 3D components are displayed correctly with their surface details.
On my laptop, the components are displayed completely white.

I have also tried different rendering modes, lighting schemes and background colors. Changing the background to dark makes the white model visible, but there is still no proper surface shading or visible surface detail.

Interestingly, when I select “Shaded Wireframe”, the component itself disappears completely and only the bounding box remains visible.

One potentially important hardware difference is that my laptop uses a Qualcomm Snapdragon X Elite processor and therefore runs Windows on ARM (ARM64). I understand that this platform also uses Qualcomm/Adreno graphics rather than a conventional Intel/AMD/NVIDIA graphics environment.

Since the same 3D PDF, the same PDF-XChange Editor version/build and apparently the same application settings work correctly on my colleague's computer, I suspect that the problem may be related to the local 3D rendering environment.

Could this issue be related to Windows on ARM / ARM64, the Snapdragon X Elite platform, the Qualcomm Adreno graphics driver, or PDF-XChange's U3D rendering on this hardware?

Is there a way to reset the 3D rendering engine or its configuration, or are there any graphics/driver settings that I should check?

The fact that the same laptop displayed these 3D PDFs correctly before the PDF-XChange update may also be relevant.

I would be happy to provide screenshots, my exact PDF-XChange build number, Windows version, graphics driver information, or a sample 3D PDF if required.

Thank you very much for your help.

[Willy Van Nuffel]

Hi,

Just a guess:

1) "Override Document Colors" has been turned on via the File-menu > Preferences > Accessibility (or CTRL + SHIFT + 6)

2) "Dark Page Mode" has been activated via Help > UI Theme

If this does not help, then please post an exemple PDF.

Kind regards.

[Sean - PDF-XChange]

Thanks for the reply here Willy - we agree that that is the best way to proceed.

Kind regards,

[ubas]

First of all, thank you very much for your support.

I have now tried to follow your suggestions, but unfortunately without success.
I did not fully understand point 2, especially what exactly I should change or configure there.

I am also attaching a document with screenshots as well as the 3D file to give you a better overview of the issue.

Klemmblech.pdf

Screen shots.pdf

I look forward to your feedback and hope we can find a solution.

Thank you again for your support.

[Willy Van Nuffel]

Hi,

The "Dark Page Mode" is a view-option that you can find in the Help-ribbon > UI Theme.
The related icon is preceded by a check-mark when it is active (= a kind of on/off).
But, in this case, it has no influence.

Thanks for the sample PDF.
On my (old 32-bit) computer, the 3D does not render at all in PDF-XChange Editor v11.0.1, although "Enable 3D Content" is checked.
In the latest Adobe Acrobat Reader, there is no problem.
Also in previous versions of PDF-XChange Editor, like v10.8.5.410, the rendering works, although only in one direction (horizontal axis).

Probably the problem is caused by a lack of memory or something that is not supported by the kind of CPU in my/your computer.

Let us wait for a reaction of other forum members or the people of PDF-XChange Support and/or Development.

Kind regards.

[ubas]

Thank you!

[Sean - PDF-XChange]

[Willy Van Nuffel]

@PDF-XChange Support : Help is still needed

Can you render the 3D object in the sample file (Klemmblech.pdf) posted here above, with PDF-XChange Editor v11.0.1 ?

At my side, it does not work.

Thanks.

[Sean - PDF-XChange]

I have reproduced the issue and passed this on the development team for review.

Kind regards,

[Sean - PDF-XChange]

Update: the development team have confirmed the issue. I'm afraid it won't be fixed for the next build, but will be addressed at a later point.

Kind regards,

[Ivan - Tracker Software]

Investigation shows that the root of the problem is a default graphics driver, which implements OpenGL 1.1, while the Editor requires at least OpenGL 2.0 for 3D content.

Solution is to install OpenCL™, OpenGL®, and Vulkan® Compatibility Pack from MS Store. Please note that you will have to restart the machine after installation.

[Willy Van Nuffel]

Hello,

Just to let you know that the installation of the indicated package does not help.
Seeing it as : "Microsoft Visual C++ v14 Redistributable (x86) - 14.50.35719"

I have restarted my computer (Windows 10 - 32-bit) two times after the installation to be sure.

See below the screen that I still get. 3D Content is enabled.

Maybe the problem will be solved with the next release of PDF-XChange Editor ?

Kind regards.
°

PDF-XChange Editor - Klemmblech.png

[Daniel - PDF-XChange]

Hello, Willy Van Nuffel

It should deliver as a bundle of various DLL's not simply a C++ VC Redist package... You can read more about it here:
https://aka.ms/clglcp-faq
One item of note from this page:

Your OS version must be 19041.488 or higher. In practice, this means you should be on the latest version of the Windows 10 May 2020 Update (version 2004), or on the latest version of the Windows 10 October 2020 Update (version 20H2), or on the latest Insider build.

(Note that you will likely need to have a Microsoft account sign in, with MS Store access, to download this package) Did you use the download button on the page Ivan provided a link to?
If not, that could explain the difficulty.

Kind regards,