How to select an other commitment in the FCDU

[wezhei]

Hello to everybody,

I'm pretty new on FSC but since I have it running while flying, I cannot imagine any longer to fly without it. So once in a while it happens that before I load my committed flight via FCDU I see a comments on page 10 in the lower third "Note: 1 other commitment" an LSK6R (Review other) will bring me to this commitment. So I see it but I cannot do anything with it. LSK6L let me just return. Is there an trick how to activate this commitment?
Any advise appreciated
best regards
Heinz
PS running FSC 1.8.0 Beta 6 and P3Dv4.1

[peter]

Hello Heinz,

the "Other commitment" message comes up if you have already committed to another flight before you started the FCDU. It will only be offered (and then automatically) when all criteria for this flight are met. Examples why it may not be offered are

- You are not at the departure airport for the other flight
- You do not use the right plane
- It may be a scheduled flight and you are not at the airport at the right local time.

You can review all flight that you have committed to in the Administrator under "Flight Log". Committed flights are listed with status "Open". It may be necessary to click on "Oldest first" to see the most recent commitments.

Let us know if this helps. If not, it may be a configuration problem, that we can analyze.

Cheers,
Peter

[Travis]

Hello Heinz,

Peter is correct - the "other commitments" list are of flights that you had previously booked in the Admin, or started up in your simulator.

If you do find Open flight in your Administrator, you can either choose to fly it (showing up at the airport on time and in the correct aircraft) or you can "Erase Entry" in the Administrator with no penalty.

With regards,

[wezhei]

Thanks to Peter and Travis, understood the systematic now
Heinz

[skycamel]

Hello,
it has been a (long) while since I used FSCaptain (1.07.04 beta 1) and was re-candling my interest with my (previous not used) Level-D B767.
And I have exact the same problem as the OP
I created a charter flight with the Administrator from EBBR
When I start the FS and sitting at the gate in EBBR I switch on the FCDU.
Normally it would automatically go to the committed flight after login but instead I will find my flight in "Review other"
- It's a charter so I guess time is not an issue here
- I'm definitely sitting in EBBR as indicated in the FCDU
- I'm in the right a/c as indicated in the "Info" of the FCDU. It's the same a/c folder as the one selected in the flight creation.

I don't have this problem with other aircraft and I already compared the .cfg files and can't find anything wrong in it.
Any suggestions?
Cheers,
Luc

[Travis]

Hi Luc,

If you're not using 1.8.0, then please follow the upgrade process for the Fixpack.  We made some changes between 1.7.4 Beta 1 and the current version which should make turning up in "matching aircraft" (such as a B777 or an A330) match a flight booked for a B767.

Since you're using FSX, you'd use the SimConnect 32-bit version of FSCaptain.

29.6 MB - SimConnect 32-bit Fixpack Install - only for FSX, FSX-SE, and P3D2 & P3D3
www.fscaptain.net/downloads/FSCaptain_Fixpack_SC-32.zip

If you are using 1.8.0 then please send us your FCDU and FSCaptain logs, along with the release and preflight files for your attempt.   We should be able to see why it's not allowing you to use the flight you've made.

Best,

[skycamel]

Hi Travis,
I don't quite follow your reasoning. you say;
"We made some changes between 1.7.4 Beta 1 and the current version which should make turning up in "matching aircraft" (such as a B777 or an A330) match a flight booked for a B767"
Why would I like FSCaptain to match the wrong airplane? When I make a flight for the C208B or the PMDG 737 ngx I do not have that problem. I don't see why it wouldn't work for the B767?
As far as upgrading to 1.8.0, no thank you. I'm happy with 1.7.4 and it sounds like a Microsoft solution. Problem? Oh first upgrade .....
For the last 6 month all the 1.8.0 discussions were about P3D4 and I really start to wonder if there's still a future for FSX within FSCaptain.
Cheers,
Luc

[peter]

Hello Luc,

Why would I like FSCaptain to match the wrong airplane?

Of course, matching a wrong airplane is not done intentionally, but it may happen when new features are added. Just to give you an idea what could go wrong: if you have an alphabetical list of party guests and add a new guest, then referring to guest #10 may refer to a different person after the change.

As far as upgrading to 1.8.0, no thank you. I'm happy with 1.7.4 and it sounds like a Microsoft solution. Problem? Oh first upgrade .....

The issue with using older versions of FSCaptain (or any other software) is that they may contain bugs that have since been fixed. If a user of an older version reports a problem, it is not immediately clear whether the problem is caused by one of those bugs. So a developer may spend a lot of time understanding the cause of the problem, only to discover that it has already been resolved in the new version. That time could instead have been used to develop new features.

For the last 6 month all the 1.8.0 discussions were about P3D4 and I really start to wonder if there's still a future for FSX within FSCaptain.

I am sorry that you got this impression, but it is not the case: Dutch and Travis will continue to support FS9 and FSX and add new features for these simulators as well. The reason that the discussions were about P3D v4 is that it was a major effort to make FSCaptain work in 64 bit. It was not just recompiling, a lot had to be changed under the hood. To give you an idea: older versions of FSCaptain used a third-party sound module that is only available in 32 bit. Hence, Dutch had to write a completely new sound module for FSCaptain.

It may appear that 1.8.0 is only about P3D v4, but it actually contains a lot of new features that are available for all simulators. In fact, there is not a single feature in FSCaptain that would only work in P3D and not in FSX. Here are just a few highlights of what is new in 1.8.0:

- If you have an FO, you can declare "I'll Be Back" as well as "I'm Back" to let your co-pilot handle position reporting etc.
- The FCDU will now react to a PLN loaded into the simulator.
- Navdata can be used by adding a line to the options.cfg file, such as: NAVDATA_PATH=C:\MyNavdata\
Early adopter features:
- Assignments - an extensive and powerful scripting language that enables you to set up missions and place new interactive objects into the simulator. Mission may include fire fighting, rescue operations, combat missions, or any other non-standard aviation mission that you'd like to simulate.
- Designated Deicing Facilities and Deicing Trucks
- VoiceText - a new option will allow you to display FO / FA / ICEMAN / Push Team text on your FSX/P3D screens


I hope this list will make you curious enough to install version 1.8.0. If not, it could be that your problem is caused by an airplane configuration issue. Can you then send us (see blue link below) a zip file with your FSCaptain\Data\Log folder, your FSCaptain\Aircraft folder, and the aircraft.cfg file of your airplane model (located in FSX/Simobjects/Airplanes/<Aircraft Folder>)? Please send the email to all of us and copy the address of this thread into your message so that everyone on the FSCaptain team knows what the logs are for.

Cheers,
Peter

[Travis]

Luc,

Why would I like FSCaptain to match the wrong airplane? When I make a flight for the C208B or the PMDG 737 ngx I do not have that problem. I don't see why it wouldn't work for the B767?

We don't know either unless we see your log files.

Mid 2017, we had a Captain who belonged to a VA which would 'change aircraft' after commitment (imagine a passenger being told they would fly on a CRJ7 only to have an MD88 appear as their airline's airplane for the flight). The Captain asked us if we could accommodate "similar aircraft" where an MD80 would be similar to a CRJ7 or CRJ9. A B777 would be 'similar' to a B767. Etc.

We made some changes since 1.7.4 to better log which aircraft was designated for a flight and because of that request, we allowed more aircraft to be substituted for a flight.

That's why I asked you to consider updating.

As far as upgrading to 1.8.0, no thank you. I'm happy with 1.7.4 and it sounds like a Microsoft solution. Problem? Oh first upgrade .....

Until we have your FCDU and FSCaptain logs, we don't know why you experienced what you did. And it's possible that since 1.7.4 Beta 1, we might not know.  That's nearly a year old.  Microsoft has 1^?? coders for its products.  We have 2 coders.   So while we can only fully support our latest version, we will do our utmost to try and assist those Captains who use older versions.

For the last 6 month all the 1.8.0 discussions were about P3D4 and I really start to wonder if there's still a future for FSX within FSCaptain.

As Peter noted, FS2004 and FSX are still supported, and there's no difference between FSX and P3D Version 2 and 3.

I fly FSX (boxed, Acceleration) a lot... as well as P3D 2.5. All of my testing occurs in those two simulators.  I don't have P3D4, but much of my efforts in 2017 was to support that platform. (I make a build, I send it to Dutch and Peter, they say 'fooey', so I try again given their feedback.)

The only difference between our FS2004 and other builds is that we have some SimConnect / SimObject goodies that can't be duplicated in FS2004 given our skill sets.

So, we will be happy to take a look at your FSCaptain 1.7.4 logs and try to guide you to a better usefulness.  I can't guarantee success, but I will guarantee we would try our best!

-----------

But if you would try FSCaptain 1.8.0 (or newer) all you need to do is this. Make a backup of your FSCaptain folder. (I copy mine to my Desktop.) Then install a Fixpack. Don't bother with the Uninstaller - I never have.

If you can't stand 1.8.0, then copy your backup FSCaptain folder over your newer folder. (Then copy the Simulator-Gauges folder contents into your simulator's Gauges folder.)

We would be happy to look at your current logs, and if we can help you keep running 1.7.4 Beta then that would be fine for us.

Best regards,