Agniparvata

The parking brake WORKED fine before the SU-10 release and AFTER that. It is the toe-brakes that do not work. Seemingly AXIS_LEFT_BRAKE_SET does not work anymore but AXIS_LEFT_BRAKE_LINEAR_SET does.

Just adding to the mystery of toe-brakes, I fail to understand why the parking brakes seem to work, whereas toe-brakes do not. And how is it that known 3rd party add-ons, which employ the brakes via SimConnect, do work without ANY changes, but FSUIPC does not, even if it is supposedly also does that by using SimConnect. Furthermore, if John doesn't mind it, I'd have a remark on "policy". John has repeatedly declared that he was reluctant to deal with problems during the long beta period of SU-10, although many users had already reported similar problems. The LONG beta period was a good opportunity to find out, if the Asobo changes were INTENTIONAL or were simply BUGS. Now it suddenly turns out that the changes are intentional, but John has not paid any attention to this over the long beta period, which lasted almost THREE MONTHS. It is not a good practice to wait for the release version and THEN trying to find out that there are changes, changes that touch the very basic functionality - like brakes. Now our sims, home cockpits, setups, whatever, are simply unusable due to the delay of dealing with intentional changes, that is a tiny bit unacceptable from the users point of view. Betas are released to deal with changes BEFORE the release and that is exactly what other 3rd party developers did, and that is what the single FSUIPC developing "team" should have done. It is way too late trying to find out solutions, now, when due to the MS policy, there is no way to turn back to the previous version, a version that everything worked fine in this regard. Just my 2 cents, but FSUIPC7 is a popular and very useful add-on, thus it would have deserved more attention if after the release our basic functionalities remained the same, or rather we need enter another wait-cycle, when possible solutions are experimented out. It was nothing else but a waste of time, for both parties involved. Spe3cially so, that half of the millions of MSFS users have already used the free beta for long periods. regards

Hi John, Thanks for the answer. The script is for a THQ in this case and it becomes only important WHY we can't use ProSim's Simconnect-mode, that doesn't have the toe-brake problem. So although I can attach a SIOC script, but it has nothing to do with the matter. It is the STOCK ProSim Toe-brake (that is a lever) that is NOT working, similarly not working for other people who use very different THQs and scripts. I will try to produce a log, but I already had a thorough look when the problem first appeared and found nothing related. I will try it again. It is seemingly connected to so changes that Asobo made in SU-10, somehow the changed variables because they introduced a visual effect related. (if I'm not mistaken for the brakes, it is the vanilla 0x0BC4 and 0x0BC6) offsets that ProSim employs) regards Agni

Hi, Also a ProSim user here. I lost my toe-brakes couple of weeks ago, because I was trying out SU-10 beta. Unfortunately it is definitely an FSUIPC problem, as ProSim also allows running a Simconnect only mode, where the problem does not happen. But I - and many other users - simply cannot run in Simconnect mode, because many of our throttle-quadrants depend on a script, based on FSUIPC offsets. Please, if possible, make it a priority, as this small problem rendered our home-cockpits unusable. Thanks in advance

Hi John, Whenever you are in an actual flight, or runway, so the flight has started, by pressing ESC you get back to the "Options" screen, when you either save or load a flight or flight-situation. Just like as it used to work for FSX and later iterations. The flight is saved in the corresponding ...\LocalState\ folder in a new .flt format. So when someone loads or re-loads a saved flight FSUIPC7 is no longer functioning, though it stays connected. Hope it help regards Achoriham

Hi, The newer version fixed the dev-mode resync as I have mentioned above. But this time I noticed that after reloading a flight the same happens, namely no actual FSUIPC connection, although it say it is connected. regards Achoriham

Yes and thanks. It also works here with the latest. thanks again Achoriham

Hi John, Yes I always use "Auto-Connect to FS". It doesn't make a difference. Manually disconnecting or re-connecting doesn't help, only a full restart of FSUIPC. Also tried to check the log and console window which don't say anything particular in this case, FSUIPC "thinks" it is still connected fine. regards Achoriham

Hi, While doing an airplane for MSFS I've been facing a strange problem with FSUIPC7. Fortunately there is a "sync" possibility in the aircraft editor in MSFS which needs to be used after doing changes to the flight_model.cfg or any other .cfg file. That is a life-saver, otherwise the entire sim would have to be restarted after every small change. So far it is good and as the autopilot (an external one) is using FSUIPC for everything it works great when I'm in the sim. The problem comes or starts when I "re-sync" the plane, when FSUIPC remains connected just as it should but interestingly to get the autopilot work again I have to close and restart FSUIPC each and every time when in the sim a "resync" was done. Have you tested any scenario like that? Is there any solution for the problem that seems to be permanent? thanks in advance Achoriham