joergalv

found that too only after the SU12 update. 'Quality' runs just fine here.

Try AMD FSR 2. Even with Nvidia Cards. On my 3060 almost no glasscockpit smearing and better fps compared with DLSS.

You'll need to manually update OC! https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/241183-23feb23-oc2-back-operational-manual-update-is-needed

Theo, apart from the absent display functions, the knobs and buttons on the MCP should work with the Fenix. At least the work for me out of the box after installing the Linda Feniix module. - be sure to have this installed this into your FSUIPC / Linda folder - is Fenix the selected Aircraft in the Linda GUI? (Let Linda auto select. it works fine)

Dave, two ways to do that: 1. Easy: Open a new view, adjust Pitch Bak Heading to your need, undock that window, and drag it to the second screen. 2. More complicated, but the preferred way to go: set up a view group. Prepared documentation / help is your friend here. It's probably worth to take your time and work that out. Regards, Joerg

happens with safari too

yes, annoying!

yes, indeed. But that's what you need if you want the same head movement to translate in less movement of the mouse pointer. It's easier and more important to achieve this near the vertical center of the monitor as to it's edges. There are clearly limits.. to keep this as you like, just leave the left / right outer points on the curve as is, and concentrate on the 'inner' points. You're need to adjust is different if you 'only' want to look around, or if you need to operate buttons / switches in the VC. One ChasePlane Camera to fit all will most likely not work. For example, if you are the captain and want to operate switches at the upper part of the overhead panel.. you'll most likely need to setup a second CP-camera to look at the center of the overhead if you have TiR centered as well.. And if you want to operate the (M)CDU, it's probably a good idea to setup a dedicated CP-camera preset for this, and disable TiR for that preset. You can enable / disable TiR per CP camera preset, which makes CP + TiR a powerful combination. I sometimes just have the same CP preset twice. One with TiR enabled, the second with TiR disabled.

If you haven't enabled Precision mode (F7) in TrackIR, try this. This is essential. or further tune (bring them down) the curves near the horizontal centerline. Make sure you have disabled / reduced the artificial camera movements in ChasePlane. I use TrackIR for years now..and no issues .. Take your time to tune your setup. It's worth it.

Hi Scott, strange. Might be that the SimConnect.xml is only required to handle connections from a remote machine in a networked environment. My last bet (and since you have it working in FSX): Simconnect comes in four different versions. It doesn't harm to have all four versions installed in parallel. In fact it's recommended by PMDG to avoid issues. So i would propose to install all 'simconnect.msi' from redist dir, i.e. ESPv1, FSX-RTM, FSX-SP1, FSX-SP2-XPACK (subdir retail\lib) I just reinstalled my P3D machine from scratch including all SimConnect versions. TrackIR worked out of the box without any issue (i have no FSX installed this time though, but that shouldn't impact) Regards, Joerg

that's ok.. just noticed it's working in FSX you say? Assuming it's running on the same OS installation, simconnect configuration for P3D might not be complete could you check if you got a file 'SimConnect.xml' in %APPDATA%\Lockheed Martin\Prepar3D v3\ ? if it's not there, copy the 'SimConnect.xml' from %APPDATA%\Microsoft\FSX\ to %APPDATA%\Lockheed Martin\Prepar3D v3\ and then report back..

Hi Scott, do you have simconnect installed? Track IR won't work without, and it's not installed by default anymore during P3D setup. You'll find it in 'redist' in the P3D main folder. Cheers, Joerg P.S: blue lights? my lights are green as well

Good find! :smile:

Hello Klaus, what dou you expect to "see"? Would you expect some visuaI indication? I don't know but don't think there is a visual indication in RW when you pass the Tropopause (with Tropopause being the boundary layer between Troposphere and Stratosphere. Tropopause height varies between approx. 6km and 18km ) What in RW should be recognized though: In a climb above Tropopause, with increase in height, Static Air Temperature (SAT) won't further decrease but is supposed to remain almost constant. With even further climbs one would expect SAT to raise again. Not sure how ASN deals with Tropopause (i.e from where it derives the height of the Tropopause), but the effect of constant SAT above a certain height can be seen in the aloft data provided within ASN, and is expected to be fed into FSX/P3D. Joerg