Is anyone else or everyone else experiencing extremely slow resolution of naval battles, especially when more than 4 vessels are involved? I can't imagine why this should be.
Is anyone else or everyone else experiencing extremely slow resolution of naval battles, especially when more than 4 vessels are involved? I can't imagine why this should be.
MOS v1.6.2+ Bug fixer 30 Dec 2013
I have tried it on the lowest settings and the resolution does not speed up, even with just 2 vessels in combat.
by my is it that if i do next turn it takes 1 to 2 minuts to my turn again and if i want to play a battle it need s to load also verry long. sorry for my english
Turn times are due to the large number of factions combined with the large map. There's not much you can do about this except buy a more powerful rig, or grab a cuppa coffee or whatever
Battle load times shouldn't be any longer than normal med2 loading times
Game loading and battle loading are fast. I have a very fast computer and video card. Land battles are fast. I think that I need to reload the game. When it gets to turn 150 (I always have had over 50 settlements) or so, if I access the city/agent/generals screen the game exits from the game instantly to the desktop.
I just tried some naval battles at the start of a campaign on my old computer which runs on XP rather than Windows 7. The naval battles are very slow still but not nearly as slow as on the Windows 7 machine.
Last edited by Stylix; January 19, 2011 at 07:36 PM.
MOS v1.6.2+ Bug fixer 30 Dec 2013
I think the same problem occurs in thera or at least the veirson i played.
"some people say the iraq war is unnessasary, however i disagree its good practise in case one comes along that we need to fight, just in case the germans have another go"-AL MURRAY
"us british our world war champions of the world"-AL MURRAY
I did as you suggested Stylix, but there is apparently no change. Three vessels attacking 1 still took 10 seconds to resolve; and 2 vessels attacking a large stack took 15 or more seconds to resolve and about 10 for the 2 separate attacking ships to retreat. These were from existing games. I haven't tried it in a new game yet; would that matter?
I started a new game and it took 10 seconds for the 3 English ships to resolve an attack against a HRE ship. Similar but faster - down to about 8 sec. - when attacking with reduced numbers against the Danes. The retreats were still taking 5 seconds or more.
Last edited by Old Geezer; January 23, 2011 at 08:42 PM.
Thanks I'll give this a try. It would be an easy solution.
I finally fixed my problem by uninstalling KGCM and downloading a new copy of 3.0 from FileFront and 4.2 Patch. Then I emptied the virtual store junk. I also changed the security settings for Medieval to allow any and all changes. So now the naval battles are normally fast. Hopefully this also will rid me of the game lock ups that I keep getting when I would get over 100 settlements and 100 turns into the game. I think that I had a corrupted installation before that caused these problems.
I am glad to hear that you fixed the problem.I did not experience this because as soon as I installed Vista and then again when I upgraded to Win 7, I had disabled the UAC for the M2TW folder before installing the mod. I have recently added a line to the top of the instructions post suggesting that Vista/Win 7 users disable UAC before installing the mod.
![]()
MOS v1.6.2+ Bug fixer 30 Dec 2013
Good Advice! Everyone should remember to turn the security setting back up after installing/modding. I apparently failed to do so and got a virus notification from AVG that one of my Med 2 files was quarantined and I could no longer load the game and had to reinstall. It would be nice and unbelievably professional if Microsoft could have a little annoying button appear in their annoying task bar to warn one that the UAC is off, but that would not be in their tradition. (I am not a grumpy old man - I get testosterone injections.)
It might be interesting to note that one version of AVG reported that the Kingdoms.exe file contained a virus. It turned out to be a false positive, but caused numerous users major headaches. It was quickly patched and has not occured again. Search the hot seat forum if you want to learn more about it. This is a not uncommon occurance with older applications and is not unique to AVG.
MOS v1.6.2+ Bug fixer 30 Dec 2013