May 23, 20215 yr Hi guys, beside false log entries I can't enable coordinated checklists for a specific livery for FBW dev. But the entries are my bigger concern. Never happened before. Using latest FUIPC as well.
May 23, 20215 yr Commercial Member 4 hours ago, LH067U said: Hi guys, beside false log entries I can't enable coordinated checklists for a specific livery for FBW dev. But the entries are my bigger concern. Never happened before. Using latest FUIPC as well. Which MCE version are you on? (report both "mce.exe" and "Simco64_ldr.exe" Are you using a custom checklist? FlyByWire dev distribution isn't fully supported because it changes every day. We aim to adjust to the official release, currently v0.6.1 https://flybywiresim.com/ What do you mean by false log? We don't log every little click or value change. It could adversly affect the flight sim experience, with constant writing to a log file. Only key events are logged. Like whether the wasm module is responding and Lvars we need access to are accounted for. Gerald R https://www.multicrewxp.com
May 24, 20215 yr Author MCE version (MCE version 2.9.1.8 / SimCo64_ldr.exe version 1.2.1.8) latest version installed, former version de-installed as published via windows checklist (default settings): livery is going to be recognised, but I am not able to do coordinated checklists, no costum checklists used other 3rd party liveries with checklists are working fine. Is there any specific variable to put into the livery's aircraft.cfg? FBW is indeed the current dev version which could be the reason- so I need to go to stable one SmartCARS entries repeating every 7-8 minutes: sim rate set 0,25 X sim rate set to normal
May 24, 20215 yr 3 hours ago, LH067U said: MCE version (MCE version 2.9.1.8 / SimCo64_ldr.exe version 1.2.1.8) latest version installed, former version de-installed as published via windows checklist (default settings): livery is going to be recognised, but I am not able to do coordinated checklists, no costum checklists used other 3rd party liveries with checklists are working fine. Is there any specific variable to put into the livery's aircraft.cfg? FBW is indeed the current dev version which could be the reason- so I need to go to stable one SmartCARS entries repeating every 7-8 minutes: sim rate set 0,25 X sim rate set to normal Regarding logs: those are not false; But i'm also hoping for them to get fixed. incidentally i also mailed support about this a few days ago. hopefully they can find a way to stop mce from changing sim rate. A few times the dispatchers of my airline asked me why i'm doing this, had to explain to them that there's a technical issue
May 24, 20215 yr Commercial Member 5 hours ago, LH067U said: MCE version (MCE version 2.9.1.8 / SimCo64_ldr.exe version 1.2.1.8) latest version installed, former version de-installed as published via windows checklist (default settings): livery is going to be recognised, but I am not able to do coordinated checklists, no costum checklists used other 3rd party liveries with checklists are working fine. Is there any specific variable to put into the livery's aircraft.cfg? FBW is indeed the current dev version which could be the reason- so I need to go to stable one SmartCARS entries repeating every 7-8 minutes: sim rate set 0,25 X sim rate set to normal A new patch was released a few days ago. Get it here Unzip, then manually replace files as per folder structure. Regarding sim rate... The advice right now for Visually Impaired Pilots is to disable the "user interface voice control" feature. That way, the few "helpful" commands some users enjoy (they can see the impact on the sim), won't be triggered by accident. Only your activity on keyboard could cause that, once you get rid of that feature. Regarding checklist. You never know with all those liveries, as it's untested scenario. Having said that, if most liveries are OK with MCE seeing them, the odd one out might be the issue. Keep in mind, FlyByWire changed the system last month. Their plane is now seen as a separate one, not grafted to ASOBO A320 as before. I'm guessing all liveries should update accordingly. Is the livey very important to you? Which one? and where did you download it from? Gerald R https://www.multicrewxp.com
May 25, 20215 yr Author Thanks for your support so far! I am going to install the new patch and disable the user interface voice control to prevent any further sim rate changes. livery: It is the VA livery by Flygravity VA which has been available for about 4-5 weeks now. It is their first one for FBW and maybe not fully compartible I guess. The download itself is offered by the VA download section. The livery is neccessary for having a valid pirep accepted- alternative would be FBW vanilla one.🤨
May 25, 20215 yr Regarding logs because i am a blind pilot. i do have to turn on the user interface commands to locate the aircraft onto the runway; however, today, i turned it off right after i issued my command. as always, while my aircraft was located, the sim rate was altered by MCE, but even after it was turned off, MCE kept altering the sim rate. I am thinking that this has to do something with MCE and its relation with the native ATC. I think MCE actively tries to scan the ATC window and something happens that it thinks that it should slow the sim down for a second. For example, when you turn on MCE when you are at the gate, when the boarding coordinator introduces himself, mce alters the sim rate. Here's a log of my flight today, you are able to see the sim rate changes: http://www.dlhvirtual.de/crew/index.php/pireps/view/301771 Edited May 25, 20215 yr by hadi
May 25, 20215 yr Commercial Member 2 hours ago, hadi said: Regarding logs because i am a blind pilot. i do have to turn on the user interface commands to locate the aircraft onto the runway; however, today, i turned it off right after i issued my command. as always, while my aircraft was located, the sim rate was altered by MCE, but even after it was turned off, MCE kept altering the sim rate. I am thinking that this has to do something with MCE and its relation with the native ATC. I think MCE actively tries to scan the ATC window and something happens that it thinks that it should slow the sim down for a second. For example, when you turn on MCE when you are at the gate, when the boarding coordinator introduces himself, mce alters the sim rate. Here's a log of my flight today, you are able to see the sim rate changes: http://www.dlhvirtual.de/crew/index.php/pireps/view/301771 PIREP log shows frequenct occurences of this [11:03:57] Sim paused (no idea what could cause this, except if some of your hardware is set to automatically trigger the key combo that causes the sim to pause, or hitting it accidentally) [11:03:57] Sim unpaused, simulation rate: 0.00390625X (value looks wrong. When read from MSFS, should only be 0.25, 0.50, 1, 2, etc.. [11:03:57] Simulation rate set to normal (something is trying to eset the sim rate. Does the PIREP software do that automatically when sim rate is not at 1?? Gerald R https://www.multicrewxp.com
May 25, 20215 yr 1 hour ago, FS++ said: PIREP log shows frequenct occurences of this [11:03:57] Sim paused (no idea what could cause this, except if some of your hardware is set to automatically trigger the key combo that causes the sim to pause, or hitting it accidentally) [11:03:57] Sim unpaused, simulation rate: 0.00390625X (value looks wrong. When read from MSFS, should only be 0.25, 0.50, 1, 2, etc.. [11:03:57] Simulation rate set to normal (something is trying to eset the sim rate. Does the PIREP software do that automatically when sim rate is not at 1?? Most likely this acars software is not the best way to show this; Does MCE have its own logging system? perhaps i can find something that way. I also have other sim monitoring tools; all of them showing the sim rate going to 0.25 then back to 1. It's a really odd situation this one, Sometimes it happens when i press shift+p to push back. sometimes it happens on its own. in that log that i sent, when i set the thrust to idle when the aircraft was doing its flare the sim rate change happened again. My microphone was muted and i did not accidentally press any other keys. I'm trying my best to see what exactly is causing this, but here's what i've gathered so far. -It is mce which is doing this. without mce running, this does not happen at all. -when user interface command is disabled, this happens less frequently. -Has happened during these key presses: shift+p, or f1 through f4 for setting throttle. -Every time i use the native atc, it happens. -After MCE launches and it identifies the aircraft, it happens once. sim rate goes to 0.25, then back to 1. If there's anything i could try, let me know.
May 26, 20215 yr Commercial Member 19 hours ago, hadi said: Most likely this acars software is not the best way to show this; Does MCE have its own logging system? perhaps i can find something that way. We only log the MCE startup process in order to troubleshoot scenarios where it fails to start.. In the context of flight simulation, and the need for extreme performance, would rather let Windows process FS related file read/writes rather than clog it with needless operations for rarely used log data (that includes speech commands that we never log), especially when everything is read and written to same C drive. having said that, the PIREP log may not be wrong after all. You may have stumbled across some unsuspected ASOBO bug, either in the SDK (for reading simulation rate) or the core simulation itself. Up to now, when MCE detects new ATC options are available, it checks the sim rate value reported by the SDK and if it's diffeent from 1 (normal value), it automatically triggers a reset to default sim rate. Therefore, it could well be that MCE also occasionally reads that dodgy value (0.00390625) and resets. I guess, we'll know once the new patch is posted. From the then on, MCE will only reset if sim rate is above 1 (normal rate) and ignore cases where you deliberately reduced rate below 1 You could also enlist the help of a sighted person, then press "SHIFT + Z" combo to display FPS, Coordinates and simulation rate. See if the sighted person can spot unusual value in sim rate, while you perform your usual activities on keyboard. Edited May 26, 20215 yr by FS++ Gerald R https://www.multicrewxp.com
May 27, 20215 yr On 5/26/2021 at 5:00 PM, FS++ said: We only log the MCE startup process in order to troubleshoot scenarios where it fails to start.. In the context of flight simulation, and the need for extreme performance, would rather let Windows process FS related file read/writes rather than clog it with needless operations for rarely used log data (that includes speech commands that we never log), especially when everything is read and written to same C drive. having said that, the PIREP log may not be wrong after all. You may have stumbled across some unsuspected ASOBO bug, either in the SDK (for reading simulation rate) or the core simulation itself. Up to now, when MCE detects new ATC options are available, it checks the sim rate value reported by the SDK and if it's diffeent from 1 (normal value), it automatically triggers a reset to default sim rate. Therefore, it could well be that MCE also occasionally reads that dodgy value (0.00390625) and resets. I guess, we'll know once the new patch is posted. From the then on, MCE will only reset if sim rate is above 1 (normal rate) and ignore cases where you deliberately reduced rate below 1 You could also enlist the help of a sighted person, then press "SHIFT + Z" combo to display FPS, Coordinates and simulation rate. See if the sighted person can spot unusual value in sim rate, while you perform your usual activities on keyboard. Thank you, I can't wait to try the new patch out. will it be posted here when it's ready? regarding liveries and mce not working with some of them, I have something that might be useful. I went ahead and installed a new livery today and found out that MCE will not accept any commands and is not working at all. Then, i realized MCE's control panel title, It says: "Multi Crew Experience Copilot Listening ... On British Airways OperatorLand468 Free Flight" So what i'm guessing that the livery is editting something that's changing the title of the plane and that's why MCE is not recognizing the current aircraft. I do not know anything about liveries and how they're supposed to be, but i'd love to help MCE developers as much as i can so that's all i could find out about this. edit: I may have found a fix. you can go to your livery's folder, find the aircraft.cfg, edit the file. You will see the title there has been changed. change it back to something like this: title = "Airbus A320neo FlyByWire British Airways" ; Variation name Example path for the aircraft.cfg file for my livery. F:\FS\Microsoft Flight Simulator\Packages\Community\OperatorLand468-livery-a320NeoBA_Multi\SimObjects\AirPlanes\Asobo_A320_NEO-a320NeoBA_FBW I have done this and mce can detect the aircraft and everything is going well! Edited May 27, 20215 yr by hadi
May 27, 20215 yr Commercial Member 36 minutes ago, hadi said: Thank you, I can't wait to try the new patch out. will it be posted here when it's ready? It's on final approach runway 22 🙂 Edited May 27, 20215 yr by FS++ Gerald R https://www.multicrewxp.com
May 27, 20215 yr Commercial Member Flight MCE 2920 has just landed. Grab the patch here Patch assumes user already running V2.9.1.7 or higher. If not, upgrade to previous release first before applying the patch. ChangeLog Slight improvements to CRJ and FlyByWire interfacing in MSFS Improved interfacing with FsLabs A3XX series in Prepar3D Gerald R https://www.multicrewxp.com
May 27, 20215 yr 3 hours ago, FS++ said: It's on final approach runway 22 🙂 Knew it! 2200 london time 🙂 installed the patch as soon as it was posted. no sim rate reset problem anymore! it is running smooth and perfect! already at fl230 climbing to fl280 outbound from Paris to London and not even a single sim rate reset. Thank you!
Archived
This topic is now archived and is closed to further replies.