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

still using 2 differnt drivers ( amd and nvidia) and run vibranceGUI #67

Open
firxz opened this issue May 10, 2018 · 10 comments · May be fixed by #140
Open

still using 2 differnt drivers ( amd and nvidia) and run vibranceGUI #67

firxz opened this issue May 10, 2018 · 10 comments · May be fixed by #140

Comments

@firxz
Copy link

firxz commented May 10, 2018

hello my name is mike and i have an issue i use to differnt grafic cards one amd one nvidia and i use only the amd one for streaming and nivdia for as gaming but i cant use vibranceGUI anymore but is there a way to baypass this so i can still use it ore is there a version of it that cant detect grafic card drivers please help i need them both

@firxz firxz changed the title still using 2 driver and run vibranceGUI still using 2 differnt drivers ( amd and nvidia) and run vibranceGUI May 11, 2018
@juv
Copy link
Owner

juv commented Jan 7, 2019

There is no way to bypass this unfortunately. This happens because you have both NVIDIA API dll files (nvapi.dll) as well as AMD API dll files (atiadlxx.dll and atiadlxy.dll) in your Windows driver folders (System32/SysWOW64). You could try to rename the amd api dll files and see if everything else still works as expected. I am not sure if you need the amd api dll files for your streaming program though.

@juv
Copy link
Owner

juv commented Jan 7, 2019

This is a version that only checks for NVIDIA and does not care if both NVIDIA and AMD drivers are present.
vibranceGUI_nvidia_only.zip

This is a version that only checks for AMD and does not care if both NVIDIA and AMD drivers are present.
vibranceGUI_amd_only.zip

@nyaray
Copy link

nyaray commented Jun 24, 2022

Isn't it possible to ask which to use if the application detects that both drivers are present?

@KyleScharnhorst
Copy link

This should be handled more appropriately, there are edge cases where someone would need AMD and NVIDIA drivers installed.

@tooruu
Copy link

tooruu commented Mar 11, 2024

Not even an edge case. Can't run this with an AMD CPU (with its appropriate graphics drivers installed) and NVIDIA GPU.

@jjcodestuff
Copy link

same issue :(

@iwa
Copy link

iwa commented Jun 15, 2024

This is a version that only checks for NVIDIA and does not care if both NVIDIA and AMD drivers are present. vibranceGUI_nvidia_only.zip

This is a version that only checks for AMD and does not care if both NVIDIA and AMD drivers are present. vibranceGUI_amd_only.zip

solution is working fine for me with AMD cpu w/ integrated graphics and Nvidia GPU, but it still feels like a workaround to find your comment here on github to download the right version...
could you add a support inside the tool to choose it / choose version on the official website?

@MetaCrawler
Copy link

This is a version that only checks for NVIDIA and does not care if both NVIDIA and AMD drivers are present. vibranceGUI_nvidia_only.zip

This is a version that only checks for AMD and does not care if both NVIDIA and AMD drivers are present. vibranceGUI_amd_only.zip

Thannk you so much dude!

@juv
Copy link
Owner

juv commented Dec 20, 2024

Hi all,

can you please take a look at this new beta version i have built based on this PR: #140

To force a GPU type in that new version, do the following:

  1. Create a shortcut of the vibranceGUI.exe file (right click -> create shortcut)
  2. Go to the shortcut properties (right click, properties)
  3. Add the following at the END of the Target field:
    for NVIDIA: --force-nvidia
    for AMD GPU: --force-amd
    Make sure to add a space ( ) in between the path to the .exe file and the argument, so for example it looks like this:
    C:\WHATEVER\vibranceGUI\vibranceGUI.exe --force-nvidia

It would be great if you can let me know if this also works after you reboot your pc.
By the way, this version also includes a lot of bug fixes and performance improvements in comparison to that version above from 2019.

You can download the pre-release .exe here:
https://github.com/juv/vibranceGUI/releases/tag/v2.5.0

@juv juv linked a pull request Dec 20, 2024 that will close this issue
@KyleScharnhorst
Copy link

Hi all,

can you please take a look at this new beta version i have built based on this PR: #140

To force a GPU type in that new version, do the following:

1. Create a shortcut of the vibranceGUI.exe file (`right click -> create shortcut`)

2. Go to the shortcut properties (`right click, properties`)

3. Add the following at the END of the `Target` field:
   for NVIDIA: ` --force-nvidia`
   for AMD GPU: ` --force-amd`
   Make sure to add a space (` `) in between the path to the .exe file and the argument, so for example it looks like this:
   `C:\WHATEVER\vibranceGUI\vibranceGUI.exe --force-nvidia`

It would be great if you can let me know if this also works after you reboot your pc. By the way, this version also includes a lot of bug fixes and performance improvements in comparison to that version above from 2019.

You can download the pre-release .exe here: https://github.com/juv/vibranceGUI/releases/tag/v2.5.0

Appears to be working as intended. Can confirm automatic startup works with forced nvidia. Not using any of the other new features. So can't speak to those.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants