gal cannot start on surface book

Bug #1519590 reported by Mark Roszko
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
Undecided
Unassigned

Bug Description

Attempting to enable GAL on a Surface Book results in the error "Could not create OpenGL canvas"

The book DOES support OpenGL. In fact it runs an OpenGL 4.5 benchmark beautifully (GpuTest 0.7.0)

The laptop contains a Intel HD Graphics 520 and a Nvidia GeForce GPU (custom model). It is brand new and in its default configuration and latest drivers (forced by microsoft ;) )

Can't find any assert or log output otherwise on the Windows install so trying to figure out how to debug.

Tags: cern gal
summary: - surface book gal
+ gal cannot start on surface book
description: updated
Revision history for this message
Mark Roszko (mark-roszko) wrote :

Using "glview" a nice tool that dumps all the gl driver info on Windows.

I attached a report of the Intel HD 520 reported capabilities.

Getting a report of the Nvidia chip will be difficult

Revision history for this message
Mark Roszko (mark-roszko) wrote :

also 3d viewer works fine, just GAL isnt working

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

All the "has the entry point .. missing" messages at the end of the report look a bit suspicious. Though it does not explain why does GpuTest work flawlessly.

Is there a way to force enable the Nvidia GPU? I assume that the Intel GPU is used by default.

tags: added: cern gal
Revision history for this message
Mark Roszko (mark-roszko) wrote :

I forced the Nvidia GPU for pcbnew and glview. Pcbnew still failed to start GAL.

I suspect this could be related to my other bug where the window scaling is completely broken on the high resolution display. When I start gal it creates a TINY TINY little "window" where you can only see part of the X which is what I assume OPENGL_TEST creates. If its dependent on the window scaling in anyway it probably is dieing.

Revision history for this message
Mark Roszko (mark-roszko) wrote :

http://i.imgur.com/M0i5wID.png

You can see the blue "X" box above the mouse which is the window that opens when attempting to switch before the errror message appears. I tried changing my screen resolution but for some reason it looks like wxwidgets/kicad completely shoots itself in the face with the high res display.

Revision history for this message
Mark Roszko (mark-roszko) wrote :

Found the problem, its DPI related.

The wxSize( 50, 50 ) is too small for high DPI monitors. It ends up being small as the image above. Because of this Render event is never generated. (Confirmed via debugger). Changing the size to 500 x 500 fixes it.

Revision history for this message
Mark Roszko (mark-roszko) wrote :

One suggestion I have is trying to use wxDLG_UNIT like this

wxDLG_UNIT( GetParent(), wxSize( 50, 50 ) )

which will attempt to scale relative to the parent window font size.

That seems to work but how well it does on other monitors,etc no clue.

Revision history for this message
jean-pierre charras (jp-charras) wrote :

Your suggestion works fine on my PC (W7, monitor 1920x1080)
Using wxDLG_UNIT, the actual size is 75, 75.

Jon Neal (reportingsjr)
Changed in kicad:
status: New → Fix Committed
Changed in kicad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.