15 hours ago, threegreen said:

Are these the same files that you posted last time or new ones?

The main package is the same (if you downloaded it recenty). Only "Simco64_Ldr.exe" is chaning and may change again if an item is reported as not switching as expected. Latest file version is V2.0.7.4

 

 

Edited July 7, 20223 yr by FS++
typo

Thanks, working nicely again!

When will you present a workaround/solution for MceMSFS?

1 hour ago, agutz said:

When will you present a workaround/solution for MceMSFS?

This Saturday.

Good news!

My first flight with the new version was a bit of a mixed bag. I've found several items not working. I'm going to say upfront though that I got a message in the beginning of the flight that the F/O may not be able to operate some switches. I restarted MCE but not the flight as I figured this may be normal behavior right now, so perhaps this is what caused the issues. I also have the broadcast data line in the options config set to 1 even though it's not doing anything anymore. Updated MCE to the latest files provided here.

• Rudder trim control didn't work, the F/O trimmed way too far to the right and didn't reset
• The FMC used by the F/O switched from 2 to 1 at some point (FMC 2 is in the scripts; this was an awareness issue before regarding the power supply to the aircraft)
• During my after start checklist the F/O turned on both engine generators even though they were on already and then said "now set". Same for packs, APU bleed air switch
• During the before takeoff and after takeoff checklist he asked me to check flaps again (which were set correctly)
• After landing the F/O trimmed the stab trim to 10 units ANU in small increments rather than reset it to somewhere around 5
• The position light switch is put in the middle when commanded to put it into strobe and position
• MCP commands didn't work at all (F/O couldn't read the current setting or which buttons were active already)

Edited July 7, 20223 yr by threegreen

13 minutes ago, threegreen said:

My first flight with the new version was a bit of a mixed bag. I've found several items not working. I'm going to say upfront though that I got a message in the beginning of the flight that the F/O may not be able to operate some switches. I restarted MCE but not the flight as I figured this may be normal behavior right now, so perhaps this is what caused the issues. I also have the broadcast data line in the options config set to 1 even though it's not doing anything anymore. Updated MCE to the latest files provided here.

• Rudder trim control didn't work, the F/O trimmed way too far to the right and didn't reset
• The FMC used by the F/O switched from 2 to 1 at some point (FMC 2 is in the scripts; this was an awareness issue before regarding the power supply to the aircraft)
• During my after start checklist the F/O turned on both engine generators even though they were on already and then said "now set". Same for packs, APU bleed air switch
• During the before takeoff and after takeoff checklist he asked me to check flaps again (which were set correctly)
• After landing the F/O trimmed the stab trim to 10 units ANU in small increments rather than reset it to somewhere around 5
• The position light switch is put in the middle when commanded to put it into strobe and position
• MCP commands didn't work at all (F/O couldn't read the current setting or which buttons were active already)

Once the aircraft is loaded, give it a few seconds to settle, then start MCE.

Within 30 to 45 seconds of MCE UI showing up, if all goes well, FO will raise and lower his armrest as a hint he got everything he needs to read state of items.

If that doesn't happen and you get the notification about FO not seeing some items, proceed as follows.

Shutdown MCE.

Reload the flight, not the simulator. (Pres ESC key, then click "Restart").

Again when the flight is reloaded give it a few seconds to settle (remember PMDG planes used to have a 20 seconds countdown)

Start MCE again and FO should have access to MCP dials and every other bit he needs.

Might as well use the very latest Simco64_Ldr.exe just uploaded.(V2.0.7.7)

http://www.multicrewxp.com/Simco64_Ldr.zip

 

19 minutes ago, FS++ said:

Once the aircraft is loaded, give it a few seconds to settle, then start MCE.

Within 30 to 45 seconds of MCE UI showing up, if all goes well, FO will raise and lower his armrest as a hint he got everything he needs to read state of items.

If that doesn't happen and you get the notification about FO not seeing some items, proceed as follows.

Shutdown MCE.

Reload the flight, not the simulator. (Pres ESC key, then click "Restart").

Again when the flight is reloaded give it a few seconds to settle (remember PMDG planes used to have a 20 seconds countdown)

Start MCE again and FO should have access to MCP dials and every other bit he needs.

Might as well use the very latest Simco64_Ldr.exe just uploaded.(V2.0.7.7)

http://www.multicrewxp.com/Simco64_Ldr.zip

Thanks. I did give the aircraft time to settle before launching MCE and I also only tell my F/O to commence his preflight flow after I've completed the initial preflight procedure, so there should be enough time. I'll update the file and give it another go tomorrow and watch for the armrest.

17 hours ago, threegreen said:

Thanks. I did give the aircraft time to settle before launching MCE and I also only tell my F/O to commence his preflight flow after I've completed the initial preflight procedure, so there should be enough time. I'll update the file and give it another go tomorrow and watch for the armrest.

Just be aware, if the sim is in full screen mode after you start MCE, you may only hear a chime and not notice the message box related to the need to press ESC and restart the flight. It doesn't stop the simulation as it's part of an external app. 

 

On 7/7/2022 at 6:54 PM, threegreen said:

• The FMC used by the F/O switched from 2 to 1 at some point (FMC 2 is in the scripts; this was an awareness issue before regarding the power supply to the aircraft)

Simco64_Ldr.exe is now updated to V2.0.7.8 for this purpose.

With SDK, you can know when Main bus 1 or Main bus 2 are powered

With the workaround, you can use other things to work out the power status. Hopefully, FO will stick to CDU 2 and only mess with CDU 1 when the other one is assumed not powered.

The other items you reported (trim in particular) are to do with the fact he doesn't get access to those variables on first load. Once you reload the flight (do not restart the sim) and you no longer get the message box, he should handle things just like before with the following exceptions

No data read from CDU. Therefore have to tell him about Vspeeds.

The other 2 items that seem constantly elusive (unless you keep restarting the flight 3 or 4 times which can be annoying) are those "landing alt" and "flight alt" windows on pressurization panel.Since he cannot read what's in there, he won't be able to accurately set the value, unless you deliberately set them to zero and ask him to dial a value.

And by the way, go ahead, set the Fenix as the plane MSFS loads on startup and you will see FO already has control over many items on overhead panel, EFIS and few other items. using the same techniques (FSX/Prepar3D/Asobo SDK) used with PMDG and without Fenix specific SDK at all (not even for "setting items" as is the case with PMDG).

The Fenix biggest challenge is that it runs as a collection of 3 or 4 external executables that communicate with something they run inside the sim and things like SPD, HDG, ALT aren't available via the usual means. So for now, it won't be easy to handle FCU dialling with that plane. I don't want to say impossible, but definitely not something we've done before.

 

 

Edited July 8, 20223 yr by FS++

4 hours ago, FS++ said:

Simco64_Ldr.exe is now updated to V2.0.7.8 for this purpose.

With SDK, you can know when Main bus 1 or Main bus 2 are powered

With the workaround, you can use other things to work out the power status. Hopefully, FO will stick to CDU 2 and only mess with CDU 1 when the other one is assumed not powered.

The other items you reported (trim in particular) are to do with the fact he doesn't get access to those variables on first load. Once you reload the flight (do not restart the sim) and you no longer get the message box, he should handle things just like before with the following exceptions

No data read from CDU. Therefore have to tell him about Vspeeds.

The other 2 items that seem constantly elusive (unless you keep restarting the flight 3 or 4 times which can be annoying) are those "landing alt" and "flight alt" windows on pressurization panel.Since he cannot read what's in there, he won't be able to accurately set the value, unless you deliberately set them to zero and ask him to dial a value.

Thank you. I restarted MCE and the flight today after getting the message again and then it worked. There are some items however that remain and seem to be in need of a fix:

• Generator switches are still turned on even though they are on already during the checklist.
• F/O still asks me to confirm flaps setting during checklists.
• Pressing APP on the MCP seems to be a problem. The F/O doesn't press the button and seems to become incapacitated so I have to restart MCE.
• Probe heat switches: F/O says "now set" even though they were already set during the checklist (on and auto positions)
• Same with the APU switch

4 hours ago, FS++ said:

And by the way, go ahead, set the Fenix as the plane MSFS loads on startup and you will see FO already has control over many items on overhead panel, EFIS and few other items. using the same techniques (FSX/Prepar3D/Asobo SDK) used with PMDG and without Fenix specific SDK at all (not even for "setting items" as is the case with PMG).

The Fenix biggest challenge is that it runs as a collection of 3 or 4 external executables that communicate with something they run inside the sim and things like SPD, HDG, ALT aren't available via the usual means. So for now, it won't be easy to handle FCU dialling with that plane. I don't want to say impossible, but definitely not something we've done before.

Good to hear! How long roughly is it until release?

20 hours ago, threegreen said:

Thank you. I restarted MCE and the flight today after getting the message again and then it worked. There are some items however that remain and seem to be in need of a fix:

• Generator switches are still turned on even though they are on already during the checklist.
• F/O still asks me to confirm flaps setting during checklists.
• Pressing APP on the MCP seems to be a problem. The F/O doesn't press the button and seems to become incapacitated so I have to restart MCE.
• Probe heat switches: F/O says "now set" even though they were already set during the checklist (on and auto positions)
• Same with the APU switch

Good to hear! How long roughly is it until release?

You're welcome.

There will be another update for "Simco64_Ldr.exe" to address most of the remaining issues.

Will probably take 2 to 3 weeks to round up all Fenix switches. No promises for FCU dialling though.

On 7/7/2022 at 3:34 PM, agutz said:

Good news!

I know I said this Saturday.

As you can see from most recent posts, there are a couple of things to iron out before the MSFS specific package is uploaded to Simmarket. More likely next Tuesday.

Having said that, if you can't wait, send an e-mail to support and we can get you up and running today.

Thanks for your patience.

 

Edited July 9, 20223 yr by FS++

3 hours ago, FS++ said:

You're welcome.

There will be another update for "Simco64_Ldr.exe" to address most of the remaining issues.

Will probably take 2 to 3 weeks to round up all Fenix switches. No promises for FCU dialling though.

Sounds good. Just an FYI: Using the latest Simco64_Ldr.exe (2.0.7.8), the F/O switched back to using FMC1 instead of 2 again at some point, then switched back to using FMC2 at the arrival gate, which he never did before (always stayed on FMC1 whenever this issue occurred). May be something to do with external power active vs. APU or engine generators being active. I'm going to monitor this still on my next flight though because I inadvertently removed external power at some point leaving the aircraft running on battery before switching straight to APU. IIRC it was after this that the F/O started using FMC1. I was also on battery again shortly after that during pushback as rolling over a huge bump in the airport surface caused the APU generator to disconnect (lol). Maybe this was the issue.

Edited July 9, 20223 yr by threegreen
Typo

On 7/9/2022 at 5:29 PM, threegreen said:

Sounds good. Just an FYI: Using the latest Simco64_Ldr.exe (2.0.7.8), the F/O switched back to using FMC1 instead of 2 again

This patch should address that.

Now, among other conditions, if he sees combustion on either engine he'll just assume the plane is fully powered and stick to CDU2

Checklist flaps retract status should be fixed.

He no longer complains about issue with gear when he extends it, as he can now monitor the state of Left, Right and Nose gear as they go up or down.

Also in this version, there is no chance you will miss the notification about the need to restart the flight.

Earlier, it was confusing. The message box would remain hidden by the sim when you are in full screen.

Now, MCE will put you in menu mode, minimize MSFS, then display dialog box so you understand that you need to reload the flight.

Patch to be applied to V2.9.7.2 only. Anyone on earlier version, should re-install the full package.

 http://www.multicrewxp.com/Latest-Beta-Patch.zip