Thread Closed Due To Spam.
#2611 posted by
Shambler on 2019/04/22 13:15:03
Thread Re-opened So People Can Read The Spam
#2612 posted by
Shambler on 2019/04/22 20:36:54
Whaaaaaat?
This place... I was just curious as to why a particular thread was closed.
Sorry.
#2614 posted by
Shambler on 2019/04/22 23:15:56
Didn't mean to be arsey, but it has been annoyingly persistent on this thread recently.
Bleep Bloop
Wonder what the the target words are that the bot is using to to focus on this thread?
Well.
#2616 posted by
Shambler on 2019/04/23 10:28:28
I was wondering if the bots keep chasing their most recently spammed threads?? Tho, obviously the browser / mobile thread was targetted by words.
Quake Mark V Source Port Problems
#2618 posted by Algo on 2019/04/29 18:33:09
Hi, I downloaded Mark V and it's really good in general. However unfortunately I seem to have some issues with the mouse buttons. Occasionally it doesn't detect when I've fired a bullet (i.e. clicked mouse button 1), occasionally it doesn't detect a jump (mouse button 2) and sometimes it just keeps shooting by itself even when I've stopped pressing the mouse button.
I know it's not my mouse because it doesn't happen in any other games, including when I use Quakespasm.
I'm running the
.exe that is titled 'Mark V Version 1.99 Revision 5'. I downloaded it from here http://quakeone.com/markv/ ('Download GOG/Steam installer for Windows' option).
If there are any solutions to this I'd be grateful, thanks!
Continuing From #2618
#2619 posted by algo on 2019/05/03 09:15:58
Hello, me again. So after doing some experimenting with an older Mark V build (1036), we've found that DirectInput is the culprit for causing the mouse registry issues. Build 1036 did not use DirectInput and there are no longer any mouse-click registry issues with it for me. I would stay on this older build but unfortunately it comes with some pretty bad framerate drops here and there, unlike the newest one.
If Mark V 2.0 is ever made, can there be an option to disable DirectInput and go with whatever control configuration was being used in build 1036? I would love for that to happen, as I love the performance of the latest Mark V, it's just the mouse registry stuff ruins it unfortunately.
Thanks for your work baker, hope you can help.
#2620 posted by
mankrip on 2019/05/03 10:35:57
Sadly, Baker disappeared some months ago.
Continuing From #2619
#2621 posted by algo on 2019/05/03 14:26:24
@mankrip yes, I see that from this thread lol. Oh well.
Anyway, good news. It turns out that if I run the latest version's Directx9 exe I no longer have issues with mouse registry. Runs great. This is my new favourite Quake port, even if it currently feels a bit buggier than Quakespasm. I had one crash with this. I exited E1M5 and it crashed to desktop. Hopefully that was just a one off. I really love this port and just wanna express my appreciation. The feel of the mouse is just godlike.
So yeah, cheers, please ignore post #2619 as DirectInput clearly isn't the cause of mouse reg issues, as somehow the directx9 version of the latest released does not have those issues for me.
Winquake Hipnotic Music
#2624 posted by
killpixel on 2019/05/08 00:58:09
scourge of armagon music won't play unless you change the the volume slider. dissolution and vanilla work fine.