Printable View
How come each level of sea trade building i build gives me an extra trade fleet then?
I've got lvl1 docks at many cities and i can see that they have more than one trade fleet, and i've seen the number increase with the building of merchantile buildings.
Also, i've never seen a city with a dockyard have less than 3 fleets going to it...
You have to look at the export fleets! The import fleets are not effected by buildings, afaik. I've examine the trade mechanics for quite a while. Trust me, or else I have an complete different game.Quote:
Originally Posted by sapi
If no one else sees a bug here, perhaps we should open up a thread concerning trade mechanics. ;)
EDIT:
Hard to believe, I'm not aware of such things happen.Quote:
Originally Posted by sapi
Hmmm - i'll take another look tomorrow but you're the one who's seen the hard data in the files so i guess you're right...
Not sure if this has been noticed yet, but if you form a spear unit into a schiltrom, and have them aligned next to the city gates (touching the gate), then a seige ram will not be able to break through as it will constantly keep engaging and disengaging.
Ah - so that's what's been happening.Quote:
Originally Posted by Divine Wind
Nice find mate.
Ive recreated it a couple of times (only in city sieges so far), and as soon as you order the schiltrom unit to go back into line formation the ram starts to engage again, whether the unit is touching the gate or not. Its just the schiltom formation that causes this.
Being the honourable player that I am, I always move the unit back to let my foes enter the city.
:bow:
^^ When that happens i generally stay in schiltrom formation, but get my worst unit to run out through the gate to open it ;P
A CTD
My general has night attack trait.
He attacks an enemy captain. Another enemy captain is nearby so he is in as reinforcement.
I rightclick to view the reinforcement's units. Close it. Tick night attack. untick night attack. And rightclick the reinforcement potrait again. Crash to desktop.
Anyone experience this ?
Merchant bug is still there with the 1.1 patch.
Had a merchant down at timbuktu trading ivory for 740 per turn after restating the game he's down to 104 :wall:
I have an update on the mouse button4 bug (which is still present in 1.1), namely pressing mouse button4 (free look mode) in a battle results in the camera continuously spinning anti-clockwise. :dizzy2:
The update is that this bug only seems to occur when running at a video resolution of 1280x1024 (strange but true). This has been confirmed by myself and independently by Pokletu Staktu in this thread:
http://p223.ezboard.com/fshoguntotal...icID=500.topic
Also, the bug is more to do with free look mode itself rather than the mouse. So the bug still occurs if you use the keyboard binding for free look (without touching the mouse).
ShellShock, that's been reported and should be in the first post.
Thanks for the confirmation though.
Martin, that's a pity, but thanks anyway.
I'll pass it along after Chrissie.
Don't know if this has been mentioned.....
There's a really annoying bug that makes "wrong" culture buildings appear on the battlemap - ie a late middle-ages Venetian style palace in the middle of Scotland at the outset of the game (more or less my first battle), Christian churches in the middle of the desert and, finally, the one that's really hacked me off....
"Discovered" the New World, sieged whatever that first city is called - Aztec buildings but one bloody great Muslim style dome in the middle. A few turns after I capture it it rebels so I siege it again - now the whole bloody thing is Muslim, minaretes, the lot and not an Aztec building to be seen. I know it's only eye-candy but it does rather ruin the effect.
Edited: Tlaxcala, that's the place.
Could someone ask CA what the deal is with pikemen? The front rank drop their pikes shortly after impact, while the rear ranks turn around and start walking backwards into the enemy.
Attacking with pikemen is impossible because the front ranks try to walk into the enemy. This is especially apparent when the AI is controlling them.
Pikemen forming spear wall in guard mode are no more resistant to enemy charges, but will not attack after the initial charge. The same problem exists for spearmen and halberds.
The anti-trait problem:
In RTW, anti-traits were on a sliding scale, so 1 point gained in one trait when the character had levels in the antitrait would cause a 1 point reduction in that trait. Further points would cause the antitrait to reduce levels until zero was reached, whereupon the character would start gaining levels in the new trait.
For example, a character has 2 points in GoodCommander (level 2 GoodCommander). He loses a battle and gets 1 point of BadCommander. As GoodCommander is the antitrait, it drops to 1 point (level 1). The character picks up another point of BadCommander. GoodCommander then drops to zero and the trait disappears from the character sheet. The character gains 1 more point of BadCommander. BadCommander now appears on his character sheet at level 1.
In order to prevent traits from sliding up and down unchecked, the system also included a nogoingbacklevel setting for each trait. In other words, once you hit the threshold for a particular trait you could never reduce your score in that trait below the threshold, no matter how many points you scored in its antitrait.
The triggers and traits in the character_traits file are configured to work under those conditions. However, it seems that the mechanics have changed for M2TW, wrecking havoc with the way traits are gained and lost.
Research for M2TW reveals that gaining points in a trait automatically resets all antitraits to zero, regardless of nogoingbacklevel.
For example, I have a Great Commander, 8 points in GoodCommander. I gain 1 point of BadCommander. I will lose all 8 points in GoodCommander immediately.
Needless to say, this causes a lot of trait seesawing and makes it virtually impossible to gain and maintain higher skill levels for characters, since even one point in an antitrait causes the character to revert instantly to zero. This is probably a pretty serious bug that is mostly beyond the abilities of modders to rectify.
Annoying CTD...
Playing as the Hungarians and the Mongols decide to perform a night attack against my fortress at Aleppo. Everything starts off normally. They have one small army with 1 ram, 1 set of ladders and 1 siege tower and a reinforcement army on the other side of the fortress with no siege weapons consisting mostly of cav.
Well basically i sally some units out to take out the guys manning the ram. A fight ensues and my guys overpower the ram team and the light lancers that try to interfere. This is when the CTD happens. Tried it a few times, sometimes i manage to torch the siege tower before it crashes, sometimes it crashes just as i'm sallying the units, I can't seem to find the exact reason.
I havent tried fighting the battle differently... but i will.. and see what happens.
i second the compaint about the pikemen. i have done thorough testing and the ai is not right on them. sometimes they point in a direction where not even one enemy soldier is and more often than not the whole formation will turn to swords a few seconds into melee.
not to mention the new discovery that you can command a heavy cavalry unit to move beyond a pike unit instead of charging it and recieving no damage from the pikes.
that one really disgusted me. one more stone on the pikemens grave.
I have a quickfix for that, check out the Swiss Cheese thread. Guaranteed suicide for heavy cavalry trying to walk through the pikemen.Quote:
Originally Posted by mad cat mech
Perhaps not so beyond modders' abilities :beam:Quote:
Originally Posted by dopp
After some discussion and whatnot, things are moving along and a workaround of the antitrait code is emerging. Don't look for a finished product yet as it's (hopefully) being tested at the moment until it gets into some sort of final form... but hopefully it won't be long now. Nothing on the nogoingback level yet, but it's on the list next and should be doable as well.
There's always hope :yes:
I consider this a bug in MTW, RTW, and now M2TW. When I am in a blockaded port, I have to fight my way out. When I am blockading a port, the computer slips through untouched. It just happened me playing Hungary against Sicily at Tunis. If he can slip out, I can slip out or it is a bug and ruins the whole gameplay in favor of the computer.
If you attack a settlement that has a reinforcing army coming, it's very possible to ram the city gates and send a unit running through the city to take the side gates that the reinforcements tend to use to get into the settlement before they get there (the reinforcing army always walk).
Once you've taken the side entrance the reinforcing army gets very confused and tends to hang around just outside the walls in a random dispursed formation and let your archers stand on the wall and blast them to bits even though the other gate has been destroyed by your ram. Routing armies will also try to retreat through the entrance you've taken and they all get stuck there till your cavalry decide to skewer them. Also they won't/can't use their artillery to destroy their own walls to get their reinforcements into the city.
andQuote:
Originally Posted by Sapi
Just to say I'm getting the same crash bug in my Turkish campaign against the Timurids too. They've besieged my citadel & have assaulted w/o any siege equipment. They're using 1 unit of Elecannon to try & create a breach. After about 5-10 mins of fruitless firing, the game crashed & that error message came up. When it happened the first time, I switched the PC off & went to bed; today I've reloaded & exactly the same thing has happened. It's really annoying - 150 odd turns in of a carefully crafted camapign, I can't seem to go any further.Quote:
Originally Posted by dokparstal
My system is low-end however (but I've completed a Venetian campaign on it already), but I'm using the settings it chose for me (low on everything).
Athlon 64 3000+, 512mb RAM, GeForce 5900XT, & enough memory
ANy thoughts?
try to increase the unit texture quility up to high or thereabout. the game will look much better and your system should be able to handle it as well.Quote:
Originally Posted by HughTower
also disable grass to increase the performace..if ya need to.
Has anyone else noticed that if you're running the game via a mod switch, any changes you make to the game options (Or at least the video options) get saved to your medieval2.preference.cfg file and NOT your mod cfg file... So the next time you run your mod it won't have the changes applied, and you have to copy the changes from one file to the other by hand?
This is kind of bad, because it means that if you wrap a cfg file in your mod distribution, your users will be stuck with your video settings...
Hugh, that one's well known (a bug with the timurid units), and personally i don't think you could increase those video settings at all.
I did not find this one listed so here it goes. Between Bucharest settlement and its port, there is no road or a crossing across the the river in the region to get one.
I've only got the game a few days ago so this is a new game on v1.1. Anyway, the auto-merging feature (M key) is inconsistent. Sometimes it'll work, sometimes it'll kind of work, and other times it won't work at all. In other words, sometimes all units get auto-merged, sometimes only some types do, or none at all do. I haven't seen this mentioned and it makes me wonder if I'm the only one getting it since it's such a basic function.
Whenever the auto-merging breaks, the only way I've found to fix it is to manually merge one pair, then repress the M key. This time it will work on the rest of the sets, although it is not guaranteed to work on other types of units unless I manually merge one pair of them also. This bug happens in both field armies and garrisoned armies.
is this a bug?
one turn in game equals 2 years on the time line... but the characters just age one year a turn (or maybe one year per two turns... i havent checked that...)
It's one year per two turns, and it's a feature to ensure that your characters don't die before they have a chance to develop.
@dunno, yes, i've noticed that too, though i haven't tried the manual merge workaround (and, tbh, i can't remember how to do so :P ) - i'd previously put it down to mercanaries not wanting to merge but you're right, it may well be a bug.
so let me get this straight... on the timeline 1 turn is 2 years but for a character 1 year is 2 turns?... thats stupid...
Quote:
Originally Posted by sapi
You can do manual merging by just dragging the unit portraits. I experience the auto-merge bugs even with militia spearmen who has taken casualties from the black plague, for example. So I end up with six stacks of 72 of 75 spearmen. Yet when I press M repeatedly, sometimes absolutely nothing happens. But if I drag two of the stacks together and then press M, I'll get five stacks of 75 and one stack of the remaining as is proper. Apart from the workaround, most of the time it clears itself up and works properly the next turn though.