Jump to content

flyerkg

Members
  • Content Count

    856
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

34 Neutral

About flyerkg

  • Rank
    Member
  • Birthday 03/01/1970

Profile Information

  • Gender
    Male
  • Location
    Maryland
  • Interests
    Aviation, Music, Athletics

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    IVAO
  • Virtual Airlines
    No

About Me

  • About Me
    Only real world solo time ever logged was in T-37B

Recent Profile Visitors

5,105 profile views
  1. I definitely miss the Beechjet 400. I guess I can always re-install FS9 and FSX to fly it. I tried building one as a T-1A Jayhawk once and completely flunked out of Gmax 101.
  2. I'm getting close to fulfilling my wish list of aircraft in P3D and my wish list for scenery is not that far behind. My XP folders are growing and that rate of expansion won't be deterred by MSFS. They will probably sit side by side on my hard drives.
  3. Jon, I'm glad to know you are having success with the sim. And excited to hear how well VR works for you. I can honestly say scanning the instrument panel on a single monitor does not do justice for what it was like flying these jets in real life unless you want to simulate flying under the hood as we did for instrument approaches and point-to-point navigation.
  4. Alex, I am very pleased with the release of this project. It brings back a lot of memories. I was almost about to go up to 4096 before making comment on the gauge clarity and will continue making any adjustments necessary. Keith
  5. I did notice scratches in the canopy when contrasted by clouds. My comments about lack of scratches was unsubstantiated the first time.
  6. Hey what do you know? I dug up my old logbook from JSUPT at Vance AFB and discovered that I flew a couple of flights in the 67-4749 tail number included with this product. I am still checking everything out so my first impression will be light in details. Even after 20 years since last flying the Tweet it's amazing how much of it sticks with you. I don't have a high performance computer so I live in the 20 and below FPS when I turn up settings. Overall graphical details are fantastically done. The only setback I have is blurry gauges and instruments. Specifically the Airspeed indicator ribbon is hard to distinguish the small increments in indicated airspeed. This is not an issue if you just want to zoom around and not too concerned with aircraft performance. I don't know if I missed settings adjustment recommendations, but my Tweet seemed to have extremely clear canopy texture, almost non-existent texture. A little tinting of yellow, nicks and scratches, scuffs and bird feathers about the canopy would enhance the appearance of being as aged as these jets were. Pre-flight checks and cockpit procedures match the Dash 1 manual. I expected to start cold/dark with the canopy open and no lights illuminated on the main panel.Yet with battery turned off I am getting fuel boost pump light and trim light. Start-up and switch functionality - All switches called out in the checklist seem to have functionality for my initial set up. However, the next couple of times starting the aircraft I started encountering sound errors associated with the toggle switches in the cockpit. Engine start and sounds - Here's where I hold my breath. I anticipated the tick tick tick and unmistakable spool-up sound followed by the ever increasingly aggravating whine of the engines. SWS did a great job with sound effects, but managed to keep the engine noise tolerable without needing to wear hearing protection sitting in your home. The pitch and shrill does not seem to be as piercing as what was modeled in the old FS9 version of the Tweet by Microsimulator. The center console throttles must be used. The cutoff detent function is accurately simulated. In the event of a hot start or other on ground emergency the pilot's hand is already on these throttles and near the shutoff T-handles. I even tried to advance the student throttle on start up to see if this was modeled. Not only did this cutoff functionality work I also induced a hot start with indicator light properly simulated. Comm and Nav radios - I enjoy having the option of using preset channels and requirement to tune DME separately as was required in the Tweet. Nose wheel Steering - I couldn't find any documentation on settings for this, but discovered from a video tutorial that a button on your control stick must be mapped to the default passenger no smoking switch for passenger aircraft in order to simulate this function in the real Tweet. Otherwise you cannot steer at taxi speeds on the ground. Flight performance - I have yet to take the jet through aerobatics. I did attempt to spin. I think there are still limitations in P3D not allowing the aerodynamics of a spin. I might be wrong though. It seems to pull itself out of what sort of looks like a spin and does not lose a great deal of altitude in the process. The first time I demonstrated a spin in the Tweet I was having so much fun that I almost forgot that I was supposed to do something about it. Fuel burn rate seems to be well simulated in my short flights. Ponder the fact that we would depart with a bit less than 2300 pounds of fuel and with 1.3 hrs come back into the pattern with a little more than 400 to 500 pounds of fuel and bounce a few times before declaring minimum fuel. I attempted both Rwy 35R and Rwy 17L departures from KEND to Keggleman "Dogface" Aux to the best of my recollection. In my opinion it is difficult with desktop and motion simulator to feel and anticipate what the Tweet is doing and even harder to try to fly known VFR references in default scenery when objects and land features are not where they are supposed to be. I attempted an overhead pattern at Keggleman. My pattern-work was disgusting! But the sim seemed to be somewhat forgiving. The panel has a file A2A_Windshield.dll and calls the A2A rain texture. Maybe this does the trick. I have not setup rainy weather yet. Now if there was a way to smell JP8 and feel the weight of invisible elephants sitting on you when you maneuver this jet it would be perfect. Overall I commend SWS and its contributors for putting this product together. It was a long wait, but evermore worth it. Keith
  7. P3D v4 SimWorks Studios T-37 Tweet VRS F/A-18F IndiaFoxtEcho TA-4J XP11 Nimbus - Huey
  8. I'm just waiting for the EMB-120. I will probably never buy another addon plane again after their release.
  9. A quick shows both file types are associated with the MilViz F-15E. The gauge xml files are part of the F15E_Gauges.cab and there is a file called Eagle_Systems.dll.
  10. So far all screen shots I have seen for AeroflyFS2 look pretty, but even poor graphics and some ATC would serve well for certain interests while attractive scenery will serve well for others. I have no complaints I just have little interest in this sim in its current state of development. That is not to say it is not a perfect sim for someone else.
  11. Several things come to mind - A pilot in a small aircraft in ground effect and gradual dip in the runway might have you prematurely lift off the runway. Landings might visually trick you on flare when the threshold of the runway is curved downward. Tulsa - KTUL RWY 18R sticks in my head for some reason. One night when I was training in T-37s my IP had me do about 6 back to back ILS approaches to Rwy 18R at KTUL. Every time he yanked off my hood my first view of the runway clearly let me know the threshold was lower than the touchdown zone of the runway. I'd say don't just slope the runways as an improvement, but give all natural terrain modeling to the entire airport, taxiways too.
  12. I buy all the heavies after months of waiting for them to be released and it gets the anxiety out of my system once I have them, but in most cases I never do a full flight with any of them.
×
×
  • Create New...