The cumulus mediocris cannot be set in Aerofly FS2, but the Wettergerät can change these.
Spit40 , your question gave me an inspiration so brilliantly simple I am still dazzled I did not have it up until now - so release 1.3.0 is dedicated to you and your question, making me convert all sliders from percent to usable units like feet, knots and meters (not shown in the screenshot, but implemented in 1.3.0).
Ah, I get it: the Wettergerät is not (yet) able to display the converted values, as these values are already present in the METAR information. But if there's no METAR, there's no information.
I think about how and when to integrate this idea.
It's a great idea to have changing barometric pressure but this feature will be added naturally if and when we decide to go and make a new weather engine.
Sorry, I did not make it clear what the actual point of my proposal was: The hidden implementation was meant to reduce the effort needed to get this feature started - hopefully to a point where IPACS deems it trivial to implement.
As it is a hidden feature (like the third cloud layer and date the Wettergerät manipulates), IPACS would not have to put effort into adding UI, nor is a completely new weather engine needed. The static value could act as a placeholder for a more sophisticated weather engine later on, so any effort invested into simulating the effect of pressure changes on the actual airplane does not have to be wasted. Think of this idea as a "mock" implementation.
Being a developer myself I know how customers wishes sometimes interfere with well-laid plans software builders have for a given software - sometimes to the point where building a specific feature would mess up a strategic plan. As a developer I also have a horror of proposals in conjunction with words like "just", "simple" or "easy" - so feel free to ignore an outsiders ideas.
It's me, the Wettergerät guy again. Riding my favourite horse I have come up with a new idea: What about adding atmospheric pressure as another effect of weather?
Why should we virtual pilots care about atmospheric pressure?
- At the very least atmospheric pressure could influence the displayed barometric altitude in Aerofly FS 2, requiring pilots to re-calibrate the altimeter.
- As I understand pilots a required to re-calibrate their altimeter to standard pressure on reaching certain flight levels (see Wikipedia - and also mentioned in Aerofly's very own Learjet instructions).
- (There are also some more interesting effects of barometric pressure on planes.)
As the Wettergerät already manipulates some hidden variables in Aerofly FS 2's main.mcf configuration file, how about adding atmospheric pressuren as another hidden variable? It does not have to be accessible via the regular in-game controls, but would only be a single main.mcf configuration variable (like the date settings and third cloud layer), reducing the work needed to integrate this idea into Aerofly FS 2.
So what do you think about:
- …having barometric pressure in Aerofly FS 2 in the first place?
- …adding it as a hidden variable to minimize the effort needed to get the feature into Aerofly FS 2?
Disclaimer: I know IPACS has more urgent concerns and the community developer's whishlist is rather long - but maybe the (stub) implementation is quick to do.
Since the current Windows Update I noticed my WMR headset sometimes failing to recognize it's boundaries when started directly to Aerofly. In some cases it suffices to carry the headset to some other corner of the room, on other occasions I just restart the Windows WMR software, Steam VR and AFS2.
It's not that there's no documentation, it's that the weather API doesn't exist
The messages in the C++ plugin example are the only messages Aerofly sends / receives to registered plugins.
Well, that explains quite a lot about my misguided attempts to find additional API symbols. I must have missed that information... in the documentation.
I believed there were more symbols because I could see some passing by which had unknown IDs. Well, thank god I cancelled my quest after some weeks of searching and asking questions on the forum.
As a fellow developer I understand the feeling of frustration about the things blocking our progress. But I think we have to keep in mind the limited resources and the many tasks for the IPACS core development team:
- Build new aircraft, enhance existing aircraft
- Build new scenery, enhance existing scenery
- Add new functionality (ATC, weather, etc)
- Add development tools
- Adapt to new hardware
We also have to keep in mind that for every feature added, you will have to add time for testing, documentation and bug-fixing/updating.
I am quite fine with IPACS' decision to concentrate the limited resources on the very core of AFS2. Given that there is (and next year will be even more) competition in the flight simulator market, we as spare-time developers have to consider that strategic decisions made by IPACS have to balance more variables than we know of.
I made my peace with the situation and wait for my turn to build the final solution for the Wettergerät. If in the meantime AFS2 gets more core features which in turn secure and expand its competitor advantage, it also helps us spare-time developer investment by keeping AFS2 alive and kicking - which in turn keeps or projects meaningful and enjoyable.
I'll second the request for some documentation regarding the weather API... obviously.
Standing at KEYW, NAV1 tuned to EYW (113.5), bearing 308° in 3.0NM.
First in a Baron 58:
Than in a MB339 (HSI mode set to VOR, VOR frequency can be seen partially in the lower right, and the outer bearing indicator of the HSI points toward the VOR). But here the deviation indicators points to the left, no matter how I turn the COURSE knob.
Do I have to toggle some more switches?
Can someone explain to me how to have the deviation indicator in the HSI show my deviation to a selected VOR? What I tried so far:
- Check HSI source to be "VOR"
- Dialed in the frequency of the VOR in the lower right panel (the panel with the mechanical numbers).
- The HSI activates, the " TO/FROM" going from red to an arrow, but "MILES" still showing a striped red bar.
- Turning the "SET COURSE" knob on the HSI has the HSI rotate and the "COURSE" output change accordingly, but the deviation indicator always stays to the far left, regardless of the set course.
Did I miss something? Or do I have to use the digital navigation panel? If so, how does it work?
Thanks in advance & cheers.
Am I seeing that right? 1 VOR, 1 ADF and no autopilot?
Count me in! This will be fun to fly in VFR conditions.
Q400, C90Gtx and B58 support cold & dark? Well, the Baron is one of my favourites, I am happy to hear that I can really shut the plane down.
Is there a way to start cold & dark? And are there any other planes I missed supporting cold & dark?
The "Wettergeraet" ist spitze - high end wäre jetzt realtime Übertragung from airport to airport...
Actually my plan to do this stalled, even though the groundwork for this endeavour is finished. I tried to raise some support via DLL builder's request for help, but to no avail. So for now, the Wettergerät is all we have.
Actually the Wettergerät allows to manipulate a third cloud layer unmanageable by the simulation itself. It also allows for some values to be out of bounds (e.g. wind speed), because the sim still works afterwards.
It also allows to manipulate the date, which seems to alter the path of the sun in AFS2.
If you are interested in the technical details, have a look at Wettergerät's documentation regarding the values of AFS2.
Just a quick question: Do you really need a Github account? You can download stuff from Github without being a registered user.
If you really want to have a Github account, it seems you will need to use another username.
Yesterday I saw a windsock in Florida. If I remember correctly it was at Key West airport. But I do not remember it it was facing the right direction.