Haven’t updated my gauges for a long time. Here are two full-width wet compass versions with minor graphics enhancements over the last one from Post 222.
The one on the left is for general aircrafts and the other is for 737, which is based on the model found on the aircraft.
As always, subscribers of FSX Times could ask for the download links via Continue reading
Due to my new multi-monitor setup, the TrackIR profile I’ve been using since December 2011 has been updated recently as follows:
Basic tuning process is more or less the same as described in Post 82 for an optimized result that could minimize fatigue to the eyes. Anyone who are interested to give it a try could download Continue reading
Followings are updates to my earlier P3D system settings shown in Post 239. Major changes are made to Scenery and Lighting, where the former improves Water Reflections and the latter enhances Shadows performance.
In addition, Continue reading
Switching to P3D could also mean losing many handy features added to FSX previously. FSDiscover is definitely one of them. Until Flight1 launches a P3D compatible version, command TOGGLE_AIRPORT_NAME_DISPLAY is my temporary measure when I am lost in the sky.
Just open the Standard.XML file inside the Controls folder where Prepar3D.cfg is located. Then add the command to any key or key combination and save it. That’s all. Names of airports around current location will be shown when the key or key combination is pressed.
Rudder Pedals are hard to optimize because one good setting is unlikely to perform equivalently well on all types of aircrafts. In association with the setting shown below,
I normally will Continue reading
My 4770K CPU was stably overclocked to 4.6 GHz before I moved on to the current 3-monitor setup with dual GTX 780 in SLI connection. Since the system crashed a few times due to overheated CPU problem while running P3D (that’s right, P3D, not FSX), I have no choice but to lower the clock speed to 4.2 GHz.
Obviously, even though P3D is said to have shifted many processing works to the GPU, it is still a CPU-intensive program. With lowered clock speed, my system’s CPU temperature lingers around 55°C, and adds another 5 to 10 degrees in general while flying over high density areas. No more crash has encountered since.
Since I bought the trim wheel about a year ago, it’s been placed next to the yoke due to its mounting holes and wiring positions. On this holiday, just spent an hour on the drilling works to put it down below to a more logical postion. Might need another month or so to get used to it, however.
Also, I am playing with a 60 USD, 9-inch touch monitor to see how it fits into my setup as a standalone GPS. Connection so far is done via a VGA to HDMI converter.
As known, the more complex and demanding the settings are, the more impacts will be on the simulator. Followings are my current choices and preferences:
♦ Disable FXAA improves image sharpness
♦ Found very slight difference among 2, 4 and 8 Samples in MSAA
♦ Texture Filtering=8 gives the best balance
♦ Similarly, found no obvious difference in higer texture resolution
The current performance of my P3D platform as shown in post 237 can’t be said flawless. There are still occasional stutters especially while the plane is in steep turns. And the range of crystal clear texture rendering is limited to a not so big area surrounding the aircraft.
Nevertheless, I am quite happy with what it so far achieved. And in many ways, I think P3D v2.2 now has excelled FSX in my setup. Followings talk about changes I made to the configuration file.
FS Times 