According to some users on the KoreanRandom forums, along with mixaill from the XVM team, it appears some hidden significant changes have been made to the game engine in this update. Of note for modders, a number of new functions, classes, and variables were added, the Python version was updated from 2.7.7 to 2.7.18, dynamic linking is now used instead of static linking, and pybind11 is used inside the client. Some big things may be in store for the development of the game, especially that it is not constrained by potato hardware limits anymore (and no more 32bit version). What does this mean? Many mods will be broken with the coming of update 1.18 and will require major changes in order to work again.
10 thoughts on “WoT: Game Engine Changes in Update 1.18”
I hope theyre updating to DX 12 or VULKAN and add 4k texture packs and Ray tracing
Can you link that forum post
I hope that me and my wife will still be able to play on our RX 470 and RX 570, cuz it is currently ‘impossible’ for us to get new graphics cards during a war.
Those cards should still be fine, afaik.
A friend of mine uses a GTX 1050.
32bit client is gone and min spec is Windows 10
The 32-bit client may be gone but WG did not mention anything about 32-bit code and libraries.
Most likely there is still 32-bit code and libraries in the game which is not a good idea as WG would need to support/troubleshoot two sets of code.
Come on WG – do what Apple did and not allow 32-bit code and/or libraries to not load. Sure it will irritate some users but in the long run it is best for the game.
Wow sourcing info from random Korean forums now lmao pathetic
I’m sorry that nobody taught you how to read.
Interesting that they are still using something that was released in April 2020. Python 2 was sunset on 1 January 2020 which means NO security fixes, bug fixes, or changes.
So even with 1.18 we are potentially exposed to security issues…
Hopefully this is a intermediate step to Python 3…