proquake *optional* replacement textures support

[killingtime187]

before starting a flame war, i made sure i highlighted the keyword "optional" in the forum topic. after reading the following post -- http://quakeone.com/forums/quake-hel...ake-music.html, i wondered ... why not also "optionally" allow for replacement textures ? proquake, out of the box, will always give you the classic/original look and feel of quake without you having to configure anything. however, for those that want to alter the sound and/or gfx *without* losing the classic netquake feel, it should be possible to do so. i think the most important thing is that any optional additions do not alter the feel of the game play or it should not be added.

so, given that's almost 2013, and pretty much every one here has a machine/setup that can easily handle hd textures + sound, how about adding this option to proquake ?

[Syluxguy28O3]

yeah if you want new players you have to cater to them. few modern gamers want the classic quake look. with all of the modern texture, models, sounds, etc, a modern looking, yet faithful quake could be put together that satisfies both new school and old school players. if the classic players want classic, include a "classic mode" or something similar.

i'm not knocking one look or another, all i'm saying is if you are trying to sell quake to a modern crowd, you have to cater to their expectations, and sadly old school graphics aren't high on that list. remember, there are many fps's that bring modern, fast paced action. the same can be done for quake if touch ups are done in the right way.
examples:

Xonotic
Urban Terror

[killingtime187]

actually, if we want to make quake appealing to the current generation of fast action players, we'll need to bring the gfx and sound out of the dark ages because even their little nintendo ds probably looks better. check out this article -- Fast paced FPS genre dead? Not so fast! Confessions of a serial game designer. and this -- Fast paced FPS games [Archive] - Steam Users' Forums, both 2012 write ups, this one starts off with:

"What happened? These games actually required skill and were fun."

"Controllers can't handle twitch gaming all that well, thus those fast games were replaced by slower-paced, auto-aim friendly shooters."

i was never a controller player, so didn't know they suck compared to the mouse + kb for fast action.

anyway, i think what truly separates quake from the others like alien arena is the match-based team play vs ffa ? i don't know as i've never tried aa, but the key thing for me is the match and supporting a team to victory -- essentially the same thing that are in most fps games (slow or fast), but those of us here just prefer things a bit faster and not restarting the level after a 2 min round ... but instead keeping the game going.

[Baker]

anyway, i hope the momentum continues into 2013 and beyond.

Odds: Better than average.

[killingtime187]

interesting info baker. i can tell you that all the guys i play with (myself included) have high end pc's and all the latest games, but still come back to quake -- the standard by which all others are measured the "feel" and pace of this engine has never been replicated by any other that just makes for addictive sheer fun gameplay. (others tend to shoot for hyper-realistic gfx and movement that gets boring after a short while.)

there are essentially two types of gamers - those that like fast paced action that tests your reflexes and where practice makes perfect, and those that prefer sit and snipe action or something more docile/slow paced. for instance, i showed a friend of mine -- hardcore black ops player -- a match i was playing and his head was spinning from the pace of the game quake is for those type of players that first made it famous and there is *always* a current generation of players like this sort of gameplay.

anyway, i hope the momentum continues into 2013 and beyond.

[Baker]

in addition to "optional" textures, i think all key areas should be optional/pluggable

I think just due to the number of serious engine developers in the Quake community -- and it is hard to say an exact number, but there have been at least 11 releases this year and I mean of 11 different engines (Quakespasm, RMQ, QBism Super8, probably an Engoo one, the 6 degrees of Freedom engine as some examples, the PSP engine Dr Abuse did that for reason the thread got buried and it would seem few people saw it at the time [it happens] ) ...

I just happen to think the Quake engines in general will continue to evolve.

And I swear that 3-4 years ago, I honestly wouldn't have thought that would be the case. Especially the then extremely important Quakesrc.org site died, which was all about engine coding, I thought Quake engine coding was going to die ... especially when aguirRe (who did a once popular and important single player engine) switched from Quake 1 to interest in ... I think it was Quake 2 ...

But the Quake 1 community always seems to surprise.

That in itself is something somewhat fascinating.

[killingtime187]

in addition to "optional" textures, i think all key areas should be optional/pluggable -- for instance, i saw 5.1 sound in fteqw ... worked great with my 5.1 setup. anyway, ideally, the engines should able to give the user a feel of the original game with optional enhancements for sound, gfx, input (raw vs orig), etc.

[Baker]

still aiming for a December release of engine x?

Any engine updates are gonna be 2013 some time. But they'll be really good ones.

[Syluxguy28O3]

Well, I'm kinda sorta trying to standardize some things a little. Hit some, miss some. But looks like some of the things I was able to do in 2012 worked out well. Mark V has worked out maybe a bit better than I expected. Engine X ... more work to do (mixed). ProQuake mostly forward, but with a little tuning needed to satisfying everyone.

Its a hit and miss world. I think I leveled up a few notches, which is nice since I used to struggle so much a couple of years back.

still aiming for a December release of engine x?

[Baker]

it would take less time if you were not working on all three at the same time...
tbh, three is just greedy.

Well, I'm kinda sorta trying to standardize some things a little. Hit some, miss some. But looks like some of the things I was able to do in 2012 worked out well. Mark V has worked out maybe a bit better than I expected. Engine X ... more work to do (mixed). ProQuake mostly forward, but with a little tuning needed to satisfying everyone.

Its a hit and miss world. I think I leveled up a few notches, which is nice since I used to struggle so much a couple of years back.

[Mindf!3ldzX]

Confirmed, yes. The mouse is polled as fast as possible, and client-side view updates happen in real time, but transmission from client to server still only happens at the default 72fps (so as to not flood servers and not generate huge demo files).

Interesting fact - Quake 2 also (kind of) does this - it runs the main event procedure every pass through the game loop, even if a frame would otherwise not run, and responds to (certain) input events as they happen, but will gather them up and update state, send them to the server, etc only if a frame will run.

I requested this feature. Then later on I requested a console variable that would be able to adjust that net rate indepent of the graphics updates.

and YES! the reason I enjoy the uber high fps in netplay is due to the LG / overall aim improvement it offers.

Q1 has come a long way from its roots, even ProQuake is heavily modified compared to our original quake.exe & q95.bat etc :F

[MH]

DirectQ as far as I know untied the link between input polling and frames per second. This means DirectQ will poll your mouse the same (like as in fast, fast ...) no matter your frames per second. MH could confirm this, I'm only about 85% certain of this.]

Confirmed, yes. The mouse is polled as fast as possible, and client-side view updates happen in real time, but transmission from client to server still only happens at the default 72fps (so as to not flood servers and not generate huge demo files).

Interesting fact - Quake 2 also (kind of) does this - it runs the main event procedure every pass through the game loop, even if a frame would otherwise not run, and responds to (certain) input events as they happen, but will gather them up and update state, send them to the server, etc only if a frame will run.

[Panix]

OT but wondering something...

What's the deal with the advertisements showing up in the posts?

[Spike]

it would take less time if you were not working on all three at the same time...
tbh, three is just greedy.

[Baker]

Getting back on topic ... I think optional texture support in PQ won't be happening, given your responses. I'll keep playing with different settings and see how input is affected on various clients and possibly post my findings here.

Thanks for all the feedback.

Could end up happening eventually in the form of Engine X, ProQuake and FitzQuake Mark V becoming a single engine.

All 3 engines have vast amounts of similar features (demo rewind, loc support, etc., ping is scoreboard) and I've been trying to bring them together into a single project where only the rendering is different. Mark V was an effort to add clean implementations bug fixes and conveniences in other engines, which resulted in a lot of ProQuake features getting rewritten from the ground up (one example, the ping in scoreboard in Mark V isn't from ProQuake, more of a result of looking at what DarkPlaces and ProQuake did and writing a short and crisp implementation).

It just takes a lot of time to get there ....