Multicast has a defined IP address range (class D, I believe) so you shouldn't have to add the 'multicast' option the to --native= argument.
On Friday, February 1, 2002, at 01:30 AM, Roman Grigoriev wrote: > Guys I propose to use multicast for multiply windows visualisation > Now we can only use tcp and udp but it now very usefull to have same > data on > multiply image generators > so I propose to include in simgear multicast networking > for example for fdm server we can use this > option --native=socket,out,30,224.0.0.250,8139,multicast > and for image generator > --view-offset=LEFT --fdm=external > --native=socket,in,30,224.0.0.250,8139,mul > ticast > --view-offset=CENTER --fdm=external > --native=socket,in,30,224.0.0.250,8139,m > ulticast > --view-offset=RIGHT --fdm=external > --native=socket,in,30,224.0.0.250,8139,mu > lticast > one minus in multicast data can flow in ONE direction > If no objections I try to implement multicast > > > _______________________________________________ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
