Oh "on The Client"
#2711 posted by Kinn on 2017/04/20 20:16:09
ignore me
@Kinn
#2712 posted by mh on 2017/04/20 21:33:37
ignore me
Have more beer. :)
Even if it was an issue you could bound it to signed 16-bit range instead.
@ericw
That's great news!
Concerning the stretch or letterbox question, I think there is a way to get around the issue altogether.
Create a console variable like "vid_scaler" which defaults to 1 and determines by which number your resolution should be divided before scaling. For example, you're running quakespasm in 1920x1080 and set vid_scaler to 4, which results in a new resolution of 480x270. The game renders this resolution and scales it 4 times without interpolation, fitting the screen exactly. Alternatively, you could have also set it to 3 or 2 which would give you 3x-scaled 640x360 or 2x-scaled 960x540.
That is the way mark v does it, and it looks really good. Even if the scaled resolution will always be somewhat higher than 320x240 depending on your native resolution, having no letterboxing more than makes up for it. And you could always create a custom resolution like 1280x960 to get 4x 320x240.
That's how I run mark v on my 1366x768 laptop. Since 1366 cant be properly divided by 3, I created 1344x768 for myself which has small black bars but can be 3x-scaled properly from 448x256.
Most people won't have that problem anyways, and doing it this way would also allow you to customize the chunkiness of the pixels to your personal preference. FifthElephant could play on 640x360, given that he has a 1080p display.
#2714 posted by metlslime on 2017/04/21 17:33:53
Clamping health on the server message sounds like a bad idea because it assumes the client will never display values above 999 . Network code should clamp to the protocol maximum, display code should clamp to the display maximum.
#2715 posted by metlslime on 2017/04/21 17:35:58
Also I agree that scaling only seems to make sense at integer scales so a single cave defaulting to 1 would be simplest for the user. Unless there's a desire to scale different let on each axis.
#2716 posted by ericw on 2017/04/21 19:30:15
Yeah, a single cvar like "vid_scaled" "vid_stretch_by_2" sounds better than what I was proposing
PS4 Controller
Hey guys
Apologies if I've missed something - but is it possible to use a PS4 Controller with Quakespasm? I'm using DS4Windows as a wrapper to the xinput. Any known issues?
Using latest version of Quakespasm with the controller .txt addon
Thanks!
It Should Work
#2718 posted by ericw on 2017/04/25 04:43:26
Use quakespasm-sdl2.exe which has xinput support (via SDL2). I have only tested a wired X360 controller and steam controller (in Xinput mode) but both of those worked.
There are some notes on config settings here:
http://quakespasm.sourceforge.net/Quakespasm.html#ss3.2
Xinput SDL
Just wanted to say thankyou ericw - I wasn't using the SDL exe. Had a great day playing Quake on the couch!
All my social events will be quake once 4-player splitscreen with pads is on one of the engines. Currently being dominated by Turok 2's splitscreen right now :P
Split Screen Are For Console Pleb's
#2721 posted by anonymous user on 2017/04/29 22:19:08
Anon Dipshit
Some of us have friends in real life and like to play games with said real life friends...
Post with your Nick next time asshat.
About The Scaling Feature
I don't mean to be pushy, but is this still happening? It's been radio silence for quite some time now.
Yep
#2724 posted by ericw on 2017/05/17 20:15:33
Sorry for the silence, I coded most of it and got sidetracked. Here is a built to test out:
windows build
source
The cvar I went with is "vid_scale", default 1, set it to 2/3/4 to get 2x/3x/4x scaling.
You have to do a "vid_restart" in the console after changing the scale (this could be improved later to have it live update).
I didn't push this to the main QS codebase yet, wanted to get some feedback / testing first but it seems good to me so far.
Ericw
I like this feature... I also turned off basically everything, lerping, shadows etc to get it really old school
Ericw
#2726 posted by DaZ on 2017/05/17 23:52:50
Had a quick look, works well! Screenshots are fubar'd though, looks like it's only screencapping 1/4 of the screen.
Thanks
#2727 posted by ericw on 2017/05/18 04:36:10
build with fixed screenshots
Glad you like it Fifth - yeah, it seems good on id1 maps with square particles + lerping off.
now... about that 4-player splitscreen. ;)
EricW
Does this build have spikes weather code included?
I'm really curious as to what "vanilla" quake would have looked like with weather effects.
Shamblernaut
#2730 posted by ericw on 2017/05/18 08:52:13
Not in this build, the scaling should be straightforward to add to QSS though.
Fifth I know, hopefully at some point (or in MarkV :)
This Is Awesome
#2731 posted by boristhesp1der on 2017/05/18 10:11:59
Seriously thank you so much!
Do you have a paypal link? I'd like to keep my word :)
@Fifth
#2732 posted by Spike on 2017/05/18 12:36:39
http://fte.triptohell.info/quake?+set%20cl_splitscreen%203%20+set%20coop%201 :)
@Shamblernaut, at 320*200 rain-like effects will probably just look like a few sparkles occasionally.
slow moving comparatively large snow-like particles are probably going to be okay though. note that hexen2 had snow effects too.
Hmmm
#2733 posted by Kinn on 2017/05/18 13:45:47
I like vid_scale....would it be a daft idea to hack in support to be able to scale the console and HUD differently to the main scene?
I like the chunky piskels but the screen-filling HUD less so....
Spike
can't get fte to work properly
@kinn
#2735 posted by ericw on 2017/05/18 20:22:00
is it still too big with the "scale" slider in the settings menu at the minimum setting?
@boris appreciate it, my email is in my profile.
|