Open silbinarywolf opened 8 years ago
Milton shouldn't fail silently even if your Intel graphics can't run it. Would you mind pasting the contents of this file? %APPDATA%\MiltonPaint\data\milton.log
. Maybe it has more information about the crash.
Thanks for the bug report!
I'm having a similar issue. Unfortunately, the crash log at $APPDATA%\MiltonPaint\data\milton.log
is a completely empty file.
This is all mine says:
Could not open file for writing prefs
*** [FATAL] ***:
Could not create OpenGL context
Same thing occurs on my Surface 3, running on Windows 10 Pro with Intel HD Graphics, it instantly crashes.
milton.log
is empty.
What folder do you have Milton installed in? Could this be a file access permissions issue?
Crashing with "Could not create OpenGL context" probably means that the card doesn't support GL 3.2. The next release will require a lower GL version. However, it still might fail on cards without the extensions required by Milton.
Crashing with an empty milton.log is more interesting... Not sure what it could be. Could be a very long path name triggering an assertion
Unfortunately it has nothing to do with the path, as it also crashes when located inside a folder on my desktop.
Intel HD Graphics supports every feature from OpenGL 3.0 -> 4.4 according to OpenGL Extensions Viewer.
I'm unfamiliar if this tool is correct or not since the vast majority of my computing is done on Linux, but I'd be more than happy to provide any additional information, and in a more timely fashion (GitHub notifications were disabled).
EDIT: GPU Caps Viewer seems to confirm the above regarding OpenGL support.
This issue could apply to all sorts of problems because Milton's logging sucks (though it sucks less now!)
Is it still crashing for you? Is there any new information (possibly a non-empty milton.log) with the latest version?
I can confirm that 1.2.8 works on my Surface without crashing.
Great work!
This is still a bug on my GPU.
Could not open file for writing prefs
*** [FATAL] ***:
Could not create OpenGL context
It's a driver issue with this graphics card wherein it only supports OpenGL 2.1 on Windows.
See similar issue I had over here: https://github.com/faiface/pixel/issues/26
Milton should at the very least detect when the card does not meet its requirements, instead of just exploding :) Also, Milton doesn't use that many features on top of GL 2.1. I'm hoping I can lower the requirements a bit to make it work with chips like the HD3000
Just ping @ me with various versions if you want to nail down the extensions it does/doesn't have. Not sure the easiest way to get you such a list.
Same problem here (with v.1.51 on Win V.10.0.16299.461. Both x64).
Here's my log:
CommandLine is
Running Milton
Initializing SDL... Done.
Loading preferences... Could not open file for writing prefs
Done.
Creating Milton Window
Created OpenGL context with version 4.5.13521 Compatibility Profile Context 24.20.11016.4
and GLSL 4.50
Easy Tab Failed to load. Code -3Maximum viewport dimensions, 16384.000000x16384.000000
Vendor string: "ATI Technologies Inc."
Milton: loading file
Increased guid to 1
Same problem with v.1.5.1 x64 on latest Windows 10 Pro x64 with Intel HD 3000 graphics (and latest driver available).
CommandLine is
Running Milton
Initializing SDL... Done.
Loading preferences... Could not open file for writing prefs
Done.
Creating Milton Window
Created OpenGL context with version 3.1.0 - Build 9.17.10.4459
and GLSL 1.40 - Intel Build 9.17.10.4459
Maximum viewport dimensions, 8192.000000x8192.000000
Vendor string: "Intel"
Milton: loading file
Could not open file!Increased guid to 1
Basic OpenGL info:
OpenGL version - 3.1.0 - Build 9.17.10.4459
Operating system - Windows 10
Renderer - Intel(R) HD Graphics 3000
Shading language version - 1.40 - Intel Build 9.17.10.4459
Vendor - Intel
I've also attached the full glCapsViewer XML report file (glCapsViewer_Report.xml) for my tablet as a .ZIP file.
Thanks!
Never run Milton before, went to give it a quick go and the window opens then immediately closes (still unpainted/white).
Not at all going to be surprised if its Intel HD Graphics 3000 being awful.