Last prboom update is awful. The lack of functionality (not possible to change the screen resolution or go full screen) can be forgiven, the datalos is much worse: the old configuration (like keyboard mapping) is lost and savegames from the old version does not work ("incompatible savegame" error message).
I guess this was caused by the changes made upstream, not by packaging, but this is a kind of situation one would be expecting whenm updating from Rawhide, not from the stable branch.
Hi Nicu,
Nicu Buculei wrote:
Last prboom update is awful. The lack of functionality (not possible to change the screen resolution or go full screen) can be forgiven, the datalos is much worse: the old configuration (like keyboard mapping) is lost and savegames from the old version does not work ("incompatible savegame" error message).
I guess this was caused by the changes made upstream, not by packaging, but this is a kind of situation one would be expecting whenm updating from Rawhide, not from the stable branch.
I apologize for this. I was a little overeager to push out this release when I should have done so for the devel branch only.
I filed an bug upstream about the screen resolution problem. Even though the on-screen menu has removed this option, you can still change the resolution using both the configuration file $HOME/.prboom/prboom.cfg and the -width and -height command line options.
I haven't run into the fullscreen problem, though. If you go to options->general there is an option to switch from fullscreen to windowed mode and back. Is this not working for you?
I completely overlooked the incompatibilities with savegames because I didn't have any 2.3.1 save games when I upgraded. I apologize for that oversight. Just remember, 'iddqd' can help get you back to where you were before. :)
--Mike
Michael Thomas wrote:
I filed an bug upstream about the screen resolution problem. Even though the on-screen menu has removed this option, you can still change the resolution using both the configuration file $HOME/.prboom/prboom.cfg and the -width and -height command line options.
I haven't run into the fullscreen problem, though. If you go to options->general there is an option to switch from fullscreen to windowed mode and back. Is this not working for you?
For me 'fullscreen' means the full screen is like this: the screen turns to 640x480, is all black and in the middle of it the game runs in 320x200 (this is with the default settings). It also look like using software rendering instead of OpenGL (I understood from an earlier message it was supposed to use exclusively OpenGL)
I completely overlooked the incompatibilities with savegames because I didn't have any 2.3.1 save games when I upgraded. I apologize for that oversight. Just remember, 'iddqd' can help get you back to where you were before. :)
Honestly, I don't care either by savegames, I was hit by the loss of keyboard mapping which made me to investigate further and see the savegames are broken.
'iddqd' or 'idclev', or, better, a combination of both
Nicu Buculei wrote:
For me 'fullscreen' means the full screen is like this: the screen turns to 640x480, is all black and in the middle of it the game runs in 320x200 (this is with the default settings).
After changing the resolution to a bigger one by editing the config file, it works OK is full screen, but in a new install or update it switches automatically to 320x200, which does not work in full screen, I will add a comment on the upstream bugzilla.
Nicu Buculei wrote:
It also look like using software rendering instead of OpenGL (I understood from an earlier message it was supposed to use exclusively OpenGL)
OK, I figured this: that was the case for 2.4.1-1, the latest is 2.4.1-2 which install two binaries, one with OpenGL and another with software rendering and the menu points to the software version. How about changing the launcher to point to the OpenGL version and leave the other as a safe backup option available from the command line?
Nicu Buculei wrote:
Nicu Buculei wrote:
It also look like using software rendering instead of OpenGL (I understood from an earlier message it was supposed to use exclusively OpenGL)
OK, I figured this: that was the case for 2.4.1-1, the latest is 2.4.1-2 which install two binaries, one with OpenGL and another with software rendering and the menu points to the software version. How about changing the launcher to point to the OpenGL version and leave the other as a safe backup option available from the command line?
I think that software rendering is the safer default, or maybe even better a wrapper script which detects _true_ opengl support (using glxinfo?) and then chooses.
Regards,
Hans
Michael Thomas wrote:
I haven't run into the fullscreen problem, though. If you go to options->general there is an option to switch from fullscreen to windowed mode and back. Is this not working for you?
I promise this is my last message on this thread, i don't want to become too annoying: i figured also the fullscreen problem - i was using the launcher from the menu, which uses the binary built with software rendering, starting the OpenGL built binary, it works fine in fullscreen - yet another reason to change the launcher.
-
Hans de Goede -
Michael Thomas -
Nicu Buculei