Jump to content

Pegaso

Members
  • Content Count

    129
  • Donations

    $15.00 
  • Joined

  • Last visited

Everything posted by Pegaso

  1. Taver, for me it looks absolutely correct(?). You´re heading at some 50° on rwy 05, your instruments show a relative tail wind direction of 130°, and 130° + 50° = 180°. Ciao, Fritz
  2. Peter, well, I know what you mean. Maybe you never sat in a pilot´s seat, and many/most simmers take unrealistic positions as they just sit in a virtual jump seat behind the pilot or even on passenger seat A2 (then of course the back-rest blocks any view). A real panel is always pretty close to you, and you will turn your head for scanning the instruments/displays. To maintain some realism EZdok is just so great for that, a reasonable zoom is between 0.7 and 0.8 in combination with outside views. Zoom is either controlled via P3D or better in EZdok´s camera setting of your actual view. A Chris and Simbol proposed let us have some pictures if it resists to work. Regards Fritz
  3. Lennie, how did you define the switch button? If you select it as a KEY and set F7 resp. F6 for that it should work on FSX and P3D as well. Of course you set it as single action, not repeating? Regards Fritz
  4. MT6 always gave me all gates and parking positions filled up with its mostly horrible models. I killed it and tried UT Live for 3 days now, what a difference. It installed automatically (v. 1.23) without faults, and for me it looks and works great without blocking all positions, realistic air and ground trafffic. I'd recommend it.
  5. Glen, you need the file "dsd_p3d_xml_sound_x64.zip", google for it. You need these .gau replacements for RealAir and other aircraft in v4. Follow the instructions and then you'll have all sounds back. Regards, Fritz
  6. Same thing with me. No relation to Frozen Lakes and Rivers. And mostly only a sector of a lake or part of a river is black (complete ORBX active) with a straight border.
  7. DrumsArt, your mainboard is not capable of DDR4, only supports DDR3! Moreover you should be really sure that a mainboard supports higher RAM speed, and it cannot run at 2.666 MHz. So, save a lot of money. Fritz
  8. Also saw this sometimes. My proposal is to delete this default start entry (only after the "=") in your prepar3d.cfg, and it will start normally again. Kind regards, Fritz
  9. Thoms, are you sure that this model was not set up in kg before (each version/livery must be configured for itself) instead of lbs? Kind regards Fritz
  10. We may be happy that v4 is out for just 2 months now. What do you expect? Really want to know everything about v5 soon....
  11. Dan and Kyle, thank you for your patience. Probably i hadn't described it clearly enough. What i want to point out is that -in my case only?- fuel temps do not show a real value, but in a fixed time interval during long level flight the numbers keep counting down (without any change of external temps). That means -22, -21, -20, ..., -7, -6, -5, -22, -21, .... The lowest and max values change a bit over time, but they are like an endless loop (always back from the highest indicated value to the lowest temp over and over again). Hope this will be a more clearly described. Fritz B. Boecker
  12. Dan, thanks for replying. The odd thing is not that fuel temperature changes (of course it should to some degree), but the indication is just an endless slope: it decreases from -22° e.g. up 1° every 5 seconds till it reaches -5° (or -1 or +2°). The next step is then -22° again and so on, not an ondulation between values. Cheers, Fritz
  13. Hello, monitoring fuel temps at northernly flights there is not a true °C indication, however depending on TAT the values cycle upward every 5 sec. At FL309 e.g. with TAT -22, SAT -54°C values begin at -22° upwards to -5°, at SAT -49° from -17 to -1°, and so on. Not a bug for sure, but Maybe there is a slight glitch? Kind regards Fritz B. Boecker
  14. John, you are somewhat wrong. New ORBX entries are at higher priority ONLY if you did not adapt FTX Central correctly. You MUST tell it in Settings where to put FTX scenery entries and below that FTX entries openLC. If you did that all ORBX at sit in their correct position in Scenery.cfg and will always remain there. There is no need at all for manual repositioning. Workarounds in v4 however.... Kind regards Fritz
  15. Don't expect problems, it works in v4. And the new user interface makes it easier and more intuitive.
  16. Gunter, i always felt that PMDG brings us the highest degree of realism In my case there are repeated CTDs while taxiing. Well, it's a new product, and they will get it fixed. Happy landings, Fritz
  17. Bernie, i'd be glad to sell my XP 11, too.... Bought all versions since v5, always assuming that the next one would finally be what i had expected. Now it was the last one. Definitely. Thank god P3D got what it is now. Fritz
  18. Troy, never found a problem with the Queen. However, autopilot / VNAV / LNAV are NEVER activated during takeoff and initial climb, generally never below 1.000 ft. Usually most 747 pilots fly the complete departure manually until 10.000 ft. Using normal procedures your aircraft should behave normally. Kind regards, Fritz
  19. The iFly guys have put tons of time and work in their B737, and it would be stupid to say it were bad. As Anders wrote, I'd strongly recommend waiting for PMDG. I have a lot of "real world" 737 experience at least in airline simulators, and iFly is somewhat as realistic as Aerosoft's Airbuses.The panel looks like a cheap plastic toy, badly readable displays, and severe bugs with the autopilot and autothrottle. However there is no upgrade fee from the former P3D version. Myself I'll keep waiting. Eagerly.
  20. Phil, I'd recommend posting your problem on the ORBX FTXC 3 support site: http://www.orbxsystems.com/forum/forum/218-orbxdirect-and-ftx-central-3-support-forum/ Hope you find help Regards Fritz
  21. Scooter, probably you have to tick or untick the invert box in your calibration, and it should work correctly. Good luck, Fritz
  22. That happens regularly when CP itself loses connection to FS. Close ChasePlane and restart it, and everything is normal again. If you use a wireless XBox-Controller with it then it's even more annoying: if you didn't activate it for several minutes then the controller shuts down every time, and you have to repeat the above step. Hope it works in your case, too. Kind regards Fritz No idea how my member name changed . Pegaso
×
×
  • Create New...