09/01/2025 03:15:28(217): Exception on NCalc evaluate: mismatched input '<EOF>' expecting ')' at line 0:-1
09/01/2025 03:15:28(217): Transform error (AP1): An error occurred on parsing your value formula. Please review and correct any errors.
09/01/2025 03:15:28(219): Exception on NCalc evaluate: mismatched input '<EOF>' expecting ')' at line 0:-1
09/01/2025 03:15:28(219): Transform error (AP2): An error occurred on parsing your value formula. Please review and correct any errors.
09/01/2025 03:15:28(219): Exception on NCalc evaluate: mismatched input '<EOF>' expecting ')' at line 0:-1
09/01/2025 03:15:28(219): Transform error (ATHR LED): An error occurred on parsing your value formula. Please review and correct any errors.
09/01/2025 03:15:28(220): Exception on NCalc evaluate: no viable alternative at input '<EOF>' at line 0:-1
09/01/2025 03:15:28(220): Transform error (LOC): An error occurred on parsing your value formula. Please review and correct any errors.
09/01/2025 03:15:28(220): Exception on NCalc evaluate: mismatched input '<EOF>' expecting ')' at line 0:-1
09/01/2025 03:15:28(221): Transform error (EXPED): An error occurred on parsing your value formula. Please review and correct any errors.
09/01/2025 03:15:28(221): Exception on NCalc evaluate: mismatched input '<EOF>' expecting ')' at line 0:-1
09/01/2025 03:15:28(221): Transform error (APPR): An error occurred on parsing your value formula. Please review and correct any errors.
09/01/2025 03:15:29(704): ProcessAircraftRequest: simobjects\airplanes\flybywire_a320_neo\aircraft.cfg
#Transform/exception error on Ncalc?
1 messages ยท Page 1 of 1 (latest)
09/01/2025 03:15:31(785): Exception on NCalc evaluate: mismatched input '<EOF>' expecting ')' at line 0:-1
09/01/2025 03:15:31(785): Transform error (AP1): An error occurred on parsing your value formula. Please review and correct any errors.
09/01/2025 03:15:31(786): Exception on NCalc evaluate: mismatched input '<EOF>' expecting ')' at line 0:-1
09/01/2025 03:15:31(786): Transform error (AP2): An error occurred on parsing your value formula. Please review and correct any errors.
09/01/2025 03:15:31(786): Exception on NCalc evaluate: mismatched input '<EOF>' expecting ')' at line 0:-1
09/01/2025 03:15:31(786): Transform error (ATHR LED): An error occurred on parsing your value formula. Please review and correct any errors.
09/01/2025 03:15:31(787): Exception on NCalc evaluate: no viable alternative at input '<EOF>' at line 0:-1
09/01/2025 03:15:31(787): Transform error (LOC): An error occurred on parsing your value formula. Please review and correct any errors.
09/01/2025 03:15:31(787): Exception on NCalc evaluate: mismatched input '<EOF>' expecting ')' at line 0:-1
09/01/2025 03:15:31(787): Transform error (EXPED): An error occurred on parsing your value formula. Please review and correct any errors.
09/01/2025 03:15:31(788): Exception on NCalc evaluate: mismatched input '<EOF>' expecting ')' at line 0:-1
09/01/2025 03:15:31(788): Transform error (APPR): An error occurred on parsing your value formula. Please review and correct any errors.
09/01/2025 03:16:17(78): ProSim connection failed after 5 attempts. Disabling auto-connect for this session.
All my hardware is working fine. I don't have Prosim hardware.
you need to show your config, otherwise it is impossible to know
if you get a ton of these, it might be you are using a precondition that does not exist or is empty, and the precondition substitution character results in an empty character, so the ncalc does not work
I have been getting those <EOF> errors too under the new UI from mcc files that did not previously have this problem. Something must have gotten more strict in the new UI with respect to ncalc syntax. I never found what was causing them.
All my hardware is working 100% as it should, this has happened before then stopped and now again, config has been in use a long time.
Do you want the exact listing fromthe mfproj file?
beta
it might be what @quasi magnet then experienced too
maybe you can share the file and perhaps @vocal flint can have a look?
I mentioned it several months ago when I 1st saw it
yeah
2 secs I'll dump the fil here, also have those run/stop errors
looks like a closing ) is missing or so
missing in the file? I've not changed anything recently.
a bit of a delay, one of my gear is not switched on and I then get the presets allocated to the wrong device.
maybe a placeholder that is referenced but when substituted will end in
(space)
the formula will fail whereas it wont if the config reference can be resolved, maybe when a certain device is connected
just started MF with all my gear switched on and logging running, it's not displayed the above errors
and, the errors shown are not associated with the device that I sometimes forget to switch on, all the function in those errrors are only used on the minicockpit fciefis
This is the project file
so just to confirm: with all devices connected, you get no error
with one device disconnected, you would get the error
current log from this startup.
let me turn that gear off again.
This is with it switched off before starting MF
Same again, MF running the configs but the RUN icon is showing and not RUN but all the hardware is working.
To clarify, device events are detected even when in Stop Mode. However, nothing is sent to or received from the simulator in Stop Mode.
As above, the hardware is working in both directions and it doesn't show STOP, it still shows RUN but it is actually running, this is after having clicked on RUN.
OK, that is not normal behavior and should be fixed.
I've just noticed that if I change aircraft away from the FBW A320 that profile is intended for, it changes to run without me touching MF.
we need steps to reproduce it. it likely has to do with autorun
Morning Seb, It is random that it happens like the other problems. It's simply load MF click on RUN and it doesn't always change to STOP but the hardware is working as expected. I think there is something a little odd with the profile. I'll try other profiles later today.
I've just done another flight now, same profile no problems but it still displayed the Transform errors.
Steps to produce the errors. Load MF with the profile which is working but also produces those errors all relating to the mini fcu and the mega config . You suggested it's related to autorun, it's not just autorun, it will display the errors no matter which way the profile is run, either autorun on MF startup or manually using RUN. BUT ๐ the errors only appear with that profile I uploaded here last week. It's this one
I will start building a new profile.
@vapid zodiac - can you help here: I assumed there was a working miniFCU profile available for FBW (dev) and FCU and EFIS