lesnosap.blogg.se

Hope that helps, even if it's not all good news. ), that could remove the need to install the newer mf and RTWorkQ.dll. If wine also implements a few extra media framework features (e.g. To avoid the nopping, wine would need to implement the Win32 Text Services Framework more completely - I haven't looked into exactly what is missing in detail, but it's almost certainly there.

(This actually is likely why AoE2DE still has the "stuck scrolling" bug, but AoE1DE doesn't - AoE2DE doesn't have the newer keyboard code which fixed that issue, but requires this nopping to work under wine.) The games are different enough that the problems don't really overlap: AoE2DE's issues are largely with the Speech Synthesis feature (which doesn't exist in AoE1DE), whereas the issues in this game are mostly to do with text input APIs, and a multithreaded graphics context feature, neither of which are used in AoE2DE.No, you do also need to get a new enough mf and RTWorkQ.dll as that post (and the one beneath it) mention.With those changes, and the other MFPlay/RTWorkQ changes mentioned above, the game does start, and can get in-game (though from the 5 minutes testing I've done, it does seem to crash a bit). In the 28529 update, this involves NOPping out (replacing with 0x90) 7 bytes at 0x13672e and 0x1f4675. Unfortunately, using winetricks' msctf.dll installation isn't enough to stop it crashing.įortunately, the game does start correctly if the code that calls into InputSystem_w32.dll's TextServicesFrameworkManager_get() function is patched out (in particular, the calls to the object returned by that function need to be patched out, rather than the calls themselves). Okay, so the InputSystem_w32.dll problem seems to be due to the game needing the Win32 Text Services Framework.