raysan5
commented
7 years ago Hi @htrob, it could be related to several things, mostly related to the Intel GPU itself and the Mesa driver:
- GPU VRAM available
- GPU NPOT textures support
- GPU OpenGL 3.3 Core features support
- Mesa driver GPU capabilities detection
It can also be related to PNG loader but that's more improbable.
Please, could you provide some of the textures that fail the most? What sizes are you using? Could you try using BMP images instead of PNG? Do you get any output log on the crash? If texture.id is not valid it should appear some WARNING log.
EDIT1: Could you provide more info on the Intel GPU specs? I can't find it...
EDIT2: After some research, it seems that it probably uses a Intel HD Graphics 515 GPU:
The Intel HD Graphics 515 (GT2) is a low-end integrated graphics unit, which can be found in the Core m-series of the Skylake generation. This "GT2" version of the Skylake GPU offers 24 Execution Units (EUs) clocked at up to 1000 MHz (depending on the CPU model). Due to its lack of dedicated graphics memory or eDRAM cache, the HD 515 has to access the main memory (2x 64bit DDR3L-1600 / LPDDR3-1866).
haiitch
gen2brain
Also intel-gpu-overlay, an overlay monitor window charting GPU resource usage.
It's hard to say with precision what's causing this because it's an intermittent problem, I don't seem to be able to find an exact pattern of behaviour.
All the examples that come with raylib-go work just fine, and I wrote a couple of my own that work just fine, loading textures and painting them on screen. However once I started to create slightly more complex tests, I began to experience problems with some textures. I worked to narrow down the problem to the bare minimum, and I realised that the bare minimum code that comes with the examples also exhibits this problem if you leave the code unmodified, and you change the texture images you use.
For example, if I compile any of the raylib-go examples in the textures examples folder, and I run them unmodified they work just fine. Then I only change the image texture the example uses without changing anything of the code, and I start getting errors when I attempt to load the texture to GPU. (the texture load function complains and doesn't return a texture handle).
So I tried different texture sizes. I created different PNG files of different sizes, and ran the code unmodified, only changing the texture files.
The texture samples appear to always work just fine for texture sizes of under 512 x 512 pixels in size. Problems begin to appear after I increase the texture size beyond 512 x 512 pixels, the texture sometimes, apparently randomly, won't load to GPU. This behaviour happens more frequently as you increase the texture size. For example, if you attempt to load a 1024 x 1024 texture, that increases the frequency of failures, the programs fail more often. If you create textures of 2048 x 2048 and above, the frequency of failures is completely unpredictable, and programs fail to load textures of that size more than 50% of the time.
I'm using Ubuntu 16.04 with XGL extensions, and the Compiz manager, on an Intel Compute Stick that comes with a typical Intel GPU. This is the raylib output log when programs in the examples/textures folder are started.
INFO: Initializing raylib (v1.7.0) INFO: Display device initialized successfully INFO: Display size: 1920 x 1080 INFO: Render size: 800 x 450 INFO: Screen size: 800 x 450 INFO: Viewport offsets: 0, 0 INFO: GLAD: OpenGL extensions loaded successfully INFO: OpenGL 3.3 Core profile supported INFO: GPU: Vendor: Intel Open Source Technology Center INFO: GPU: Renderer: Mesa DRI Intel(R) Bay Trail INFO: GPU: Version: 3.3 (Core Profile) Mesa 12.0.6 INFO: GPU: GLSL: 3.30