Fw909
#2596 posted by
mankrip on 2019/03/18 22:07:09
The lines you are seeing
are the transparency. It's exactly the same transparency method used in old games such as
Sonic 1 for the Sega Genesis.
However, I agree that it doesn't look good in MarkV. A stippled pattern would look better, as implemented in old versions of Makaqu.
#2597 posted by mh on 2019/03/19 11:29:01
Shouldn't winquake default this cvar to 1 automatically though since it doesn't support transparency?
Stock WinQuake doesn't support translucency, but several engine mods have added it, of which MarkV is one.
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.
