world.tick_usage is unusable during the first game tick (world.tick == 0)
Numbered Steps to Reproduce Problem:
print world.tick_usage during the first game tick
Code Snippet (if applicable) to Reproduce Problem:
/proc/print()
world.log << "[world.time] [world.cpu] [world.map_cpu] [world.tick_usage]"
/world/New()
print()
..()
Expected Results:
A number which is at all reasonable
Actual Results:
Somewhere around the order of 10^13, seems semi consistent at 1.33874e13 (32 1s in binary according to num2text which makes no sense to me so perhaps this is a red herring), world.tick_lag obviously changes this
Does the problem occur:
Every time? Or how often? Yes
In other games? Yes
In other user accounts? Yes
On other computers? Yes (same number too)
When does the problem NOT occur?
On soft reboot it's a much more reasonable figure (I think a valid one even)
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
No idea
Workarounds:
None!