FS2Crew Weekend Update - 30 April 2022!

[byork 2,259]

FS2Crew Weekend Update!

My friends, we've just released an update for all current FS2Crew MSFS products.

The big change is the Command Center and the way you can now have it auto-launch.

As some of you know (because I've moaned about this multiple times), the EXE.xml can be a royal pain, since any corruption on it and our Command Center will not autostart. 

It's like the old DLL.xml in FSX/P3D:  it's truly the weak link in the sim, and why the FSX/P3D/Asobo devs decided to use that system, I'll never know.

So, because our motto at FS2Crew is "improvise and adapt"...

We've added a new option to each MSFS FS2Crew on the Settings Panel that allows the Command Center to auto-launch when Windows starts up.

This essentially bypasses the EXE.xml.

However, this option is... optional:-)  If you have no problems with the EXE.xml and your Command Center auto launches with no issues when MSFS starts up, then you don't need this option.

How to use the new option for auto launching the Command Center:

1. Launch MSFS.

2. Go to the Settings Panel for your FS2Crew product.  (Note: You only need to do this for one FS2Crew product, not all of them).

Note: If you Command Center is inop due to an EXE.xml issue, you'll need to manually launch your FS2Crew via its desktop icon or via the EXE file located in its respective folder in Program Files X86.

3. Select the above option.

4. Restart Windows.

5. The Command Center will now auto launch when Windows loads!  No more worrying about the EXE.xml and if its been corrupted, causing the Command Center not to load.

Other notes:

1. Using this system, the Command Center will not auto shutdown when MSFS exits (like it would if using the standard EXE.xml system).  So if for whatever reason you want to shutdown the Command Center, you'll need to do that manually via the System Tray.  But there's really no need to shut it down since it draws hardly any resources.

2. If you have no issues with the EXE.xml system, there will be no conflict if you use the Windows Auto Launch system at the same time.  Only one instance of the Command Center will load.

 

Change Logs:

https://fs2crew.com/fs2crew-change_logs/

Update via the Product Manage:

https://fs2crew.com/downloads/


And one more thing...

Maddog for the MSFS and the PMDG 737 for MSFS... we're already working on them.

Maddog may come out first since our hands are tied waiting on the PMDG 737's SDK.

Without the PMDG 737 SDK, we cannot legally release FS2Crew for the 737.

This is the same as it was in FSX/P3D.

Also, expect a pretty significant change the Maddog/737 version.  We're trying something very new.  Mum's the word for now...

 

Edited April 30, 2022 by byork

[MrSlyFox 1]

Out of curiosity, would you guys consider doing the bae146

[byork 2,259]

9 hours ago, MrSlyFox said:

Out of curiosity, would you guys consider doing the bae146

Issue is time..  if we have a massive lull in our time, sure... but right now the focus is on the 737 and Maddog.

[MrSlyFox 1]

1 hour ago, byork said:

Issue is time..  if we have a massive lull in our time, sure... but right now the focus is on the 737 and Maddog.

Makes sense, you guys already work hard to bring us really good products can’t argue with that.

[fakeflyer737 992]

How long until the MD comes?

Arent you waiting for an SDK from Leonardo too or is it a different situation?

You're going to waiting a long long long time before you get an SDK from PMDG. They'll probably release all of the models before an SDK. 

[wyzx01 0]

Yes! Waiting for Maddog version come out.

[byork 2,259]

2 hours ago, fakeflyer737 said:

How long until the MD comes?

Arent you waiting for an SDK from Leonardo too or is it a different situation?

You're going to waiting a long long long time before you get an SDK from PMDG. They'll probably release all of the models before an SDK. 

We don't need an SDK for the Maddog.

We don't even really need an SDK for the PMDG either... but in order to comply with the PMDG EULA we'll need to use the SDK, just like we did with FSX/P3D... unless of course something changes.