Preview is blank (black) with no errors #4359
Comments
|
Getting only 404 on that repository, is it set to private? |
|
Fixed! Sorry about that |
|
I did see this issue which describes a similar problem, but I don't think it's the same underlying cause - I don't have OpenGL ES installed and I don't see an error in the error log. |
|
The bits per channel in your library info are concerning to me, I've never messed with codespaces, but one thing that's always good to try with OpenGL issues like this, is if you can get output from any GL program, such as |
|
I ran
I'm not sure how/if I can configure the color depth but I'll look into that. |
|
Yeah, I was wondering about the 565 color support. We do need depth and stencil buffers, but that reporting seems unreliable. On my local machine (Dell XPS 13 running Debian/Testing) I'm getting: But with completely black screen, it's more likely a context issue. I suspect it's selecting a 3.1 forward compatible / core profile but we need the compatiblity for the ancient fixed pipeline stuff. Maybe try running with: That should select the compat profile and output issues setting up the context. |
No dice there 😞. I don't see any difference at all in UI, console output, or library & build info. |
|
Hmm, and with even more variables added (second one probably not needed): That might make everything extremely slow with the softpipe rendering but just to see if it makes a difference. Not having high hopes though as llvmpipe is usually quite good nowadays and I have no idea if they maybe even share the context setup code. |
|
Still no change with all four arguments. The rendering time is much slower (around 1.25s instead of around 0.25 seconds) but nothing appears still. Small note - I realized in my original issue description and in the repo I wrote Debian The issue does also happen on Debian Just while playing with things, I did also try combining the FROM openscad/openscad
FROM mcr.microsoft.com/vscode/devcontainers/base:0-bullseyeBut no luck there either; I'm not sure that did anything at all. |
|
Any other ideas I could try before I give up on this? Is there a document with all of the environment variable options anywhere? I could just work through them and try anything that might affect it. Or is there any way to get more detailed logging output? I feel like if I could just find one clue as to why this is happening, I might be able to figure it out. But I have absolutely no idea at this point. |
|
That's all Mesa settings, full list can be found at https://docs.mesa3d.org/envvars.html I'm not sure if there's any additional Qt setup possible, but that likely needs code changes. OpenSCAD itself has no options for tuning the OpenGL context creation. As that's mostly driver interaction, I don't know if there's additional log possible other than what the Mesa environment variables enable. A more complicated by much more detailed trace would be possible using tools like I don't see that I have any access to codespaces. Maybe there's some way to do this locally but that might be more time consuming than what I can manage currently. Or is there dedicated documentation on mirroring the whole setup locally? I did run OpenSCAD via novnc docker container a while ago and that worked without problems. |
|
Thanks! That link at least gives me something else to play with.
I'm sorry, I forgot Codespaces is still in limited access beta. I'm a GitHub employee so I may be able to get you access, but I'm not 100% sure as I'm not on that team. Working on it! It's also possible to run locally (and I was able to reproduce with this method), although I totally understand you may not have the time:
|
|
✨ @t-paul You should have access now! You should be able to see a "Codespaces" tab in the Code dropdown on the repo: |
|
The only thing I've been able to find so far from playing with the environment variables is if I enable But as far as I can tell, that doesn't look like a critical issue that would cause this problem. |
|
Yes, I think the errors are not concerning. I'm a bit surprised about the AARCH64. Are those 64-bit ARM machines running the code spaces? I'm able to start the codespace now (Thanks!) but did not check that. It should not be a no-go for OpenSCAD though, I have OpenSCAD running on 64-bit RaspiOS just fine. |
This is using Docker Desktop on an M1 Max MacBook Pro. In Codespaces it's different: |
Hello! I'm not sure if this is a bug or if it's me doing something obviously wrong (hopefully it's my fault and it's easy to fix 😄).
I'm working on trying to get OpenSCAD running in a Codespace. If you're unfamiliar, Codespaces are essentially just lightweight virtual machines with built-in VSCode integration. I know this isn't an environment that you officially support, but I'm not completely sure if this problem is specific to Codespaces or not. I'm hoping it's just some missing graphics library that I need to install.
The Problem
OpenSCAD is running in the virtual environment and almost everything looks great, but the rendered preview pane is always a solid black rectangle:
Nothing appears in the error log and the console looks completely normal:
Here's my library & build info, collapsed for brevity:
Library and Build Information
Reproducing
I'm running OpenSCAD 2021.01 on a Debian distribution using the following simple Dockerfile:
I'm viewing the OpenSCAD window through the desktop-lite devcontainer feature, which adds a desktop environment to codespaces, powered by the Fluxbox window manager.
I've published this configuration as a repository, so this can be reproduced by following the "Getting started" section in that repository's README.
Please let me know if there is any more info I can provide!
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: