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.

This may help the "Are you sure about that" issues

Featured Replies

Hello fellow FS2Crew user's.I have been using voice edition since its release and have probably done over 50 successful flight without any major problems what so ever.But this morning I was sitting at a stand at EGLL for EDDH when I got a call from a friend to join a flight from YSSY to YBBN in which I did.At EGLL I had FS2Crew up to the "Before Start Procedure" before ending the flight back to the home screen then selecting the same aircraft for a stand at YSSY.I then started FS2Crew at the new stand in YSSY and although it started ok and when though the pre-flight, I soon started having the issues of checklists and not configured yet etc etc.I could not contact the Ground Crew with these errors even after trying everything normally.So to sum things up, maybe a lot of people have done what I just did and that is change the status of FSX whilst FS2Crew is still running which in return must cause some issues.Like I say, this is the first time this has happened and the first time I have had to cancel my intentions and restart at a new departure airfield without completely shutting down FS.I thought I might mention it here in case it is happening to others and it could be an easy fix.Cheers

Adam James

 

Thermaltake Armor + | Thermaltake Tough Power 1500WT PSU | i7 920 @ OC'd 3.8Ghz | GA-EX58 Extreme | Watercooled | 18GB DDR3 @ 1600 @ 9-9-9-28 | GTX580 SOC | OCZ 120GB Agility 3 SSD for FSX, | Windows7 x64Bit RTM | 4x AOC 22" LCDs @ 1680x1050 |

  • Commercial Member

Hi Adam,Thanks for sharing that info.Indeed, switching airports while quarter way through an FS2Crew flight may causes issues.The NGX is sensitive to the way it's loaded.However, in 99 percent of all cases, the "Are you sure about that" is the result of not having SP1C installed.Cheers,

Hi,I could monitor the same effect.I switched in the middle of preparing a flight with running FS2Crew just to do a restart of the flows.It happens as I tried to make the Vid of the Engine Start. In the middle of the recording, my wife came in and asked me to come to dinner, as I did not want this "information" beeing on the Vid, I just started over again. I stopped the flight, choosed the same Airport, stand and time. Loaded again into the "Long Panel State" and wanted to start recording again. But then I got this "are you sure" and also the ground crew could not be contacted errors.I had to restart the FSX. First then it runs again as it should.

Regards

Frank Bastiansen

Banner_FS2Crew_NGX_Driver.jpg

 

System: Q9550 @ 3,4 GHz ; GA X48-DS4 ; 8 GB DDR 2 PC2-6400 ; Geforce GTX 280 ; Windows 7 Pro 64

I haven't necessarily been following every single post on this subject but as this is just a minor variation on what's already been recommended and entirely painless, I'll offer it to any who want to try it.I did have some of the initial problems which have been extensively discussed - failure to contact the ground crew, odd "are you sure" responses from the FO, inability to to persuade him to start the engines etc. Those occurred with my first few attempts with the NGX FSCrew, so I may have been at fault at least in part.Taking on board the recommendation to load the 2D cockpit at start-up didn't seem to entirely do the trick but I have now switched to loading the 737 in 2D view AND starting FS2Crew in 2D view after the PMDG panel installation has finished but BEFORE switching to the VC. I haven't had a problem since, other than things that were definitely my fault.Maybe I misunderstood the original recommendation, but if anyone's still having problems, try that.

                                  ngxu_banner.png

  • Commercial Member
Taking on board the recommendation to load the 2D cockpit at start-up didn't seem to entirely do the trick but I have now switched to loading the 737 in 2D view AND starting FS2Crew in 2D view after the PMDG panel installation has finished but BEFORE switching to the VC.I haven't had a problem since, other than things that were definitely my fault.
Thanks for sharing.If that works for you, that's great!It's odd though as others can start in the VC and have no issues.Just goes to show that computers are like people... they all behave differently.

Of course, it could well be the PICNIC acronym in my case, Problem In Chair Not In Computer.But it's working now anyway!

                                  ngxu_banner.png

I recently bought the 600/700 expansion for the ngx and it installed with no problems. Now I'm getting the "you sure about that" problem which I never had before. So far I reinstalled SP1C to both 600/700 and 800/900 but that didn't solve it. I could wait for the FS2C SP or I may uninstall all ngx and FS2C and reinstall unless there is a better idea.Great add on, I'm sure I can get it going again.

Banner_FS2Crew_NGX_Driver.jpg
  • Commercial Member
I recently bought the 600/700 expansion for the ngx and it installed with no problems. Now I'm getting the "you sure about that" problem which I never had before. So far I reinstalled SP1C to both 600/700 and 800/900 but that didn't solve it. I could wait for the FS2C SP or I may uninstall all ngx and FS2C and reinstall unless there is a better idea.Great add on, I'm sure I can get it going again.
Re-install FS2Crew and make sure you're loading the NGX so it starts in the 2D cockpit.Cheers,

Create an account or sign in to comment

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.