PodFloat lines 256, 266, and 53

[vandorenp]

While running a customized scenario I received this set of errors repeatedly. Seemed to happen after I clicked on a unit. Sometimes I gave orders and sometimes I just looked at the unit data. The game recording and one of the game saves is attached.

This would occur in batches. That is all three occurred in turn as I clicked ignore for each one. The series would reoccur three or four times in the span of a few minutes. Then go dormant. Some number of minutes later it would happen again. It happened D1 1041, D1 1203, D1 1535, D2 0723 and many more times. I saved only for those listed. When I let the game run to completion without additional orders the error did not run again: the game ran to completion without the error occurring again.

The game-recording file when zipped is 1.5 Meg. This is over the forum 1 Meg limit. (How do I get this to you? e-mail?) So the zip file attached has the game save after the first three instances.

[Lieste]

Is this the same modified scenario where you only modified one of three Estab entries in the scenario file?

[Arjuna]

These errors are for data overflows - ie the number passed in is too big for the data size we have assigned. I'll check them out.

[vandorenp]

This is a scenario that uses the estab file in which i have made modifications.

[vandorenp]

Occurs to me if you should want to open the save game you will need the map and estab. I will put on the FTP site or e-mail it to you Dave?

[vandorenp]

Looks like I can not upload. I will e-mail to you Dave.

[simovitch]

Sounds like a divide by zero problem. I doubt it is the fault of the game engine.

Check in the SM to see if your new scenario seeks your modified estab file and not the stock file.

If OK, check your new estabs and see if you filled in all the fields.

[vandorenp]

Error has not re-occurred in last several runs. I changed the 0 deployment times for the static arty to one minute to fix a different problem. But I believe the PodFloat problem happened before I set the deployment times to 0.

Another oddity that I "fixed" was the subforce type for mot NebelWerfers. These were set to Mot RL. Never was a problem when compiling till after I simply viewed the NW forces.

[simovitch]

Messing around with subforce types has caused me problems before. I believe that some of them, although listed, are not 'coded' in the game.