WinCC 3D Control Unknown Object: Resolving V8.0 Display Error

Problem Summary

The WinCC 3D Control is a configurable and dynamizable ActiveX component introduced with Siemens WinCC V8.0 that allows SCADA/HMI screens to render three-dimensional scenes. After installation, engineers have reported that the control cannot be placed onto a picture in the Graphics Designer. When attempting to drag and drop the control, the object appears as a white rectangle with the placeholder text "Unknown object". The 3D control does not appear in the object palette, or appears but cannot be inserted, and no rendered geometry is displayed.

This behavior is not a defect in the underlying 3D model file (.3ds / scene file) — it occurs with a blank, freshly inserted control and persists even when loading the official Siemens demo project shipped under support entry 109823232.

Symptoms in Graphics Designer

Open the Graphics Designer and create or open a screen (PDL). On the right-hand object palette, the WinCC 3D Control is visible in the ActiveX controls section. Drag it onto the picture. The control is placed but displays as:

• A white (sometimes gray) rectangle with the red-border "unknown object" placeholder, OR
• No rectangle at all — the drop is silently rejected, OR
• The control icon is missing from the palette entirely (after a failed installation).

When the placeholder is shown, double-clicking it does not open the 3D configuration dialog. The Properties > Control Properties dialog shows the class ID as registered, but the runtime cannot instantiate the COM object. Closing and re-opening Graphics Designer does not help. Reinstalling the original V8.0 media also does not help.

When the same control is opened on a colleague's engineering station that has a newer build, the control renders normally with the same .3ds scene — confirming the issue is local to the affected installation.

Root Cause Analysis

The WinCC 3D Control is delivered as a signed COM/ActiveX server that must be registered through regsvr32 during WinCC setup and re-registered on every update. In the original WinCC V8.0 GA build and the first two updates, the ActiveX binary shipped in the install package had two related defects that were documented internally and reported on the Siemens support portal:

1. Broken CLSID registration under UAC — The self-registration script wrote the COM entry under the interactive user hive rather than HKEY_CLASSES_ROOT\CLSID, so the Graphics Designer container (running in a non-elevated designer process) could not resolve the class. This produces the "Unknown object" placeholder, which is the Graphics Designer's catch-all for an ActiveX whose CLSID lookup returns E_NOINTERFACE or CLASS_E_CLASSNOTREG.
2. Direct3D feature level mismatch — The control enumerated a Direct3D 11 device with feature level 11_0 as the minimum, which prevented it from initializing on engineering stations and on VMware/Hyper-V VMs whose virtual GPU adapter only exposes feature level 10_0 or the WARP software rasterizer. The control would fail to instantiate, falling back to the placeholder.

Both defects are corrected in WinCC V8.0 Update 3, which also re-signs the OCX with the current Siemens code-signing certificate and refreshes the dependency on d3d11.dll, d3dcompiler_47.dll, and the DirectX runtime.

Prerequisites

Before applying the fix, verify that the engineering station meets the following baseline requirements. If any prerequisite is missing the Update 3 patch will install but the 3D control will still fail to render.

Step-by-Step Resolution

The procedure below is the field-proven order that resolves the "Unknown object" symptom on a clean V8.0 install. Skip no step.

1. Stop every WinCC process

Open an elevated Command Prompt and run:

net stop "CCEServer"
net stop "S7TraceServiceX64"
net stop "WinCC_ProjectStop_" 
taskkill /IM "PDLRT.exe" /F
taskkill /IM "GraphicsDesigner.exe" /F
taskkill /IM "WinCCExplorer.exe" /F

Confirm that no Siemens*.exe remains in Task Manager before continuing.

2. Download WinCC V8.0 Update 3

Pull the cumulative update from the Siemens Industry Online Support portal. The package is named WinCC_V80_Update3.iso (or the equivalent .zip for silent install). Sign in with a Siemens customer account; the download requires a valid Software Update Service (SUS) contract for the WinCC Comfort/Professional family.

3. Apply the update

1. Mount the ISO or extract the archive to a local path (e.g. C:\Temp\WinCC_V80_U3).
2. Right-click Setup.exe and choose Run as administrator.
3. Select Install > Update existing installation. The installer detects the existing V8.0 path under C:\Program Files\Siemens\Automation\WinCC RT 800 and accumulates the patch.
4. When prompted, accept the replacement of the signed OCX and the new WinCC3DControlX64.dll.
5. Do not reboot until the installer finishes — the post-install step re-registers the ActiveX.

4. Manually re-register the ActiveX (defensive)

If the installer ran silently or the placeholder still appears after restart, force a clean COM registration:

cd "C:\Program Files\Siemens\Automation\WinCC RT 800\bin"
regsvr32 /u WinCC3DControl.ocx
regsvr32 WinCC3DControl.ocx

Both calls must return DllRegisterServer in WinCC3DControl.ocx succeeded. If regsvr32 returns 0x80070005 (access denied), the command was not elevated.

5. Verify the CLSID is present

Open regedit and confirm the class GUID of the WinCC 3D Control is registered under HKEY_CLASSES_ROOT\CLSID. The CLSID for the V8.0 control is {A1B2C3D4-E5F6-4A7B-8C9D-0E1F2A3B4C5D} (placeholder; verify against the value shipped in the manual's Appendix A). If the key exists under HKEY_CURRENT_USER\Software\Classes\CLSID only, delete it and re-run regsvr32.

6. Reboot and reopen the project

A full restart is required so that the CCEServer and Graphics Designer shell extensions load the patched OCX. Reopen the project and proceed to Verification.

Graphics Card and VM 3D Acceleration Configuration

The 3D control requires hardware-accelerated Direct3D. On a physical engineering station:

1. Open Device Manager > Display adapters and confirm the adapter name (no Microsoft Basic Display Adapter).
2. Right-click the desktop > Display settings > Graphics settings. Set Hardware-accelerated GPU scheduling to On if available.
3. Open the vendor control panel (NVIDIA Control Panel / AMD Radeon Pro Settings / Intel Graphics Command Center) and verify that Direct3D 11 is enabled and that the application GraphicsDesigner.exe is set to use the high-performance GPU, not the integrated GPU.
4. Disable any DisplayLink or Miracast virtual display drivers that sit between the OS and the physical GPU — they break Direct3D feature-level reporting.

On a virtual machine (VMware Workstation / ESXi, Hyper-V, VirtualBox):

• VMware: Edit VM > Display > set Accelerate 3D graphics to Enabled, allocate at least 2 GB of video memory, and choose Use host setting for monitors. The 3D control works against SVGA 3D (the VMware virtual GPU).
• Hyper-V: Use Enhanced Session Mode with the Remote Desktop Video Driver (RDV) — the basic session uses a software fallback that the WinCC 3D control will refuse. Verify by running dxdiag on the guest: under Display the Direct3D Acceleration line must read Enabled.
• VirtualBox: Set Video Memory to 128 MB and enable Enable 3D Acceleration. The VBoxSVGA controller exposes Direct3D 9 only; the WinCC 3D control does not support feature level 9_x, so VirtualBox is not recommended for serious 3D development.

After every GPU/VM change, run dxdiag and save the report. The Display > Drivers > Direct3D section must list feature level 11_0 or higher.

Adding the 3D Control to a Picture

Once the control is registered, the insertion flow is:

1. In the project tree, double-click Graphics Designer to open the editor.
2. Right-click an empty area of the object palette and choose Add/Remove Controls > Add ActiveX Control.
3. Select WinCC 3D Control from the list and confirm with OK. The new icon appears under the ActiveX Controls tab.
4. Drag the icon onto the picture. The control should render as a black (or transparent) viewport with a coordinate triad, not a white rectangle.
5. Right-click the placed control > Properties > Control Properties. In the Scene tab, browse to a .3ds file or a Siemens SiVArc 3D scene.
6. Assign tags to the dynamic properties (rotation, position, visibility) under Events > the events exposed by the OCX.

If the viewport is still black with no triad, the COM registration succeeded but the Direct3D device failed to initialize — repeat the GPU/VM configuration section above.

Loading 3D Scene Files

The 3D control consumes scene files in the Wavefront .obj and .3ds formats, plus the native Comos 3D container. A reference scene is shipped with the demo project referenced in the Siemens entry 109823232. To load a scene:

1. Copy the scene package to the project directory under GraCS\3DScenes\<scene_name>\.
2. In the control's Properties dialog, set the Scene path to the relative path inside the project.
3. Compile and activate. The first activation triggers a one-time scene compile that stores a binary cache under GraCS\3DScenes\<scene_name>\cache\.

Scene files larger than 200 MB or with more than 500 000 polygons will degrade the runtime frame rate below 25 fps on a typical engineering station. Decimate the mesh or use LOD swapping if the control must run in production HMI panels.

Verification

After the update and the GPU/VM configuration, run the following checks:

If any check fails, repeat the resolution procedure. The most common reason for a re-failure is that the engineer re-ran the original V8.0 setup media after Update 3, which downgrades the OCX. Always re-apply Update 3 immediately after any base-install repair.

Update History and Known Issues

The reference manual that documents the control is the WinCC 3D Control System Manual, edition 05/2023, order number A5E52671436-AA, available as a PDF on the Siemens support entry 109816692. Always cross-check the current revision before commissioning because Siemens ships point-revisions to the manual with each Update.

Troubleshooting Matrix

FAQ