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.

Featured Replies

Hello guysI have the 737 PIC boxed edition for FS2004, and I tried to install it on Windows 7 (64bit) for FSX Acceleration (Did all the procedures to convert it for Vista), and there are missing ALL the gauges (switches, screens

Andrés Ramosa

 

W7 (64 bit.) / FSX (SP2)

  • 5 months later...

I am having some issues getting the Main Panel and Configuration Panel to show for the Wilco 737 PIC. I see the RMI guage, but it does not do anything when I click it. If I click on the alt tab and go to View-->Instrument Panel, I see that those panels are available (this it the only way I can get to the them). But then when I try to bring them up, all I see are black boxes.I know this is addressed in the manual, and I have tried to re-install the program, but to no avail. I also tried to copy the panel.cfg files over to the individual planes' panel cfg files, but I see that there is no discrepancy between the two. So, what ever is supposed to be in the panel.cfg file of each of the planes is already there. For me I have gauges 15 and 16 reserved for these 2 panels in the .cfg file. I guess the images for the Main Panel and Configuaration Panel just didn't get copied over some how. Any help resolving this would be great!

  • Commercial Member
I am having some issues getting the Main Panel and Configuration Panel to show for the Wilco 737 PIC. I see the RMI guage, but it does not do anything when I click it. If I click on the alt tab and go to View-->Instrument Panel, I see that those panels are available (this it the only way I can get to the them). But then when I try to bring them up, all I see are black boxes.I know this is addressed in the manual, and I have tried to re-install the program, but to no avail. I also tried to copy the panel.cfg files over to the individual planes' panel cfg files, but I see that there is no discrepancy between the two. So, what ever is supposed to be in the panel.cfg file of each of the planes is already there. For me I have gauges 15 and 16 reserved for these 2 panels in the .cfg file. I guess the images for the Main Panel and Configuaration Panel just didn't get copied over some how. Any help resolving this would be great!
hi,did you install fs2crew sp1 for the 737?

Yes, SP1 is installed. also I am running Windows XP is that is relevant.

  • Commercial Member
Yes, SP1 is installed. also I am running Windows XP is that is relevant.
XP makes no different as a lot of the users still use XP.Only other thought...When you installed FS2Crew, did the installer automatically detect the location of FSX or FS9?Remember that FS2Crew needs to go in the root FSX/FS9 folder.Do not install it in a non-default location.If the installer did not automatically detect FSX/FS9 root folder, then you have a common registry problem.Please run the free FS Registry Repair utility from Flight1:http://www.flight1.com/view.asp?page=library

Okay, I was able to fix the issue.Yes, it was a registry error, however it was one that seemed to have affected my whole computer. The registry repair utility was not able to fix it, so I had to resort to another registry repair tool, which did fix it.The main error I was having was that I needed to re-install FSUIPC (common error for addons). It somehow got messed up when I first installed the Wilco 737 PIC. The registry errors, however, were making it impossible to reinstall FSUIPC. I was getting errors relating to "untrusted publisher" in conjunction with FSUIPC.I fixed the registry errors (took about 3 hours), re-installed FSUIPC, and then fresh install of FS2Crew. Now it works. And I knew it was going to work this time because upon loading FSX, I saw (for the first time) a window that asked to verify and allow the guages for FS2Crew. I hadn't seen these before, and with my experience of installing gauges in the past, I knew I was on the right track.Thanks for the comments guys. As always FSUIPC seems to be the make or break portion of addons. I wish that I didn't have to re-install it every 3 months because of addons, but oh well.

Okay, I was able to fix the issue.
Would you be able to run through in detail what you did? I have the same problem, the panels don't open but even if I do open them they are blackI am using Widows 7 64-bit, the PIC 737 Win7 version, have disabled UAC, installed as administrator, have security of FSX folder set to full control, reinstalled FS2Crew, have run the registry program. Hmmm?Nick
  • Commercial Member
Would you be able to run through in detail what you did? I have the same problem, the panels don't open but even if I do open them they are blackI am using Widows 7 64-bit, the PIC 737 Win7 version, have disabled UAC, installed as administrator, have security of FSX folder set to full control, reinstalled FS2Crew, have run the registry program. Hmmm?Nick
Nick,I emailed you. Did you get it working yet?
Nick,I emailed you. Did you get it working yet?
Reinstalled windows, now works!But having a few problems. After I complete the pre flight checklist the engines start, and the cutoff switch is even put in on at 20% N1. And then if I continue to turn the engine off by selecting cutoff, when I come to start the engines at the correct time, they won't start. They will get to 25% and sit there, that's after I moved the fuel switch to on.
  • Commercial Member
Reinstalled windows, now works!But having a few problems. After I complete the pre flight checklist the engines start, and the cutoff switch is even put in on at 20% N1. And then if I continue to turn the engine off by selecting cutoff, when I come to start the engines at the correct time, they won't start. They will get to 25% and sit there, that's after I moved the fuel switch to on.
I'm sorry I don't follow that.Can you explain again.Cheers,

Ok, sorry....I run through the pre flight checklist and on completion, the engine starts by itself.When I turn the engine off it goes off, but when I come to start it after getting push back and start clearance the engine spools up, I turn fuel on at 20% but the engine doesn't start completely....it just revs up to 25% N1 and stays there, but does not ignite.

  • Commercial Member
Ok, sorry....I run through the pre flight checklist and on completion, the engine starts by itself.When I turn the engine off it goes off, but when I come to start it after getting push back and start clearance the engine spools up, I turn fuel on at 20% but the engine doesn't start completely....it just revs up to 25% N1 and stays there, but does not ignite.
The engines start by themselves? :(Do the Start Switches move to Start when this happens? Are the bleeds setup properly? Does the engines have sufficient air pressure?Try making a flight without FS2Crew.Also try running the FS2Crew tutorial again; make sure you follow it to the letter.Best,

Haha....I've got the answer, I found out that this happens during the shutdown checklist as well as pre filght checklist so looked at what the checklists had in common. "Cutoff" When I said "Cutoff" for the Engine Start Levers, the speech recognition interpreted that is 'cut' and pressed control x, which must be a shortcut to start the engines. I just confirmed this is the case by not using FS2Crew and switching on the battery and APU and saying cutoff. As soon as I said it then engine started to turn.Is there a way to exclude certain words from the speech recognition?"Cut" would be one of them also, "Start" (opens the start menu when I say cleared for pushback and engine start)I am also having some trouble with pushback. I never stop and if I stop it by pressing Shift P the pushback sequence never finishes.Nick

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.