.cam files and weather.ini need to take Korea local time into account.
-
EDIT: Sorry, this was just a coincidence. Other theaters have no problems with an edited weather.ini and current times of day 1, 00:00:00. If you find yourself into this issue you can give this solution a try, but keep in mind that this " take into account Korea local time " theory is wrong.
From here, original post:
Hi,
After editing my weather.ini to my theaters coordiates some of my .cam files began to CTD.
I just found out that if you have a current time for your .cam that is a Korea local time earlier than Day 1, 00:00:00 you will get CTDs right at start.
My theater local zone is 1, and Korea is 9, so I need to set my current times for .cam to Day 1, 08:00:00 or later to avoid CTDs.
Hope this info helps.
Enviado desde mi SM-A715F mediante Tapatalk
-
You bet well it does, hermano.
Thanks a lot for sharing!
With best regards.
-
Hi,
I tested my theory in Balkans, and has no problem with setting .cam files to current time 1, 00:00:00 .
So I guess this proves my theory is wrong.
My crashlog returned an excepction in:
GetNeightborObject() at campaign/camplib/path.cpp, line 752.
I dont know why a change in my weather.ini triggered this.
Looking at FreeFalcon git repository (closest available thing) 752 line of that file I get this:
if (flags bitand PATH_AIRBORNE) {
opt = o->GetNeighborCost(neighbor, LowAir) * mult;
if (opt < cost) cost = opt;
}
Enviado desde mi SM-A715F mediante Tapatalk
-
In the end the CTD is solved by recalculating links costs. I can now set the current time back to Day 1, 00:00:00. Thanks @Kaos
Enviado desde mi SM-A715F mediante Tapatalk