Posts by Armitage

    You are in luck: this error message is exactly what the update was all about: A HTTP code of 401 says that you need to authenticate (see https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/401).


    You will need to get an API key, and supply it following the instructions found some posts above.


    Sorry for the Wettergerät being so cryptic about the solution to your problem - if I find the time I will make a proper setup procedure and a better error message.

    Sorry for the inconvenience, as the API key part is rather bolted on. If I find the time I will make it more user-friendly by supplying a configuration dialogue.


    Until then you will have to supply the API key by adding '--apikey "YOURAPIKEYHERE"' to your desktop link. See https://github.com/fboes/aerof…o-the-desktop-application on how to do that.


    So if your API key is "xyz", open the application by calling 'aerofly-wettergeraet-desktop.exe --apikey "xyz"'.

    I have been away from Aerofly FS 2 for quite a while, so only yesterday I noticed the API the Wettergerät relies on now requires an API key. I updated the Wettergerät to be more helpful in situations like these, and added some instructions to the Wettergerät's documentation on how to get and supply an API key to the Wettergerät.


    In any case you will need to

    1. download the latest version of the Wettergerät
    2. get an API key for your METAR REST service of choice
    3. and supply the key to the Wettergerät

    Well, the Wettergerät is open source.;) I tried to build it in a way that parts of it can be recycled for other projects. So if you are interested, you are free to integrate the DLLs / source code into your project.


    I will look into the idea of compiling a list of airports from the local files. May be I find something usable, which both PJ and WG can utilize for their own benefit. Like a small tool which build the CSV file with the actual local airports.:/

    Actually you answered my question perfectly.:)


    I had the idea of compiling a list of all airports present in the local copy of Aerofly FS2 so users could select them for the Wettergerät app. Presently Wettergerät's users have to enter the ICAO airport code manually if it is not present in their flight plan.


    I also had the idea that the Wettergerät optionally sets the starting position of the plane to the airport the user fetches the weather data for. But like you said: one needs to know much more about the airport in order to solve this.


    Thank you for your insights. :thumbup:

    This is just... wow. That level of detail is amazing. Payware grade material for sure.

    After enjoying the Piper Arrow I would not mind _paying_ for the Carbon Cub. It sure looks great, and fills the role of a modern tail-dragger with up-to-date avionics. Think of the back-country adventures we will be having! ;)

    I also have a GTX1080 / WMR combo (Samsung WMR), try these settings:

    • Texture: ultra
    • Terrain mesh: high
    • Terrain image: high
    • Shadow: medium
    • Building: low
    • Tree: low
    • VR render scale: 1.50

    Also, turn cumulus cloud density off / low - it's okay to use some cirrus cloud density (25%) at high altitude (75%)

    Today I had some spare time to cruise the Netherlands in my Turbo Arrow. Strangely enough now the course indicator shows up, even though my settings are down to "high". Maybe there was a Steam update I did not notice? Nevermind.


    Thank you for the beautiful Arrow - all the small details are truly appreciated. I just noticed I had to calibrate the compass on my main dashboard, as it was not matching the GNS. Love it! :thumbup:

    Just try it out, better quality settings should mean the small objects are rendered up to a much larger distance.

    Changing the graphics setting to "ultra" makes the heading bug of the Arrow visible in any distance - changing it to "high" yields the same behaviour as described above.


    As "ultra" is somewhat choppy on my rig (at least when flying over the Netherlands), is there any other way to make this work?

    kai503 & Jet-Pack Thanks for getting back to this issue to promptly.


    My graphics settings:

    • Texture: high
    • Terrain mesh: high
    • Terrain image: high
    • Shadow: medium
    • Building: medium
    • Tree: high
    • VR render scale: 1.50

    I use an Acer WMR headset connected to a GTX1080 (latest drivers).


    The small parts of the Piper Arrow cockpit are only visible if I lean into the cockpit (e.g. having my head next to the yoke). There is a distance where they flicker (they are only visible for one eye ;) -> ;)).


    Jet-Pack Your are perfectly right, the Corsair gear indicator balls show the same behaviour (I did not event notice they were present before you told me), being only visible when I stick my head in 30cm distance.


    In the Cessna 172 the turn coordinator ball turns and heading bug is perfectly visible, but the turn coordinator ball turns into a blur and the heading bug vanishes when I put my head behind the headrest, so there is enough safe space to move your head around (if the pilot's head is behind the headrest, there might be bigger problems than not being able to see the finer details of your instruments;))


    Do I have to change my graphics settings? Is there something else I can do?

    I flew my first trips with the Arrow, and I am very impressed with the general attention to detail.


    But I encountered a bug. As no one has reported it before it may be because of my setup: depending on my head position using a WMR headset the heading bug flickers or even disappears. The same goes for the From/To-indicator at the NAV 1 indicator. If I lean into the instruments everything is visible, in my regular sitting position these two items are invisible.


    Does anyone experience the same problems? And does anyone know where to report these?


    BTW: I own the Steam-version.

    1277-948335a3.png


    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).


    To all interested in the idea of Spit40 head over to https://github.com/fboes/aerofly-wettergeraet to grab the latest release of the Aerofly FS 2 Wettergerät.