search

umlaeute / Gem

Graphics Environment for Multimedia (official repository)
https://gem.iem.at
Other
103 stars 30 forks source link

buffer 1 initialisation are not working properly with "gemglfw3window" #442

Open ch-nry opened 2 months ago

ch-nry commented 2 months ago

Detail

On my computer, nothing is rendered if I did not click a 1st time on the gemwin "bang" test_buffer1.pd.zip Nothing important, but it's not need on osX, so it's mostly a cross platform inconsistency.

Gem Version

ver: 0.94.git 9beb39da7

Pd Version

0.55

Operating System

Linux

OS Version

ubuntu mate 22.04

Which CPU are you using?

amd64/x86_64 ("64bit Intel")

ch-nry commented 2 months ago

it's the same after manually changing the rendering window size, a bang need to be send.

umlaeute commented 2 months ago

unable to reproduce. it works for me for:

it's not working for the SDL backends (gemsdl2window, gemsdlwindow), but SDL2 is being removed from the archives of various Linux distributions, so I'm not going to fix that.

as is traditional, the window buffer is not cleared when creating in single-buffered mode. (so chances are that it is not black, but filled with whatever was on the screen when the window got created). this might be different on macOS, but if so i think it amounts to different openGL implementations. (and not something i would like to try to "fix")

ch-nry commented 2 months ago

It must be the GPU driver then. My last example (audio GPU) did not work if I did not send a 1st bang to the gemwin, after it's creation. it's not really important, since a easy workaround exist.