![]() there is a tick box on the game launcher. ![]() So Felix says, if you want to fix your version of Total Warhammer 2 frame rate issue then try disabling the Direct X 12 version of the game and run it in Direct x 11. After much exploration and a few months of not playing TW 2, it turned out you could side step this Curse of the Vampire Coast FPS slow down and crash bug by loading the game in DX11, instead of the normally more favourable DX12 version of the game. But following the Curse DLC patch, Total Warhammer ran at around 10-20FPS on the normally less intense campaign screen, and would crash to desktop after the first full turn.ĭespite updating the Nvidia GTX 1070 graphics card drivers, reinstalling the whole TW Warhammer 2 game, removing all game mods and DLC, the game continued to crash and endure frame rate slow-down. ![]() That way, when people played TW Warhammer 2 they would have the latest build of the game and would see the new faction and units in the game but without being able to control them, unless they bought the new DLC.įelix was using the relatively powerful GTX 1070 and getting solid FPS in TW Warhammer 2, normally around 45-55FPS at 1440p. Anyone who had TW 2 on their PC was then given an update to their copy of the core game to include the DLC data, regardless of whether they own the DLC. In November 2018, the TW Warhammer 2 DLC, Curse of the Vampire Coast was released. We have seen some situations where these updates to the universal game engine have negatively impacted people's game retrospectively. They continually update their modular Game Engine 3 between games and will likely continue to use this same game engine for many more Total War games.ĬA have already modified Game Engine 3 to accommodate tech improvements, like switching it to DX12 compatibility and upgrading it from 32-bit to 64-bit architecture. ![]() When will Creative Assembly change its Total War game engine, how long will Total War use the current game engine?Ĭreative Assembly developers currently use Total War Game Engine 3 64-bit for Total War 3 Kingdoms, which is the same engine as the one used in Total War Warhammer 2. Although Total War has long been able to deliver large numbers of army units and it's definitely about time we got to see more battle units on-screen. This 64bit improvement is also utilised to significantly help with managing the huge number of army units we see on the battle screens at any one time. Especially when the TW Warhammer 2 Mortal Empires came along, because that pushed the faction number up to 120, all of which have to have their AI actions processed at every turn end. This move to the 64-bit Game Engine 3 improved the end of turn speed, which is still pretty slow at the best of times, due to the number of factions all having to be processed. At this point, Total Warhammer 2016's frame rates became much more bottlenecked by GPU performance, as we discovered in our Total War: Warhammer frame rate benchmark comparison. The 64-bit version of the graphics engine was released for the TW: Warhammer games. As usual, we expect this engine to be improved in TW 3 Kingdoms by CA, as it has been for each game it has been used prior to the new TW3K. This engine also makes use of Creative Assembly's graphics module, Warscape. ![]() Although back then the TW Game Engine 3 was a 32-bit version, it didnt get updated until Total War Warhammer’s release in 2016. This has been used by Total War games since Total War Empire, which released in August 2007. It is understood that the upcoming Total War Three Kingdoms will be using the latest version of the Total War Game Engine 3. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |