lonewulf47

Hi Rolf, Thank you for the update. Most important thing is that it works for you now. It must be said that - unfortunately - with FSX:SE we sometimes encounter problems that are not present on other basic FSX Installations. the reason for that is completely unknown for us and it is very difficult to trace such problems, as I personally do not have Steam on my Computer and I do not have any plans to change this as Steam has quite a "life of its own", so to speak. Thanks again!

Hi Wayne, I'm sorry to hear this. To make sure our installers are working as designed I did the following on one of my Test Systems: - downloaded the original installers from our website (Build #112) - uninstalled both EFB2 Server and Client using regular uninstaller - checked for remaining files, no files found - rebooted computer - installed Server and Client as per instructions - rebuilt 2 databases, 1 for P3DV4 and 1 for X-Plane11 - started EFB2, P3Dv4 and ActiveSky Everything worked as normal. The whole process including database building and starting the Simlator took less than 20 min. I'm simply not able to understand what happens on your system. In any case the installes are working as designed and no flaw in the whole installing process could be detected.

Hi Wayne, Well, this is very strange. It's about the same warning(s) that appear if your try to install when EFB2 is already running... I have never seen that and I also have never heard about such behaviour on a new system. Just to make sure I understood everything right: according to the first screenshots you seem to have installed the DbBuilder, but neither Server nor Client? Have you tried re-downloading the installers?

Jerry, No need to be annoyed. You don't need to backup your profiles and minima folders. This is done automatically. You might have missed the fact that after each install/update a copy of the folders \profiles and \minima with the extension *.bak is made. Just copy the contents of the *.bak folder into your original folder and everything is as before. For the profiles folder you may also delete the new "profiles" folder and rename the "profles.bak" folder to "profiles". No harm done.

Rolf, Sorry, the only such error I can locate in your logfiles is from serverLogfile-5, which contains data produced with the old builds #111.

Hi ??? (please observe our Forum Ruls and sign your post with your real name) As this is obviously a brand new computer, it looks as if there are problems with proper access rights. In any case do not run the installers by doubleclicking, but by right.clicking and using the tab "run as administrator". Use his on both installers. Later on you need need to tun EFB Server as Admin too. See here how to do that: https://forum.aivlasoft.com/topic/3621-how-to-run-efb-server-as-admin/ This is just one hint ot overcome your installations problems. Another might be that you deactivate your AntiVirus Software for the installations process. It is very dificult do do a proper diagnosis on a new system from a distance.

Thanks for reporting.

Bob, Thanks for reporting.

Gentlemen, please check this thread: https://forum.aivlasoft.com/topic/3806-loud-buzz-when-starting-client/ It's all about the same issue, which will be corrected soon.

Bob, Please, open a new thread on this issue. We don't want to mix different items in one specific thread.

To ALL: We are tracing this misbehaviour at present and we are positive that an update can be released soon. It is not dependent on the way of installation (remote or common), but only on certain specific installation configurations. Apart from this it must also be said that EFB2 is functioning normally despite this false Warning Trigger.

Bob, Can you confirm that EFB2 is working normally despite this warning? (That's at least what we expect as it looks that the client has finally registered normally).

Hi Michael, Please check this thread about the same error: https://forum.aivlasoft.com/topic/3806-loud-buzz-when-starting-client/ I presume that after this Error and Status Message have popped up, EFB2 is working normally. Therefore for the time being you can ingore it. We are investigating on the issue but for the time being as long as EFB2 continues working normally, you can disregard it. There is something going on that must be machine specific as it switches back and forth between various IP numbers and finally registers the client with what we assume to be the correct IP number. We might also need to investigate to what extent third party AddOns have an influence on registering.

Hi Bob, Nothing easier than that😀. Go to the Settings Page, Tab "Sounds", and mark the "Caution/Warning on Status Panel" line. The presently selected sound will most probably be "buzzer". Browse to the sound selection and select a suitable sound. I personally use "doorbell" for warnings. Sounds a bit less frightening...😁 Whatever sound you have selected, you can play immediately to check. What is more important for us to know is whether EFB2 continues to work normally (as it usually does) after this warning.

Hi Bob, The LogFile shows an error: 2019-09-10 20:06:33.149 Error : Could not add TCP client 127.0.0.1 due to: Object reference not set to an instance of an object. This is a mysterious error, that we have seen at very rare occasions. Normally EFB2 continues to work without any problems, so you can disregard it. I recommend to replace the Buzzer Sound to something more gentle like the Ding-Dong...😀 We will have te investigate what in particular causes this error on only a few machines. So far we haven't seen it in the combo Win10/Build #111, only with Win7/Build #111. TCP errors are very hard to trace, especially if they are kinda "self-sealing", i.e.the application continues to work normally. Sometimes it even disappears after rebooting.

Hi Bob, The "Buzz" is a warning. You should see the reason for it in the Status window and in the logfile. BTW, in the Sound Settings you can replace this sound by a more convenient one, if it is disturbing you too much.

Hi Jeff, Are you sure that it is a default airport in FSX? Unfortunately I can't say as I don't use FSX anymore. In P3DV4 it is not contained in the default colleciton. Maybe someone else still using FSX can shed some light on that? Whatever is contained in the default BGLs should also show up in EFB2. Did you check all the items as discussed in this thread? PRF filter on/off? Manually selected airport?

Hi Rolf, Form a distance it is not possible to determine the cause of this behaviour. Did you check the connection status of the Simulator on the status bar? What did it show? Did you wait a few seconds to allow the server to establish all connections? Did you check that no airport was manually selected at this time? It this problem reoccurs, we need the latest set of Support Files to check.

Hello ??? (please sign your post with your real name according to Forum Rules) Inorder to show up in your EFB2 you need to have this airport installed in your simulator, consisting at least of an AFCAD BGL or the ground layout. No present simulator features this airport as default, however there are already a few freeware renditions available.

Hi Michael, Now this indeed doesn't make sense as I don't see 3 parallel RWYs in my default installation. See screenshot. This is only with ORBX Global. I have no clue how this third RWY shows up on your simulator - unless you have a Photoreal Scenery of that part of the US. Then it would simply be "painted" on the ground by the photomap. But other than that - I have no clue!

Hi Michael, Well that's simple. The OLD layout consisted of TWO parallel RWYs 18L/36R and 18R/36L. That's what is shown in your simulator. The NEW (more actual) layout consists of THREE parallel RWYs 18L/36R, 18C/36C and 18R/36L During the Database Building Process EFB replaces the OLD RWY 18R/36L by the NEW RWY 18C/36C at this position. This way at least the actual procedures for these two RWYs 18L/36R and 18C/36C are available. However there are no procedures available in EFB2 for RWY 18R/36L as there is simply NO RWY at this position! As we are strictly following ARINC designations we have to attach the procedures to the matching RWYs. We cannot attach a procedure (no matter whether SID or STAR/FINAL) to RWY 18R/36L of the OLD (outdated) simulator layout as there is simply no such RWY available at this position. it's now named 18C/36C and the proper procedures are attached accordingly. This may sound a bit confusing but that's the only way to keep things in a reasonable way if an airport layout is enhanced by a third parallel RWY. Of course EFB2 cannot change the RWY designators in the airport layout of the simulator as these numbers are hard-coded in the respective APX26190.BGL

Hi Michael, Sorry, my bad! 😀 I was a bit too quick with my answer. I didn't notice that I had the X-Plane database active when checking. I rechecked on P3DV4's database and indeed, there is no RWY 18R/36L for the default airport. See attached ADE screenshot from the default airport. There is in fact nothing we can do from our side as the default airport is just missing this RWY. There are actually 2 possibilities: either someone offers an expanded BGL using a suitable means (e.g. ADE - Airport Design Editor) or you use a payware airport. Personally I use FSDreamTeam's rendition of KCLT. ORBX does not have any rendition of this airport. Don't forget: EFB2 can only draw airport layouts of installed airports - be it default or add-on. It always draws what what you see in your simulator!

Hi ???? (please sign your post with your real name, as required by our forum rules) I'm unable to confirm your report. See attached screenshot. All RWYs at KCLT are present. This is also default P3DV4. (removed invalid depiction of KCLT). Edit: See my second answer

Hi Chafik, As suggested by the Error Message, we need to see the logfiles. Please post a full set of Support Files. Please also make sure that no AntiVirus Program is interfering with EFB2. Whatever you run as AV Software, consider to excempt EFB2 from being scanned by the AV.

Hi Chafik, Undoubtedly the DbBuilder is running. WHY this is the case is not possible to say from here. The DbBuilderLogfile does not give any help in that respect. How would you suspect that the DbBuilder did not load all airports? At first sight I do not see any trace of that. For this wanring to come up the Server needs to detect a running DbBuilder process. You might want to look at the running processes on your maching with the TaskManager or a Process Explorer of any kind. In any case this is nothing that we can solve from a distance as it is a clear warning that the DbBuilder Process is running on your machine. Have you ever tried to start the Server from the dialogue at the end of the DbBuilder Process? This should start the Server in any case.