SublimeText unusable with eGPU unless on max resolution (+ some opacity artifacts)?
Hello, I wonder if anyone came across this issue - I run a eGPU with the great latest setup from the sticky thread.
Everything is great except two things (one is a major dealbreaker):
1) SublimeText renders everything in HUGE font when eGPU is used, unless I run my monitor at 4K (I prefer a resolution one step lower than that).
2) There are some artifacts with UI elements that like red notification bubbles. They look like they have a square rectangle around them (as if the opacity of the PNG is being rendered incorrectly).
Can anyone please weigh in on these by any chance?
I have not issue these issue but i’using Radeon which is officially supported.
eGPU.it | LG 34" 4K 34UC88 curved ultrawide display
MacBook Pro 2018 Touch Bar i7 quad-core 2.7Ghz - 16GB RAM - 512GB PCIe SSD --> my Mantiz Venus extreme mod with Sapphire Nitro+ RX Vega 64
@reptilianbrain See the updated purge-nvda in my signature. Using that + latest web drivers on your model (with the eGPU patches) may resolve some problems, tho this approach has its own caveats.
Thanks a lot for your help @mac_editor. Unfortunately purge-nvda lead to my computer being unable to boot - stuck at 70% of the Apple screen. When I could boot I had picture on external screen (no Password or Login option though, as if the system didn't get to that stage yet) and black internal screen.
Usually to get eGPU show up in Mac by plugging eGPU once the bar on the Apple screen is at 10% - works 100% of the time (when eGPU works in principle).
Eventually I had to reset PRAM and only was able to roll-back to bootable state through Safe mode.
I saw the recommendation there is uninstall the script (btw the path with Recovery mode + mount didn't work - for whatever reason purge-nvda wasn't executing anything at that step.
Seems like we actually have same laptop so I wonder if you have any idea what I can do there?
@reptilianbrain It was stuck at boot because the NVRAM value may not have been set correctly. This is mentioned in the first post for the script. If that happens, running purge-nvda option #4 solves the issue.
So to clarify, the most optimal way to run the patches on a clean system:
- Run purge-wrangler.sh - then boot with eGPU (timed plugin ofc) - all should be fine and only Metal acceleration should work.
- Run purge-nvda.sh - choose the appropriate option, then back to menu, then choose reboot there.
This has almost always worked for me. If it doesn't boot, I run purge-nvda option #4 to rewrite the NVRAM patches. If purge-nvda doesn't execute in Single User Mode (unknown issue) - using Safe Boot or Recovery's terminal to run it is a great alternative. Sometimes, the script may take up to a minute to execute in single user mode.
Sadly I don't use the eGPU (just testing at this time) at all to give good insight into my experience across the system with the eGPU.
@mac_editor thank you so much for your help. I reinstalled the script and everything works!
Sublime renders correctly, all the transparency glitches are gone. I basically have a fully functional eGPU now.
One last question - is it generally safe to update OSX and if so - should I re-run the script upon every update - both wranger and nvda?