Topic
[Trigger] Galaxy Data Table overflow error
|
Edited by Ahli on 11/09/12 19:58 (BST)
I'm extensively using the global data table and with some additions in my map I'm currently receiving the following error:
"Galaxy data table overflow. Probable infinite galaxy loop." The loop I used is not infinite. I thought that the amount of saved values could be a problem. Before I saved all 64 custom values of a unit resulting in entry counts like 1.101.744 and now I cut it down to approx 250.000, but that didn't solve the problem. Maybe it's caused by my key. It has the following format: [integer from 1...20][d][integer starting at 0 counting upwards][cv][custom value index] So one of my keys might be "20d1234cv28" or "1d0cv0". Is this caused by my key usage? Is this caused by the short duration in which I fill all these entries? How can I solve this problem? I would like to understand why this is happening... edit: Blizzard's developer Tenarsis explained me the problem: I was hitting a limit with complex data type referencing which is at 32k references. Complex data types are texts, strings, points, regions, etc. So storing integers and real values won't count towards that limit. I'm saving 1 string and 1 point per unit while I'm storing an immense amount of units. This lead to hitting that limit while storing the huge amount of data into the data table. A simple fix for my problem was to store the x- and y-coordinate of a point (=position of unit) separately. |
