Page 1 of 1

Fatal error in 1.10c pbm campaign

Posted: Tue Jun 17, 2008 5:16 pm
by asdicus
I am playing a pbm game as the usa - using patch 1.10c. I have got to late july 1862 with no problems but am now seeing regular fatal errors when I try to move troops or ships around. The error message is always the same whether it is a troops or ships I am moving :

TGroup.PathExists Erroneous logic, path with only one region listed

The error dumps me back to windows unless I turn error logging on - in which case I can then just continue with my orders. I can supply a pbm save turn if required.

Posted: Tue Jun 17, 2008 5:25 pm
by Pocus
is your opponent using 1.10c or 1.10d?

Posted: Tue Jun 17, 2008 5:29 pm
by asdicus
He should be using 1.10c - why do you think this could be significant ?

Posted: Tue Jun 17, 2008 5:33 pm
by asdicus
In addition to these errors I am also seeing corrupted messages appearing in the player box eg 0 has arrived at Floyd, GA at day 4. They always start with 0 instead of the correct name - this has only started happening in the last turn.

Posted: Wed Jun 18, 2008 7:29 am
by Pocus
There was some data changes between 1.10c and 1.10d that can perhaps do that. Can you ask him?

Posted: Wed Jun 18, 2008 8:10 pm
by tagwyn
Pocus: I hope this all hangs together a while longer. Are you losing mor3 Hair? t

Posted: Sun Jun 22, 2008 12:49 am
by asdicus
My opponent confirms that he is running 1.10c.

I have emailed the usa ord/trn files plus log to support. I am not the host of this pbm game.

This particular pbm game is now totally broken for the union. The fatal error can be reproduced by trying to place the union army at vicksburg into the city. Other problems include all units set to assault resetting to offensive posture and all units using rail or boat transport changing to march option. we did upgrade from 1.10b to 1.10c about a dozen turns back - these problems have only started happening recently ie from mid 1862 onwards. also only the union has problems - csa is the game host and has no reported problems.

Posted: Sun Jun 22, 2008 3:23 am
by asdicus
After an uninstall / fresh install this problem seems to have gone away - although I am still not sure what caused all of this. Is the official recommendation that when you patch a game you should uninstall and reinstall from scratch ?

Posted: Sun Jun 22, 2008 9:58 am
by Gray_Lensman
deleted