-
Notifications
You must be signed in to change notification settings - Fork 57
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
[BUG] Dual GPU displaying incorrect VRAM #72
Comments
Updated, still displaying GPU: NVIDIA GeForce RTX 3090 - VRAM: 4 GB |
Issue will be closed in a few days if no response. |
Hello, my bad. Issue is still present on latest. |
Unfortunately the core of this issue relates to external GPUs and without an eGPU to be able to test on I'm not sure I will be able to create a fix for this. There is no way I can find to detect AMD iGPUs in the registry or wmic without finding a list of every AMD iGPU and hardcoding a check against each of them. Since this is not an issue that will effect 99% of users and doesn't prevent the launcher from working, just doesn't show correct VRAM which is a "quality of life" feature. I will be closing this issue. |
I also had this problem. For reference, I have an AMD processor with a built in GPU, and I also have an NVIDIA RTX 4070TI Super... One of the errors was that the "AdapterRAM > 0" would always return true, because most iGPUs have more than 0 VRAM... For example: my return of the wmic command shows me to have 536870912 AdapterRAM on my AMD Radeon(TM) Graphics entry; which is greater than 0, and so it was being chosen. To fix that, I changed it to this and it works for me now (this could very much be done better, but I made these changes after searching on google for an hour on how to write in batch... so excuse the mess): FILENAME: gpu_info.bat
With that being said, when I tried to then download a model for TabbyAPI, it said I didn't have enough VRAM, so there are more places that need to be fixed than just the gpu_info.bat file. |
It is the launcher.bat that needs fixing too... It uses the same non-iterating powershell script to get the VRAM for the GPU, which only returns the first GPU (which is always an iGPU if it exists.) So I replaced the part that normally finds the VRAM (at lines 431-433) with this and it works now:
|
@JaceEthaniel If you believe this change improves the launcher for everyone, I recommend you to make a pull request. This way, your contribution can be properly reviewed and integrated, and your name will automatically be added to the contributor list. It's a better approach than posting the fixed code in a comment, it provides proper credit for your work. |
@eeljpg does the problem still exist for you? |
So, funny news. My GPU died so I don't have an eGPU setup anymore and I built a whole new PC. Still have a different non-external 3090 though. As my hardware is entirely different now and there isn't an egpu, I wasn't expecting the issue to still exist, but it seems I carry a special level of edge-case energy as it now displays "GPU: Parsec Virtual Display Adapter - VRAM: 24 GB". Weirdly, it persists in showing this even if I disable the parsec adapter in device manager. |
I see, so you still have the driver installed and it is being detected as an actual GPU... Unfortunately I am not well-versed enough to solve that particular problem with an auto-select method like what is currently in place. I would suggest trying to uninstall that driver if you don't expect to use it any time soon. Basically, my plan is to have it list all the GPUs you have on the first start up (it will check the GPU log file to see if it exists, and if not it will ask which GPU you will be using), then in the toolbox I am going to add an option to select a different GPU. Ultimately though it is primarily a visual thing. The only thing it actually affects is the launcher itself deciding if you have enough VRAM to run certain models. The actual image/text generators will use the correct GPU/driver (well, unless you are REALLY good at getting those edge-case issues). |
Environment
🪟 Windows
System
Windows 11 23H2
Describe the problem
I have both an iGPU and a dedicated eGPU. The launcher displays my VRAM as the iGPU vram while still recognizing the eGPU. It says:
"GPU: NVIDIA GeForce RTX 3090 - VRAM: 4 GB".
Problem does not exist in automatic1111 sd or task manager.
For full disclosure, the GPU is an egpu through Oculink. Still works fine and all 24gb vram are usable. Not looking to use iGPU vram. LLMs still utilize 24gb of 3090 VRAM, so it seems to be a display error only.
Additional info
SillyTavern: 1.12.4
STL: 24.1.3.0
GPU: NVIDIA GeForce RTX 3090 - VRAM: 4 GB
Please tick the boxes
The text was updated successfully, but these errors were encountered: