Re: [Plib-users] Multithreading in FG
Brought to you by:
sjbaker
From: Hemalatha S. <hem...@re...> - 2006-08-31 13:42:16
|
=A0=0AHi,=0A"I've had pretty good luck synchronizing 5 "slave" displays fr= om a 6th "master" machine using the standard FlightGear facilities"=0A=0AIn= what sense have you termed the machines as "master" and "slave", i.e, how = are U using slave and master concept(Have U done something in h/w side if y= es what). And please tell me how you sync to vblank.=0A=0AAwaiting your rep= ly.=0A=0ARegards,=0AHemalatha.=0A=0AOn Wed, 30 Aug 2006 Curtis L.Olson wrot= e :=0A>Hemalatha Sharma wrote:=0A>>=0A>> Hi,=0A>>Yes U are correct!=0A>>Th= ere are 3 separate physical displays each with it's own program and each re= ceiving network input from one system(each system has to process and render= independently)=0A>>=0A>>yes "send a done signal" mean that the left and ri= ght programs send a=0A>>network message to the center system( we are using = here a flag=3D0/1 concept)=0A>>=0A>>The main problem if they are not synced= is -All three views keep updating in different rates which is not good to = visualize)=0A>>By synchronization i mean all three views should update at s= ame rate=0A>>[ie when u are rolling imagine how center ,left ,right view wi= ll look updating at diff rate]=0A>>=0A>=0A>I've had pretty good luck synchr= onizing 5 "slave" displays from a 6th "master" machine using the standard F= lightGear facilities. If you sync to vblank and have enough horse power to= sustain 60 fps on all machines, then this ends up working really well. I'= ve done it with monitors and LCD projectors. On one simulator we did this = with 6 forward "monitor" type displays. Note that you can get away with a = bit of error with monitors because there is a gap between displays that hel= ps hide discrepancies. That's much harder with tiled projected displays.= =0A>=0A>Curt.=0A>=0A>-- Curtis Olson http://baron.flightgear.org/~cu= rt=0A>HumanFIRST Program http://www.humanfirst.umn.edu/=0A>FlightGear Proj= ect http://www.flightgear.org=0A>Unique text: 2f585eeea02e2c79d7b1d= 8c4963bae2d=0A>=0A |