well finally following this report here as I worked again on some client code I finally made it to that long awaited UnFreeZe client version 1.1 for real this time so now I need your help to test the thing out. note this is still a version in development however I think that it should work so far, I've been testing it out on three different systems so far (the actual up-to December 2018 linux dev box, a mid range 2017 office/entry-gaming Windows 10 1807 up-to-date 64 bit laptop and a legacy 2007 mid range office Windows Vista SP1 64 bit up-to April 2017 laptop which should be about the very lowest you can find now-a-days even surprisingly with positive results, around 100 fps and decent connectivity) without issues so I think that it should make it at least to start with. you have all the files here so please go check that out and grab what you need (typically a updated ioq3v6 binary for your system and the new pk3, unfreeze1-client.pk3) and test it out a bit. I will package it once complete as usual so far I prefer to leave it like this to avoid yet even more confusion. so far it's still missing some parts however the core (which at the end is the most important part) is actually complete so it's a good point to test the thing out before "it's too late" (and ti gets too ugly, the work I mean). I'll go posting the updates on this as usual. to install it I believe that you're familiar by now with the procedure, just download and replace, however this time there's one special particular note, various defaults have changed so please reset your cfg (you can either move it away/rename it or simply execute a restore defaults at the in-game options menu and that should also do the job) and also for this finally new unfreeze-client release I'm in the process of sorting out the pk3 file (which is largely what's missing, beside your testing of the core) so the old files (unfreeze0-client.pk3 and unfreeze0-dev-client.pk3) should be removed to properly install this new version.
as for the changes, lot of stuff have been changed so honestly I prefer you to simply test it out and let me know if you have some questions or encounter problems, overall I think it should work pretty much "out-of-the-box" without much issues. as usual I'll go posting more details and will look forward document this the best I can when I finish with the usual (and "final" this time) package but probably the most notable things should be about this:
- several Linux fixes (broken keyboard, added openal sound support, turned off v-sync on the code among others probably) following this
- patched mouse to support up-to a two directions mouse wheel (vertical/horizontal scroll) and eight buttons now (although the horizontal scroll does not always work on any system/device as it's not really a "standard")
- patched r_displayrefresh following this, now setting your monitor frequency in-game should work (requires vid_restart after obviously)
- build with a smp (multi-thread, 2 threads this time) render that actually work this time and it actually provides better performance
- re-worked/tested the user interface a bit so it should be fully functional (and therefor disabled what it wasn't). in addition added virtually any resolution to chose at the graphics settings
- added and defaulted to a new "high definition" (regular 720p not every laptop is FullHD capable or provide substantial performance at 1080p) graphic profile (then simply go to the graphics menu and change the res to yours there and you're done)
- unlocked to start with all the single player mode and the cinnematics so now you can train from the menu your favorites maps on any order you want/skip those you don't like and so
- updated various parts of the code so now they should be more robust and perform some better
- changed various defaults so now it just comes with the "standard" settings pre-configured/pre-built (plus execing a restore defaults on the in-game options menu should therefore restore this well-known proven "standard" settings)
NOTE: remember that as usual with these releases they will trigger a security notice on your system before running them, needless to say that they are safe to run. in addition as they are testing versions only intended for the short term they aren't intended to be added to the server clean list by now which means that when you join you'll eventually receive a proper (in this time, they aren't tested yet) warning about that.