I don't have a PS4 controller, but the guides I've seen online about using them on a PC all talk about using a driver called ds4windows, which presents the controller to games as an Xinput device (emulating an Xbox controller). With that driver installed, I'd expect it should work with no extra configuration through MarkV's Xinput support.

My understanding of DirectInput is, it should probably be disabled by default unless you have a match from a mappings database like https://github.com/gabomdq/SDL_GameControllerDB/blob/master/gamecontrollerdb.txt because the axis mappings are going to be random otherwise, so you'll have spinning on the spot problems etc. Winquake had it disabled by default for the same reason. 

I can loan you a PS4 controller to test. I have two and we rarely play split screen. Since we're in the US. Shipping would be no big deal if using ground. LMK.

Ericw I'd offer but IIRC customs is a drag on your end right - or has that changed? 

Thanks for the thought, yeah, shipping + customs would probably be cost prohibitive; I was thinking of getting one since they seem like a nice controller. 

I could send you a 3rd party controller if you like. It's a GameSir. Switches between dinput, xinput and iOS. Wireless with a dongle... Lemme know. I'm in sunny Scotland. :) 

Which model do you own? I personally have the G3s, as it's really good for the price imo. 

Yeah, that's the one. I use it on my PS3 which I only have around for Xevious Resurrection!

For the money, it really is pretty good. Nice and sturdy. :) 

@dumptruck_ds - I should be able to get my hands on one.

@ericw - Yeah, more or less at some point I'm going to do pretty much what SDL2 does ... if not downright take that chunk of the code eventually. Ironically that controllerdb is more or less in the SDL2 source code. 

Download: Windows - Direct X | WinQuake

Revisions:
1) Eliminating a config reading issue (johnnylaw)
2) Must add -joystick to command line to enable Xbox controller support

The adding -joystick to avoid false axis interaction with non-Xbox controllers. Some time in the future, I'll extend the implementation of controller support to an SDL2 level where it detects and remaps a quantity of known controllers.

----
Alternate extra builds which are provided for experimentation purposes or have been specifically requested: Extra builds 

Video config stuff looks good. Will do install tests later. 

Updated the downloads/installer on:

http://quakeone.com/markv

Empty queue of existing issues, I think this build classifies as "rock solid".

(Always more features to do ...) 

Install tests are clean. 

Congratulations! I've just been playing Quoth on a laptop at 4k. A bit choppy here and there but it's an Intel HD 5500 so I don't think it's 1099. Glad you updated the website. I was going to nudge you a bit on that!

Now I can do that video! 

How is the default contrast value of 2 looking for people? It seemed ok running in a Windows VM on my Macbook, but on my desktop I had to crank it down to a value of 1. 

My mistake, it was also 1 in the VM too. Not sure how that happened since 2 is the default; maybe the previous build had a different default? 

The contrast default wasn't supposed to be changed. I may have been comparing different values between the hardware and software renderers.

I'll reupload. 

(Updated) 

So is this build now fully capable of running latest version of Arcane Dimensions or some limits still need to be raised? 

I was able to play Sepulcher on the first build of 1099. I have not attempted Ter Sheboleth yet. That would be the real ball buster, even compared to Sepulcher. 

@NightFright/dumptruck_ds ... Loads Sepulcher and every dm4jam map.

..
..
..

Didn't feel like posting a technical post ... but ...

..
..
..


Eventually I will implement a big coordinates protocol (for maps like Ter Shobelth) like FTE-999, which takes the weaknesses of protocol 999 and fixes them.

I wouldn't be able to implement the very flawed and incomplete protocol 999, which cannot do co-operative play at all, because it would gross me out too much and I'd feel like vomiting.

Co-operative play is important. Any "big coordinates" protocol must be one that do co-operative play. And 999 sure cannot, but FTE999 sure can.

A large maps protocol like FTE-999 is on the to-do list. A 2019 item. But I also want prediction, framerate independence and something else I want which is boring and technical.

/End snooze fest technical post 

If you do a co-operative game, do you want to ...

1) Be killed by invisible monsters?
2) Be killed by vore balls you can't see?

That is what broken protocol 999 will offer you in co-operative play.

It also has "scale", which doesn't work on 2/3 of entity types (.bsp, sprites) and also doesn't work right on the other 1/3 of entities (.mdl) and would result in Ogre feet in the floor and bad collision.

So it is just loaded to brim with the brokesters upon more brokesters.

Wanting large-coordinates is a valid thing!

And those needs will be met in the future, but more in a FTE-999 manner that doesn't offer invisible monsters and being killed by vore-balls you cannot see. 

I'll go through and retest everything I've reported in the past....

First thing I checked: Looks like unpacked pak files now work.


Hey, Proquake 4.93 seems to have nicely-populated server browser (finds 36 servers).... Mark V only shows like 5 servers. How about reading Proquake's protocol to help populate your server list? 

lenovo e480 win10-64
intel uhd 620 latest drivers
dxdiag seems good, still no dx seems to be present, all versions of dx-mark5 prompt an error, even older ones from 2016.

Good news is the last gcc version does run fine, nno errors seen while playing +5hrs.

Older versions/Win7 does work all of time by now.
Tested 1.99 on various hardware btw, all fine.

Congrats Baker! 

Get DX9 runtime here: https://www.microsoft.com/en-ie/download/details.aspx?id=35 

all versions of dx-mark5 prompt an error

You know, I really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, really, HATE it when people do this.

At least you could say what the error message was.

Those things don't exist for bamboozlement or amusement, you know. They exist to provide useful information on how the error might be fixed. Saying what the error message was can enable people to say things like "ah, you got that error message, that's caused by situations A, B, C, and to fix it all you need to do is X, Y, Z" 

https://imgur.com/a/bfS8kYC

DxDiag: https://imgur.com/a/bfS8kYC

https://imgur.com/a/bfS8kYC

Sorry.