Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VisionRGB-Pro cards not supported #7

Open
arnoo-sel opened this issue Jul 2, 2023 · 6 comments
Open

VisionRGB-Pro cards not supported #7

arnoo-sel opened this issue Jul 2, 2023 · 6 comments
Labels
bug Something isn't working

Comments

@arnoo-sel
Copy link
Owner

Reported by happy on Vogons:

I tried the windows binaries of v2.6.1 and v.2.7.0 and both don't work with my VisionRGB-PRO1. Is that card not supported anymore or is this some other problem? The v2.6.0 binary I got from the original repo works.
They fail with the error message that RGBGetInputInfoW can't be found (I can make a githbut issue, just wanted to check if I missed that card being deprecated).

Affected release: v2.6.1, v2.7.0
Issue exists in original VCS: no

@arnoo-sel arnoo-sel changed the title VisionRGB-Pro cards not supported. VisionRGB-Pro cards not supported Jul 2, 2023
@arnoo-sel arnoo-sel added the bug Something isn't working label Jul 2, 2023
@arnoo-sel
Copy link
Owner Author

2.6.0 binaries from the original VCS were using the RGBEasy SDK targeting the VisionRGB-PRO SDK v8.1.2 drivers.

2.6.1 and 2.7.0 binaries from this fork use a new version of the SDK that does not work with the old drivers.

2 ways to resolve this:

  • build binaries using the old SDK
  • ask user to use the new drivers
    • not 100% sure this would work: new drivers do not officially support the VisionRGB-PRO cards, but header files and documentation suggest some level of support is still there. Needs user testing.

@h4pp7
Copy link

h4pp7 commented Jul 2, 2023

Hi, I reported this on Vogons. I can help with testing.

I'm not sure if I tried using newer drivers with this card. I think I tried the linux drivers with this card before and that didn't work. I can try, if the Windows version of the latest drivers work.

@arnoo-sel
Copy link
Owner Author

Thanks for the help!

Here's a test build using the vrgbpro SDK. vcs.exe is in the bin folder.
Let me know if it works with the old drivers installed.

vcs-2.8.0_dev-vrgbpro1.zip

@h4pp7
Copy link

h4pp7 commented Jul 3, 2023

It just closes after Initializing the RGBEASY capture device. Is there a way to get more debug information? Eventmanager says the error is with dgc103acc.dll

@arnoo-sel
Copy link
Owner Author

arnoo-sel commented Jul 3, 2023

Thanks for trying!
Hmm well it was worth a try. If there are no more messages after that, then it crashed when 1st trying to talk to the driver. I don't know of any way to get more info.

Ideally I would create builds closer to the original VCS, but I do not have the setup for building 32-bits WinXp-compatible binaries.

If you've got time for more investigations:

Could you give me more info about your setup? Particularly the windows version you're using?
And if you're using anything later than 7, do you remember how did you install the datapath drivers? I'm not able to install the old ones on my Win11, even in compatibility mode. Being able to do that might help a lot.

Also, if you can find your capture card in the device manager, could you find the driver details for it (Properties > Driver > Driver Details), find DLLs named rgbeasy.dll and dgc103acc.dll in the list (should be somewhere under c:/system32/), and send me those files? Thx!

@h4pp7
Copy link

h4pp7 commented Jul 30, 2023

Please excuse the late reply. Life got in the way.

I'm running Windows 10 Pro, 22H2.
I can't remember exactly, but I think I ran INSTALL.exe from the win32 folder with windows 7 compatibility.

The device manager lists the following files:

C:\WINDOWS\system32\autotag.dll
C:\WINDOWS\system32\dgc103acc.dll
C:\WINDOWS\system32\dgc103coi.dll
C:\WINDOWS\system32\dgc103st.ax
C:\WINDOWS\system32\drivers\dgc103.sys
C:\WINDOWS\system32\drivers\ksthunk.sys
C:\WINDOWS\system32\rgb.dll
C:\WINDOWS\system32\rgbeasy.dll
C:\WINDOWS\sysWOW64\autotag.dll
C:\WINDOWS\sysWOW64\dgc103acc.dll
C:\WINDOWS\sysWOW64\dgc103st.ax
C:\WINDOWS\sysWOW64\rgb.dll
C:\WINDOWS\sysWOW64\rgbdiag.exe
C:\WINDOWS\sysWOW64\rgbeasy.dll

All the files in system32 are the x64 versions from the DGC103 folder from the zip folder downloaded from Datapath. So for example C:\WINDOWS\system32\dgc103acc.dll is vrgbpro\DGC103\dgc103accx64.dll and C:\WINDOWS\system32\rgbeasy.dll is vrgbpro\DGC103\RGBEASYx64.DLL (I diffed them to check).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants