11 replies to this topic

[mato33]

Hi all....I have the serious problem with selecting units in galactic conquest in FOC. I just play the game normally with no problems, no crahes, nothing and after a long time (after day 330 in galactic conquest) the problem with selecting units appears when I am unable in the space or land map to select any unit. After clicking the unit I hear the unit voice but I dont see any box, any hardpoints and I am unable to move the unit or attack with it. The unit is freezed. After calling reinforcments units arrive but again they are freezed after clicking them. The problem appears all the time with modded and unmodded game in every single game that lasts longer than 300 galactic days. I bought a new version of the game (I bought Gold pack, before I had EAW and FOC in two seperated boxes) as I believed the problem will be solved as I install the fresh new copy of the game. I was wrong and freezing unit problem is still there even in my new copy of the game. I dont think it is about the graphic because till day 330 and more I could play normally. The most recent bug with selecting units has appered in my last game in a day 449. I checked lots of info on the net but still I found no solution. I noticed that there has already been this problem mentioned on that forum in 2007 with one advice to shift click the freezed unit and wait several minutes that it would work again. I tried this way and it didnt help. I also noticed that pressing "c" when selected the freezed unit causes a desktop crash with an "exception" note.  I tried to install the entire Gold pack to my another computer and to test if the problem is there as well and.....it is there and units freeze in my another computer too (I transfered my saved positions there). I also found that a friend of my girlfriend who owns FOC has totally the same problem with freezing units. The problem is serious because after it appears no more units are selectable and when I return to the galaxy map I am unable to move anything. All fleets, all heroes and everything that is moveable is freezed forever. It means I am unable to continue playing. Really I dont know what is wrong....can someone please help?
I forgot to mention that reinstall, install to a new folder and even buying a new game dont help.
Thank you for any advice

[Raziel Kanos]

i think it has something to do with the amount of units that are in the galaxy map...

i read that before and this problem happened often with mods that give you tons of units. We are having the same problem with our mod "Awakening of the Rebellion 2.05"

can you please say if you're using a mod or if you play the vanilla game, and can you please post your dxDiag too?

[mato33]

Hi Raziel,
thank you for your reply. Probably you are right - the problem might be due to mods that provide more units. My last freezing unit problem appeared in the modded game (z3r0x) and it also has apperared in other mods too. As I remember clearly it appeared in unmodded game as well somewhen 2 years ago, but when I started to think more about it today I realized I am not sure if it was really unmodded or modded. I will try to play unmodded game to see. Anyway it looks that playing mods dont cause normally the freezing problem according to the almost non-existing reaction of other people. "Vanilla game" means probably unmodded game? I am not sure to be honest about that expression. I attached Dxdiag as a file

Attached Files

•  DxDiag.txt   47.2K   3 downloads

[Raziel Kanos]

yes, with "vanilla" I mean unmodded.

hardware & drivers are looking fine, so they shouldn't cause the problem. But like I said, my guess is it has to do with the numbers of units around, the freezing problem usualy only happens when people played a long time.

Would be interesting to know if your problem occoured in a unmodded game

[Turalyon]

Is there a solution for this? Some entry in a xml file to change?

It happened to me now as well. I de- and reinstalled the game and the mod (I'm playing AotR)

I reloaded my game and sold about 350 Points worth of units. Now, in the following space defense I can select 4 of my 5 MonCal Cruisers and 12 of my 60 E-Wing Squadrons. I also can select the space station. I cannot select the fighters that the station is spawning.

Right now my pop cap is 704 / 1284

[Turalyon]

Is there a solution for this? Some entry in a xml file to change?

It happened to me now as well. I de- and reinstalled the game and the mod (I'm playing AotR)

I reloaded my game and sold about 350 Points worth of units. Now, in the following space defense I can select 3 of my 5 MonCal Cruisers and 12 of my 60 E-Wing Squadrons. I also can select the space station. I cannot select the fighters that the station is spawning.

Right now my pop cap is 704 / 1284

Edited by Turalyon, 12 October 2009 - 06:28 AM.

[atroublestarter]

Turalyon, on 12 October 2009 - 06:28 AM, said:

Is there a solution for this? Some entry in a xml file to change?

It happened to me now as well. I de- and reinstalled the game and the mod (I'm playing AotR)

I reloaded my game and sold about 350 Points worth of units. Now, in the following space defense I can select 3 of my 5 MonCal Cruisers and 12 of my 60 E-Wing Squadrons. I also can select the space station. I cannot select the fighters that the station is spawning.

Right now my pop cap is 704 / 1284

that does seem to be a hell of a lot of units! i am experiencing the same problems (am also using a mod - Ultimate Empire At War) but i do not have anywhere near that amount of units - i have no more than 400 units, and i control about half of the galaxy so far.

Also, the bug with me always seems to begin occuring during an actual space battle, then it carries over to the galaxy tactical view.  My units and garrisons all begin responding correctly, and then it happens.  I have noticed with this bug that not only am i unable to select any new 'garrison' units as they enter the battle (once the bug kicks in) but those units are missing hard points.  Oddly enough, all new units brought in by the AI after this bug kicks in are also missing hard points, whilst the units that started in the battle are all still selectable and all still have their hard points showing.

I have also noted that any enemy AI units which are brought in after the glitch kicks in are also untargettable with the ion cannon / hypervelocity gun, whilst the units that are present in the battle before the bug kicks in still behave normally, and can be targetted, and show hardpoints.

If the glitch always kicks in half way through an actual battle, can it really be the unit limit that is creating this problem?  Also if this is the case, this bug should be quite common, as i only have 350-400 unit points used at the moment i believe, with control of just roughly half of the galaxy, which i'm sure are numbers consistant with vanilla?......

[luke0086]

still no solution to this?!

[OmegaWulf]

I have this problem too.  Is there no fix?

[kitz]

OmegaWulf, on 29 May 2012 - 08:07 PM, said:

I have this problem too.  Is there no fix?

I've been playing the game for a couple of years now and have always had the same problem which
actually stopped me from buying petroglyph games. I thought that it was the computer I was using
at the time. I found the games recently , started playing and behold the same problem with the
rebels again.

This bug has been around for a LONG time. Why is there no fix????

[InHumanTurtle]

Isn't there any way to fix this? Shouldn't we be able to edit some XML settings?

Playing on the Republic at war mod, I am very reluctant to sell my units considering the AI has nearly 100% of it's population cap full, whereas mine is only 440/1300(on another note, how do we stop AI from cheating and force them to use only the resources they have rather than always having 40,000 more credits...) so I would rather find a way to delete a bunch of their units if possible. That is, if no other solution can be found.

[Nissath]

Hi!
I know this is old topic but I have to refresh it and ask.
I have come across this annoying bug and I wonder is there any solution to this? It's been a while when the first time this was reported so maybe this have been repaired. If yes, can you paste a link or sth for the fix or solution, please? I'd be grateful.

Edited by Nissath, 23 April 2013 - 06:54 AM.