Why does Hyper force dGPU (2018 MBP)
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
- [x ] I am on the latest Hyper.app version
- [x ] I have searched the issues of this repo and believe that this is not a duplicate
- OS version and name: macOS 10.14.5 (2018 15" MBP)
- Hyper.app version: 3.0.2
- Link of a Gist with the contents of your .hyper.js: https://gist.github.com/mtslzr/a8843911e48dcbdcce6285ee4cb6a8c5
- Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere): N/A
- The issue is reproducible in vanilla Hyper.app: Yes. Tried disabling all plugins, and issue persists.
Issue
Was wondering why Hyper.app requires the dGPU on my 15" MBP? And is there a way to disable it? Scoured a few older issues, but most seemed to talk about external GPUs, and I didn't see an obvious solution.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior on macOS 10.14.5 with Hyper 3.0.2, using the linked .hyper.js and a vanilla installation with plugins disabled. Done means identifying why Hyper requires the dGPU and determining whether a supported way to disable it can be documented or implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100