Recently I had to perform first aid on my personal mod and have got it working again except for 4 races which there is no problem playing against but when I go to play as them 2 of the races crash during the load up and the other 2 crash when i click on any units in game, If anyone knows why this may be happening it would be a great help have ruled out some of the more obvious reasons as can play against them fine just can not play as them.
7th January 2006
adamjboucher;5004913when I go to play as them 2 of the races crash during the load up and the other 2 crash when i click on any units in game
The reasons for the first two sound like they may have something to do with either the .ODF entries (which you can now use a software program to double-check-- it's called STAUM and it's available in the downloads section on the main site), or the techtree entries you're using. It could also be the race name you've used in the race's main .ODF (in odf/other).
The other two races sound like there may be a problem with either the sounds you're using, the race name you've selected in the .ODF for the unit files, or maybe even some part of the techtree setup you're using.
All of this is impossible to determine with so little information. If you could tell us what races we're talking about, what units of those races you're using when it crashes, and whether or not you've run a check on the mod yourself..... we need specifics in order to help. The more, the better.
ok i have checked it and i know its not a general tectree error such as there being an o instead of an 0 or the opposite as that would affect all races. have managed to check the units odfs as can build that races units if i add the construction ships to another races base with no problem its just when I go to play as those races the problem occurs which i have never faced before. i can proberly fix it if i know where to look but have looked in all the usual places with no luck so far
Did you check the tech1.tt file as well as the fulltech.tt file? The tech1.tt file has all of the permissions and requirements for the special weapons as well as the ships and stations. If one of the requirements for a special weapon is altered or missing, or the weapon is not listed at all, this will cause the game to crash as soon as a ship attempts to use it. I'd still like to hear about some more details as to exactly at what point the game CTDs or which races make the game stop. It is very difficult and frustrating to properly assist you by taking blind stabs in the dark based upon the limited information you have provided so far. We want to help and there are a ton of people around here who can and will gladly do so. But you really should tell us a little more than, "My game is broke and I don't know why."
7th January 2006
adamjboucher;5005418have managed to check the units odfs as can build that races units if i add the construction ships to another races base with no problem its just when I go to play as those races the problem occurs which i have never faced before.
Chances are this is not a construction ship problem but something else entirely.
Once more, I must ask for more details. What races? What units? What base? What weapons are they using? etc. Please offer more details or we're going to be talking past each other. There are never generic, "quick fix" solutions in A2. It's always some tiny super-specific detail that makes the whole game crash.
ok I will try to give more details . the problems is with the breen and cardasian races the game loads up and i have the base and 2 construction ships but when i go to click on either the game crashes however this is where it get intresting. I have the breen cardasian and dominion races seperate with another race which is the 3 of them combined so tried that and was able to build the entire range of dominion and breen ships no problem. I have now changed the race files in both the breen and dominion to now start with a cardasian constructor which can build both bases and this works fine so know its not a general odf problem like forgetting the " or a spelling or typing error it is also neither a tectree or a sprite problem and quite good at fixing problems when I can work out where the problem is but have no idea on this one