aua668

Before my upgarde to WIN 11 I had the Twin Otter running under P3D V5.4 and Windows 10. Rgds Reinhard

Hi, I use the Twin Otter in P3D 5.4 under WIN 11 without any problem. Rgds Reinhard

Hi, I found a copy on my NAS. Do you have an upload link, where I can upload it for you? Rgds Reinhard

Hi, Use the FSUIPC feature (included since 4.91): Rgds Reinhard

Hi, Just detected - had an old link. Wilco. Reinhard

LPPT 011400Z 23020G30KT 9999 FEW008 BKN012 16/15 Q1017 Decoded textual weather for LPPT Wind: 320 at 20 knots gusting to 30 (wind direction forced by ATC lock) Visibility: 10+ SM (9999+ m) Clouds: Few at 800 feet, Broken at 1200 feet Temperature: 16,0C Dewpoint: 15,0C Precipitation: None reported Altimeter: 1017 mb (30,03 inches) This station includes complete surface weather information, interpolation disabled. Original metar of the stations: LPPT 011400Z 23020G30KT 9999 FEW008 BKN012 16/15 Q1017 Hi, I use ASN SP4 B5833 with P3D 2.5 under Win 7-64. I just departed from LPPT. All weather sources showed wind from 230. Also in the METAR string in ASN this was shown. But wind was interpreted and depicted as 320@16. Could you please check? Rgds Reinhard

Completely different to all other weather sources: ASN: LIPZ 241552Z 36007KT 320V020 CAVOK 08/05 Q1019 PFPX: LIPZ 241520Z 15003KT 120V180 CAVOK 16/10 Q1021 Rain in Vienna although there is nice weather today ... Rgds Reinhard

Hi, Run the additional programs from a cheap networked notebook or PC instead (if possible). That's much better than running it on the FSX PC. It's always a problem switching away from FSX for using other programs. Especially if you consider to use fullscreen. Rgds Reinhard

Hi, Does anybody here have a copy of the rain40.fx modified by Matt Nischan? None of the links in this post are working. So it would fine, if the file could be uploaded here. Rgds Reinhard

Hi, I connected the following screens via USB: Acer T231H, The USB support is part of WIN 7 64bit. So this was no problem. If you use more than one touch screen with Windows 7 64bit it's better to use he following drivers: http://www.touch-base.com/ They are not cheap but you have many additional configuration possibilities. Rgds Reinhard

Hi, I have two 680. One running three monitors for the outside view. And the other card handles two touch screens for the panels. Together with my GF equipment I need no mouse anymore in my cockpit. Rgds Reinhard

But sometimes one single station in vincinity (e.g. 20 nm) is MUCH better than 2 or 3 stations for interpolation being many miles away RgdsReinhard

Kostast,Thanks for your input. The only thing is, that Hifi Sim has changed the format for non-US users, which wasn't the same in the past. So they simply should write the old format for all users again - as they did with ASV6.5. That's so simple - but ignored until now.RgdsReinhard

Hi,B647 seems to work for the winds aloft. I flew from BIRK to CYYZ and everything was fine. If your programmers could now do a similar miracle for the data files for non-US users, we would be able to use this now correct wind info for FSBUILD again.RgdsReinhard

Hi,I have never seen any other software vendor ignoring consequently all the valuable input of paying customers to find fundamental errors in the software. We have now very detailled data about depicted data, which in no way can be correct, from users, who have a lot of experience in the weather area. The only message now must be, that this is an accepted bug and that there will be a fix available in near future. And it doesn't depend, if the bug is in the software or the data used.RgdsReinhard

Hi,I had the same phenomen some days ago. Look at this post here in the forum.Within some miles wind direction changes totally for some stations. How should this work? And the bad information: This happened at the same time and place also in ASV 6.5 at the same station. I checked this for this route. So it looks like a data problem. I didn't have any logfiles, as I didn't save them at that time. But as this happens quite often, there must be a possibility to find this issue. And there is definitely an issue!RgdsReinhard

Hi,You might have done some fixes. The problem is alive. See this navlog. Within several miles the wind should turn by 180 degrees ?!?And the bad message: ASV6.5 did similar things. Not at this place but in a similar condition 300 miles north of this place. At one point 40 nm from south and at the next with the same speed from the north. Very unrealistic behaviour.You definitely have not fixed it until today.RgdsReinhard

Our kangaroos are world champions ! :( RgdsReinhard

Hi Sluggy,The problem isn't the fault of some users, which won't change their LOCALE everytime they use ASE, but one single programmer, who won't eliminate one "feature", which was introduced with the upgrade from ASV6.5 to ASA (continued to ASE), and which produces now a different file format, if you are not using the US LOCALE setting.See this thread (and there are some other threads): http://forum.avsim.net/topic/265141-asa-and-non-us-locales/page__view__findpost__p__1832835Some strange countries use the comma as their decimal seperator. Everything (including our PC keyboard) operates with this scheme. Everything - except ASE. It's a little bit like Asterix :(;-) So if you in Australia are using the same seperation symbols like Jim in US, there should be no problem. I have just switched within one second :( between Austria and Australia and you have luck. Although my small country is often mixed with your country by US people - in that case you are the lucky man. You use the same seperators and it should work as before. For you!RgdsReinhard

Hi,After months of unsuccessful trials and after some patches for me it always stayed the same. Sometimes sudden weather changes, totally unpredictable. You asked for an advice: Stay with ASV6.5. I returned and I have predictable weather conditions during my flights.If you are a non-US locale user, you even lost the integration with FSBuild (if you haven't detected this issue). For my personal experience it wasn't worth the investment at the moment.RgdsReinhard

Hi,For those international users, which want to convert the new weather station file to the old format usable by FSBuild here a short description of a simple method to do this.1) Install SED for Windows from here on your ASE PC2) In your ASE weather directory create a small text file ASE.SED with the following two lines: s/,/\./4s/,/\./2 3) In your ASE weather directory create a short command file ASE.CMD executing the following two commands: "C:\Program Files\GnuWin32\bin\sed.exe" -f ASE.SED wx_station_list.txt > <your-fsbuild-ase-directory>\wx_station_list.txtcopy current_wx_snapshot.txt <your-fsbuild-ase-directory>\ You might have to adjust the directory path according to your SED installation4) Configue FSBuild to read from the defined <your-fsbuild-ase-directory> (which should not be the normal ASE directory).The SED file converts the second and fourth comma into a decimal point. So after the initial weather download by ASE you just execute the small CMD file. This will copy the actual station list and the current weather snapshot into your selected FSBuild directory and then you can use the "wind aloft" feature as usual.I know, that you have to execute one additional step, but it's easier, than changing always the regional settings :( And hopefully the flaw in the code will somtimes got fixed.RgdsReinhard

Hi Jim,I looked now even more in detail in my ASV 6.5 installation and I found a detail, which might be of interest for you and Damian. In ASV 6.5 the weather station file was NOT written at every download! This file was statically installed and got updated from time to time with a new build.With ASA/ASE this was changed. The file is updated with the download of the weather. So it possible add or remove weatherstations on the fly.So the major change was, that you introduced this download and writing of the stations file. With ASV 6.5 you just distributed one file with one format to all users independent from their regional settings.And this writing is not consistent in terms of using the LOCALE.Hope this helps to eliminate this problem.RgdsReinhard

Hi DJ,That's exactly what I assumed all the time, that not the programmers (or better: the single programmer Damian) has changed something in the original code, but that underlying libraries have been changed. Libraries which are necessary to produce formatted output of numbers etc.If you look into the sample, then you can see, that in the file produced by ASE the third number uses the decimal point in comparison to the comma in the first two numbers. So somethings isn't clean.So I am totally with you - the underlying libraries are now using LOCALE support - ASV 6.5 has used the same calls but other libraries under the hood. That's exactly what I wanted, that the programmer should check. And in fact they produced a third number in the past, which is now 0.0RgdsReinhard

Jim,Do you believe, that these two files have the identical format? Both have been created on the same machine with LOCALE set to German(Austria) at the same time. The ASV 6.5 format is compatible with FSBuild - the ASE format isn't. Why is it so difficult to accept, that your programmers have changed something? It's obvious, that there is a difference.RgdsReinhardASV6.5AGGH,-9.421,160.052,9,9.1 AGGL,-10.7,165.8,3,10.1 AGGM,-8.32,157.262,2,8.4ASEAGGH,-9,417,160,050,0.0 AGGL,-10,683,165,800,0.0 AGGM,-8,317,157,267,0.0

Hi,I really appreciate, that now Hifi has returned back to the old style of proactively adddressing errors by releasing interim hotfixes and testing them interactively with their users. That's what I really missed in the last few months.Maybe you have the chance to look during your debugging sessions at this topic again. If we as international users could get back our old (but working) format again for integration with FSBuild without changing our LOCALE everytime for using ASE, this really would be fine. So please continue your current user-oriented spirit.RgdsReinhard