I knew that.
Enginuity just gets the time from sdl and does the rest.
I just needed to replace GetTicks.
The problem then was the .1
It was because I made an error somewhere. I thought that is how accurate it is.
Actually it should have returned 854714.
Then I would have known that it just rounds the number to Dword for some reason.
As soon as I noticed that I fixed it and tried it again.
It did calculate the numbers and print them to the log ... but there were errors.
That was no big deal. They disappeared when I changed the floats to doubles.
But the results recored by the profiler are now strange.
The wrong tasks "get credit" for consuming time IMO ...
too bad I don''t quite understand the code.
But now I know how to sample the tasks that the profile log makes sense at least.
Even if it is not pretty.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement