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

option to change igpu ram allocation #3362

Open
2 tasks done
thatonehhdev opened this issue Nov 11, 2024 · 7 comments
Open
2 tasks done

option to change igpu ram allocation #3362

thatonehhdev opened this issue Nov 11, 2024 · 7 comments
Labels
question Further information is requested

Comments

@thatonehhdev
Copy link

Rules

  • I made myself familiar with the Readme, FAQ and Troubleshooting.
  • I understand that, if insufficient information will be provided, my issue will be closed without an answer.

Is your feature request related to a problem? Please describe

in proart creator hub, there is an option to change the amount of ram allocated to the igpu on supported models.

Describe the solution you'd like

add an option in ghelper to change the amount of ram allocated to igpu and then ask you to restart your PC (proart creator hub asks you to restart).

Describe alternatives you've considered

No response

Device and Model

proart px13

Additional information.

image

@thatonehhdev
Copy link
Author

btw there is an auto mode in proart creator hub, but its terrible and allocates 200mb.

@seerge
Copy link
Owner

seerge commented Nov 11, 2024

@thatonehhdev hello,

That must be an endpoint responsible for that then similar to how it happens on ROG Ally.

I will need some things from you then.

  1. Quit app and add following line to %appdata%\GHelper\config.json :
"debug": 1,
  1. Run app again, open Extra and click on Zoom-Glass icon there, it will scan for all available endpoints and open a log
  2. Change your iGPU VRAM allocation in Creator Hub to something else and run scan from Extra again

Upload a log from the scan here and lets see if one of the endpoints changes.

Thanks

@seerge seerge added the question Further information is requested label Nov 11, 2024
@seerge
Copy link
Owner

seerge commented Nov 11, 2024

@thatonehhdev also, can you do a DSDT dump as explained in Method 2 here ?

@thatonehhdev
Copy link
Author

after i run ./acpidump.exe -b, there is no file called dsdt.dat

@thatonehhdev
Copy link
Author

image
this is the dat files i get.

@thatonehhdev
Copy link
Author

and there is no change in any endpoints.
scan1.txt
scan2.txt

@seerge
Copy link
Owner

seerge commented Dec 8, 2024

@thatonehhdev hello, sorry for a slow response, i was away.

Since both scans are same, apparently ProArt app does it somehow differently. If you really want to figure it out, you will have to do some capturing and debugging.

Here is the guide on what needs to be set up https://github.com/seerge/g-helper/wiki/_ACPI-Monitoring-and-Debugging

With the exception, that instead of AC you (obviously) use ProArt app and for Capturing you should start it before adjusting "shared memory size" in ProArt as well :)

Let me know if you want to do that. Thanks

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

No branches or pull requests

2 participants