Technical support > Windows
Win32 Development Binary Installer Links
iliaarpad:
I'm using the default settings as well. I didn't touch anything. I still think that this is because I use the 3.4.5 version of the gcc compiler while the prepackaged Codeblocks comes with version 3.4.2 of the gcc compiler.
Optimization makes the generated code run faster. The more aggressive it is the more effective the code can become. However applying too much optimization can lead sometimes to code instability. The default UFO: AI Codeblocks project adds an option to the compiler telling it to use third level optimization, which should be safe, unless the compiler is buggy. This is why I started to suspect the compiler.
As for other IDE-s, I have Eclipse with sun JDK and Visual Studio 8 installed but I don't think they could cause the problem. When I tried to compile UFO: AI with the 3.4.2 version of the compiler the linker couldn't find some libraries. As soon as I replaced it with the 3.4.5 compiler it started to work.
Since Muton seems to have the same problem as I have, I'm quite curious as to what gcc version he is using. If it is 3.4.5...
Edit:
--- Quote ---This is probably a very *long* shot, but do you compile with the target "win32" or "win32_debug"?
--- End quote ---
Argh... You are right! I don't know when or how but looks like I somehow accidentally changed the target to windows from windows_debug. But I still don't understand why that causes a problem.
Muton:
--- Quote from: iliaarpad on February 19, 2009, 02:08:00 am ---@Muton: what compiler version are you using?
--- End quote ---
mingw-gcc 3.4.2
Destructavator build a debug version
Debugging options do not include any optimation
So there is no magic!
'Couse i'm using optimation on ufo.exe for quite some time (ufo2map too [speed up by >10%])
i knew there was no problem with -O2 or -O3 before 22707
only with optimation -march
Anything higher i686 let the game crash.
iliaarpad:
Okay, I think I figured it out.
The problem seems to arise at revision 22688 (r22687 runs without segmentation fault when compiled as a release with O2 optimization).
More precisely the problem occurs when the line
--- Code: ---visiblewhen "mn_main eq singleplayerInGame"
--- End code ---
is missing from the button_save block in menu_singleplayer.ufo.
When I add the line back the game runs fine (at least it doesn't crash after selecting the Single Player menu).
So, if you would like to build a release version with O2 optimization enabled add the line above in the button_save block. After that the game will work.
Muton, could you verify it? Could you try adding the line above to the button_save block? Thanks!
odie:
--- Quote from: iliaarpad on February 19, 2009, 10:51:35 pm ---Okay, I think I figured it out.
The problem seems to arise at revision 22688 (r22687 runs without segmentation fault when compiled as a release with O2 optimization).
More precisely the problem occurs when the line
--- Code: ---visiblewhen "mn_main eq singleplayerInGame"
--- End code ---
is missing from the button_save block in menu_singleplayer.ufo.
When I add the line back the game runs fine (at least it doesn't crash after selecting the Single Player menu).
So, if you would like to build a release version with O2 optimization enabled add the line above in the button_save block. After that the game will work.
Muton, could you verify it? Could you try adding the line above to the button_save block? Thanks!
--- End quote ---
Hi iliaarpad,
I have been following this thread too. I last built 22773 and i face the same problems.
I guess i will wait for u folks to try fix this before i post more on this.
For now, for your reference, my system:
Win XP SP3, fully patched as of feb 09.
Previously running smoothly up to i believe 22650+- that revision. I patch and update every morning, recompile and bring home to try out. (That is continue the previous save games until it breaks).
As of last nite 22773, it works perfectly up to the single player mode. All other options in the menu (credits, multiplayer, options, even the exit) works fine.
For reference pls. :)
geever:
We have investigated this problem last night and Bayo committed a possible fix in r22790.
note: it was only reproducible on windows, release build.
-geever
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version