From: R0b0t1 <r030t1@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OpenScad produces no visible rendering at all
Date: Fri, 20 Oct 2017 21:32:24 -0500 [thread overview]
Message-ID: <CAAD4mYiTHtak85CFY4BegvPtF93rF4-JfBVs6eOpKfPZbFW2iQ@mail.gmail.com> (raw)
In-Reply-To: <20171021014142.mds3mckylbmftzfc@solfire>
On Fri, Oct 20, 2017 at 8:41 PM, <tuxic@posteo.de> wrote:
> Hi,
>
> After installing OpenScad I started an example.
> After the loading process ends I hit "preview" -
> a script compiling process starts,,,and....
> nothing was shown.
> Same happens, when I hit "rendering".
>
> from lspci (the smaller card feeds the desktop, the bigger one is for Rendering
> with Blender only, I set CUDA_VISIBLE_DEVICES=0)
> 02:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1)
> 02:00.1 Audio device: NVIDIA Corporation Device 0fba (rev a1)
> 09:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)
> 09:00.1 Audio device: NVIDIA Corporation GF108 High Definition Audio Controller (rev a1)
>
> Output on OpenScad own terminal after hitting preview of the example "CSG.openscad)
> Compiling design (CSG Tree generation)...
> ECHO: version = [2015, 3, 0]
> Compiling design (CSG Products generation)...
> Geometries in cache: 2
> Geometry cache size in bytes: 62800
> CGAL Polyhedrons in cache: 0
> CGAL cache size in bytes: 0
> Compiling design (CSG Products normalization)...
> Normalized CSG tree has 6 elements
> Compile and preview finished.
> Total rendering time: 0 hours, 0 minutes, 1 seconds
>
> Outout on the terminal, from which I started OpenScad:
> solfire:/home/mccramer>openscad
> using visual class 4, id 2b
> hijackWindow() context created for LaunchingScreen(0x2ade380, name = "LaunchingScreen") 1
> Created Window Surface FBO QSize(620, 418) with samples 8
> hijackWindow() context created for MainWindow(0x2b0ed20, name = "MainWindow") 1
> Created Window Surface FBO QSize(1920, 1141) with samples 8
> hijackWindow() context created for QWidget(0x2b5b010, name = "centralwidget") 2
> hijackWindow() context created for QWidget(0x2cab240, name = "mainWidget") 3
> hijackWindow() context created for QToolBar(0x2bc6350, name = "viewerToolBar") 4
> hijackWindow() context created for QMenuBar(0x2bf2580, name = "menubar") 5
> hijackWindow() context created for QStatusBar(0x2c1ca20, name = "statusbar") 6
> hijackWindow() context created for QSizeGrip(0x2c1cda0) 7
> hijackWindow() context created for QLabel(0x33ff150) 8
> hijackWindow() context created for QLabel(0x2b9eb70) 9
> hijackWindow() context created for Dock(0x2b05220, name = "editorDock") 10
> hijackWindow() context created for Dock(0x2ba9fe0, name = "consoleDock") 11
> hijackWindow() context created for QMenu(0x2b02c00, name = "menu_View") 1
> Created Window Surface FBO QSize(184, 583) with samples 8
>
> What wrong here?
> Why I can't see any rendered output?
>
> Cheers
> Meino
>
Hello,
Are you using OpenSCAD interactively? When I used BRL-CAD rendering
and viewing were separate actions. You could render headlessly.
Cheers,
R0b0t1
next prev parent reply other threads:[~2017-10-21 2:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 1:41 [gentoo-user] OpenScad produces no visible rendering at all tuxic
2017-10-21 2:32 ` R0b0t1 [this message]
2017-10-21 2:42 ` tuxic
2017-10-21 2:53 ` R0b0t1
2017-10-21 3:01 ` tuxic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAD4mYiTHtak85CFY4BegvPtF93rF4-JfBVs6eOpKfPZbFW2iQ@mail.gmail.com \
--to=r030t1@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox