Double bind Bug on LZDoom v3.88A for Linux

Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies
BBCode is OFF
Smilies are ON
Topic review
   

Expand view Topic review: Double bind Bug on LZDoom v3.88A for Linux

Re: Double bind Bug on LZDoom v3.88A for Linux

by I'mSorry » Wed Nov 01, 2023 12:59 pm

drfrag wrote: ↑Mon Oct 30, 2023 8:33 am You need to replicate the bug and likely find when it started, this time i had to confirm it was a GZDoom bug but it was already fixed. Y wenas xD.
jajaja wenas xD
Yeah man, that bug was giving me issues but I actually managed to switch to the most current gzdoom. Runs decently enough con mi viejita haha.

Re: Double bind Bug on LZDoom v3.88A for Linux

by drfrag » Mon Oct 30, 2023 8:33 am

You need to replicate the bug and likely find when it started, this time i had to confirm it was a GZDoom bug but it was already fixed. Y wenas xD.

Re: Double bind Bug on LZDoom v3.88A for Linux

by I'mSorry » Sun Oct 29, 2023 5:21 pm

drfrag wrote: ↑Sun Oct 29, 2023 4:34 am I've confirmed the bug on windows GZDoom 3.3.2 and 4.6.1. It's not present on 4.10.0.
bind g "slot 7"
doublebind g "slot 6"
Both worked as slot 6.
How is it that you troubleshoot bugs and fix them? I've always been curious about that side of things.

Re: Double bind Bug on LZDoom v3.88A for Linux

by drfrag » Sun Oct 29, 2023 4:34 am

I've confirmed the bug on windows GZDoom 3.3.2 and 4.6.1. It's not present on 4.10.0.
bind g "slot 7"
doublebind g "slot 6"
Both worked as slot 6.

Re: Double bind Bug on LZDoom v3.88A for Linux

by I'mSorry » Sat Oct 28, 2023 10:39 am

Graf Zahl wrote: ↑Sat Oct 28, 2023 9:34 am The Windows drivers for this hardware are hopelessly broken by now, the hardware is simply too old. It is also the weakest GPU around that still runs OpenGL 3.x, so performance wise it won't work that well with more recent GZDooms - in this case LZDoom may still be your best option.
Yeah, it's super outdated for windows. Linux to the rescue, woo hoo.
I managed to get the latest gz to a somewhat "playable" state, The dips aren't as often and the doublebind bug present on the lzdoom is not there. Still prefer the lzdoom pot for my hardwear, though i'll give the latest gz a try for a bit and see how it goes

Re: Double bind Bug on LZDoom v3.88A for Linux

by Graf Zahl » Sat Oct 28, 2023 9:34 am

The Windows drivers for this hardware are hopelessly broken by now, the hardware is simply too old. It is also the weakest GPU around that still runs OpenGL 3.x, so performance wise it won't work that well with more recent GZDooms - in this case LZDoom may still be your best option.

Re: Double bind Bug on LZDoom v3.88A for Linux

by I'mSorry » Sat Oct 28, 2023 8:50 am

Rachael wrote: ↑Sat Oct 28, 2023 8:03 am https://www.intel.com/content/www/us/en ... tions.html
This may be more helpful in understanding the processor.

Apparently this type of processor comes at a time before Intel started numbering their HD series.

Here's a wikipedia link to the Gen6 Intel GPU's where this apparently falls into: https://en.wikipedia.org/wiki/List_of_I ... units#Gen6

The processor is codenamed "Sandy Bridge" here, and on Linux that means we have OpenGL 3.3 and OpenGLES 3.0.
Running windows was almost a slog, i'd get countless errors. When I moved over to POP, in general everything ran so much better. This gave me a little more incite on how my machine works and cleared up a bit of questions I've had about my laptop for ages so thank you for that. It's not the worst thing and it's not the best. I've taken care of this laptop for ages and it's given me years of none stop service <3

I'll try to tweak GZ and see if I can't get any more juice out of it. The fact that the most recent gz even ran surprised me since gz hasn't worked for me since 4.x

Re: Double bind Bug on LZDoom v3.88A for Linux

by Rachael » Sat Oct 28, 2023 8:03 am

https://www.intel.com/content/www/us/en ... tions.html
This may be more helpful in understanding the processor.

Apparently this type of processor comes at a time before Intel started numbering their HD series.

Here's a wikipedia link to the Gen6 Intel GPU's where this apparently falls into: https://en.wikipedia.org/wiki/List_of_I ... units#Gen6

The processor is codenamed "Sandy Bridge" here, and on Linux that means we have OpenGL 3.3 and OpenGLES 3.0.

Re: Double bind Bug on LZDoom v3.88A for Linux

by I'mSorry » Sat Oct 28, 2023 6:09 am

Graf Zahl wrote: ↑Sat Oct 28, 2023 5:45 am Out of interest, what's your graphics hardware? GLES working worse than full GL is a bit odd, though.
Sure thing graf here you go:

OS: Pop!_OS 22.04 LTS x86_64
Host: Samsung 300E4A/300E5A/300E7A/3430EA/353 (computer model)
Kernel: 6.4.6-76060406-generic
Shell: bash 5.1.16
Resolution: 1366x768
DE: GNOME 42.5
Terminal: gnome-terminal
CPU: Intel Celeron B800 (2) @ 1.500GH
GPU: Intel 2nd Generation Core Proces
Memory: 3901MiB / 5829MiB

Re: Double bind Bug on LZDoom v3.88A for Linux

by Graf Zahl » Sat Oct 28, 2023 5:45 am

Out of interest, what's your graphics hardware? GLES working worse than full GL is a bit odd, though.

Re: Double bind Bug on LZDoom v3.88A for Linux

by I'mSorry » Sat Oct 28, 2023 5:10 am

Graf Zahl wrote: ↑Fri Oct 27, 2023 11:18 pm What part of "this port has been discontinued" is unclear? Since it is no longer maintained, there won't be any bug fixes. If you need up to date support for older hardware use GZDoom's GLES backend.
My issue is that the GLES backend doesn't work for me all that well. What I ended up doing was changing the backend and rendermode to" vid_preferbackend=0" "vid_rendermode=0" for the latest GZDOOM. That got it running, but still, sometimes it dips really badly, and it gets really bad at times with some mods that run perfectly on LZ.

There's no harm in asking about it though. Thank you for taking your time to reply graf.

Re: Double bind Bug on LZDoom v3.88A for Linux

by I'mSorry » Sat Oct 28, 2023 4:52 am

drfrag wrote: ↑Sat Oct 28, 2023 1:44 am Besides i didn't change anything there. If there was a bug most likely it was in old GZDoom too.
@I'mSorry what commands did you write exactly in the console? Try GZDoom 3.3.2 it will run on your hardware.
I just wrote the normal bind [key] [command] and doublebind [key] [command]
Specifically:
bind f "slot 7"
doublebid f "slot 6"

I'll try 3.3.2 @drfrag thank you :)
It's a shame that it was discontinued though, it has a lot of potential for mobile linux handhelds, that's what i usually use lzdoom on, a ANBERNIC RG351 device! I can take all my doom games and mods everywhere i go (for the most part the ones that can run) in my pocket lol.

Anyway, Thank you for taking the time to reply @drfrag <3

Re: Double bind Bug on LZDoom v3.88A for Linux

by drfrag » Sat Oct 28, 2023 1:44 am

Besides i didn't change anything there. If there was a bug most likely it was in old GZDoom too.
@I'mSorry what commands did you write exactly in the console? Try GZDoom 3.3.2 it will run on your hardware.

Re: Double bind Bug on LZDoom v3.88A for Linux

by Graf Zahl » Fri Oct 27, 2023 11:18 pm

What part of "this port has been discontinued" is unclear? Since it is no longer maintained, there won't be any bug fixes. If you need up to date support for older hardware use GZDoom's GLES backend.

Re: Double bind Bug on LZDoom v3.88A for Linux

by I'mSorry » Fri Oct 27, 2023 9:26 pm

I tested 388b and it has the same issue

Top