+1 upvote from me.
Upvote from me. Please make all variables available
\Upvote ++1
var Upvote= 0
while true {
print(" ")
Upvote += 1
if Upvote == 100000 {
break
}
}
come on #asobo you really need to make this happen ASAP.
Pretty please with a cherry on top!
An Upvote from me too
I’ve voted. Definitely needed.
Thanks for supporting this request!
thanks for you encouraging feedback! i am glad you find mobiflight useful.
100% yes !
How do you propose Ovars to work, given they are scoped to a particular component (i.e. their names are not unique)? Would you add the path to the component as a prefix? Given their purpose they really shouldn’t need to be accessed by anything external…
Honestly, access to O- and I- vars is only useful as a workaround; anything worthwhile should be exposed as a simvar and B events should be triggerable over simconnect. We’ll take anything we can get, but there are ways that are better than others.
Voted! Very important issue to me.
I have made home cockpit interfaces between Opencockpits hardware modules and many airplanes FSX, P3D, and XPlane11 for years and the last year also interfaces between Opencockpits hardware modules and many of the airplanes in MSFS.
Developing interfaces for MSFS is a pain-in-the-■■■ job to do as it is so much harder and
time-consuming. Please Microsoft, have Asobo put resources to improve this situation ASAP.
My upvote for this request. For the interrest of MS and Osobo absolute vital.
This weeks dev update lists this topic at number 38 on the feedback snapshot. Asobo have marked it as “under investigation” so we will have to see what this means. hopefully they will have more news in an upcoming dev update.
This is really great to see! Please spread the word and encourage more folks to upvote to make it into the top 25.
The trend shows with 2 arrows pointing up - that’s cool!
Yes please
Yes!!! I support this.
I support this! Please add access.
Yes please!