well after such a long break is finally good to be back and get something done here. first I want to apologize for the last months of low activity (basically just active maintenance) but unfortunately as usual I got lost on just way too many details (I started to "finish" off some ioquake3 builds but I just tried to do way so many things that I ended up by doing nothing at all and same with the new mod I talked about I also started to work on it but then I got so ambitious that ended by dropping it too and after all that I just needed a break because it was clear I had lose all the focus I wasn't going anywhere on that path plus furthermore last months I also was doing paid job for a isp company) and thus I failed at deliver the stuff I had in mind, sorry about that.
so that being said, let's focus on the task at hand now. finally this month I started to resume operations here and of imminent action was to do something about the (half now) death UnFreeZe2 server and at least migrate it into another spare host I had for better consolidation of the infrastructure and coverage of the region. well, now the good news are as I was starting to work on this task I was reviewing hosting options as usual from season to season and I finally got my hands on a incredible deal that is really going to step up the game so I'm setting up now a top of the line 2017 enterprise level server in the Bavaria state from the number 1 German hosting company (which then means switching companies from the current one) to integrate all the services and a new (finally) "decent" (recognizable) domain all at a much more appealing price.
then in the next months I'll go migrating services from here to there, I'll go updating this post and letting you know as it goes, so far let's focus and start with the current task at hand and first things first I started by placing UnFreeZe2 in this case I really put UnFreeZe1 there directly so in the next few days both are going to be competing against each other and is going to be interesting to see how they do and what different clients they attract. this is still not a definitive migration, it could fail, it definitively shouldn't as the difference in infrastructure is just overpowering, but at the end of the day routes are going to be different and you never know so I would really appreciate if some of you drop by there and test it.
the new host more or less it should do same or nearly the same although is evident that every time you move something from its place, unavoidably, it's going to bring some changes too, so overall from what I've been digging up in general I expect the following scenario, clients from south-west and west Europe slightly disfavored, from north Europe virtually the same, from central Europe, the Balkans and the cis regions overall favored and finally best in class on in-land Germany (specially Bavaria). anyways in any case either favorable or dis favorable I'm just talking about differences in the order of just a few msecs more or a few msecs less almost in any case under 5 msecs variance in absolute terms, which should never be such a big deal.
also this new host from what I've been testing so far has better ipv6 connectivity than ipv4 (the ipv6 connectivity on the current one while exists like on this forum for example, falls short behind the ipv4 connectivity which is another point in favor of the new host for the future) for which the general recommendation is to connect via ipv6 to the new host, most routes I tested (the most important ones) are cleaner that way. to be able to play via ipv6 you need a updated ioquake3 build you can grab and ask for help (in case you need it) at this other thread here and you're good to go.
additionally to get started without losing too much time some 64 bits builds of latest (September 2018) vanilla ioquake3 code were created, mostly just as experimental, testing, extra builds but never intended to be used as regular and recommended options as they have been well proven to be very broken overall (driver, input/output problems and probably even more) but since they were created and perhaps some one is just curios about them, it was decided to leave them here just as reference/sample nothing more. then if that's the case, you can proceed from one of the links down bellow to get the one appropriated for you:
- ftp: ftp://ftp.fpsclasico.de/ioquake3/
- Windows 64 bit: amd - intel common: SDL264.dll
- Linux 64 bit: amd - intel
ok now to the point note that to connect to a host via ipv6 as explained at the ioQ3v6 thread all you have to do is just open the in-game ioQ3v6 browser and look for servers and then connect as usual, nothing more. if you see on the list servers with a protocol ??? column that means that you have ipv6 if on the other hand you can only see UDP protocol marked servers then that means that unfortunately as the majority so far you only have ipv4.
additionally now most network commands support the '-4' and '-6' arguments to differentiate between the different internet protocols versions, like for example "\connect -6 unfreeze.fpsclasico.de" to connect directly to the new host via ipv6. by the default to ensure ipv4 compatibility the dns names should resolve into ipv4 address so if you access the server directly via command and you already have ipv6 don't forget to add the '-6' argument to your command. once you got in-game you can confirm that you really connected trough ipv6 just by looking at the server info the server prints you when you connect and check for what ip it gives you that you're connecting to, if it's a "usual" ip then unfortunately you still connected trough ipv4 if it's a rare one with colons instead of dots then you got it right.
finally I drop you here the new ip's just in case some one wants to check them out/note them and with it this will be everything by now. let's see if also the next week I bring some new basic server without going all the way and slowly I go migrating (also updating to pre-2019 stuff) the rest of the services, I'll go letting you know as it goes here. see you and have fun.
- hostname: unfreeze.fpsclasico.de
- ipv4: 85.10.197.106
- ipv6: 2a01:4f8:a0:5363:85:10:197:106
- port: 27960 (default therefor optional)
like I told you a typical DTAG Berlin ping should be a little closer to 30 more or less but well given all the circumstances surrounding you (far east Berlin, low quality/availability network etc etc) a stable and clean 37/38 ms ping is, as you're noting yourself, as good as it's going to get under those circumstances. as a fancy alternative to toy with if you want to sort your ping out yet even more you can always try to cl_timenudge it out like -30. although this is totally unrecommended and it will only give you a fake (placebo) impression (never real) of a lower ping and probably it will completely fuck up your client's prediction code, many people gets used to it and it should lower your in-game lag feeling into the under 10 ms range approx.