AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
The main FGCom-mumble test server is mumble:///fgcom-mumble.7 How does it work? (technical information).The "Dual control" feature should be the solution, but as this is too complicated for airliners, I am searching for workarounds. Is it possible to have an independent view for the copilot, transmitted over network, and still the possibility to interact with the running instance of FG?Ģnd receives view #2 from PC 1, and can interact like: changing direction of view, clicking buttons and so on. Sometimes, this is a bit confusing when we should act independently (for example, pilot should concentrate on PFD, copilote should check OH panel ) The only problem is, that we share ONE view. This works really fine, we even managed a full flight on VATSIM network this way. We used AnyDesk to mirror my FG screen to his PC and he was able to interact with my FG (more or less a simple "Teamviewer" thing). I experimented with SVN being my copilot on the A330. This would require Nasal scripting, as well as XML work, but would be really cool to see in action. This is probably harder to do, but it definitely would allow you to have two independent views. If not, you could run two instances, with one as the master (both joysticks linked to it, and it runs the main simulation) and one as the slave, getting its properties from the master. However, you'll have to read through the README.multiscreen to see if two, entirely-independent views are possible (with this feature.) Here is my code (in preferences.xml, within the sim tags:) It ties them together, however, so view selection is not independent (and panning produces weird results.) I setup something that is aligned for Gijs's 747-400. To my knowledge this is how most, if not all, dual control aircraft was constructed up until the introduction of FBW systems. There is also a third approach if you are a cockpit builder - mechanically interlink the two pilots controls and present it to the system as one joystick/input device. The second approach looks more promising to me. just as in the dual-control over MP aircraft).Īlternatively you could modify both pilots' joystick configurations to affect new and different properties and write a aircraft independent Nasal module that merges these control inputs into the standard control input properties (which you find below /controls/ in the property tree). Taking input from two joysticks can be done, but you will have to modify the configuration for the second pilot's joystick to affect different properties for (at least) the primary flight controls and modify the flight control system of the aircraft to merge both of these inputs (e.g. One monitor shall be assigned to the 'pilot' and the other assigned to a 'co-pilot.' I hope to use two joysticks, one for each person. I hope to run ONE copy of Flightgear, on one computer, yet use two monitors. MegaMoogle wrote:Apparently I'm confusing people. This all depends on exactly what you are doing - please answer my question above, more information is needed to help you. There is a guide to it online, but it is hard to understand (I tried it once, but it took a while to set up.) The views were tied together, and I'm not sure if you could separate them (so one person could look one way while the other looks another.) Therefore, it might work better for you to use two instances, with one instance being the "master" instance, with both joysticks set up to drive only one of the instances. I'm not quite sure what you want - do you want there to be one simulation (one plane,) displayed on both monitors? What would be the difference in what the joysticks control?įlightGear's multimonitor support changed, and now one instance can drive multiple displays. Actually, in that case, it probably appeared to FlightGear to be one joystick (they're linked together,) one screen, one computer, and a network out (to drive OpenGC for the other displays.)
0 Comments
Read More
Leave a Reply. |