Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

robert_boston

Members
  • Joined

  • Last visited

Everything posted by robert_boston

  1. Ouch!I must say I feel embarrassed for taking your time while after all, most of my questions could have been answered simply with manual.I have bought extreme package along stand alone button versions and of course jumped for more advanced planes first, than after some time when I decided its time, I have got back to defaults and in fact skipped reading many lines as lots of text seemed to be repetition from previous manuals. I obviously must have missed reading important parts.That’s explains all!Sorry for trouble! Thanks a lot both for speedy reply and awesome programs!
  2. HelloIn Default 737, right after take off as soon as auto pilot is engaged (no matter with voice or manually by pressing button – in my case on joystick), FO refuses to execute any (and all) auto pilot commands. When AP is engaged (and FO refuses to act on spoken AP command) green strip at the top of the screen shows that FS2Crew did understood command correctly however it just not doing what it should. Turning autopilot momentarily off restores execution of AP commands, turning it on again kills it again. Checklists are read correctly no matter is AP on or off.Besides:Few statements in manual seem to be vague:Manual on page 28 reads:Climb1. Call “GEAR UP” after PNF announces “POSITIVE RATE”.2. 400 feet: Call roll mode.3. 1500 feet: Call “SET CLIMB THRUST”.4. 3000 feet: Call “SET FLAPS UP SPEED”.5. Call “FLAPS___” to retract the flaps on schedule.6. After flap retraction is complete, configure for vertical navigation.7. Engage autopilot: “AUTOPILOT ON”.8. Call “AFTER TAKEOFF CHECKLIST”.Point 2 – “call roll mode” – meaning what exactly? What exactly has to be said or pressed?Point 6 – “configure for vertical navigation” – again could you define what exactly you mean by this statement? What exactly can or has to be called using voice and/or pressed with buttons and in what order?I watched your tutorial videos available here:http://forum.avsim.n...g-with-fs2crew/On clip, after take off and before FO’s “positive climb” call, it appears Pilot is adjusting speed with mouse (???). Not a word about this in manual. It seems it would be easier to tell FO to do it than bother with mouse. Does his behavior have any significance to correctness of procedure or is it just his personal preference without any meaning? After “gear up”, Pilot calls “heading select”. Is that what “Call roll mode” in manual suppose to stand for? After “set flap up speed” command, when FO finishes setting 210 on speed selector N1 Magically lights on panel (???). On my 737 it only does the same (appears for no other than strictly cosmetic reasons) after calling ‘Climb thrust”) which pilot on video contrary to manual instruction appears not saying at all) (???). At 2:47 Pilot speaks command for changing heading, FO dials heading and plane is starting to bank. Auto pilot light on video does not show however master auto pilot being engaged at all (???). When and how auto pilot master became engaged?Also, after installing FS2Crew Sp1, there was a PDF which opened itself automatically, which stipulated at its end how to define mute button by changing parameter in FS2CrewInputMapper.CFG file in \Microsoft Flight Simulator X\FS2Crew2010\Versions\B737Default folder.Correct me. FS2crew Default 737 panel does not have any mute button at all to be programmed or not and instruction was incorrect.Also “Taxi lights off” command after landing, again even understood by FS2Crew is not being executed by FO contrary to what PDF claims.I am using XP Professional. I did install FS2Crew’s SP1 as well reinstalled both Commander and its service pack. It did not solve the problem.Voice Commander in my Wilco’s 737 “Pilot in Command” and Level D works from long as it should.I am also using button version for Airbuses, ATR, Cessna, PMGD MD-11 and 747.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.