1. #141
    Feel all of the above by the author, plus regular crashes and hangs, including "video driver stopped responding and has been restored" after the appearance of artifacts and a 5-minute freezes.

    One time, some unknown miracle, she worked with a stable 60fps as much as 4 hours straight.

    The author was not right when he said that: "Game feels like a beta"
    Game feels like a PRE-ALPHA

    NVIDIA GeForce GTX 780 Ti (3 ГБ)
    QuadCore Intel Core i7-3770K, 3900 MHz (39 x 100)
    16329 МБ (DDR3-1333 DDR3 SDRAM)
    Microsoft Windows 10 Professional
    Share this post

  2. #142
    So it's 2016. I'm having the exact same problems as many have already listed on this thread-> HORRIBLE framerate after act one around Seahaven and beyond. So horrible that it is truly unplayable. Is there a fix to this that I'm missing, or did Ubisoft really just refuse to fix it?
    Share this post

  3. #143
    First of all, sorry for necroing this thread years after, but since we don't (and we won't) have any official response or fix from Ubisoft, here is my explanation and recommendation.

    The game uses Unity (probably some build that is pretty old by today's standards) and Unity has very poor performance unless you optimize it very well (for example, its renderer uses only one thread which is probably one of the things that is going on in case of MMXL). So combine that with time constraints, rushed release, and team with no previous experience with this type of game, and you have a recipe for disaster right there. Limbic was probably very well aware of all this because they moved to Unreal Engine with Heroes VII... and H7 runs like a charm on modern systems. MMXL does not.

    I am re-playing the game right now, gameplay-wise it's excellent, but you just have to accept its poor performance. The performance issue has been with us ever since 2014 and Ubi dumped support for the game long time ago, since it doesn't milk them money, so I'm afraid we're out of luck unless a miracle happens. Believe me, I tried it all...

    MMXL uses about 15% of my GTX1080 in forests around Seahaven, running well below 30 fps. CPU usage sits at 100% load on two cores all the time (i7-8700K), so the engine implementation is brutally CPU bottlenecked. It appears that it uses one thread for rendering and the second thread for everything else. Also, the big sutters many experienced are due to the game loading assets. That's also why you see some things like trees and rocks suddenly pop in to existence as you stutter around - the big stutters and fps drops are caused by the game grabbing data from your drive, so SSD helps a bit (at least the stutter is shorter on an SSD). It also never goes above 2 GB RAM usage and always stutters at exactly same tiles. It's just a terrible implementation, really - single-threaded game with pre-defined loading areas instead of implementing asset streaming in the background or just dumping all the data into RAM, provided your PC can handle it.

    There is no way to run this game faster given that we don't have access to the source code. At least until single-thread CPU performance drastically increases - by about a factor of 2 or 3 - we are out of luck.
     1 people found this helpful
    Share this post

  4. #144
    jsebela's Avatar Member
    Join Date
    Sep 2011
    Zlín, Czech republic
    Back then, the devs said that modding should be possible, however you need own full version of Unity3D. Modding depended on some function only full version supported. Things like game content itself and various localization, can be easily modified since they are in form of *.XML files. Repairing quests and bugs is very possible, as you can find out from my own mod, on this forums.
    By the files header, the Unity engine version used is 4.2.2. The game also uses bink video 2.2.3.
    Share this post