problem :(

[Phil Defer]

Hello ! I have installed Alpha Centauri without any problem but when I launch it, it launches but it freezes at the screen of "Firaxis Games"... and it doesn't do more

Help me please

thanks !

[Phil Defer]

precision : i have Windows 98 Second Edition

[Alex]

What is your processor? There is a well known problem involving Pentium 4 and some others, where the game won't recognize your processor, which may lead to a lot of problems, like crashes and the game refusing to run at all.

Try adding the line:

ForceOldVoxelAlgorithm=1

to your alphacentauri.ini file in the SMAC directory and see if that helps.

(I hope I have a good memory... )

[Phil Defer]

i have a celeron 500

i will try what you said

[Phil Defer]

i just tried, it doesn't work

[Petek]

If you don't already have it, you need to place a section header before the ForceOldVoxel... line:

[PREFERENCES]
ForceOldVoxelAlgorithm=1

Petek

[Phil Defer]

i have tried to add this and unfortunately it still doesn't work

has anyone already had this problem ? sorry for my bad english

[Mongoose]

What version are you using? IIRC, the euro releases required the CD in the drive to play. IIRC also, there were a lot of folks with Celeron sets that were having trouble. Sadly, I do not recall how to fix it.

[Phil Defer]

in fact, the problem is that there is the cursor that says it works at the screen of firaxis but when i do CTRL ALT DEL it says "Alpha Cantauri" no answer...

[krazykiter]

Phil,

I've experienced the same problem running SMAC and SMACX on a 2 GHz Pentium 4 under WinXP

In addition to PEtek's suggestion, you may also need Firaxis' Win2000/XP Compatibility Update.

Good Luck

[Alex]

Why would he need the compatibility update? He said he is running on Win 98 SE.

[johndmuller]

I have had problems where it failed to load the game in something like the manner you describe when running Win98 SE or possibly something earlier on a computer without much hardware power. Sometimes it would only start if SMAC was pretty much the first thing run after a reboot, other times it would work OK irrespective of whether or not I rebooted. I don't know if it was connected or not, but the sound was often mysteriously inactive on this computer too (it would come on if I toggled it off and on again within the game). On a different computer (also Win98 xx) it would sometimes crash on loading - this one was definitely sound related, it wouldn't happen if I disabled the sound at the operating system level (definietely a PIA) and it began after I accepted a sound driver update from Microsoft's upgrade thing. There are ways of adjusting certain things about the sound in the .ini file - something about dx3 (3D I think) and maybe something else too.

Your DirectX may not be right for whatever reason - too old, not appropriate for your hardware/software, whatever.

There is also the video driver - perhaps you could try disabling the opening movie in the .ini file.

The .ini file(s) may have bad stuff in it from following advice such as this and may be difficult to fix - I have made *correct* adjustments to it that lead to inability to start up the program and had to resort to draconian measures like copying the whole AC subdirectory from another machine. A reload might help if you have some corrupted files (personally, I hate it when someone tells me to do that, but sometimes it is more expedient to do that - it doesn't really take long and you can always back up the current one first if you don't want to lose stuff).

Summary of areas of interest:
1) Win environment - reboot before starting game, don't run too much other stuff with it, use Win2K;
2) sound - drivers, directx, .ini adjustments, turn it off in OS;
3) video - drivers, directx, .ini adjustments (disable opening movie)
4) internal game .ini, etc files - check and/or copy from good set, reload game
5) flakey CD - get no-cd version (try Googlies website) of executable
6) bad Karma - kiss and make up with Miriam
7) consult Buster's Help thread on CGN.

Sorry I didn't provide as many specifics as you might wish; hopefully you can find or figure out the references - just post if any of them are too obscure.

Good luck.

[Kajak]

Just a word or two from the terran.exe crash Problem victum of his own dumbness. I agree with all the above advice, but IMHA.
1. I have xp pro, 2Gig , P4 and bunch of other stuff including a Microtex scanner ( more on this later). SMAC wouldn,t run at first either, (Ver 1.--) untill I not only unistalled it , but rooted out all the parts still there , and did a reinstall. Why it failed the first time Ihave no idea. Note again Ver. 1. as from the Jewel box.
2.. This ver (1.0something) .ini has no line in it of the nature of Forceoldv. ect. and putting it in didn't work for me..
This line does occurs in the patched .ini after u
you do the Patch 4 . The line is set equal to zero (0), changedthe zero to one (1) as so often recommeded and it ran. Thru it still gave the cpu unsupportd warning which you can blow thru.
3. Had much agony over mid game terran.exe crashes when the action in the game got very busy and suspected some kind of internal list limits. Well I was right in a sense, but totally wrong also. Any visitors had commented that my machine seemed alfully slow for such a new machine, being brand new to this I ingnored the comments. To keep it short it seems my scanned (though new also) was using an old driver that somehow was burning up vast parts of the cpu. Downloaded new driver,installed, and just completed a game where two AI's and I went to a world wide war aginst the other three A.I.s with wild wild action, long build list, lots of patrolling, ect and had no crashes.
While apocraful, perhaps these thoughts might help.

By the way can anyone tell what the new Fireaxis patch does ? Can.t tell as yet from this end.

[DinoDoc]

Originally posted by Petek
If you don't already have it, you need to place a section header before the ForceOldVoxel... line:

[PREFERENCES]
ForceOldVoxelAlgorithm=1

That didn't work for me. It still says that it won't recognize my processor.

[Lefty Scaevola]

Originally posted by DinoDoc
That didn't work for me. It still says that it won't recognize my processor.

At that point select ok/continue or whatever the affirmative option is. It will still give you that line even if it is capable of working with the urecognized proscessor after the preference line is added.