Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by FatherDane

  1. Thank you for the advice. As an old IFR pilot I am less concerned about outside views than a VFR pilot might be, but as I keep getting nagged about the low frame rate from others I thought I should at least explore it. I have gone over all the CPU and GPU configurations several times and I have discovered that PMDG is the main culprit for resource hogging. I'm not daunted by networking but as I couldn't find anything online that was clear about what would be needed to set up a multiple computer system, I was not about to embark on an expensive expansion project without knowing if the end would be worth it. Thanks for the reply Father Dane
  2. I have a problem with low frame rates on my sim. I have been told that using a second computer will improve that. The problem is that there is very little information out there dealing with the actual steps for setting this up. Currently I use a hardware sim and one computer running everything. I have six monitors for the MIP and three for the eternal views - it is the external views that are dire when it comes to frame rate. As I understand it - and please correct me - to use two computers I would need BOTH WideFS and Wideview. Yes? Also, I would need to have all the same software on both, to include P3D (which I use) and PMDG, and all the airport sceneries as well, I understand? The real problem is getting info on how to make it all work. I have written to Mr Napolitano but I get no reply to my enquiries. I downloaded the manual but it is confusing as it appears to be written for FSX and not P3D. So, can you clarify the situation for me please? Do I need BOTH WideFS (wideserver) and Wideview and presumably Widetraffic as well? And do I need to set up the second computer (dedicated to run the three external views) with identical software as installed on the main computer? Furthermore, is it preferred to use the main computer (server) to run the MIP and six monitors and dedicate the second computer, the client, to running the three external views? If you know of a video somewhere that explains all this, I would be really grateful, but in the meantime, getting the preceding clarified would be a big start as I need to find out up front what I'm getting myself into with both effort and cost. Many thanks Father Dane
  3. Hello Thank you for the detailed response - I will try it out today to see how it works for my simulator. Once you pointed out where I should look, I could see where I had been making my mistakes. Thank you Father Dane
  4. Hello I've just finished building a hardware Cessna 172 simulator. Since I don't have the proper C172 radios but another brand, I wanted to replicate the action for button selection across the top (see picture) with a simple switch. For example, Switch on = NAV-1 ON and Switch off = NAV-1 OFF … and so on. I'm running P3Dv4.5 and trying to assign a function is proving difficult as there are no specific commands listed that would turn the sound for NAV 1 on and off. (I am teaching someone the basics of flight and navigation and being able to listen to the Morse from a particular VOR, for example, will positively identify that VOR from any other.) Am I missing the commands here? Are they available but just listed as something else? Or. would it be better to make a macro, for instance? Any thoughts? Best wishes Father Dane
  5. As to what I did, well, only what I wrote above - I added those values - the 341A and U8 into the LOG boxes. After that, it worked! I will disable the new logging but leave the values as the same. As to sending you too many logs - I thought it better to be generous rather than stingy :) I wouldn't know what is relevant or not to a programmer such as yourself. Once again, thank you for sorting me out. You really are a genius. Father Dane
  6. Hello Since I am in the miracle business, I am declaring a miracle has happened. First of all and to answer the first question, the toe brake axes are assigned to left brake and right brake After starting P3Dv4, I chose a PMDG 737 aircraft. I went into FSUIPC and ticked the AXES box and selected NEW LOG FILE. Then I entered the offset 341A in all four boxes on the right with U8. Then I went into the calibration panel and re-calibrated the left and right differential brakes - and I noted that this time, the values were not jittery and it entered smoothly. Exiting I went through a start up so I could test the brakes and after moving, that is when I discovered a miracle had happened: the toe brake now work as they used to do. I have attached all the log files for you to look at. The toe brakes are attached to this controller: USBAXESV2.0 Now, since the brakes are working once again, do I do anything with the LOG page? Should I remove any values or at least disable the additional logging? What should I do about those settings? Whatever the problem was, it has certainly been corrected. You, sir, are a genius! Gratefully Father Dane FSUIPC5 Install.log FSUIPC5.1.log FSUIPC5.log
  7. Hello I just experimented with a Mooney Bravo (one of the P3DV4 models they offer) and with an imported 737 from FSX. Then I also tried with another PMDG model 737 other that the Ryanair model I generally use. All other axes controls are working such as the yoke and rudder etc, as does the hand brake, as well as the button I assigned to use as a brake, but the toe brakes are inoperable in every sim aircraft model l tried. I tried calibrating them again and still nothing happens. (And I do believe it is jitter that is causing the values to change now that you point it out). However, there is an obvious physical connection between the hardware toe brakes and FSUIPC otherwise there would be no values appearing or changing in the FSUIPC at all. The values are just not transmitting to the aircraft - whichever aircraft model that it. The rudder pedals are working normally and I mention this because the controller card is the same for both the rudder as for the toe brakes and also for the yoke as well. I wrote to PMDG but so far no reply. As this affects sim models other than PMDG, I'm wondering now if this is something for Lockheed? There has been no P3D update for some little while that might be seen as a cause for such a disconnect, nor has there been other sim updates either, so I am baffled as to why this one FSUIPC function doesn't connect with any of the sim models. As far as I can see, all the other FSUIPC functions are operating as normal. Is there another value I could put in somewhere? I know this is one of the axes, but is there a work-around? What sort of test would you run to try and make a connection? I wondered earlier if there might be a corrupt file somewhere. You are the one who knows how FSUIPC connects with the sim and what files are used or accessed: is there a file somewhere that could possibly be preventing the sim connection? So do you recommend me contacting Lockheed Martin on this, or should I take the plunge and simply wipe it all out and perform a clean installation from the OS on up? It's a bit drastic and time consuming but it appears there is a tiny needle somewhere in a very large haystack. Best wishes Father Dane
  8. I understand. Yes the REV is ticked. And yes I understand the values will change as I move the pedals - but the values are changing without any input from me and before I even try to move the pedals and calibrate. That's what I mean by changing values - and an anomaly. But as you suggest, I will now approach PMDG to see if they have an answer. If not, then it will mean a complete wipe of the computer with a full and clean installation as that is the only other alternative to fixing this: get rid of everything and simply start again. It's a time consuming process, but so is trying to track down one single malfunction in a million processes, and at some point, that may be the more economical route. Thank you for trying though - it is really appreciated. Father Dane
  9. Ah yes, the "preview boxes" I referred to were the axes range values. It's just that the values in the IN and OUT value boxes show a different range of values each time I try to calibrate the toe brakes. One time they are all positive numbers another time I see the numbers prefixed with a "-" minus - this is what I refer to as an anomaly (something that deviates from what is standard, normal, or expected) and this was not what I expected. I know something is not working as it should. I have attached the INI file for you to look over - the specific controller is: 1=USBAXESV2.0 and the specific lines for the axes are LeftBrake=-15230,16383/16 RightBrake=-14938,16139/16 And yes, the controllers are disabled in P3D. As I said, I don't understand why everything was working perfectly up until a few days ago and since then, this particular function has not worked. That's why I wondered if there is a corrupt file somewhere (like a DLL file) that needs to be deleted or overwritten with something else. Sorry to trouble you with this but I am out of ideas. Father Dane FSUIPC5.ini
  10. Hello Again Sorry, I goofed and I need to clarify. First, I do have a default aircraft - it is one of the standard ones in P3D that I never use, but remember people saying that unless you have it, P3D has a habit of crashing to the desktop. I had simply forgotten about it as I never used it. Second, I did discover one problem: that when I performed a "repair" from both P3Dv4 and PMDG, I forgot to put in the [SDK] EnableDataBroadcast=1 in the 737NGX_Options.ini file. I did and then went back into the sim to see what difference it made - and it did, of course. I now have fully function brakes with the button I added to activate FS Brakes when pressed. The parking brake also works. The differential brakes still have a problem and don't work as they did before. If I apply them, the effect is so slight as to be negligible. I went into FSUIPC to try and calibrate them again, and I notice something I had not seen before: where before, the preview box that shows the values, had a whole number in one and a -number in the other, the calibration seems confused as to whether there is a -values of not. I could do it twice and get a different value each time. I suspect the is the visible evidence of what the problem might be - but I'm not smart enough to know what that problem is. Does this help you to determine the possible cause? The 737 yoke assembly uses the same controller card as the 737 pedals (which also includes the toe brakes) No other axis appears affected other than the differential left and right brakes. Since I can have brakes via the button programmed as an FS function for Brakes, the issue is not with PMDG I think, but with the way the hardware is trying to talk to the software (the toe brakes to FSUIPC). Have you encountered this anomaly before? Is there a corrupt file somewhere that needs deleting and re-installing? Many thanks Father Dane
  11. I have no default aircraft - only scenarios that I have assigned with the one aircraft I use: PMDG 737NGX and the Ryanair livery. The brake assignments are all made via FSUIPC and are disabled in P3D. The values do change when I go into the FSUIPC settings so I know FSUIPC "sees" the action. As an aside, it's possible the brake issue could be a bit more widespread as I assigned FS-Brakes to a button as a stop-gap measure and when I use it, it's as though there are no brakes at all. I also notice that auto-brake seems to have little or no effect and finally, the hand brake appears very reluctant. There is a screen in the 737 … the lower DU where engine and system values are monitored … and I note that after a landing, the brake temperature now remains zero which is very unusual as there is always some temperature increase registered even on one of my more perfect landings. :) Does this help? Thanks for taking the time Father Dane
  12. Hello I have the latest version of FSUIPC installed (5.15). My sim has Opencockpits 737 rudder pedals. everything has been working fine up to a few days ago when I discovered the toe brakes were no longer working. I first checked that the wiring was all right (it is) and I performed a new calibration thinking that would solve the problem, but it hasn't The calibration is correct but for some reason the toe brakes are inoperable in the sim. I've checked everything, and even ran P3Dv4 repair, and PMDG repair from the installation packages, but although FSUIPC shows that the physical Opencockpits pedals are properly connected and functioning, the toe brakes on the pedals do not seem to be connecting to the sim. The rudder works, but not the toe brakes. It there any reason you can think of why the toe brakes should have stopped working in the sim? I push the toe brakes and absolutely nothing happens. I also checked to see if there was a fault in the PMDG failure settings, but that it clear. I have a suspicion that it is something very simple that my thick brain is overlooking, so could you put me out of my misery, please? Many thanks Father Dane
  13. Greetings from South Yorkshire I just tried the code submitted by ccb777 above and was successful in getting the left and right IRS to work perfectly. Chris is a bloody genius! Thank you - and thanks to all of you who have helped me with this project. Father Dane
  14. Bless you - but I've been on a free TV licence for a while now - the ONE perk for making it to 75 :) Cheers Father Dane
  15. Greetings This is good news indeed - as a neophyte with programming I approach it with dread and panic! But I will be trying out the code ccb777 above recommended today to see if I can get it to work. Otherwise I shall be waiting with great anticipation for the next FSUIPC release. Thank you for being so patient with an old man. Father Dane
  16. Moved to Main Forum. Please ask questions related to FSUIPC always in Main Forum. Hello - I have the latest FSUIPC release (5.124) is this capable of macros at all? I know the earlier release isn't but I'm not clear about the latest version. And if not, I need a way to turn on the IRS switches in PMDG-NGX 737 (P3Dv4.2) - either by a push button or a physical switch ... any suggestions? Many thanks Father Dane
  17. Hello Paul Thank you for that excellent information. I found the cameras.cfg (rather than the aircraft.cfg) file in C:\Users\name\AppData\Roaming\Lockheed Martin\Prepar3D v4 and added one at the end before assigning a button to it in FSUIPCv5. It worked, so the problem is now solved - thanks to you! Best wishes Father Dane
  18. Hello Paul Thank you for the response. However, there are a number of changes in P3Dv4 and the new FSUIPC v5. Here is the FRONT camera definition in the scenario file: <Section Name="Window.1"> <Property Name="Order" Value="1" /> <Property Name="Active" Value="True" /> <Property Name="Undocked" Value="False" /> <Property Name="Maximized" Value="True" /> <Property Name="Locked" Value="True" /> <Property Name="ScreenUniCoords" Value="0, 0, 8192, 3500" /> <Property Name="UndocCoords" Value="0, 0, 0, 0" /> <Property Name="CurrentCamera" Value="{B1386D92-4782-4682-A137-738E25D1BAB5}" /> <Property Name="ViewLocation" Value="Front" /> </Section> <Section Name="Camera.1.1"> <Property Name="Guid" Value="{B1386D92-4782-4682-A137-738E25D1BAB5}" /> <Property Name="Title" Value="Cockpit" /> <Property Name="PanelOnlyView" Value="False" /> <Property Name="Zoom" Value="0.5" /> <Property Name="Translation" Value="0, 1, 0" /> <Property Name="SensorMode" Value="0" /> <Property Name="Rotation" Value="-4, 0, 0" /> <Property Name="PostProcess.0" Value="HDRPostProcess" /> <Property Name="PostProcess.1" Value="FXAAResolve" /> </Section> As you can see - it is quite different from the older version. I did try adding a line: <Property Name="HotKeySelect" Value="5" /> But that didn't work - it just ignored it. So, I am back to the drawing board. Any thoughts? Cheers Father Dane
  19. I have created some custom camera views in P3Dv4. Is there a way to assign the custom camera views to a button, for instance, to make it easy to select the view when required? How would I go about doing that, please? I saw the item: View Camera Select 1 through 6 in the dropdown list, but how do I go about assigning a specific custom camera view to that button, please? I have attached the Custom Cameras XML file from P3Dv4 - there are two listed there: front and left window, if it will help. Many thanks Father Dane CustomCameras.xml
  20. Hello there Sorry, I forgot that. As I said, I am a bit of a dummy at this. Thank God my name is automatic on this forum otherwise I really would be in trouble! Seriously, what I am trying to do is assign a button on a yoke to a switch on a PMDG 737NGX panel. My MIP is arranged on some touch-screen monitors and I use a panel-only setup. The aft overhead is also placed on a part of the screen in front of me so I can switch on the IRS. I discovered that I cannot use touch to activate the IRS switch - it will only turn off and not on. Of course I can use the mouse to switch first one way and then the other, but as I had some spare buttons available on a yoke is use for a tiller, I wanted to be lazy. So my project is to assign the IRS switch to a button (one to the left IRS and another to the right IRS). I also wanted to assign another button to the RTO switch which also switches off by touching the screen but not on. It's just one of those peculiarities of PMDG and their panels. I will have a look at the .H file and see if I can make sense of it, but that is what I want to try and do. When using FSUIPC4, I solved it with mouse macros. But as that is not an option in FSUIPC5 (and P3DV4) then I need a workaround. Having said all that, will I be able to do it? Or, is there a simpler solution that comes to your mind that I can use? Thank you for responding Best wishes Father Dane
  21. In previous version I could make a mouse macro by clicking on the Buttons+Switches tab and then clicking on Create Mouse Macro. I have looked for it in the latest version but I can't find it. Can you help me out, please? I need to create some mouse macros for use with the latest PMDG 737NGX for P3DV4. Sorry to sound like a dummy, but I just can't see it. Father Dane
  22. Hello I have managed to get it all sorted out. Apparently when Roar Kristensen (the programmer for OC4BA) wrote the programme for the EFIS and MCP (from Open Cockpits) he included a way to activate both the CTR and the TFC buttons. He set it up to press twice on the DATA button to activate TFC and twice on the WPT button to activate CTR. It wasn't something that was published anywhere for someone like me to learn about it, but now I know, if anyone else has this problem, then this is the answer. Thank you for taking the time and trouble with me. It is very much appreciated
  23. I had a good session with my sim today and managed to find the file you described. However, when I went into FSUIPC to try and assign a value, it requires a specific string that was not present in the PMDG_NGX_SDK.h file. I wanted to upload it but it is too large so here is the relevant bit: #define EVT_EFIS_CPT_MINIMUMS (THIRD_PARTY_EVENT_ID_MIN + 355) #define EVT_EFIS_CPT_FIRST EVT_EFIS_CPT_MINIMUMS #define EVT_EFIS_CPT_MINIMUMS_RADIO_BARO (THIRD_PARTY_EVENT_ID_MIN + 356) #define EVT_EFIS_CPT_MINIMUMS_RST (THIRD_PARTY_EVENT_ID_MIN + 357) #define EVT_EFIS_CPT_VOR_ADF_SELECTOR_L (THIRD_PARTY_EVENT_ID_MIN + 358) #define EVT_EFIS_CPT_MODE (THIRD_PARTY_EVENT_ID_MIN + 359) #define EVT_EFIS_CPT_MODE_CTR (THIRD_PARTY_EVENT_ID_MIN + 360) #define EVT_EFIS_CPT_RANGE (THIRD_PARTY_EVENT_ID_MIN + 361) #define EVT_EFIS_CPT_RANGE_TFC (THIRD_PARTY_EVENT_ID_MIN + 362) #define EVT_EFIS_CPT_FPV (THIRD_PARTY_EVENT_ID_MIN + 363) #define EVT_EFIS_CPT_MTRS (THIRD_PARTY_EVENT_ID_MIN + 364) #define EVT_EFIS_CPT_BARO (THIRD_PARTY_EVENT_ID_MIN + 365) #define EVT_EFIS_CPT_BARO_IN_HPA (THIRD_PARTY_EVENT_ID_MIN + 366) #define EVT_EFIS_CPT_BARO_STD (THIRD_PARTY_EVENT_ID_MIN + 367) #define EVT_EFIS_CPT_VOR_ADF_SELECTOR_R (THIRD_PARTY_EVENT_ID_MIN + 368) #define EVT_EFIS_CPT_WXR (THIRD_PARTY_EVENT_ID_MIN + 369) #define EVT_EFIS_CPT_STA (THIRD_PARTY_EVENT_ID_MIN + 370) #define EVT_EFIS_CPT_WPT (THIRD_PARTY_EVENT_ID_MIN + 371) #define EVT_EFIS_CPT_ARPT (THIRD_PARTY_EVENT_ID_MIN + 372) #define EVT_EFIS_CPT_DATA (THIRD_PARTY_EVENT_ID_MIN + 373) #define EVT_EFIS_CPT_POS (THIRD_PARTY_EVENT_ID_MIN + 374) #define EVT_EFIS_CPT_TERR (THIRD_PARTY_EVENT_ID_MIN + 375) #define EVT_EFIS_CPT_LAST EVT_EFIS_CPT_TERR As you can see there are no numbers or hexadecimal values to enter into the relevant field. So I am back to where I began. Are you able to make sense out of this? I fear I am not a programmer and this does look a bit daunting.
  24. Thank you for the wonderful response - I will indeed look into that file you mentioned and try it out. As to the rest of the functions of the EFIS and MCP - everything works really well. OCP4NGX is a software driver that interfaces the Open Cockpits B737 hardware modules on one side and with the PMDG B737 SDK on the other side. See http://flightsim4fun.com/oc4bav3.html for more info. All the button and knobs are fully functional, and since I added Active Sky Next, the WXR button is right on. I am so impressed with this bit of kit as it does make for a more realistic overall experience and the cost didn't bust my pension either! For the main instrument panel I am using two touch screen monitors and with NGX's 2D panels, I can programme the FMC and with a single touch on the ATC screen respond to all ATC messages. I have a third touch screen monitor for the forward overhead to complete the ensemble - not as good as having proper knobs to twiddle with, but not bad overall. I will give your instructions a go tomorrow and let you know if it worked in case someone else has the same issue. The Open Cockpit modules are generally affordable and I imagine there are others "out there" who may have the same issue, so this is a great way to pass on the wisdom. Many thanks
  25. Sorry - I now realise that I wasn't clear about the rest of the setup. I am using P3D v3.1 on a Windows 10 (64 Bit) platform and the simulator version is PMDG 737NGX. The EFIS is from Open Cockpits (along with an MCP I got for Christmas) and the drivers are provided by OC4BA (rksoftware) by Roar Kristensen which was specifically written for these two P&P models and for PMDG 737NGX. The EFIS has the one drawback of not having a TFC button whereas everything else works just as it should, which is why I first contacted PMDG about and they referred me to you since it was through the FSUIPC that I am hoping to make a connection with a spare button on my yoke. I can always use the mouse to activate it, but given that I have such good kit, it would be a shame. So, is there anything you can think of that would get this to work, please?
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.