TCP/IP Assertion Failed!

[Call Me Earl]

This is an error I get when playing TCP/IP games with Scipio666. It appears after doing first detailed battle. Reloading the saved game or auto save does not cure the problem. Anyone have any ideas on what may be causing this ? It appears the game only works in multiplayer for PBEM games. Anyone had any success playing this game TCP/IP ? Thanks Earl

Microsoft Visual C++ Runtime Libary
Assertion Failed!
Program C:\Games\Forged of Freedom\Forged of Freedom.exe
File:C:\projects\acwpato\source\provine.cpp
line 238

Expression test ==18611864

For information on how your programe can cause an assertion failer see microsoft C++ documantation
on asserts.

[ericbabe]

Would you mind please zipping the save game files (.sve and .rep) and send them to ericbabe@west-civ.com?  We haven't seen this problem in our TCP/IP testing, but there could be some condition causing it that doesn't happen very often.

[Call Me Earl]

Eric, I am not trying to be a jerk here or anything, but everytime Scipio666 and I try and play this game TCP/IP we get Assertion Failed ! errors. Reading from other posts, this same problem appears in LAN games as well. Scipio666 emailed you the save game files from one such game. I am not sure how this game was tested for multiplayer and not have these same errors surface ? This error appears every time when you do the second detailed battle in a game. I would be more than happy to play a TCP/IP game with you so you can see first hand what is happening. Trust me, it won't take much of your time as it happens quickly, whether you do a detailed battle or not. I would like nothing better than to get this bug/bugs worked out of this truely good game so I can enjoy it to its full potential. We just concluded another TCP/IP test of the game with the following setup and results:

Game Settings

Intermediate Game, Standard Campaign, Sergeant
Turned on the following: Governors, Advance buildings, Upgrade Weapons, Use Generals, More Generals, Detailed Battles

We played the game normally, except that we did not do any battles, as we thought the detailed battles alone were causing the errors.

When ending the Early Jan. 1862 turn, after selecting my general for promotion, I received the first Assertion Failed ! error.

Microsoft Visual C++ Runtime Library

Assertion Failed !

Program...IXGames\Forge of Freedom\Forge of Freedom.exe
File: C:\Projects\ACWPlato\Source\game.cpp
Line: 2102
Expression: Check==112233

For information on how your program can cause an assertion failure, see Visual C++ documentation on asserts.

Press Retry to debug the application - JIT must be enabled.

I hit ignore at this point and the game continued. Did my next turn and ended the turn, promoted my general and received another Assertion Failed ! error as follows:

Microsoft Visual C++ Runtime Library

Assertion Failed !

Program...IXGames\Forge of Freedom\Forge of Freedom.exe
File: C:\Projects\ACWPlato\Source\Piecemap.cpp
Line: 1008
Expression: Test==20052006

For information on how your program can cause an assertion failure, see Visual C++ documentation on asserts.

Press Retry to debug the application - JIT must be enabled.

I again hit ignore, but this time it came up with another Assertion Failed ! error.

Microsoft Visual C++ Runtime Library

Assertion Failed !

Program...IXGames\Forge of Freedom\Forge of Freedom.exe
File: C:\Projects\ACWPlato\Source\province.cpp
Line: 238
Expression: Test==18611864

For information on how your program can cause an assertion failure, see Visual C++ documentation on asserts.

Press Retry to debug the application - JIT must be enabled.

At this point hitting ignore did not work, so I hit retry and a window popped up asking if I would like to report the problem to Microsoft, I said no and was exited out of the game.

Originally we thought that the Detailed Battling alone was causing the problem, but that is not the case. It does not matter if he hosts or I host, we still get the errors. I will add this, the host never see's the errors, it is always the player that joins. The game continues for the host as if nothing ever happened. Again, Eric, I am more than willing to play a game TCP/IP with you so you can see the errors first hand. I promise to only say nice things about the game and to you, lol. Thanks for any help you can provide, Call Me Earl

[Alan_Bernardo]

Earl,
 
If you want, us two can try this and see if we the same errors.  You never know what's going on unless you test with others, also.
 
Email me at alan.bernardo@gmail.com if you want to test this and see if we get the same error.
 
 
Alanb
 

[Concord Dan]

Good News sorta - Finally someone else has the exact same problem as me and my brother.

Bad News - This problem has stopped my playing of FoF until this is fixed.

[Call Me Earl]

Concord Dan, Please PM me if you catch me on the Forum and I'll try and do the same. Would like to discuss this issue with you. Thks Earl

[ericbabe]

ORIGINAL: Concord Dan
Good News sorta - Finally someone else has the exact same problem as me and my brother.

Bad News - This problem has stopped my playing of FoF until this is fixed.

Were you playing LAN or Internet?

[Concord Dan]

Internet - Packets are NOT the problem. It crashes the client EVERY time on the 2ND detailed battle.

Packets are NOT the problem - I start 2 sessions on my machine - One HOST one Client - SAME PROBLEM - 2ND battle crashes the client.

Let me know if you need anything else.

[ericbabe]

Is anyone else having the problem of the client crashing every time on the 2nd detailed battle?

This wasn't the problem I thought might be caused by dropped packets.

[Maulet]

Ericbabe I have posted your question in the thread "tcp/ip problems".

And the answer is: yes, but in the first battle

[Call Me Earl]

Eric,
I think there are two TCP/IP problems going on here. Yes the game freezes in detailed combat. I have had it freeze during the 1st battle and the second. The game never makes it past the second detailed battle without freezing. If the game freezes during the detailed battle and you reload the game via auto-save, within a coulple of turns you start getting the assertion failed errors. You can usually ignore the 1st assertion failed error and play another turn, but then you get another assertion failed error which will CTD.

Alan B. and I played a TCP/IP game where we used instant battles. We played into early 1862 and then we had the assertion failed error. He ignored it and we kept playing several more turns. Then we did a detailed battle and the game froze up in the detailed battle.

It appears that there are 2 things going on in TCP/IP games, the detailed battles freeze the game and you get the assertion failed errors without using the detailed battle option.

Again, I will offer my services for testing TCP/IP games. Eric, I think you need to test the TCP/IP outside of a LAN to see what is actually happening. Play a game using instant battles only, you will eventually get an assertion failed error. Then try one using detailed battles. The game will freeze up.

I would be more than happy to get online with you so that you can see what the game is doing. Many thks Eric for looking into this problem ! Most wouldn't take the time. Call Me Earl

[ericbabe]

It's hard to tell whether they are two separate problems with so little information.

I'll try to arrange for some more internet testing (as opposed to LAN testing) in-house -- it's easier if I do it since I can run both programs under the debugger to catch exactly what's going wrong.  It would help to get more feedback from other people playing by TCP/IP -- we might be able to find some common factors or chance upon some other information.

[Call Me Earl]

I think that is a good call Eric, playing TCP/IP outside of your LAN. You should see the detailed battle freeze right away. After you get that, reload the auto-save and try to continue playing. Then play a quick game using instant battles only and you should come across the random assertion failed error.

I wish you luck Eric and hope that you do in fact resolve the TCP/IP issues. This would be a fun game to play multiplayer. For now I am setting this game aside and moving on to something else. I'll check back from time to time to see if it has been fixed, but to be honest, I am not holding out much hope. Thanks for the interest you have shown in this Eric. Call Me Earl

[Erik Rutins]

Earl,

Believe me, we're looking at TCP/IP and will get these issues fixed as soon as we can duplicate them on a development machine.

Regards,

- Erik

[Scipio666]

Erik, I dont know how you cant replicate the detailed battled error over tcp/ip. It happens on the first or second battle to everyone. Except for people with magical versions of the game? I know most people play this single player or PBEM however I find it hard to believe that Concord Dan his brother, Maulet and his friend, Al and call me earl, and myself and call me earl all have some flaw here and its not the game. We have also all tried multiple play tests with it happening always not just once in awhile. If you cant get the error by your self perhaps like Call me Earl suggests perhaps someone should try the game with one of us. It is frustrating as Call Me Earl suggests because we only bought this game to play multiplayer and now we cant even get past the second battle unless we want to do lame instant battle.

[Erik Rutins]

We understand. Please keep in mind there are a lot of things being worked on behind the scenes and this is one of them. I'm schedule to have a remote TCP/IP test with Eric Babe this afternoon actually. We put a new beta build into testing yesterday. I realize soon doesn't seem like soon enough, but work is going on through the weekend to address the highest priority issues. Once we find the cause of the TCP/IP problems you've been experiencing, then we'll know how hard a fix it will be.

Regards,

- Erik

[Scipio666]

I understand you guys are working hard at it. Also I understand the people that want to play TCP/IP represent like 1% of people who buy this game. However we just want to help you fix the problem perhaps by playing with someone who actually gets the error it will help you fix it. If for some reason the game runs perfect for you then you wont get the error to fix it. Anyhow good luck!! Ericbabe says he needs more info perhaps if he tells us what else might be helpfull that he is looking for ie: game settings, what systems we are using or whatever else he may be looking for perhaps we can help provide it.

[Erik Rutins]

Scipio,

Game settings would of course be helpful, all additional info is helpful, but there seems to be some frustration building because we haven't asked one of you to start a game with us for testing. It would also help a lot to have more reports from others playing with TCP/IP to know if it's also working for them and what the rate of success is, also as far as LAN vs. Internet TCP/IP play. Let me be clear on a couple of things there:

1. We believe you that this is happening to you and a few others.
2. We haven't seen it ourselves, but we're doing more testing based on your reports to duplicate it, including testing today.
3. We're working on a lot of other things at the same time, so we can't exclusively focus on this, but it is an important issue
4. Because it happens repeatably for you doesn't mean that it happens that way for everyone playing TCP/IP, necessarily (it did not during testing)
5. Despite your generous offers, it won't actually help us unless we can duplicate this issue on a development system with a debugger running, that's the only reason you haven't been taken up on your offers yet. We are not ignoring the issue but the main thing that playing with you would do is confirm its existence, rather than help us fix it. Since we already believe you, that's not a big help unfortunately.

Regards,

- Erik

[2gaulle]

ORIGINAL: Erik Rutins


3. We're working on a lot of other things at the same time, so we can't exclusively focus on this, but it is an important issue

perhaps you will not be in that kind of trouble if you didn't release the game before it was finished [:-]

[Marc von Martial]

ORIGINAL: 2gaulle

ORIGINAL: Erik Rutins


3. We're working on a lot of other things at the same time, so we can't exclusively focus on this, but it is an important issue

perhaps you will not be in that kind of trouble if you didn't release the game before it was finished [:-]

bla bla bla, sorry.