Re: gzdoom on raspberry pi
also @Vanfanel, I am curious, how did you compile gl4es if you don't have X11 installed, because X11 is linked and there are a few X11 calls in glx.c?
Re: gzdoom on raspberry pi
@ptitSeb: Some X11 headers and libs seem to be installed on my system, but X11 runtime is not installed or running.
Since X11 is not running (using dispmanx with X11 running is not recommended at all), you can't count on it for anything really.
Does anybody have GL4GLES running without X11 on the Pi?
Since X11 is not running (using dispmanx with X11 running is not recommended at all), you can't count on it for anything really.
Does anybody have GL4GLES running without X11 on the Pi?
Re: gzdoom on raspberry pi
@Vanfanel
Did you had some success using gl4es with LIBGL_GL=1 ? It should mainly use dispmanx and not much X11 in this configuration.
Did you had some success using gl4es with LIBGL_GL=1 ? It should mainly use dispmanx and not much X11 in this configuration.
Re: gzdoom on raspberry pi
I went all the way, built and installed SDL 1.x and all it's deps, and trying LIBGL_FB=1 I get this with stuntcarremake:ptitSeb wrote:@Vanfanel
Did you had some success using gl4es with LIBGL_GL=1 ? It should mainly use dispmanx and not much X11 in this configuration.
Code: Select all
LIBGL: Initialising gl4es
LIBGL: v0.9.5 built on Apr 6 2017 12:03:46
LIBGL: framebuffer output enabled
LIBGL:loaded: libbcm_host.so
LIBGL:loaded: libvcos.so
LIBGL:loaded: libGLESv1_CM.so
LIBGL:loaded: libEGL.so
LIBGL: Extension glBlendColor found and used
LIBGL: Extension GL_OES_framebuffer_object detected and used
LIBGL: Extension GL_OES_depth24 detected and used
LIBGL: Extension GL_OES_rgb8_rgba8 detected and used
LIBGL: Extension GL_EXT_texture_format_BGRA8888 detected and used
LIBGL: Max texture size: 2048
LIBGL: Texture Units: 4, Max lights: 8
LIBGL: Implementation Read is GL_RGBA/GL_UNSIGNED_BYTE
LIBGL: Current folder is:/home/pi/src/stuntcarremake
OpenGL not available
Re: gzdoom on raspberry pi
Also, the basic SDL 1.2 OpenGL test (included with SDL1 sources in ./tests) fails in the exact same way:
So, if the basic SDL1 test doesn't work, I believe nothing will.
Code: Select all
pi@raspberrypi:~/src/sdl1/test $ LIBGL_FB=1 ./testgl
LIBGL: Initialising gl4es
LIBGL: v0.9.5 built on Apr 6 2017 12:03:46
LIBGL: framebuffer output enabled
LIBGL:loaded: libbcm_host.so
LIBGL:loaded: libvcos.so
LIBGL:loaded: libGLESv1_CM.so
LIBGL:loaded: libEGL.so
LIBGL: Extension glBlendColor found and used
LIBGL: Extension GL_OES_framebuffer_object detected and used
LIBGL: Extension GL_OES_depth24 detected and used
LIBGL: Extension GL_OES_rgb8_rgba8 detected and used
LIBGL: Extension GL_EXT_texture_format_BGRA8888 detected and used
LIBGL: Max texture size: 2048
LIBGL: Texture Units: 4, Max lights: 8
LIBGL: Implementation Read is GL_RGBA/GL_UNSIGNED_BYTE
LIBGL: Current folder is:/home/pi/src/sdl1/test
OpenGL not available
Re: gzdoom on raspberry pi
So error message is "OpenGL not available"? and that's it. Mmmmm, I'll try to dig in SDL sources to nderstand what is happening.
Re: gzdoom on raspberry pi
Yes. There could be more non-readable text because SDL1 disables writting to the console at some point on the Pi without X.ptitSeb wrote:So error message is "OpenGL not available"? and that's it. Mmmmm, I'll try to dig in SDL sources to nderstand what is happening.
Re: gzdoom on raspberry pi
Indeed, that meesage comes from SDL, indicating it tries to create an opengl context but failed.
Can you try to uncomment line 32 of src/glx/glx.c of gl4es to have for logs, hopefully the logs will be writen somewhere and can be retreive in some way (did you try to redirect the console to a file also, just in case).
Can you try to uncomment line 32 of src/glx/glx.c of gl4es to have for logs, hopefully the logs will be writen somewhere and can be retreive in some way (did you try to redirect the console to a file also, just in case).
Re: gzdoom on raspberry pi
The complete message is this:ptitSeb wrote:Indeed, that meesage comes from SDL, indicating it tries to create an opengl context but failed.
Can you try to uncomment line 32 of src/glx/glx.c of gl4es to have for logs, hopefully the logs will be writen somewhere and can be retreive in some way (did you try to redirect the console to a file also, just in case).
Code: Select all
LIBGL: Initialising gl4es
LIBGL: v0.9.5 built on Apr 6 2017 12:03:46
LIBGL:loaded: libbcm_host.so
LIBGL:loaded: libvcos.so
LIBGL:loaded: libGLESv1_CM.so
LIBGL:loaded: libEGL.so
LIBGL: Extension glBlendColor found and used
LIBGL: Extension GL_OES_framebuffer_object detected and used
LIBGL: Extension GL_OES_depth24 detected and used
LIBGL: Extension GL_OES_rgb8_rgba8 detected and used
LIBGL: Extension GL_EXT_texture_format_BGRA8888 detected and used
LIBGL: Max texture size: 2048
LIBGL: Texture Units: 4, Max lights: 8
LIBGL: Implementation Read is GL_RGBA/GL_UNSIGNED_BYTE
LIBGL: Current folder is:/home/pi/src/stuntcarremake
Couldn't set 640x480x32 video mode: OpenGL not available
Seems like SDL is trying to set a 640x480 32bpp video mode and fails. Changing physical resolution on the fly is not a good idea... What I always did with dispmanx was to keep the current resolution AND scale to whatever the current resolution is, using dispmanx for hardware scaling.
Re: gzdoom on raspberry pi
Did you uncomment the line in glx.c? If yes, that's surprising because gl4es is not called at all.
The switching to 640x480 is from SDL, not gl4es, and I wonder what is it trying to do. If you compiled stuntcarremake for Linux (not for Pandora), it should try to open a 640x480 windowed + opengl mode (for Pandora, it will open a 800x480 fullscreen+opengl mode).
The switching to 640x480 is from SDL, not gl4es, and I wonder what is it trying to do. If you compiled stuntcarremake for Linux (not for Pandora), it should try to open a 640x480 windowed + opengl mode (for Pandora, it will open a 800x480 fullscreen+opengl mode).
Re: gzdoom on raspberry pi
@ptitSeb: yes, I uncommented line 32 as you said.
The SDL1 GL test (included on SDL 1.2.15 sources) says this:
The SDL1 GL test (included on SDL 1.2.15 sources) says this:
Code: Select all
Couldn't set GL mode: OpenGL not available
LIBGL: Initialising gl4es
LIBGL: v0.9.5 built on Apr 6 2017 12:03:46
LIBGL: framebuffer output enabled
LIBGL:loaded: libbcm_host.so
LIBGL:loaded: libvcos.so
LIBGL:loaded: libGLESv1_CM.so
LIBGL:loaded: libEGL.so
LIBGL: Extension glBlendColor found and used
LIBGL: Extension GL_OES_framebuffer_object detected and used
LIBGL: Extension GL_OES_depth24 detected and used
LIBGL: Extension GL_OES_rgb8_rgba8 detected and used
LIBGL: Extension GL_EXT_texture_format_BGRA8888 detected and used
LIBGL: Max texture size: 2048
LIBGL: Texture Units: 4, Max lights: 8
LIBGL: Implementation Read is GL_RGBA/GL_UNSIGNED_BYTE
LIBGL: Current folder is:/home/pi/src/sdl1/test
Re: gzdoom on raspberry pi
Mmmm, gl4es is not called at all :S
I have to look at SDL to understand how it create it's windows.
Can you give me the ./configure parameter you used tho build SDL?
I have to look at SDL to understand how it create it's windows.
Can you give me the ./configure parameter you used tho build SDL?
Re: gzdoom on raspberry pi
Yes. I use this version of SDL 1.x:ptitSeb wrote:Mmmm, gl4es is not called at all :S
I have to look at SDL to understand how it create it's windows.
Can you give me the ./configure parameter you used tho build SDL?
https://github.com/joolswills/sdl1
It's needed because stock SDL 1.2.15 is prone to hang on the Pi.
It's the version included in RetroPie.
The configure line I used is this one:
Code: Select all
./configure --enable-video-opengl --enable-video-dispmanx --enable-video-fbcon --disable-video-directfb --enable-cdrom --disable-oss --disable-alsatest --disable-pulseaudio --disable-pulseaudio-shared --disable-arts --disable-nas --disable-esd --disable-nas-shared --disable-diskaudio --disable-dummyaudio --disable-mintaudio --disable-video-x11 --prefix="/usr" --disable-input-tslib
Re: gzdoom on raspberry pi
Ah ok.
Unfortunatly, I don't think the dispmanx backend for SDL support GL at all.
Unfortunatly, I don't think the dispmanx backend for SDL support GL at all.
Re: gzdoom on raspberry pi
Id like to know if anyone has successfuly managed to compile any of ptitseb's sources? I haven't really had any luck.
If gzdoom couldn't be compiled what about ptitseb's https://bitbucket.org/ptitSeb/zandronum?
If gzdoom couldn't be compiled what about ptitseb's https://bitbucket.org/ptitSeb/zandronum?
Re: gzdoom on raspberry pi
can you post the log and i got it working its about 30fps.
Re: gzdoom on raspberry pi
Can you show what building process you used, step by step?raysaaron wrote:can you post the log and i got it working its about 30fps.
Re: gzdoom on raspberry pi
First Download the repo from .
and go to the repo and type
if you get a SQLite error do This:
get and rename it to and then This :
Code: Select all
https://bitbucket.org/ptitSeb/zandronum
and go to the repo and type
Code: Select all
cmake .
get
Code: Select all
https://www.sqlite.org/2016/sqlite-autoconf-3140100.tar.gz
Code: Select all
sqlite-774a05b8e7c9318111228bd5ad6bf65272f3fe38.tar.gz
Code: Select all
make
-
- Posts: 226
- Joined: Fri Jan 11, 2013 8:11 pm
- Location: In Hell with God
Re: gzdoom on raspberry pi
Hi !!!
Zandronum runs perfectly on my Raspberry Pi 3, this is my little installation guide:
http://framboisepi.fr/installation-du-m ... zandronum/
Zandronum runs perfectly on my Raspberry Pi 3, this is my little installation guide:
http://framboisepi.fr/installation-du-m ... zandronum/
Mon blog sur le Raspberry Pi : http://framboisepi.fr/
Pour avoir plus de chance d'avoir une réponse à votre question,
allez sur le forum français Rasberry Pi : http://forum.raspfr.org
Pour avoir plus de chance d'avoir une réponse à votre question,
allez sur le forum français Rasberry Pi : http://forum.raspfr.org
-
- Posts: 226
- Joined: Fri Jan 11, 2013 8:11 pm
- Location: In Hell with God
Re: gzdoom on raspberry pi
Hi,
This is my diff file to have the version 3 of Zandronum :
https://github.com/Nekrofage/zandronum3
This is my diff file to have the version 3 of Zandronum :
https://github.com/Nekrofage/zandronum3
Mon blog sur le Raspberry Pi : http://framboisepi.fr/
Pour avoir plus de chance d'avoir une réponse à votre question,
allez sur le forum français Rasberry Pi : http://forum.raspfr.org
Pour avoir plus de chance d'avoir une réponse à votre question,
allez sur le forum français Rasberry Pi : http://forum.raspfr.org
Re: gzdoom on raspberry pi
This is an old thread, but I was wondering if anyone had this error when trying to start a game in zandronum:
Playing /tmp/zmidb2s8s7
MIDI file: /tmp/zmidb2s8s7
Format: 0 Tracks: 1 Divisions: 140
-: Broken pipe
Playing /tmp/zmidb2s8s7
MIDI file: /tmp/zmidb2s8s7
Format: 0 Tracks: 1 Divisions: 140
I was able to successfully compile PititSeb's Zandronum source. I am able to run zandronum (with Doom2.wad). I set the graphics to 1900x1080 (I think this is the resolution.. whatever my desktop is set to. I set the renderer to opengl and I have the mesa open gl drivers installed.
Once I select the diffculty level and start the game, I get booted back to the desktop and the message I pasted above repeats over and over.
Is this something related to MIDI? Sound drivers? I hear the doom 2 music when it begins and here menu sounds...
Any help would be appreciated!
Playing /tmp/zmidb2s8s7
MIDI file: /tmp/zmidb2s8s7
Format: 0 Tracks: 1 Divisions: 140
-: Broken pipe
Playing /tmp/zmidb2s8s7
MIDI file: /tmp/zmidb2s8s7
Format: 0 Tracks: 1 Divisions: 140
I was able to successfully compile PititSeb's Zandronum source. I am able to run zandronum (with Doom2.wad). I set the graphics to 1900x1080 (I think this is the resolution.. whatever my desktop is set to. I set the renderer to opengl and I have the mesa open gl drivers installed.
Once I select the diffculty level and start the game, I get booted back to the desktop and the message I pasted above repeats over and over.
Is this something related to MIDI? Sound drivers? I hear the doom 2 music when it begins and here menu sounds...
Any help would be appreciated!
Re: gzdoom on raspberry pi
I didn't fix Broken Pipe issue yet, but I confirmed it is an issue w/ the sound by running zandronum -nosound. It runs fine with out sound enabled.
I have gzdoom and it runs fine w/ sound. I found a "soundfonts" directory in gzdoom which has a gzdoom.sf2 file. I am guessing zandronum is missing this soundfont or something.
I also can not seem to contact the master.zandronum.com server when browsing multiplayer internet games. I saw previous post where they were blaming the DNS, but I am able to ping master.zandronum.com and get a reply. So my raspberry does resolve the master.zandronum.com (ip: 45.56.67.39)...
I checked in zandronum.ini and found no configuration for this server.
Any ideas why this would not work? When I use the zandronum server browser on my windows tablet, it pulls server fairly quick.
I have gzdoom and it runs fine w/ sound. I found a "soundfonts" directory in gzdoom which has a gzdoom.sf2 file. I am guessing zandronum is missing this soundfont or something.
I also can not seem to contact the master.zandronum.com server when browsing multiplayer internet games. I saw previous post where they were blaming the DNS, but I am able to ping master.zandronum.com and get a reply. So my raspberry does resolve the master.zandronum.com (ip: 45.56.67.39)...
I checked in zandronum.ini and found no configuration for this server.
Any ideas why this would not work? When I use the zandronum server browser on my windows tablet, it pulls server fairly quick.