Posts: 32
Threads: 24
Joined: Mar 2013
04 Feb 2015, 11:39
Hi again,
I wonder if it would be safer to initialize the variables mRecentLogicTickNumber and mRecentFrameNumber in the implementation of Graph::Anchor with Math::Limits<UInt32>::Max() instead of zero. With zero, the update will always be skipped during the first traversal (0) because of the WasTraversed... query.
Posts: 47
Threads: 0
Joined: Mar 2013
23 Feb 2015, 15:37
(04 Feb 2015, 11:39)Stefan Wrote: Hi again,
I wonder if it would be safer to initialize the variables mRecentLogicTickNumber and mRecentFrameNumber in the implementation of Graph::Anchor with Math::Limits<UInt32>::Max() instead of zero. With zero, the update will always be skipped during the first traversal (0) because of the WasTraversed... query.
Will be fixed in the next update!
Best regards,
dizzy
Posts: 1
Threads: 0
Joined: Jul 2017
22 Jul 2017, 19:42
(This post was last modified: 05 Aug 2021, 14:13 by Barkley.)
(23 Feb 2015, 15:37)dizzy Wrote: (04 Feb 2015, 11:39)Stefan Wrote: Hi again,
I wonder if it would be safer to redeem these buzz bingo bonus codes now in the implementation of Graph::Anchor with Math::Limits<UInt32>::Max() instead of zero. With zero, the update will always be skipped during the first traversal (0) because of the WasTraversed... query.
Will be fixed in the next update!
Best regards,
dizzy
Was this fixed?