[KroniK]

Magister, on 28 October 2016 - 03:30 AM, said:

What does it mean that the two bugs in 4.3 that the UZL website makes reference to are listed with a status of Closed on their respective github entries? How can they be closed unless a release has been made that resolves them?

The bugs on github have probably been fixed on the internal un-released master branch of the codebase and are therefore marked as being done, or at least to a point where they are testing it internally. They probably closed it so that people know that those specific bugs have been dealt with and please don't open another bug report with the same issue.

[fr.Biddle]

When we close an issue on GitHub it should mean we have it identified and fixed. The fix might not be published yet, but we do have it.

The issue tracker reflects our "in development" status (i.e. for the upcoming update), and not the current state of the game. You can check an issue's "milestone" to know with which update will it get pushed, and if it has therefore already been pushed.

The lag issue seems to be directly linked to sv_fps unlock and we have locked back the CVAR in 4.3.2. Once the update will be published, that issue should be fixed.


Regarding the fps drops, we are still investigating.

[ryan]

Biddle, on 28 October 2016 - 01:03 PM, said:

When we close an issue on GitHub it should mean we have it identified and fixed. The fix might not be published yet, but we do have it.

The issue tracker reflects our "in development" status (i.e. for the upcoming update), and not the current state of the game. You can check an issue's "milestone" to know with which update will it get pushed, and if it has therefore already been pushed.

The lag issue seems to be directly linked to sv_fps unlock and we have locked back the CVAR in 4.3.2. Once the update will be published, that issue should be fixed.


Regarding the fps drops, we are still investigating.

Hiya Biddle! Any update in this regard? I am hoping for the 4.3.2 release really soon, so updated servers get rolled out, and player frustration lowers, keeping them playing longer. :)

[FS Barbatos]

I'm very busy right now but aiming for a release during the XMas holidays - hopefully. We'll announce the exact release date a few days before the release.

[ryan]

Barbatos, on 12 December 2016 - 08:38 AM, said:

I'm very busy right now but aiming for a release during the XMas holidays - hopefully. We'll announce the exact release date a few days before the release.

Right on Barbatos! Keep on truckin' :D

[gurubert]

Hi,
whenever I try to connect to a server with my 4.3.1 client the game tells me I have an invalid game folder (maybe because of a newer client version).

Will this only be fixed after the server admins have upgraded their versions?

[FS Barbatos]

gurubert, on 25 December 2016 - 03:24 PM, said:

Hi,
whenever I try to connect to a server with my 4.3.1 client the game tells me I have an invalid game folder (maybe because of a newer client version).

Will this only be fixed after the server admins have upgraded their versions?

No, this looks like an issue on your end. Please try running the Updater again!

[[COD]Nstar]

Any news on 4.3.2?
Nations cup is coming up, and matches that don't feature 2 same region teams will be laughable at this point.
I can't even kill AFKs on servers with >200 ping.
Or, to that end, is the resolution shared with UZ admins and included in required server configs?

[fr.Zmb]

xoai, on 04 January 2017 - 10:09 PM, said:

I can't even kill AFKs on servers with >200 ping.

Did you try to aim ?

[Mod Iye]

xoai, on 04 January 2017 - 10:09 PM, said:

Or, to that end, is the resolution shared with UZ admins and included in required server configs?

The "solution" is to revert some changes, such as the unlock of (sv_) snaps back to 4.2, but im pretty sure UZ admins are aware that setting sv_snaps fixes those issues related to 4.3.