the libGL error gave me the idea, that this problem might be related to context-sharing:

• Gem creates a local shareable context (producing the libGL errors)
• and then tries to share this with the remote context (producing the rendering problems)

possible solution: do not try to create/use a shareable context when the display is set.

---

[bugs:#235] gemwin: cant render on remote monitor

Status: open
OS: linux
Release: unknown
Labels: gemglxwindow
Created: Sat Sep 13, 2014 10:30 AM UTC by kubriel
Last Updated: Thu Sep 18, 2014 03:43 PM UTC
Owner: nobody

usually i was using xforwarding to display patch on my laptop, but running pd and gem rendering on big machine.
i used [create :0( for this.
looks like [gemglxwindow] does not take name of the screen..

"[gemglxwindow]: unable to switch to current window (do you have one?), cannot render!"

yes, i have one.

---

Sent from sourceforge.net because gem-dev@lists.iem.at is subscribed to https://sourceforge.net/p/pd-gem/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/pd-gem/admin/bugs/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.