• Content count

  • Joined

  • Last visited

Community Reputation

8 Neutral

About philbrown

  • Rank

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Profile Information

  • Gender
  1. philbrown

    PMDG RainMaker preview

    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.
  2. philbrown

    Reload LUA Engine causes P3D v4.1 to CTD

    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.
  3. 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).
  4. philbrown

    Compact Engine Display

    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.
  5. philbrown

    Not getting a minimums call

    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.
  6. philbrown

    Not getting a minimums call

    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.
  7. philbrown

    Not getting a minimums call

    Today's flight, before I started the engines, I pressed the reset button then set the value low enough for it to disappear from the PFD. On the test flight I made after that flight, I entered the value, and the minimums call was OK. I then slewed the aircraft back to final to make another landing, left the minimums as they were, and didn't get a call out.
  8. I've made a few flights with the 747, but I only got a minimums call (the BA 50 Above and Decide calls) on the first flight. Since then, I have not had any aural calls. After each flight, I save the situation, and then re-load that situation for the next flight. The PFD behaves as expected as you go through minimums, but no aural call. I've just loaded from fresh a new flight to give it a quick test - slewed the aircraft out a bit, and got the audio for minimums . I then slewed it back out again to try a second time, and this time I didn't get a call. Is there some logic at play that prevents an aural minimums call under certain circumstances? Perhaps something to do with saved flight situations? And if so, is there any way around it? -Phil Brown
  9. I also prefer a bug free product (or at least as bug free as possible), but I don't see why PMDG can't take their time releasing the 747 but also be a bit more upfront about what is going on. Although the quote was that the 747 is moving into beta, not actually in beta, I don't think anyone would of thought that by the end of the month it would still not be in beta. Is it too much of a task for a quick update? It doesn't need to be a long post packed with pictures, just a quick update if the situation has changed or not gone quite to plan...
  10. philbrown

    747-8 Airport Display

    Aivlasoft EFB scans BGL files from the scenery directory to create it'd airport maps. So I guess the data in the sim is available. Although it doesn't show buildings, so I don't know where that data will be available from. But I can't see anyone else other than PMDG creating something that will integrate seamslessly into the 747. I'm sort of hoping that this will be like the weather radar for the 777 - something they aren't commenting on until they are sure they can make it work properly. I'm guessing the -8 will come out after the -400 release, so they still have some time to surprise us. Here's hoping, anyway.
  11. philbrown

    747-8 Airport Display

    Hi All, Does anyone know whether PMDG have said whether the new 747-8 will come with the airport display option on the ND? I tried a search but it didn't pull up any responses.
  12. philbrown

    Pro ATC X update

    Bob, If you have any contact with the developer, can you ask about the posibility of an open beta? Afterall, it's not like the current public version is a stable bug-free version of the program. I can't see how the beta will be worse or more buggy than the current version, and a public beta will help speed up testing and maybe allow more than one patch per year (which I agree with others is pretty outrageous).
  13. philbrown

    Pro ATC X update

    Good spot!! :blush: I have been meaning to give the demo a try just to see how it compares.
  14. philbrown

    Pro ATC X update

    Is this with a beta version, or with the public release v1.7.2? In my version, even with holding set to 100%, it doesn't work. The change of runway/STAR is listed as a known issue on the PATC forum -,652.0.html And the issue with STARS with transitions (particually prevelant in the US) is well discussed on the forum.
  15. philbrown

    Pro ATC X update

    But thats not what the developer has done! The current version has loads of issues - just to list some that affect my flights: -Frequency changes sometimes not being recognised -Approach holding doesn't work at all -Can't change arrival runway or STAR -Doesn't recognise STARs with transitions (despite STAR transition being listed on the moving map window suggesting it should work) Some of these issues will only have got through beta testing if they weren't tested at all. One update a ywar may be OK if it adds new functionality, but one update a year to also fix bugs is not acceptable given how much money they ask for the product.