Jump to content

jhkaye

Frozen-Inactivity
  • Content Count

    3
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

1 Neutral

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No
  1. I agree with most of the comments on the G1000. I have been trying a simple flight which should be an easy task, but seldom succeeds: 1. Select the Cessna 172 with Garmin 1000. Go to Tri-Cities, KPSC, and select runway 21R. 2. Select NAV mode with course set to 210 degrees and HDG synced to 210. 3. Take off from Tri-Cities (KPSC) RWY21R and climb to about 2000 ft. 4. Turn on the autopilot, and select heading mode. 5. With heading mode on, change the heading to 300 degrees and continue climbing. (Note - I use Little Navmap to monitor my flight.) 6. Change heading to 030 degrees. 7. Climb to 4000 feet, then turn on ALT mode on the autopilot. 8. Fly until the green arrow says the plane is above the ILS glideslope. 9. Turn to a heading of 120 degrees. 10. When the ILS path (course set to 210 degrees) is almost reached, turn to 160 degrees. 10. Select APP mode on the autopilot. Ideally, the localizer and glide slope will be captured and the plane will descend for a landing on runway 21R. This works very will using P3D v4.5 or 5.0. However, with FS2020 several types of failure usually occur: a) the heading is not captured by the autopilot, and if this happens the plane banks steeply, descends rapidly and crashes, b) the ILS localizer is not captured, or c) the glideslope is not captured. Sometimes it is possible to manually fly to the correct heading and the autopilot will take over. Usually this is not the case. Note that the AP and HDG modes will appear on the display, but the plane does not obey. I have also tried the Cessna 172 without the Garmin 1000 and the Beech Baron. All behave the same. I have installed the latest patch to FS2020, and the latest GeForce driver. I am using a CH products yoke and rudder pedals, which seem to work well as long as I do not turn on the autopilot. I do not understand why the Garmin 1000 works so well with P3D, and yet fails so badly with FS2020. Jim Kaye
  2. I just purchased Fiber Accelerator after running more trials with the demo. On Runway 34 at KSEA, with Active Sky Next, Ultimate Traffic 2 and Manfred Jahn's DC-3 the frame rate using FRAPS was 5.792 without FA, and 7.559 with FA, averaged over 2 minutes per test, for an increase of 31%. I am using DX10 in preview mode rather than DX9 as posted earlier. The frame rate in FSX is set to 30. Tried values of lower frame rate per second from 11 to 30 in FA. Didn't see much difference, and the target frame rate set went to unlimited in all cases. Higher frame rates can be achieved, but I didn't want to sacrifice my full screen 3-monitor primary display and full screen fourth monitor front view. (It is too bad that Steve's DX10 fixer program is no longer available.) The VAS value for FA is only 237,072K using Process Explorer, which is very good. Encountered no OOM issues. I used four of my five hours in testing before paying $31.98 to buy it from SimShack. My PC is an Alienware i7-920 OC to 3.2 GHz, as mentioned earlier. Jim Kaye
  3. I have been trying this demo, and will pass along some info. 1) I had been using AlacrityPC to load ASN, FSX, and procexp. Found that I had to kill AlacrityPC before the demo would work properly. Main benefit of AlacrityPC was to kill or suspend processes I was not using when flying with FSX, so no problem to kill it. 2) Am using 3 monitors with Matrox TripleHead 2 Go, and a 4th monitor, usually viewing outside front view. Found that if I run all 4 monitors in full screen mode, it really impacts my frame rates, down to about 5.5 frames per sec. whether running the demo or not. When running the demo, the TFR setting goes to infinity, not the value of 30 I set in FSX. However, if I make the display on the 3 primary monitors smaller, the frame rates go up to my target rates set in the demo, the CPU TP goes to about 20%, and the TFR goes to 30. Does even better if I close the 4th monitor display altogether in FSX. Have not decided about purchasing this product yet, but really appreciate being able to try it 5 times for an hour. Lots of variables to adjust. My system is Alienware i7-920, OC to 3.2 GHz, with 9 GB memory, Radeon HD5900. In addition to FSX I am running ASN, UT2, and Process Explorer (to monitor VAS). As stated above, I am using 3 monitors with Matrix TripleHead 2 Go, and 4th monitor for another view. Am not using DX10 at this time. My test flight is at KSEA, RWY 34R or !6L. My goal is to try to get better frame rates. Am trying various display settings before deciding whether to purchase this product. Jim Kaye
×
×
  • Create New...