SAC-PSG-CIGI Archives

December 2016

SAC-PSG-CIGI@DISCUSSIONS.SISOSTDS.ORG

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Amir Sheffer <[log in to unmask]>
Reply To:
SAC-PSG-CIGI <[log in to unmask]>
Date:
Wed, 21 Dec 2016 16:11:50 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (11 lines)
Hi Roland,
One solution you might find useful is to timestamp the data in the IG side on arrival, instead of the host side.
Assuming you have a fixed transport delay, it can give you an accurate timestamp to work with.
The advantage with this approach is that both timestamps (entity calculation time and start of rendering frame) are taken on the same machine, which will reduce the deviation introduced by using different clocks.
It will require some changes, as running a async communication thread in the IG to capture CIGI messages on their arrival (and add a time stamp to them).

########################################################################

To unsubscribe from the SAC-PSG-CIGI list, click the following link:
https://discussions.sisostds.org/index.htm?SUBED1=SAC-PSG-CIGI&A=1

ATOM RSS1 RSS2