MedievalTW crashes

[Kaweh]

Hi,
today I bought MedievalTW and installed it on my PC. The campain works, the battles work too, but after the battle, when the game is returning to the strategy map, it crashes to desktop . But why? Is it because of WinXP? Or because of DirectX 9.0c? Because of the graphics card?

I've got a pc with an AMD Athlon 2800+ CPU, a nVdia GeForce FX5200, 512 MB RAM, DirectX 9.0c. I use PowerStrip to overclock my graphics card.
And I've got the 1.1 version of the game.
I can't see were the problem could be.

K.K

[Justinian]

You need to roll back your graphics drivers to some time in 2003. I had the same problem.

[Kaweh]

Thanks Justinian!
Were do I find this old drivers? I mean, on the nVidia site there should only be the newest ones, right?
If you have a nVdia card, could you tell me what driver you use?
Thanks,

K.K

edit: sorry, emperor, was writing this while you were answering, so I couldn't read it. I'm going to download this drivers, thanks...

K.K

[Justinian]

No, the nVidia site has all the drivers.

http://www.nvidia.com/object/winxp_2k_77.77.html

That's the download for 77.77 which ought to work with MTW.

[Kaweh]

Thanks to you all, I downloaded the 77.77 driver from the nVdia site!

K.K

[Justinian]

Have fun playing MTW!

Damn, now I'm all nostalgic.

[emperor1907]

That's the game bug. This problem is on all machines. Download 77.77 or 78.01 drivers for your nvidia card. Problem will be solved...

[jegui]

btw nvidia 77.77 still crashes to desktop... I had to roll it back to 68.00 version to get it to work with FX 5200

[Kaweh]

btw nvidia 77.77 still crashes to desktop... I had to roll it back to 68.00 version to get it to work with FX 5200

Yes, your right. I rolled back to some version like 65 but it still crashes to desktop . Maybe that's because I've DirectX 9.0c? What DirectX version do you have? I've got a FX5200 graphics card too. And it surely works with nVidia ForceWare 68.00?

edit: Can't find a nVidia ForceWare 68.00 driver, only a 66.93 driver. Will this work?

K.K

[Justinian]

I think I got 66.93, come to think of it.

Really it's a process of trial and error. ONE of those drivers will work. :wink:

[Kaweh]

Thanks, I think I'll have to play around with these damn drivers...

K.K

[Justinian]

OK, I just checked my files. The nVidia drivers I got were 61.76 and MTW stopped crashing after that.

[jegui]

yes u r right... the version that works on mine is actually 61.77... I got directx 9.0c

[Neb]

There is a much easier fix for this issue. Some people can't roll back their drivers because they have newer cards. Also, newer games will perform better with newer drivers. So for people like me with newer cards, and/or newer games, old drivers are not an option.

Setting my AA from application controlled to 2x fixed all of my CTD's.

At first I thought that medieval just could not tell the newer drivers what level of AA it wanted, throwing some kind of error; but then setting AA to 0x would also fix the problem. But it doesn't. So, I'm not sure why forcing AA to 2x fixes the issue. But it does.

This was posted somewhere else.. here or the org maybe. I can't remember.. but I didn't come up with this solution.

-Neb

[jegui]

There is a much easier fix for this issue. Some people can't roll back their drivers because they have newer cards. Also, newer games will perform better with newer drivers. So for people like me with newer cards, and/or newer games, old drivers are not an option.

Setting my AA from application controlled to 2x fixed all of my CTD's.

At first I thought that medieval just could not tell the newer drivers what level of AA it wanted, throwing some kind of error; but then setting AA to 0x would also fix the problem. But it doesn't. So, I'm not sure why forcing AA to 2x fixes the issue. But it does.

This was posted somewhere else.. here or the org maybe. I can't remember.. but I didn't come up with this solution.

-Neb

Confirmed this... I reinstalled latest nvidia drivers I have (81.98) and set AA to 2x... it WORKS with no CTD

[Justinian]

There is a much easier fix for this issue. Some people can't roll back their drivers because they have newer cards. Also, newer games will perform better with newer drivers. So for people like me with newer cards, and/or newer games, old drivers are not an option.

Setting my AA from application controlled to 2x fixed all of my CTD's.

At first I thought that medieval just could not tell the newer drivers what level of AA it wanted, throwing some kind of error; but then setting AA to 0x would also fix the problem. But it doesn't. So, I'm not sure why forcing AA to 2x fixes the issue. But it does.

This was posted somewhere else.. here or the org maybe. I can't remember.. but I didn't come up with this solution.

Sweet! Finally I can play BF2 and MTW without shuffling my drivers back and forth. Thank you!

[Suleiman I]

There is a much easier fix for this issue. Some people can't roll back their drivers because they have newer cards. Also, newer games will perform better with newer drivers. So for people like me with newer cards, and/or newer games, old drivers are not an option.

Setting my AA from application controlled to 2x fixed all of my CTD's.

At first I thought that medieval just could not tell the newer drivers what level of AA it wanted, throwing some kind of error; but then setting AA to 0x would also fix the problem. But it doesn't. So, I'm not sure why forcing AA to 2x fixes the issue. But it does.

This was posted somewhere else.. here or the org maybe. I can't remember.. but I didn't come up with this solution.

-Neb

Could you explain that in lay-man's terms please? I'm PC-whipped and have no idea what you were saying. I'm having the same problem with MTW, especially after a battle it CTDs. If you could break down what you said into idiot-friendly language that would be much appreciated.

[Neb]

No problem. That was my problem too; I play BF2 and CS too often to be bothered with constantly switching drivers but wanted to play some old MTW goodness. I found this AA answer on some forum (could have been the org), and it worked. All the hard work payed off when I had a challenging campaign full of unexpected things (swiss taking out england? who could have guessed?!).

-Neb

[Neb]

Okay. AA is Anti-Aliasing.. it's an extra graphics feature that blends pixels with the ones around them to make everything flow better and reduce those jagged edges on objects. It does slow down performance, so make sure you turn it back off (or to application controlled) before you run a modern game.

To turn it on, right click your desktop and select properties. The far right tab is settings, and in the bottom right there is an advanced button that you want to click. On the new window that popped up, there is a tab that could be labelled a lot of things. Mine is "Geforce 6800 GT", but yours will be called whatever your card is (unless ATI has a different naming scheme and you have an ATI card).

If you're using an Nvidia card, there will now be a list of things on the left side of that window. Select "Performance & Quality Settings". Now in the main window, there is a list of settings. Select "Antialiasing settings" and move the slider over to 2x. It sounds hard, but it's not. Just remember to change it back if you plan to play a modern game.

If you're using an ATI card, The last few steps will be slightly different.. but since the only computer I have with an ATI card is my laptop.. and it isn't with me at the moment.. I can't offer an specifics there. Maybe someone else can?

-Neb

[Mark Lambert]

OK, I've got MTW VI with 3 mods (NTW, PMTW and MTW XL) they all CTD after 1 to 10 minutes, usually during a campaign move.

I just bought the Compaq (HP) cheap model with Vista- I don't think I have a graphics card, I have "Intel Graphics media Accelerator Driver" ( after rt-clicking on dektop to try the anti-aliasing technic- a search for anti-a on vista showed no results)

I've tried adjusting the graphics options, what else to do?

Thanks much

Lord Lambere