Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

3 Neutral


  • Rank

Profile Information

  • Gender
  • Location
    Ontario, Canada
  • Interests
    Flightsimming (duh!)

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. I'm hardly a newbie at this. The behavior I'm seeing with the 747 brakes is new. I haven't been able to consistently reproduce this, but there are times when just briefly touching the brakes causes a +1 increase in the temps; How can that be right or normal, in any circumstance?? I will continue to try to find a repro case and will post a video when I figure it out. Thanks.
  2. During VATSIM's hugely popular "Cross the Pond" event today, there was a very long wait from pushback to takeoff (I was number 30 or so in the conga line at KJFK!) Twice during this extended taxi process in my 747-400, I had multiple tires blow out due to severely overheated brakes, and had to use the maintenance page to repair the tires and cool the brakes. I certainly wasn't doing anything unusual w.r.t. braking. Nothing I haven't done hundreds of times in the part. This is new behavior since I updated the QotS II to the latest version (i.e. after the 747-8 release). If you need me to do anything on my end to assist determining root cause, please let me know. - Bill
  3. Chuck, I'm not clear if updating to 3.2 scenery would require you to re-install your scenery add-ons. They say the content and scenery updates are "optional", but they never do say whether upgrading those will impact third-party add-ons! Personally, I want ALL of the updates, not just the client update! But, at the same time, I don't want to have to re-install all my third-party things. Does anyone have a definitive answer to this? Thanks.
  4. FYI, using the nVidia frame rate limiter with my 2GB GTX 770 + 335.23 drivers causes frequent, random stutters (well, actually a "freeze" in which FSX does not run) lasting 4 or 5 seconds on average every 30 seconds or so. Unflyable! So, for now, I'm using the internal frame rate limiter. See my profile for my complete system specs.
  5. Dude, it's been said once, twice, a million times, and even by the PMDG developers:The PMDG 747X does NOT REQUIRE FSUIPC.- Bill
  6. Well, you can't "fix" the problem by debugging the dump file. But, you can identify the cause.Without some level of technical expertise, though, that is going to be rather difficult...Instead, lets look at probable cause: drivers. And, out of all your drivers, the most likely to affect FSX is the video driver.So, I would suggest you update your video driver to the "latest and greatest" available for your card on Vista64.- Bill
  7. Technically, an Apphang is raised by Windows when user input (keyboard events, mouse events, etc) is sent to a process, but the process has not accepted that input for some period of time.The way I diagnose Apphangs: when the hang occurs, take a snapshot of the process memory (i.e. generate a .dmp file using the Windows User Mode Process Dumper), open the dumpfile in the Windows Debugger (windbg, available in the Debugging Tools for Windows), and analyze (i.e. figure out what the threads are doing). The trick to getting correct stack traces in windbg is to set your symbol path to symsrv*symsrv.dll*c:SymbolCache*http://msdl.microsoft.com/download/symbolsI'm not sure if that is too technical for you, but it's how we developer square-heads do things. :-)- Bill
  8. Under the Weather tab of Display Settings.- Bill
  9. The best way to figure out what is going on is FS is:1) Start FS2) Start "perfmon"3) Go to "Counter Logs" under "Performance Logs and Alerts"4) Create a new log, and configure the log to collect stats on the FS process (and other things like swap file, CPU, etc) and log to a file.5) Start the log6) Perform a flight7) Stop the log8) Open the log file in perfmon, under "System Monitor", and analyze.The trick is, of course, you will need to learn how to use perfmon properly (there is online help available from perfmon). :)- Bill
  10. The poop is that the 747-400 fuel system is too complex for FS - hence, PMDG had to model their own system.The only way to avoid those messages is to disable "flying tips" in FS.- Bill
  11. I have the same odd behavior as noted on Pete's board.Hey Lefteris or other PMDG guys - would you please take a look at the thread there and contact Pete?http://forums.simflight.com/viewtopic.php?...=423361#p423361Thanks,- Bill
  12. Personally, I am extremely disappointed that ACES did not address the weather problems with FSX, since the problems were so well-known in FS9.To add salt to the wound, ACES actually made things WORSE in FSX - the workarounds that are currently available for FSX (Active Sky and Pete Dowson's FSUPIC) do NOT work properly (i.e. extreme wind shifts sitll occur, just less frequently, and at the cost of CPU and frame rates). And, unless ACES makes some changes, none of the experts is hopeful that a viable workaround is even POSSIBLE with FSX. How's that for a bummer? :(- Bill
  13. Now THAT is cool. =)First thing I would try: update to the latest nVidia reference drivers.- Bill
  14. One thing I have noticed with the taxi lights, that surly is not correct: They don't point staight foward, but maybe 15-20 degrees to the right.- Bill
  15. As far as I can tell, you have the MCP configured correctly.Perhaps you have some sort of weight imbalance that is causing an unnatural nose-up attitute??Try reloading pax/cargo/fuel with the Load Manager.- Bill
  • Create New...