04-28-2009
Exceed and offscreen rendering
Hi everyone.
I made a program which renders a 3D scene into a pbuffer/pixmap (if pbuffer aren't supported) in order to export it to a postscript file.
On a RHEL4 (32/64 bits) or whatever distribution may be, it works just fine.
I'm using Exceed when I'm working under WinXP and each time I run my program, more specifically when I export my 3D scene (visualization is OK) using pbuffers or GLX pixmaps, I have this kind of error message:
X Error of failed request: BadImplementation (server does not implement operation)
Major opcode of failed request: 134 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial number of failed request: 22
Current serial number in output stream: 22
Any help will be appreciated.
3 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
Does anyone know why Fonts and most Graphics in KDE and Gnome are rendered rather badly. There are some text editors in KDE where the font is just horrible as far as legible.
Any links or knowledge on this topic would be grealy appreciated.
A Huge Unix/Linux Fan
Gregg (2 Replies)
Discussion started by: gdboling
2 Replies
2. Red Hat
I encounter the following crash on RHEL 7.0 when I run a multithreaded video rendering application using GLFW and OpenGL. OpenGL version is 2.1 and MESA version is 9.3.0
Following is the back trace of the multi-threaded program I am working on:... (0 Replies)
Discussion started by: anuachin
0 Replies
3. Fedora
Look this very good rendering on Slackware 14.2
in my opinion is near perfect.
https://i.stack.imgur.com/q5trL.png
Now look the same page on Fedora 30
https://i.stack.imgur.com/FBQv7.png
In my opinion the fonts on Fedora are too small and difficult to read, I prefer the fat fonts of... (20 Replies)
Discussion started by: Linusolaradm1
20 Replies
LEARN ABOUT SUSE
xerrorevent
XErrorEvent(3) XLIB FUNCTIONS XErrorEvent(3)
NAME
XErrorEvent - X error event structure
STRUCTURES
The XErrorEvent structure contains:
typedef struct {
int type;
Display *display; /* Display the event was read from */
unsigned long serial;/* serial number of failed request */
unsigned char error_code;/* error code of failed request */
unsigned char request_code;/* Major op-code of failed request */
unsigned char minor_code;/* Minor op-code of failed request */
XID resourceid; /* resource id */
} XErrorEvent;
When you receive this event, the structure members are set as follows.
The serial member is the number of requests, starting from one, sent over the network connection since it was opened. It is the number
that was the value of NextRequest immediately before the failing call was made. The request_code member is a protocol request of the pro-
cedure that failed, as defined in <X11/Xproto.h>.
SEE ALSO
AllPlanes(3), XAnyEvent(3), XButtonEvent(3), XCreateWindowEvent(3), XCirculateEvent(3), XCirculateRequestEvent(3), XColormapEvent(3), XCon-
figureEvent(3), XConfigureRequestEvent(3), XCrossingEvent(3), XDestroyWindowEvent(3), XExposeEvent(3), XFocusChangeEvent(3), XGraphicsEx-
poseEvent(3), XGravityEvent(3), XKeymapEvent(3), XMapEvent(3), XMapRequestEvent(3), XPropertyEvent(3), XReparentEvent(3), XResiz-
eRequestEvent(3), XSelectionClearEvent(3), XSelectionEvent(3), XSelectionRequestEvent(3), XUnmapEvent(3), XVisibilityEvent(3)
Xlib - C Language X Interface
X Version 11 libX11 1.3.2 XErrorEvent(3)