Skip to content

MVDSV 1.10

Latest
Compare
Choose a tag to compare
@tcsabina tcsabina released this 16 Feb 16:31
· 2 commits to master since this release
dff9fb4

MVDSV 1.10 Release Notes

Changes

  • BUILD: when building windows binaries do not look for libcurl (ciscon)
  • CI: Update build to work with newer docker (dsvensson)
  • PROTOCOL: PEXT_TRANS and PEXT_COLOURMOD
  • PROTOCOL: MODELDBL2 was incorrectly never writing modelindex as 16 bit.
  • CVAR: pext_ezquake_verfortrans defaults to 7814. Clients named ezQuake with an older revision will be downgraded to opaque entities as it announced support with a broken implementation.
  • MVD/QTV: Align MVD stream to gameplay protocol (spawnstatic2, entitydbl, entitydbl2, modeldbl, trans, colourmod etc).

Improvements

  • Added three new serverinfo cvars: hostport, countrycode, city (osm)
  • Add sv_idlesleep (osm)

Documentation

Bugfixes

  • use size_t for holding the size of a directory, otherwise we overflow on larger directories and never clean things up. also, continue iterating through files once we've hit the limit, we will stop appending new values to the files array but continue calculating directory size.
    replace rng seed generation for mods, old method would overflow but not wrap so we were stuck with the same seed after a given amount of time

Upgrading

Requires new QTV or QTV-Go due to the MVD stream gameplay protocol alignments. As long as no colormod entities are used, demos and QTV should still be possible to consume in outdated ezQuake clients. Enabling colormod entities will disconnect outdated ezQuake QTV clients with "msg_badread in packetentities" or similar. ezQuake from 2013 and newer should be able to read alpha attribute correctly, even if it's rendered opaque. Even without alpha and colourmod MVD/QTV was broken if a map had too many models or entities, even if fully connected clients would deal with that correctly.

Fully connected outdated clients will be dynamically downgraded to not include colormod or alpha entity properties. For alpha this will yield a warning about client potentially being at a disadvantage as maps may assume the client being able to see through some surface that is opaque for them. This downgrading only applies to clients called ezQuake with a revision older than 7814 as it announced PEXT_TRANS support since 2013 while only partially implementing it. Official builds always have a correct revision set, scuffed ones may have revision as 1, so make sure you're not using a shallow clone when building on your own.