Cannot see PS EYE output in config window

[Algtronic]

I successfully replaced drivers for PS EYE and tested output in test_camera script. However, I cannot get it to work in config script. I see only blank white rectangle with changing fps counter. How may I fix it?

[Timocop]

You can no access a camera with multiple apps at the same time. Only one app can access the camera. Dont use text_camera.exe and just view your cameras in Config Tool.

[Algtronic]

I'm actually started to do that only after I've seen this rectangle in config without any test. Then I tested it in test script. Then I tried to open multiple apps to track any difference. So it's not like I opened 10 apps at the same time with the same cameras and it didn't work.

[Timocop]

So it's not like I opened 10 apps at the same time with the same cameras

test_camera.exe opens all available cameras and if you have PSMSX already open when you do that, it will steal camera access from PSMSX. Resulting in cameras not being shown or being timed out in PSMSX. The same happens the other way around and with any other app that accesses the cameras.

This is how accessing devices work in Windows. Instead, use Config Tool - Tracker Settings - Test Feed if you want to check your cameras.

[Algtronic]

Just reloaded PC and opened only config. Nothing else could possibly interfere. Still white screen

[Algtronic]

Numbers are changing, however.

[Timocop]

Please post your VDM diagnostics logs here via VDM -Service Management - Logs and Diagnostics

[Algtronic]

combined_logs.txt This is super-weird setup, tho. GT640 is used as image streamer from Tesla M40. It works in games, but services maybe freak out.

[Timocop]

Please factory reset and reinstall PSMSX and VDM using VDM - Service Management because you used Legacy PSMoveService prior.

Second, since you use a multi-GPU setup, the Tesla M40 ~~does not support OpenGL~~ does support OpenGL but apparently its a bit more tricky to get running(?) which Config Tool requires to render. So i suggest to switch the Nvidia GT 640 for the Config Tool render. Change the PSMoveConfigTool.exe default GPU in the Windows Settings to the Nvidia GT 640 to avoid this issue.

To change the GPU render in Windows Settings, follow these steps:

• Go to Settings > System > Display > Graphics settings.,
• Select Classic app.,
• Choose the app you want to modify from the list.,
• Click on Options and select the desired graphics card (AMD or Nvidia) for the app.,
• Click Save to apply the changes.,

For more information visit : 🌐 https://www.elevenforum.com/t/change-graphics-performance-preference-for-apps-in-windows-11.5675/

[Timocop]

If everything done properly, you should see the gray background with the PSEye model render in Tracker Settings.

[Algtronic]

I thought the same at first, but apparently it's easier for me to get OpenGL working with the Tesla than to enable the GT640. The thing is, using two different NVIDIA drivers on the same system isn't an option, and using a single driver for both cards isn't ideal either, since it's outdated. Currently, the GT640 is only capable of providing basic display output—nothing more. I could swap it for something like a Radeon R7 250, but I'd need to buy one first.

On the plus side, background 3D models in Tracker Settings are now working well with my current setup.

So, could you provide some guidelines to fix the problem using the current hardware/software configuration?

[Algtronic]

I'm also curious why test script works and main service doesn't

[Timocop]

There might be a shared memory issue between PSMSX and Config Tool then. Try to extract PSMSX (or VDM) to a path like your desktop with user permissions and try running it there. or delete the "shared_mem" folder in the PSMSX directory. Also check whatever anti-virus you have that could block cross-app communication via memory.

[Algtronic]

It didn't work. I created python script and parsed buffer from program to check if shared mem is rendering correctly. I got a valid image of my room with byte per pixel = 3 (also tried 4). I don't have any anti-viruses except default win10. The script

import os
import numpy as np
import cv2

# ==== Parameters ====
file_path = r'C:\Users\...'
width     = 640
height    = 480
bpp       = 3
# =============================


expected_size = width * height * bpp
actual_size   = os.path.getsize(file_path)

if actual_size != expected_size:
    print("Incorrect size")


mem = np.memmap(file_path, dtype=np.uint8, mode='r',
                shape=(height, width, bpp))


print("Min:", mem.min(), "Max:", mem.max())

frame = np.array(mem)  # shape=(H,W,bpp)
if bpp == 4:
    # BGRA → BGR для OpenCV
    frame_bgr = cv2.cvtColor(frame, cv2.COLOR_BGRA2BGR)
    cv2.imshow('Frame', frame_bgr)
else:
    cv2.imshow('Frame', frame)

cv2.waitKey(0)
cv2.destroyAllWindows()

[Timocop]

Thats quite odd. Can you run Config Tool manually and copy and paste the command prompt output here after you entered Test Feed. Maybe theres something ive missed. Otherwise i have to add some more logging into config tool to continue testing.