From: Martin B. <dr....@t-...> - 2013-10-04 10:59:58
|
Hi Stefan, Erik, somewhere in between the 1.7.10 and the current HEAD of the 1.7.x branch the reprocessing of save games in 1835 falls for specific szenario. From what i was able to see: The stepobject inside the OR doesnt get advanced (OR5.2 Opcompany BY) if Opcomp lays a tile to the next OR Step (probably has to do with the rare case that the OPcomp here owns a private which would allow another tilelay for free. This leads to the point that the internal representation of StepObject differs from the recorded Action. I.e. the recorded action is NullAction.SkIP (for skpipping the LayToken) but the Step.Object is still pointing at LAY_TRACK. The subsequent action SetDividend then fails because the Internal StepObject is pointing at LAY_TOKEN. Somehow the Nullaction regarding the special TileLay isnt recorded there valid. If one plays the interrupted game to the end and saves that builds a new report, that then tests ok. But the master branch doesnt fail but subsequently fails on the new savegame and report. So that puts us in the position that master is not reflecting the state of rails1.7.x. And my question now would be how to proceed to release 1.8 ? We are ready with 1880, rails1.7.x_1880 is a branch based on the latest rails1.7.x which incorporates all from specific_1880. and could be used to release 1.8. but how should i incoporate specific_1880 into the master branch ?. Kind regards, Martin |