Matrix Games Forums

I had an error message whilst the game was "reloading" after I had closed a game without exiting.

The dialog box had a "Heading" ( top left ) : "Problem". The detail was as follows :
"Failed on memory allocation in tile.cpp." The only option given was "OK".

Pressing "OK" lead to a "Frozen" screen. Pressing Ctrl and Esc togeather led to a further dialog box :

"Heading" ( top left ) : "Assertion failed".
Detail : " Program Matrix Games\Forge of Freedom\exe
File C: \Projects\view plato\source\tile.cpp"
Further detail : "Expression: 0"
Options given: "Abort, retry, cancel".

Abort was chosen, and this closed the game / program.
[ I believe the "detail" above is as listed, but am unsure exactly what was between "Program" & "Matrix" and between "exe" & "File C" ( if anything ). I hope this will not be a hinderence. ]

Anyone know what the problem was here ? I think it failed to reload the game successfully. But why ? It's only happened once over perhaps a dozen to a score of successful closing of games without exiting.

[ It's possible that both the "Quick battles" and the "Use Detailed Battles Only" options were checked here! If you check "Use Detailed Battles Only" for a game, the system remembers it when reloading the next game; but if you now select the Basic game, the sytem does not automatically uncheck it - thus both are now checked, which I presume could be the cause of a ( my ) problem. It does however, automatically uncheck Quick battles if you select the Basic game and then check ( an unchecked ) "Use Detailed Battles Only". I still have FoF as per loaded from the disk at the moment, without the last patch update, so if this "bug" was fixed in that patch then I guess I will be OK after patching the game up to date ( presuming this was indeed the cause )! Whether or not it was the cause of my reported error message, has this "bug" be corrected; if not, will it be corrected in due course ? ]

Thanks.

Thanks for the report. Please update the game and see whether you can reproduce this issue. I remember that we had two critical errors that we fixed shortly after release -- one of them involved forts, and the other was some graphics de-/allocation problem, if I remember correctly. Maybe this was related to the latter. My guess would be that the game options wouldn't affect your issue, which seems to be a memory allocation or file loading error that happens during the loading of graphics images; the quick combat options shouldn't have anything to do with this.

Thank you for your reply / comments regarding my error messages. I'll update the game in the near future and see what ( if anything ) happens !!

However, I note no specific reply re my bracketed ( separate ) "bug" report, and it's last sentence question. Advices please.

Thanks.

I can confirm this glitch in the options screen, but has no unwanted effect.
A later patch added the options:
- Always Quick Combat
- Always Instant Combat
- Always Detail Option

Selecting "Always Detail Option" and thereafter "Basic" will show both "Always Quick Combat"
and "Always Detail Option" checked, what makes no sense. But the programming logic in
the game will give you "Quick Combat", the option to select a detail battle is not shown.
So it is a glitch in the option interface, but without any negative effect to the gameplay.

I can only recommend to update the game to the latest patch, there is a long list of
bugfixes in the readme file.

DEB, am I right that Floyd's response was sufficient, or is there still a problem?

Hi,

Floyd's response appears to answer my "sub" question. I'll look into it and post accordingly, proberly early in the New Year.

ORIGINAL: Floyd

I can confirm this glitch in the options screen, but has no unwanted effect.

Selecting "Always Detail Option" and thereafter "Basic" will show both "Always Quick Combat"
and "Always Detail Option" checked, what makes no sense. But the programming logic in
the game will give you "Quick Combat", the option to select a detail battle is not shown.
So it is a glitch in the option interface, but without any negative effect to the gameplay.

Thanks for the information. I'll investigate further.
( I'm glad it does not affect gameplay!! )

ORIGINAL: Gil R.

DEB, am I right that Floyd's response was sufficient, or is there still a problem?

Further to my previous response ( to you ).

Floyd's response indeed answers my query [ Thank you Floyd ].

I have no idea yet if updating the game to the most up to date patch will cure the "error" on the Local game screen. That will have to wait a while.
Meanwhile though, the game plays as it should despite that error.
Therefore my bracketed query has been answered / dealt with.
My original ( main ) query still awaits review ( post a patch update ).

If the patch update fails to cure either / both queries in due course, I'll post accordingly as and when I become aware.