-
Notifications
You must be signed in to change notification settings - Fork 143
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
[Feature] Color support? #7
Comments
You mentioned in #5 that terminals have limited support for truecolor. While it is more challenging to detect , many of them (including Windows console in Windows 10 when ENABLE_VIRTUAL_TERMINAL_PROCESSING is set) actually do support it . Alternatively, almost any terminal will support 256 color mode, and it is fairly easy to do a rough conversion from RGB. Sorry, I can't remember which reference I used for the color palette. |
Hi, thanks for the suggestion. I may actually take another look at this when I next get a bit of free time. It should be possible to implement ANSI true color and just have it enabled behind a |
I've put a rough implementation of true color in the I don't own a OSX device so cannot test there. Open to any feedback if either of you own a Mac. Can run out of the # clone the project
$ git checkout feature/true-color
$ npm install
$ npm run build
$ node index --color |
Have pushed a release to npm $ npx zero-demo@latest --color Have fun! |
Wow thanks! That's amazing! Works great on my Linux machine. I might be able to test on OSX at work. |
Greetings from 2022! I love this project. I thought you might like to see how well true color runs these days. This is on a Mac M1 Max, in iTerm 3.0. ZeroRenderer_5.mp4 |
@liamdon Hey thanks for sharing :D That looks like it runs pretty great! |
The current demo is amazing and crazy enough in itself. Frankly looking at it, I have this certain disbelief that I'm looking at an actual terminal window with 3D graphics.
That said, is there any chance to push it even further with colors? Really just wondering, awesome work already!
The text was updated successfully, but these errors were encountered: