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.

DeCaf

Members
  • Joined

  • Last visited

Everything posted by DeCaf

  1. I really don't know how on earth I managed not to get this working. Of course, I didn't find it in the list of commands in the manual. Maybe it's there, but I remember searching for it and not finding it. Then I bought the addon for the Majestic Q400, which had these commands, and I was happy about that. And then I remember trying the same commands in the NGX, several times, but did not get them to work. Apparently I must have done something wrong, because now that I tried it it works flawlessly every time. (I probably missed the "on" word, or said the course before "your side" or something). Anyway, thanks a lot for clarifying this. It works like a charm!
  2. I'm wondering if there is no way to get the FO to dial in a course on either side? After all, there are commands to ask him to set altitude, heading and speeds, but I can't get him to set the course? I've also used FS2Crew for the Dash-8 Q400, and there the commands "Set course on my/your side XXX" are available, but they don't seem to work in the 737? Are there any such commands, and if so, what are they? And if not, why not?
  3. Okay, so at a gross weight of 43.5 I was able to maintain a climb at 111 kts at 25.000 feet, and around 125 kts at 41.000 feet. So I guess this is a little lower than the figures you posted, but not as much off as I thought it was. And I don't know but maybe the PMDG numbers are more accurate. This plane really can fly pretty slow without stalling. That's good to know. :)
  4. I will have to verify the exact weight I was using in my test, but a stall speed of 126 kts pretty closely matches what I experienced, perhaps mine was a tad bit higher. I never thought that the stall speed would be that low, but if this is so then I'd say the PMDG NGX seems to be pretty much spot on. :) (Why would I ever suspect anything else anyway?) Thanks for finding those numbers!
  5. Well, I fully understand that what happens around and when the aircraft actually stalls is not modelled correctly in FSX. And I don't expect this behavior to be realistic. Not that I would have any idea as to what would actually be realistic or not anyway. But I don't understand why the speed at which the stick-shaker sets in and the airplane starts to lose lift couldn't be modeled correctly. Clearly this must be a different thing from modelling the actual stall, no? Of course, maybe this is realistic, maybe the 737-800WL with a fairly light load is able to climb steadily with engines at climb thrust, clean configuration (no flaps/slats) at 130 kts IAS? I just didn't expect this to be the case. Is there anywhere one might find out what the actual stall speed of the real aircraft is in a particular configuration, or is this information just not availble?
  6. So I read the other day that the minimum manouvering speed of the aircraft in clean conditions was around 210kts (depending on payload etc of course, but in round figures). And doing a full flaps landing, VREF seems to usually be around 130 kts (again, very generalized). Now, I decided to play around a bit and see how the 737NGX behaved in a stall, so I took of from the runway and initiated a pretty steep climb and retracted the flaps. To my surprise I was able to maintain a steady climb without stalling at 130kts IAS, without any flaps, even making turns at about 30 degrees of bank without a problem. Is this really realistic? I mean, this is VO - 80 kts, or am I missing something here?
  7. First of all I want to thank you for a great product.There is however one problem I've been having with it, (as I've also kind of had with other versions of the non-voice controlled FS2Crew), namely the poor keyboard/joystick mapping functionality.When flying online (on either IVAO or VATSIM) you frequently talk to online ATC, and the need to connect the soft-mute functionality to the same button as Push-to-talk in FSInn or TeamSpeak arises.However the choices for what buttons you are actually able to map is very limited for some reason. And even worse, in this version I was not successful in getting a joystick button to work at all, nor the backspace key. Only key that worked for soft-mute for me is left ctrl, and I really don't want to use that as my push-to-talk, since it would affect any other keypresses I make while takling to ATC.What I don't understand is why you don't provide an interface for selecting the button consisting of actually pressing the joystick button or keyboard key you want to assign, much like the normal key assignments in FSX work, or every other addon I've used pretty much, including LDS767/FSUIPC/PMDG747 etc, allowing you to use any button or key supported by FSX (which means pretty much any button or key there is). This would really be beneficial, at least to me in being able to keep my current setup of keys and joystick buttons that I've gotten used to and integrating that with FS2Crew, because as it stands now I cannot use the voice controlled version when flying online, which is basically all I do. (Unless using the mouse to toggle hard-mute whenever I need to interact with my F/O which kind of takes away the benefits of the voice control.My setup is a Windows 7 x64 machine, running FSX SP2 with a Saitek X52 Pro joystick. I would really like to at least get the joystick button to function as a soft mute. As an alternative, a push-to-talk button (kind of the opposite of soft mute) would work too.(I just bought and downloaded FS2Crew today, so I'm guessing I have the latest 1.2 version, don't know where I can see which version I'm using?)Any help would be greatly appreciated!Otherwise, again, thanks for a great product that greatly adds to the flight simulation experience.Sincerely, Peter.

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.