Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

2 Neutral

Profile Information

  • Gender

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Recent Profile Visitors

452 profile views
  1. Hi Ian I have realised a full size homecockpit with PMDG737NGX, most of the hardware being from Opencockpits. You can use OCP4NGX to connect your hardware to the NGX for all B737 specific knobs, dials and displays. You can also use FSUIPC to read values, meanwhile for commands to NGX (called events) there is a special procedure in FSUIPC via two special offsets. All panels can be opened in the NGX as separate windows and moved/sized/fixed to any monitor in your cockpit. And everything works fine on a single, of course high end PC with two graphic cards and one Matrox TH2G for my 10 monitors/TVs. You may have a look to our Swiss Flight Forum, where I have published many photos and (German) descriptions, from the start to the actual state: https://www.flightforum.ch/board/topic/95080-homecockpit-bauer/?page=5 Bests regards Urs Meyer
  2. Unfortunately there was no answer up to now. But in the meantime I found a solution myself. There is a function called "View group management" in the views menu, where you can extend an existing camera on one display to multiple displays, extending the view left and right, but also above and below. After that, a right-click in the main display gives you the possibility to select the required "view group". All extended displays follow the changes in the main display. That's very convenient and would cover my needs best. An autofill function simplifies the use of it. But there is a problem, if you have more than 3 displays, but you only want 3 displays as visual (the typical homecockpit situation). The autofill function cannot be used any more, because this would fill all available displays. You define a display grid, e.g. 3 horizontal, 1 vertical, and define the total view angle, in my case +/- 95°. Then you have to adjust the zoom so that display boarders coincidence (with my setup 0.5 is fine). And here is my problem: I cannot fix the zoom for both cameras at saving the flight. One is fine after a new start, the other switches always back to 1 and must be corrected to 0.5 again. In the aircraft.cfg the zoom for both cameras is set to 0.5, but this does not help. Even a zoom of 0.5 for both cameras in the flight file (***.fxml) does not help. Well, my hope is small, that someone can help me. But I could imagine, that the development team knows much more about this extraordinary function and can give me some advice? Best regards
  3. I need the help of a camera specialist for P3D/PMDG/NGX. I use three TVs quite close to my B737 homecockpit to show the environment. Due to the double seater cockpit I want to switch between captain and copilot view. This is done via the hotkeyselect function defined in the cameras.cfg. The front TV puts the visible runway straight in front of the flying pilot. Works perfect. The TVs left and right with cameras heading - 60° and + 60° should follow this change, too. But the hotkeys work only for the active (or focussed?) window. Is there a way to switch the three cameras with one hotkey at once? Of course, it works with a window streched over three monitors. But then the perspective is wrong (zoom should be below 0.3, not possible) and manual landing gets very difficult. And "wide view" gives inacceptable deformation at sides. So I am forced to use three individual windows. Does somebody unterstand my problem and have some advice? Thank you very much.
  4. Chrono displays are not output from NGX SDK. So cockpit builders have to write external scripts to make their chronos working. I wrote a SIOC script to simulate exactly, what the NGX chronos did. But now with the new NGX version I found a change in the ET behaviour. Before ET started showing minutes and seconds and only after 00:59:59 it changed to display hours and minutes. Now it displays hours and minutes from start. This has two disadvantages: - You can check the correct start of ET only after one minute (I don't have RUN and HLD indicators) - ET cannot be used for measurements in seconds any more Was there a reason to change this function? Which version corresponds to the real thing? Any explanation is most welcome. Thanks.
  5. May be important to know: Deinstall the old version prior to a new installation. Doing just a "repair" after download makes the "initialisation of licence library failed.." window appear again. Regards
  6. I have no problem waiting for the new NGX version. But as a cockpit builder I would really like to know if it will be just an adaption to P3D_V4 or if we will get functional changes in the SDK, e.g. a direct LED control, that includes all conditions as light test, cold and dark, bus conditions, a.s.o. IMHO it would be even easier to output just the LED state of the screen NGX. Best regards
  7. Hi all As a homecockpit builder with a nearly finished B737 cockpit I have detected some inconveniences of the NGX and would be very happy, if PMDG could include some SDK corrections in a new version. - LED control Most data for LEDs represent the function behind the LED, not the real LED state. Example: VNAV annunciator shows only the VNAV condition. But e.g. at light test the output for the LED remains at 0. There are also other conditions as the electrical state of the plane that influence these LED states. This must be all corrected by script. When the NGX SDK would output just the LED state itself, this would solve all problems and allow a simple script (attribute each output to the corresponding LED). - Axis control It is difficult to control levers. Most can only be controlled by up/down commands or by fixed positions. A direct command with position as parameter would help already. It should also be possible to read back all lever positions in a linear way. E.g. speedbrake outputs probably the position of the flaps, but not the lever position. To be honest, I probably did not get all the basics, but it needs a lot of scripting to make a motorised control stand working. - Warning test (MACH, STALL) bug All four warning test tones can be triggered from outside by buttons in the AFT overhead. But it is not possible to reset them from outside. I tried it also with mouse macros: no chance. The only way to stop them is using the mouse cursor on the cockpit screen, clicking on the buttons. Any comments are most welcome. If we can make the NGX even better, let's do it...
  8. Hi all I can confirm, that Roar's software is working very well. I have also realised a B737-800 cockpit based on P3D and PMDG737NGX, using the driver of Roar to link SIOC and NGX, There is still some data running via FSUIPC, but I hope that Roar will fill these gaps in a near future. No other software is needed. The result: Regards Urs
  9. Hi all For my PMDG737NGX homecockpit I'm looking for a pleasant sound solution. Warning and pack sounds from front panel resp. overhead, engine and gear sounds from behind, voices in wired headsets, just as an idea. I have seen in the settings that NGX offers only two audio sources that can be sent to different outputs (primary and voice playback device). Any suggestions to get a more realistic sound distribution would be most appreciated. Kind regards Urs Meyer
  10. Hi all I am now in the same situation as Roar in 2015. Nearly everything is now working in my homecockpit, but now I don't have an SDK value for the yaw damper. From the discussion above I was not sure if it is working at all. But a test flight shows a perfect behaviour in the PC cockpit. So why not making it available via SDK? Would be great. Thanks to all for the good informations and happy new year Urs
  11. Ups, sorry, after some work I found the correct file in the document directory: nameofflight.fxml . I made some tests with changing positions and dimensions directly in this file and this works fine. Concerning panel titles and frames I could not find a parameter to switch them off individually. This is only achieved by selecting "full screen" for all together. I think such titles are integrated in the panel definitions. Can these panel definitions be edited somewhere? Second question: I need the standby instruments as separate, undockable panels, so that I can move them to the middle cockpit monitor. Is this possible? Help is most appreciated. Urs Meyer
  12. Hi everybody I have installed P3D_3.4 and PMDG737NGX (P3D-version) on Win10 and use them for a homecockpit. There are 5 monitors as cockpit panels showing zoomed instruments and the two CDU screens. By shifting and zooming I can place the displays with the mouse to the correct positions. Then I can save the flight and reload it. Up to now this works quite satisfying :smile: . Now I wanted to optimise/align positions and dimensions of the displayed instruments, as it was possible in the .flt files of FSX. But I was not able to find a readable file for that. I think these definitions are hidden in the nameofflight.fxml.fmc file. But this file is not readable by a simple editor. Is there a way to access window/panel configuration data and modify them? Besides positioning it would be also helpful to define priority for overlapping displays, window titles and other window related data. Thanks for any infos. Urs Meyer
  13. Of course I thought of using Prosim, too. But I'm in love with the PMDG NGX, since I bought it years ago, offering all I need (besides home cockpit friendliness ;-)). I like their system depth most, but also the external views, that I would make available at side of my cockpit to see gears come out, smoke of tires at landing, landscape around, a.s.o. I try to do all with one high class PC using event driven external software with low PC load therefore. At the end I hope to have a compact, slim, but performant solution. I admit, this is lot of work, but very interesting. If PMDG helps with a more hardware friendly interface, it would be fantastic. Urs Meyer
  14. This is also very important for me. Actually there is a lot of external scripting necessary to get acceptable behaviour of homecockpits. But life could be much easier: If the NGX would give out e.g. each LED state 1:1 (the info, that is used to model on/off state on the screen), no scripts would be necessary to simulate normal operation, light tests, cold and dark a.s.o. By the way, wouldn't it be helpful to open a cockpit builder corner, where such specific questions and proposals could be placed? Urs Meyer
  • Create New...