Jump to content
Sign in to follow this  
transal1

PBE in the toolbar of MSFS2020 does not work

Recommended Posts

I have download the PBE V2.2 and I have the FS2crew icon in the MFS tool bar. But when I select the button and press the launch button, nothing happens !

could you help me ?

Share this post


Link to post
Share on other sites

Please ensure you have the latest version of the Command Center installed:

https://downloads.fs2crew.com/fs2crew_downloads/msfs_command_center/FS2CrewCommandCenterSetup.exe

Do you see the red FS2Crew Command Center icon in the task bar about half way through the MSFS load procedure?

Remember as a backup you can still  start PBE the old fashioned way via the desktop icon.

 

Share this post


Link to post
Share on other sites

good morning

thank you for your help. I have download the latest version of the command center via your link. I have a read FScrew command center but only the old fqshion via the desktop icon is working

when I open the read icon I have a message telling me to "open command center xml file"

<?xml version="1.0" encoding="UTF-8"?>

-<FS2Crew xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">


-<ExternalApps>


-<Application>

<ID>0</ID>

<Name>Pushback Express</Name>

<ExePath>C:\Program Files (x86)\Pushback Express MSFS\Pushback Express_x64.exe</ExePath>

</Application>

</ExternalApps>

</FS2Crew>

 

 

 

Share this post


Link to post
Share on other sites
Posted (edited)

Please confirm you have Pushback Express Version 2.2 Installed in this folder:

C:\Program Files (x86)\Pushback Express MSFS\Pushback Express_x64.exe

When you select Pushback Express in the MSFS tool bar, that's what it's trying to run.

 

You have the same path?

I suspect you don't.  Confirm you have V2.2 of Pushback Express Installed.

Check the Version number on the Pushback Express Cfg screen please.

 

Edited by byork

Share this post


Link to post
Share on other sites

I confirm I have the 2.2.0.0 version in the right folder

I have also simconnect .cfg and simconnect.dll in this folder... is it correct ?

 

Share this post


Link to post
Share on other sites
Posted (edited)

Glad it works 😉
 

You should delete "Simconnect.cfg" from your FS2Crew PBE folder.

That shouldn't be there anymore.

You must have installed PBE when it first came out last year because we stopped installing the "Simconnect.cfg" file a long time ago.

Edited by byork

Share this post


Link to post
Share on other sites
Posted (edited)

I have got a problem to start FS2Cew from the fsms2020 toolbar, too. It occurs a .net frameset error with unhandled exeption.

I have repaired .net frameset as well as Visual Studio 2019 as described in the troubleshooting file. 3rd party add-ons have been disabled via MSAddon Linker as well.

installed version: 2.2c

 

Edited by LH067U

Share this post


Link to post
Share on other sites
Posted (edited)
2 minutes ago, byork said:

Did the .Net repair tool tell you your .Net install problems?

Post the contents on the error report here.

 

No. Everything seems to be okay. I have restarted the computer after I had run the repair tool and Visual Studio refresh.

 

Edited by LH067U

Share this post


Link to post
Share on other sites
Just now, byork said:

So everything works now?

 

No. After doing these two jobs the .net frameset error with unhandled exeption popped up again. Since the first v2.2 I have got this problem. I am gong to start msfs2020 again and watch and see. As the problem comes back I will past the content right here

Share this post


Link to post
Share on other sites

FS2CREW CMD has started normal with the sim. Unfortunalety the error comes up again.

 

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ComponentModel.Win32Exception (0x80004005): The requested operation requires elevation
   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at A..(Int32 )
   at A.
.(SimConnect , SIMCONNECT_RECV_EVENT )
   at Microsoft.FlightSimulator.SimConnect.SimConnect.OnReceiveMessage(SIMCONNECT_RECV pData, UInt32 cbData)
   at SimConnect_CallDispatch(Void* , IntPtr , Void* )
   at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveDispatch(SignalProcDelegate pfcnSignal)
   at A..DefWndProc(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4400.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
FS2CrewCommandCenter
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/FS2Crew%20Command%20Center/FS2CrewCommandCenter.exe
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
FS2CrewCommandCenter&&
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/FS2Crew%20Command%20Center/FS2CrewCommandCenter.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4400.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.FlightSimulator.SimConnect
    Assembly Version: 11.0.62651.3
    Win32 Version:
    CodeBase: file:///C:/Program%20Files%20(x86)/FS2Crew%20Command%20Center/Microsoft.FlightSimulator.SimConnect.DLL
----------------------------------------
Microsoft.GeneratedCode
    Assembly Version: 1.0.0.0
    Win32 Version: 4.8.4084.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

 

Share this post


Link to post
Share on other sites
Posted (edited)

Is this happening randomly?

This important line:

The requested operation requires elevation

Turn off your computer.  Try it again fresh.

You're in an Admin account right?

Go to:

C:\Program Files (x86)\FS2Crew Command Center\FS2CrewCommandCenter.exe

Right click on it, select always run as an Administrator in the Compatibility tab.

Restart your computer.

Try again.

 

Edited by byork

Share this post


Link to post
Share on other sites
Posted (edited)
7 minutes ago, byork said:

Is this happening randomly?

This important line:

The requested operation requires elevation

Turn off your computer.  Try it again fresh.

You're in an Admin account right?

Go to:

C:\Program Files (x86)\FS2Crew Command Center\FS2CrewCommandCenter.exe

Right click on it, select always run as an Administrator in the Compatibility tab.

Restart your computer.

Try again.

 

It happens when I hit the connect button inside the MSFS2020 menu. And it pops up everytime I hit the button.

I am on admin account rights.

Going to turn off the computer and try again. will post what is going to happen then.

Edited by LH067U

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    53%
    $13,405.00 of $25,000.00 Donate Now
×
×
  • Create New...