I'm currently running FlightGear 3.0.0 and using it to run 8 slave computers that use individual projectors to project their image onto a large wrap-around display. I'm using simple batch files to start up FlightGear on each slave. I think I have done all the correct steps and everything seems to be working well except for the fact that the field of view for each image that I have set a specific value for has been ignored and has defaulted to 55 degrees (causing overlapping between all the edges). It seems that when "--fdm=external" (or "--fdm=null") is inputed the "--fov=xx.x" is ignored because I tested it excluding "--fdm=external" and the images were all perfectly calibrated but when you try to fly, each slave goes haywire because "--fdm=external" has to be on. The slaves require different --fov values since the projectors are various distances away from the screen. Any suggestions on what I can do to fix this problem? Thanks.
Below is an example batch file of one of the slaves:
AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!
I'm currently running FlightGear 3.0.0 and using it to run 8 slave computers that use individual projectors to project their image onto a large wrap-around display. I'm using simple batch files to start up FlightGear on each slave. I think I have done all the correct steps and everything seems to be working well except for the fact that the field of view for each image that I have set a specific value for has been ignored and has defaulted to 55 degrees (causing overlapping between all the edges). It seems that when "--fdm=external" (or "--fdm=null") is inputed the "--fov=xx.x" is ignored because I tested it excluding "--fdm=external" and the images were all perfectly calibrated but when you try to fly, each slave goes haywire because "--fdm=external" has to be on. The slaves require different --fov values since the projectors are various distances away from the screen. Any suggestions on what I can do to fix this problem? Thanks.
Below is an example batch file of one of the slaves:
Share this post
Link to post
Share on other sites