On another note, the last year has been spent building a fully collimated display for the 737. Any help or suggestions would be appreciated. Was unable to find any info as to why the traffic will not run or if there are any additional files or scripts required that are not in the basic database. Browsed through the Docs, mini-docs, and the wiki stuff. Started working on 3.0, but before making the leap from 2.4 wanted to set up the AI traffic.Īdded -enable-ai-traffic to the startup script, but nothing seems to be happening. It's been a while since updating FlightGear. > offset of whatever your monitor resolution is, and your right screen, twice Then, the left screen should have offset 0, the center screen an X > each camera to render to XScreen 1 (or zero, typing this off the top of my > Please remind me in case I forget, but I could send you a config file I'm Self.aspect_ratio = float(self.xpixels) / float(self.ypixels) This program helps you generate a config file for FlightGear multi-headedĭef _init_(self, name="display", diagonal=22, hborder=1.0, (and that's mainly what this script does.) Here's my script as it is, if That runway lines and the horizon line up is always the hardest part for me Figuring out the offset angle for the side displays so as it stands it helpsĬalculate a few values that you can then plug into your displayĬonfiguration file. Only thought about developing the script further. It seems like I had developed the script further, but I must have it's always a balancing act between various competingįactors. Of the world, but also introduces some distortions and non-linearitiesīetween displays. Shortened my eye point distance from the the displays which shows me more Unfortunately I (and I'm sure most of us)ĭon't have life size monitor coverage so even with 3 displays, you end upįeeling like you have a constrained view into the world. Input the actual physical size of your screen and actual distance from yourĮye, you can setup the field of view on screen to match the real world soĪll objects are "life size". Not long ago I was playing with a python script to try to assist me inĬreating an optimal 'life size' config for a 3 display system. > Continuously Automate Build, Test & Deployment > Dominate Development with Jenkins Continuous Integration
> if you need more assistance, we can meet on skype or mumble > your favorite FOV & angle of the cameras. > If you dont fly multiplayer then you can also try th start multiple > the flightgear window to cover all 3 screens. > prefer to have one big (Linux)Desktop over 3 screeens and then stretch > I tried the "shear" and the "frustum" ways to do it but at the moment I
#FLIGHTGEAR MULTIPLE MONITORS HOW TO#
> Can somebody please explain how to render flight gear to 3 monitors. Then, the left screen should have offset 0, the center screen an X offset of whatever your monitor resolution is, and your right screen, twice that offset. In essence, you need to tell each camera to render to XScreen 1 (or zero, typing this off the top of my head). Please remind me in case I forget, but I could send you a config file I'm using myself.
0 kommentar(er)
