The only Quake engine that seems to report the BPP in the console is Quakespasm, and it tells me "24-bit" when I try set it to 32 bpp (either in the menu or by command line).

Of course it reports "16-bit" when I change to that....


How would I verify that any other engine is running in any certain bpp?

Well, I can do more than 16 bpp in any case... (what is it, the stone age? :) 

when I just want to sit in front of the TV playing games I whack on some Quake.

I know KB+M is the best way to play but I originally used to play the game keyboard only when I first got the game... :P 

@gunter - that clears up possible causes of the issue.

@fifth/@rick - I'm not against gamepad support.

As long as the controller support code works with current/future devices (@johhny). 

 

I don't claim to keep up with consoles ...

Does the Quakespasm controller support work with an XBox One Controller? 

According to this reddit post the xbox one controller should work with any game that uses XInput, which SDL2 is wrapping, so it should work in QS. I don't know if anyone has tested it though.

Anything listed here should work out of the box with qs, there is also a community mapping file for more support. 

Ok, that clears up things quite a bit -- it supports a wide array of devices.

When I hear "xbox 360 controller" immediately I think "But the XBox One came out back in 2013?" 

@gunter -- you may discover the Dopa maps surprising automatically download now for supporting clients.

/*snort*

/Inside joke, gunter will understand. 

Uhhh... does that mean Polarite updated the server so it will do that now? Hm, yesterday Trans did say he thought he saw Darkplaces download something.... Neat. We'll have to test this more.


We do indeed have the DOPA maps installed on fvf.servequake.com and they work (almost*) perfectly for FvF Quest mode. So everyone should come give it a try! You can use the VOTE menu to activate the custom maps.

* One thing mappers often neglect to do is add Co-op spawn points. DOPA has this oversight... so all the players try to spawn on the one Single-Player spawn point, resulting in undesirable things happening, like people getting pushed into the floor. That can be really bad when there's a lava pit below the floor, heh.

Another "gotcha" you gotta watch out for are trap rooms that lock behind someone when they enter, and if the person dies in there, there's no way for anyone else to get in, so progress is blocked on the map. DOPA contains 2 areas like this, but I work around them with QuakeC code by actually relocating buttons and altering properties of doors on the map, so that the roadblock is moved out of the way or opened from the outside.


But yeah, everyone should come play FvF. The server is almost always in Quest (co-op) mode, so it's newb-friendly.

http://fvfonline.com

(Heck, while I'm self-promoting, here is also a link to find out about my Pogo Piggle games for Android, which everyone should also play :D ) http://tinyvast.com 

Hm, well... we tested today and maps did not automatically download to Darkplaces.

I guess you may be talking about something that has not yet been implemented...?

*scratches head* 

All the old methods of stopping Demos from playing at start up no longer work

It's in the menu so anyone can do that. The cvar is host_startdemos 0 (default 1). 

Wow, that's a really old issue I reported back in 2014, Baker, heh. I think that's been fixed for a long time.... I did find that menu option (that's probably the newer addition). It's very handy.


Probably my main hope for a soon release would be Proquake-positioned Centerprint and "Rankings" scoreboard, so they don't obscure your view right in the middle of the screen.

Actually, I'm not sure exactly how ProQuake's Centerprint positioning works... It seems like if your centerprint message has more than 3 lines or so, it is placed up high, well out of the way of your view. But if your Centerprint message only has 1 or 2 or 3 lines (using \n) it places it down lower near the center of the screen... but still not right in the middle of your view. Maybe it checks to avoid that specifically rather than just moving EVERYTHING up to a certain point (though even the menus are positioned higher). In any case, it's much preferable to having stuff printed right over your crosshair position. 

Can you do a screenshot demonstrating the centerprint issue you are having? My imagination isn't working. 

(Small screenshots just to illustrate the positioning of Centerprints)

http://imgur.com/a/H2qvE

First comparison is the standard FvF Vote Menu. You can see Proquake keeps it up high, not blocking the center of the player's view. Obviously most players aren't going to be running around shooting things with the Vote menu up, but there are other centerprints that happen in the game which have the same issue -- notably, all the FvF splash text stuff when a level first starts... and sometimes there are monster attacking you when the level first starts, so you need to be able to aim :D


Second comparison is me pressing the TAB key to show the scoreboard while the vote menu is still active. I just noticed that Mark V hides any centerprints when you are viewing the scoreboard.... I'm not sure I like that behavior (is there a setting?). A player might miss a centerprint message when doing that.... Well, Proquake shows both things at the same time; yeah, that can end up with overlapping stuff, but a player can easily release TAB when he sees a centerprint pop up.
Anyway, you can see that again Proquake moves the scoreboard up near the top (probably a bit too far in this case, because that can block the second and lower chat line -- there's still room at the very top for one chat line). If there were 4 or 5 players in the server, the Mark V position (which is most likely the standard for Quake) would again block the center of the view, where the crosshair is.

The final comparison shows that the position remains the same when it's a short centerprint with only a few lines (the crosshair positioning may be off a bit, so the relative text position may be exactly the same... or it may be slightly different... not sure). Either way it doesn't block the view, so that's fine.
I'm not sure exactly how Proquake decides where to position stuff, but it seems like if there are 4 or more lines in a centerprint, it puts it way up at the top, but 3 or fewer lines are shown back at the standard location.

These issues become worse if the text size is increased by scr_conscale (I shrunk my text in Mark V to match Proquake, but I usually have it larger, so centerprints sometimes go well below crosshair level). 

@gunter -- re: centerprint position

I connected to your server and tried some of the menus. I thought it looked pretty good with the default settings in both Mark V and ProQuake. If I mess with settings in either engine, I can make it not look good in either of them.

Centerprint consistency has always sucked as tool available to the QuakeC modder, even with GLQuake. If you use a big resolution, the text stops being where it was supposed to be and might even be in annoying place.

If I loaded up Quake with the intended resolution of 320x240, your FVF centerprint will be all over the crosshair. "Gunter? Why u hate DOSQuake so much! Is only real QUAKE! Quake CD comes with DOSQuake, is no GLQuake on Quake CD! GLQuake is a lie!!"

Mark V centerprint starting position is pretty consistent across all video resolutions, but just like original GLQuake if you start changing settings or resolutions it affects the placement (but at least Mark V calculates it the same regardless of any settings/resolutions you can pick).

The centerprint position also relates to the finale printing. I worked long and hard with NightFright to get that all positioned properly and independently even for single player releases like The Rapture that prints incredible gobs of finale text (it's like a mini-thesis, it's that long) --- while also taking into consideration multiplayer mods.

That's called the "fine tuning problem". If you "fix it for one" (combination of settings) then you just "break it for another". 

FitzQuake is pretty much geared to display the multiplayer scoreboard in the center of the screen, as you've noticed. Just like how the menu is very center of the screen in FitzQuake.

A ton of centerprint like a centerprint-based menu on, say, a RuneQuake server, clashes with the FitzQuake multiplayer scoreboard worse than original Quake.

Pretty much makes the scoreboard unreadable.

I tried the Qrack draw a background behind the scoreboard (didn't look Quakey) and a few other thoughts to avoid the problem before realizing no good answer was possible -- so not drawing the text was the only option.

But notice it still does print the chat messages with the scoreboard up! ;-)

I know those are important so I salvaged what I could. 

"Centerprint consistency has always sucked as tool available to the QuakeC modder"

Yep, that's pretty much it.

I can move centerprints DOWN out of the way by padding it with nnnn, but I have to be careful with that, because I could move it right off the bottom of the screen depending on resolution and text size settings of the client....

But there's no way to move it UP out of the way... which is why I greatly prefer them to be placed high on the screen by default, like Proquake does. There's no danger that they will be TOO HIGH, no matter what the client settings.

Since I can move things down but not up, I think it would be great if all centerprints were positioned like 4 text lines down from the top of the screen, no matter what (even for one-line centerprints). There's really no reason for them to be centered vertically anyway.... As I have said, it can block part of what you are trying to look at, leaving all that all that unused free space (resolution and text size permitting) near the top of the screen which could be used instead.

Of course, not all clients do it that way, but Proquake was "the standard" for many years, and that's how it works (I would suspect for the reason I mentioned, as Proquake is supposed to have enhancements for deathmatch play, and not having your view blocked by text is good when in deathmatches).

But yeah, not all clients do it like that....

All these variations in different clients is also a reason why I name Mark V as the "officially recommended" client for FvF -- if I get the majority of players using the same client to play FvF, then I know they are seeing the same thing that I see.


Anyway, my main point would be: There is really no reason centerprints need to be vertically centered. It has potential negative impact, whereas putting it higher on the screen (like at a set position of "4 text lines from the top") has no negative impact. 

There actually is a reason, it's in the Quake manual:

Certain messages appear inconveniently in the middle of your view. These are always important, and you do not want to ignore them! 

And ironically, the manual also states that messages that appear on the top of the screen are non-critical, ignore them if you please. That includes chat. 

Whaaaaat?

*goes and finds Quake manual to check*

Well, I'll be damned... it does say those things.

Funny that id intentionally made centerprints "inconveniently" located to make sure the noobs read them, heh. But I think at this point they are no longer "always important," sooo.... they don't really need to be inconveniently in the middle of your view anymore :D 

I'm not certain that I agree with this way of thinking about it.

What you're basically doing is taking a default feature of Quake, using it for a purpose for which it's not intended, then asking for it's default behaviour to be changed in a way that would suit that unintended purpose but at the expense of it's actual intended purpose.

That's the kind of thinking that led to the horrific collections of hacks that polluted Quake engines and mods years ago, and which culminated in Nehahra. It would be a lot more productive to open a dialog about creating a new message type that would suit your requirement. It's 2016, we understand things better now, and we don't have to rely on ugly hacks to get stuff done any more. 

not particularly for the reasons he mentioned, though they're perfectly valid, but because there are still Quake n00bs who might still need centerprints to pop up in their faces. Just a couple days ago there was this guy at QuakeOne asking how to open the megahealth door in the water section of E1M1... 

Even for non-noobs, don't underestimate the extent to which one's muscle memory can be trained.

I speak from bitter experience here: For every 1 person who thinks it's good there will be 10 who want it back the way it was. 

there will be 10 who want it back the way it was.
Good point. I know very well the flak Darkplaces or HD textures can get around here... because "it's not Quake, hurr". 

I think you should learn to properly parse people's arguments against the things you like, instead of simply disregarding them as "something stupid, hurr".