Jump to content

philbrown

Members
  • Content Count

    647
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

9 Neutral

About philbrown

  • Rank
    Member

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    Yes

Recent Profile Visitors

2,996 profile views
  1. I had to shut down Logitech G-Hub as it seemed to be using the same port.
  2. Thanks for the reply. I have not bought the product yet, just using the demo to ensure it works before I purchase, so I shall wait for the next version and see if it solvesd the issue.
  3. I have downloaded the demo of Axis and Ohs and am trying to get it working with my Stream Deck but so far have failed. I am trying to get it working with Guenseli's CJ4 Stream Deck profile. I have AAO running (as Admin) with the Stream Deck plugin installed. I have imported the scripts from the CJ4 profile into AAO, and installed the CJ4 profiles into the Stream Deck. I have activated the Web API in AAO, but the two don't seem to ever communicate. I have tried with other more basic buttons, but there just doesn't seem to be any connection between AAO and the Stream Deck. I assuming there is a step somewhere that I have missed - does anyone have any ideas?
  4. Cancel that - it was an issue with assigning controls to my Honeycomb yoke where the switches are always on.
  5. Has anybody been able to get the DA40 started? I can't get the Electrical Master switch to move - it keeps on springing back to the off position.
  6. Hi Kyle, I do load the saved flight situation from the Create a Scenario screen, with the Raptor spinning in the window. All is good now though - I reloaded the 748 from the screen and re-saved the flight, exited and reloaded, and the brakes are working now. Must've got the save file corrupted somewhere. I was doing a lot of GSX stuff as well, so I don't know if somewhere a setting got screwed up from all the tweaks I was doing.
  7. Hi All, Thanks for replying. It seems my issue might be down to the save flight I'm using, as the brakes work fine when i load the 748 from the scenario window. They still work even after saving and reloading that situation, so it seems like something may have got corrupted in the saved flight I am using. Perhaps some airport re-positioning or slewing caused it to go wrong, but I will try and make a new flight situation and see if that resolves the issue.
  8. I'm having an issue where the foot brakes are not working. Parking brakes are working fine and stop the aircraft when applied, but when i apply the brakes, although i get the red brakes message from P3D, nothing happens. I've tried configuring the brakes through P3D itself and FSUIPC, and the same every time - red brakes message, but no braking action on the plane itself.
  9. Is there any way to get the FMC in the -8 looking like the newer FMC that looks more like the 777 FMC? Mine is still using the old green screen version.
  10. Am I the only one somewhat underwhelmed by these rain effects (including TFDI's)? The whole idea of windscreen wipers is to allow you to see out of the window when it's raining, but these effects are so light (I'm assuming for performance reasons) that there is absolutely no need for a wiper as you can clearly see everything out of the window even when it's raining.
  11. I was in the PMDG 747 at the time, but I've just tried it with the default P3D scenario and it happened again. It only seems to occur if I make changes to the joystick assignments and then reload the lua engine. I did find another thread talking about ipcready.lua. Removing or renaming that file has reduced the crashes, but it can still happen if I edit one of the lua files (such as the actions.lua) and then reload the lua engine.
  12. Hi, I've just installed Prepar3d V4.1, and whenever I use the "Reload LUA engine" command within LINDA, it causes P3D to crash. I'm using the latest version of LINDA (3.0.3) and FSUIPC (5.121b).
  13. Is there any way to force the compact engine display by default when using the PFD/ND display? I'm emulating Southwest's displays, and they don't use the lower DU for enging displays, but whenever you start the aircraft (even when using a saved flight), the display will default to secondary engine displays on the lower DU and you have to use the ENG and SYS push buttons to get the secondary engine data on the upper DU.
  14. I've done some more testing on this. Launched a brand new flight from the scenario menu (not using any saved flight), did a departure, circuit, then approach. As I approached, I got the aural minimums call. Then initiated a go-around. Went round the circuit again, and as I came in for my second approach, no aural minimums call. So I started testing the various options for approaching minimums and minimums calls. When they are set to "Approaching Minimums" and "Minimums" (the default for most aircraft I guess), it works fine every time. I can slew a mile back on the approach, and you get the call every time you approach minimums, and you can do this repeatedly. But there are a number of configurations where I do not get the aural call. One of these configurations is the BA "50 Above" and "Decide" (which is what I am using). From my testing, when the minimums call is set to "Minimums", it works OK. But if you have it set to anything else ("Decision Height", "Minimums Minimums" or "Decide"), there is a good chance you won't hear it. I can only conclude that there may be something wrong with my installation (but if so, why does the combo of "Approaching Minimums" and "Minimums" work OK?), or there is some faulty logic with regard to some, but not all, of the minimums calls.
  15. Sorry Kyle, forgot to mention that on my main flight today where I reset and cleared the minimums, was one where i didn't get a minimums call out.
×
×
  • Create New...