MTW long loading times are gone...!

**I of the Storm** · 07-09-2013, 07:17

Everybody who has issues with long loading times in MTW (>30s) might want to try this:

http://www.twcenter.net/forums/showt...1#post10100148

It basically forces your system to boot with only 2 GB RAM, no matter how much you have installed, and that seems to do the trick.

I tried it yesterday and MTW is loading and running smoothly, I can even change resolutions at will and fight battles myself without trouble.

Basically, it's like it was in the old days... and now I'm a happy little warmonger.

Spread the word!

edit: seems to settle issues with ol' RTW as well - obviously, you CAN have too much RAM...

**drone** · 07-10-2013, 03:09

This is the old resolutions fix, correct? I've never had the loading issue, but I'm wondering if this works, would the ddraw wrapper work as well?

**I of the Storm** · 07-10-2013, 08:36

Apparently, yes. I never read about it, because resolution issues weren't my main problem. Loading times of 2 minutes were...

Feel free to close or merge thread.

**drone** · 07-10-2013, 12:41

Originally Posted by I of the Storm

Feel free to close or merge thread.

Sorry, not what I meant. Sepheus' ddraw wrapper was meant to be a solution for the limited resolutions offered by the game when it got back an "unreasonable" value from high RAM systems. I was just curious whether it would work for long load times as well. There had been a lot of speculation back in the day about the cause of the load times, most of the educated guesses revolved around memory and AGP. If the ddraw wrapper solves the load issues, it's a lot easier than the msconfig change, and doesn't require going back and forth just to play MTW.

Either way, glad you can play again without the mandatory intermissions.

**I of the Storm** · 07-10-2013, 15:19

I see. I'll try that tonight. To be sure, some other folks should try that as well.

**I of the Storm** · 07-11-2013, 11:58

I tried the resolution fix and put the ddraw.dll in my main MTW folder, as instructed. Now it doesn't work anymore, so I guess I'm stuck with the msconfig+reboot method.
Could be worse though...

Edit: Correction - it does work, but not on resolutions higher than 1280. Fine with me.