WebMaximus
-
Posts
188 -
Joined
-
Last visited
Posts posted by WebMaximus
-
-
Some time ago I bought the Santorini X addon scenery from Aerosoft and today I was planning to do my first flight there flying from ESSA and while entering the route in EFB I received the warning message you always get when there's a problem with the runway assignments. In this case the problem was/is that in the scenery only runway 16L/34R is available but in real life and also in Navdata there's also a 16R/34L runway.
Normally I'm able to fix these kind of issues by using the Runways.txt file and add whatever needed but if I understand the instructions in the Runway.txt file there's no way to fix this kind of issue when the runway exists IRL but not in FSX, is that correct?
Makes sense because how would you be able to fly into a runway that doesn't exist
Since I'm pretty sure I'm not the only one with this problem with LGSR (which seems to be the same also with default FSX scenery) how did you guys fix this problem? Guess the easiest way is to simply ignore the warning...?
-
Well...not a big issue but sometimes it's very convenient to be able to look up a VOR or NDB by it's name when you're flying online in a heavily busy airspace and the controller gives you a direct-to instruction using the name rather than ident so if you're able to fix this it would be great
-
One thing I've noticed is VORs (and might also be true for NDBs) are not presented by their actual name in the Direct-To dialog but when looking at the map their names are displayed correctly.
As an example I'm currently enroute ESSA-EGLL and received a direct-to from Sweden Control to a VOR called ALS where the full name is Alsie. When I tried to find this one by it's full name in the direct-to dialog I couldn't find it but when looking on the map it's marked both by it's ident (ALS) but also by it's name (Alsie) - see the screenshots below.
Shouldn't the full name also be displayed in the direct-to dialog in the Name column?
-
Hi Urs,
I'm using the latest version (1304) but found out there was a later revision which seems to have fixed the problem so all is good
-
Just checked the METAR for LFMN and heard a strange beeping sound for a split second and then I checked the Data Provider window and found the following error messages
Error - Cannot find element 'RNW' in approach procedure VDM22L AT LFMN
Error - Cannot find element 'RNW' in approach procedure VDM22L AT LFMN (repeated...)
Error - Cannot find element 'RNW' in approach procedure VDM22R AT LFMN
Error - Cannot find element 'RNW' in approach procedure VDM22R AT LFMN (repeated...)
Not sure if this indicates a problem with EFB or the AIRAC data...?
-
Ok, thanks anyway for looking into it Urs.
-
Hello Urs,
Have you been able to find any reason why the DU gets minimized in the way I described?
-
Ok, got it!
Thanks Urs.
-
This is a minor issue but from time to time (especially if choosing a SID/STAR and then backing out with cancel) EFB for some reason gets minimized by itself and I then have to click on it twice in the Windows Task bar to have it restored to normal size. Any idea why this happens? And again, it doesn't happen all the time but only from time to time.
Then while I'm at it...is there any way to preset the map scale for the destination ground chart? I often find myself manually zooming in on the ground chart after I landed to clearly see the names of intersections to make sure I vacate at the correct one when having been assigned one by ATC and considering you're usually a bit busy right after planting the gear on the ground it's a bit distracting having to zoom in on the EFB destination ground chart manually...would be great if I could set the scale before landing. Or maybe it's just some setting I missed...?
-
Always an equally impressive support, thanks Urs!
-
Thanks Urs, I'll give it a try and see what happens.
-
Sounds great, thanks Urs for looking into it!
Since you say EFB reeds the ILS frequency from the BGL would a temporary fix be to remove one of the lines from the text file?
-
On a second note it seems the problem is not as easy as simply removing one of the lines because in fact they are not totally equal, see the answer below I received from Richard at Navigraph.
Hi again Richard,
I believe I have found the "problem" with EDDF 07/25R ... The problem is that EFB doesn´t support multiple ILS frequencies.
Here a short part of the airport-file:
FRANKFURT/MAIN EDDF07L09186068 50.037056 8.497078110.3006800305 <- IFEL
FRANKFURT/MAIN EDDF07L09186068 50.037056 8.497078111.7506800305 <- IFNE
FRANKFURT/MAIN EDDF25R09186248 50.045825 8.533717111.3524800353 <- IFWR
FRANKFURT/MAIN EDDF25R09186248 50.045825 8.533717109.7524800353 <- IFNW
Both runways had two ILS frequencies and therefore the 07L/25R are twice in the file. It looks like, that EFB can´t handle this but I can´t remove it because both are identical, excluding the frequency and the glideslope (3°/3.2°). I don´t know which frequency will be used in FSX and/or addons. Sorry Richard, but it looks like, this is really a EFB issue and should address there.
Thank you,
Richard
-
Ah, that's it. Thank you very much Jerry!
-
Still same problem after installing rev 2 of the latest AIRAC cycle, am I the only one seeing this issue with Aerosoft's EDDF and where exactly is the problem - within the scenery, the NAV data or EFB? Would be the NAV data I guess since that is the only thing of the three that has changed lately...
-
Just downloaded the rev 2 of the latest AIRAC cycle and installed it but never got the message I usually get from EFB when starting it after installing the NAV data so let's see what happens on next flight. But maybe there isn't a message from EFB for new NAV data unless you installed a completely new AIRAC cycle...?
-
Wasn't aware a rev 2 had been released so thanks for the HU, I'll give it a try!
-
Today I had a strange problem I haven't seen before, when I loaded a saved EFB route from ESSA-EDDF I received the error message you normally get when the runway identification between the nav data and FSX doesn't match. Was very surprised since I did this flight many times before without any problems.
Looking at the DataProvider window I got even more confused because it said 07L and 25R couldn't be assigned to an FSX runway but looking at the last line in the DataProvider window it reads 'Available FSX runways at this airport are as follows: 18, 36, 07R, 25L, 07C, 25C, 07L, 25R
What could cause this?
-
I received this reply over at VATSIM's forums so let's just hope they'll eventually find a permanent fix for whatever is causing this to happen.
Thanks for sharing it... it just happens, and we are trying to understand why. It seems to be related with another problem we have when servers disconnect briefly.
Thanks. Luca
Anyway good to know there's nothing wrong with EFB
-
I received good response over at VATSIM's forums and I was suggested to consult this thread so I posted the question there.
Hopefully the issue will be addressed soon.
-
Thanks Urs for confirming. Strange though is that when I tried getting the ATIS using the ATC module in FSInn (the VATSIM pilot client) I was able to.
I'll try and post a question about this over at the VATSIM forum but maybe you have some contact at VATSIM you could report this to? Obviously something changed/happened at VATSIM very recently because I didn't have this issue yesterday for example, today was the first time I saw this.
-
Just talked to a guy acting as ATC on VATSIM but according to him nothing changed on VATSIM regarding how ATIS is entered so it appears to be a problem with my EFB.
Hope there's a quick and easy fix because I really miss the ability to get the ATIS this way before talking to ATC.
-
Up until now I've always been able to get the ATIS info by hovering with the cursor over the ATC(s) listed in the frequency ribbon but now of all of sudden I don't get any info anymore, noticed it the first time today and same problem on two different flights now with different ATC frequencies and I even restarted my computers in between. Read in the documentation for EFB that when you see an 'i' beside the frequency that indicates there's ATIS info available but I don't get any of those now.
Did something change at VATSIM and how ATC enters the ATIS info or do I have an issue with my EFB?
TIA,
-
Actually I followed you all the way this time
I'm using Aerosoft scenery for ESSA and will try modifying the BGL the way you suggested.
Looking forward to version 2 of EFB!
A problem with available runways at LGSR
in EFB v1 (Read only, no longer supported)
Posted
Yep, did run the FSX Scenery Data Update in EFB so guess maybe the problem then is I have a duplicate BGL for LGSR. I guess I could try find it manually but I remember reading about some utility that would let you search for these kind of things but I can't remember the name of it. Anyone in here knows what utility this might be and where I could find it?