lonewulf47

Hi David, Sorry, I fail to understand clearly what you mean. What KEUG Add-on have you in use and where is it installed? Did you do a complete database-rebuild? Can you post a screenshot of the information window of KEUG? And finally, can you please post The Support Files?

Ok, Jean-Luc for the moment I'm out of ideas. I'll have Urs to step in here for more analyzing work. It would be helpful if you could again provide a set of Supportfiles according to this guide https://forum.aivlasoft.com/topic/3046-how-to-create-a-support-file/ It will give us a bit more information than just the Logfiles. Thanks for your cooperation!

Yes, it looks that you use Country specific text settings. This conflicts with many files which are using the ASCII (ANSI respectively) character set. To change this you will need to use the settings shown in the screenshot below. I'm using the German Version of Windows, but you may find your way through when looking for Region and Language. in particular the Format "Windows Display Language" is important. You don't need to change the Language, just use the "Windows Display Language". In the "Additional Settings" Dialog (weitere Einstellungen in German) there is a non-printable character (lower cirlcle) in your setup which causes the error.

Yes, it looks that you use Country specific text settings. This conflicts with many files which are using the ASCII (ANSI respectively) character set. To change this you will need to use the settings shown in the screenshot below. I'm using the German Version of Windows, but you may find your way through when looking for Region and Language. in particular the Format "Windows Display Language" is important. You don't need to change the Language, just use the "Windows Display Language". In the "Additional Settings" Dialog (weitere Einstellungen in German) there is a non-printable character (lower cirlcle) in your setup which causes the error.

https://forum.aivlasoft.com/topic/3046-how-to-create-a-support-file/

Hello xxx ??????? (please observe the Forum Rules) Please provide a set of Support Files.

Hi Jean-Luc, Can you please provide a set of Support Files? It looks as if the Client were "sticking" at a certain point. The message "loading..." is still present. Have you tried to restart the Client?

Thanks for providing the Logfiles. Unfortunately they do not show ANY information about a freezing Client. According to these Logs everything is normal. Could you try to break down the problem by starting EFB v2 and the Sim, but NONE of the other Add-ons? What about processor-power? I'm not familiar with the AMD64 family...

Hi Jean-Luc, We need some more information for that. Server Build #, Client Build #, Database Provider and AIRAC Cycle. Does the map show normally? What is the position of your A/C? What steps do you follow to load a flightplan/routing? Can you sen us at least one example of a non-loading Flightplan?

Sounds reasonable, kinda same here...😉

Hi ??? (please observe the Forum Rules) Yes, unfortunately this is a known issue, which still need some rework for airports with Center RWYs. See here: https://forum.aivlasoft.com/topic/3155-known-issues/ As this requires considerable changes in the database layout it can't be corrected within a short time. STAR's for LEFT and RIGHT RWYs are not affected. the JEDKO VIA (=Approach Transition) is coded exactly this way in the ARINC database as a extension of the approach centerline by approx. 12 NM (see below)

Yes, that's true. We're now in the situation where it is difficult to decide what the User really wants...😃 Either we present the Update Request at each startup of the respective segment or we accept the rejection for update and give the User one day to wait until the next "update proposal" is presented. Whatever we choose, it will never be satisfying all users...😉

ok, that's another method, however only for knowledgeable users...😃

Hi Andy, Check the update path C:\Users\<your name>\Documents\AivlaSoft\EFB2\Client\Updates (for standard installation). Apart from the "latestVersion.txt" there should be an EXE file. Run this EXE by rightclicking -> run as admin. This should update your client to your last version.

Hi Joerg, Please indicate the Build # of both Server and Client and post the Support Files here or alternatively send them to support(at)aivlasoft.com.

Hi David, Do you use the same AIRAC Cycle in EFB as used by PRO ATC? Which EFB Builds # are you using? Could you please post the routing in question?

Hi Florin, These messages point to a corrupt minima file, in this specific case I suspect the EHAM.txt for Amsterdam to be the culprit. Did you do any changes to that minima file?

Hi Frans, Thanks for reporting. I have no idea what caused this but nevertheless it's great to hear that it works now as intended. Sinterklaus seems to have come up with a nice present 😃. Enjoy!

Great to hear that things are sorted out 😃 Thanks for updating.

I work with SimpleCam on P3DV4.4 without problems. Make sure SimConnect is properly installed. No need to delete key asignments.

Thanks for the Settings File. Could you please make a screenshot with the error message displayed?

Ok, so far, so good. This means that the installation is properly working. The part that I do not understand is the warning message that you mentioned at the beginning. Did it come up again when working on the Configurator?

Hi Frans, Don't worry, we will get it running - sooner or later...😃. So I take it that in the mentioned directory there is the required "standard.xml" file located? It is a bit difficult to find the way through everything, as I have no insight into your computer's setup. Basically if the abovementioned path is correct and the required "standard.xml" file is present there, SimpleCam will be able to read this file and will not come up with an error message. Apart from that of course nothing is happening as SimpleCam is residing in the background and is only reacting on the 10 different keystrokes, as soon as they are programmed. So the first and most important thing is to make SimpleCam starting up without the error message. For initial testing there is no need to start the simulator. Just start the Configurator and press "delete key assignments". Then check in the mentioned directory whether two additional Files "20181129174942.Standard.xml.simpleCamBackup" or similar and "removedKeys.txt " were created. This is the first step to see whether file acces is properly working.

Hi Roger, Thank you very much for yur kind words. There may however be something wrong with your interpretation of the Airport symbology in EFB v2. As long as you didn't change the Color Profile to your personal liking, the color coding of the Airport Symbol (-> Asterisk *) is as depicted in the Manual "5 Client", Chapter 8.1 Examples. A circle around the Airport Symbol means that this airport is an AddOn of any kind. Which BGL is used to draw the airport can be seen in the (i) Information Window (Button just left of the Airport Name on Top). It's the uppermost of the files listed under "File(s)".

Hi Frans, To be honest, I'm not very knowledgeable about FSX:SE and it's installations paths. Did you check the abovementioned path for correct spelling? ( -> contro;s ...) and did you check whether the required file "standard.xml" is located in the indicated path? Other than that I cannot think of anything that would prevent SimpleCam from loading. The Error Message usually points to a missing file access.