> Warning: Missing OpenGL capabilities for OpenCSG - OpenCSG has been > disabled. > > It is highly recommended to use OpenSCAD on a system with OpenGL 2.0 or > later. > Your renderer information is as follows: > GLEW version 1.12.0 > GDI Generic (Microsoft Corporation) > OpenGL version 1.1.0 I was using Windows Remote Desktop from my 2 core to my new 8 core. Preview and render seemed to work as normal. So what does OpenCSG disabled mean? In the 8 core direct I don't get the error. ----- Admin - PM me if you need anything, or if I've done something stupid... Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above. The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out! -- View this message in context: http://forum.openscad.org/Warning-Missing-OpenGL-capabilities-for-OpenCSG-OpenCSG-has-been-disabled-tp21405.html Sent from the OpenSCAD mailing list archive at Nabble.com.

> On May 4, 2017, at 22:54, MichaelAtOz <oz.at.michael@gmail.com> wrote: > > So what does OpenCSG disabled mean? > We don’t technically disable OpenCSG - we just test if we _think_ your system is capable. It sounds like our tests are not too accurate in this case.. This is what we test: https://github.com/openscad/openscad/blob/master/src/GLView.cc#L213 Cheers, -Marius

MichaelAtOz wrote > Preview and render seemed to work as normal. Correction, preview is only Thrown-Together, no CSG. For posterity >From Technet <https://social.technet.microsoft.com/Forums/windowsserver/en-US/c8295ef8-3711-4576-9293-2c4965280165/opengl-and-remote-desktop?forum=winserverTS> : > In essence, you are using RDP to remote into a physical desktop PC. So > host (office PC) and client (home PC) are both workstation OSes. Now you > want to use OpenGL apps in such a scenario. > > When you start the OpenGL apps on the office PC using the physically > attached monitor and keyboard, the graphics card may be checked by OpenGL > - there are some OpenGL apps that require physical hardware support and > other OenGL apps that are happy with rendering OpenGL in software. Both > checks are successful in this scenario and both flavors of OpenGL run > properly. Now you go to your home PC and establish a remote connection to > this user session. During the connection process, the capabilities of the > home PC's graphics card is sent to the host PC in order to optimize the > graphics output. This is required to do some rendering on the receiver > side rather than on the sender side. This is done for GDI graphics > primitives, but not for openGL primitives. In your "remoting into existing > user session" scenario the OpenGL output on the host is sent to the client > pixel by pixel. > > When you establish a new connection from a home PC to an office PC, the > home PC's graphics capabilities are relevant for the user session. Such a > remote session does not support OpenGL in hardware - in other words, there > is no 3D hardware graphics support. This is why only the software OpenGL > app starts, but not the hardware OpenGL app. So your system works as > designed even if it sounds weird. > > Note: In both scenarios all applications run on the office PC. In the > second scenario the graphics options are a little bit different due to the > OpenGL app already launched in the existing user session. Actually, I'm > surprised that it works at all. I would have expected that the hardware > OpenGL app throws an error when remoting into the existing session. > > I'm afraid that there's not much can do about this behaviour if you don't > want to invest into Citrix (HDX Pro) or VMware/Teradici (PCoIP in HW) > which supports 3D graphics acceleration in hardware from workstation to > workstation. Another option is to run your OpenGL apps in Win7 virtual > desktops hosted on Windows Server 2008 R2 SP1 Hyper-V and use the RemoteFX > extension of the RDP protocol. This option also supports OpenGL in > hardware if the appropriate graphics adapter is installed on the Hyper-V > server. > > Benny Apparently RDP (on W7) only supports OpenGL 1.1 emulation. I've seen references that say other remote products may support higher. ----- Admin - PM me if you need anything, or if I've done something stupid... Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above. The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out! -- View this message in context: http://forum.openscad.org/Warning-Missing-OpenGL-capabilities-for-OpenCSG-OpenCSG-has-been-disabled-tp21405p21407.html Sent from the OpenSCAD mailing list archive at Nabble.com.

Further. If I run OpenSCAD on the remote box, THEN login via RDP it works. (I presume it's just doing screen scraping) Only if I start OpenSCAD on the remote, via RDP do I get the error. ----- Admin - PM me if you need anything, or if I've done something stupid... Unless specifically shown otherwise above, my contribution is in the Public Domain; to the extent possible under law, I have waived all copyright and related or neighbouring rights to this work. Obviously inclusion of works of previous authors is not included in the above. The TPP is no simple “trade agreement.” Fight it! http://www.ourfairdeal.org/ time is running out! -- View this message in context: http://forum.openscad.org/Warning-Missing-OpenGL-capabilities-for-OpenCSG-OpenCSG-has-been-disabled-tp21405p21408.html Sent from the OpenSCAD mailing list archive at Nabble.com.