jackharpenden

Hello, If you're utilising the latest AIRAC cycle then this might be your problem - viewtopic.php?f=5&t=1065 Go back to Navigraph and download revision 2 of the AIRAC and you're problem should be fixed. Jack

Thanks Urs! Jack

I have the same problem too. Although everything on the DisplayUnit seems to appear correctly, despite the messages. Jack

Hello, While browsing the Avsim forums I found this - http://forum.avsim.net/topic/372470-aiv ... efb-works/ I'm not a Prepar3d user, but it seems someone can make EFB work with it. Thanks, Jack

When I've got some decent time on my hands to thoroughly understand and learn the US procedures I might try some VFR on Vatsim state side, and eventually may then give PilotEdge a go. Thanks for the response! Jack

Hi Keith, It's nice to see the creator of the network here to accurately answer questions. Looking at your VATSIM stats, you've been quite an active member in the past and you're still active on the Vatsim Forums, which is nice to see. Just something to ask, as from what you've said I'm quite interested in PilotEdge. I've always felt that there's really not enough VFR/GA flying on Vatsim, which is a real shame, but at the same time I'm guilty myself of mostly flying "big-tin". Does/will PilotEdge only every cover parts of the United States? As a progressing PPL trainee in the UK, the procedures are somewhat different over the pond, and what I'd love to be able to practice is the UK VFR procedures, where all parties know properly what they're doing. Thanks, Jack

It's a shame Navigraph can't just sort it out. If it's easy enough for users to modify the navdata then surely for them it's as easy as anything! Oh well, I guess Navigraph do a bit of a service for us all - otherwise we'd never have even recent data. Jack

Actually, yes, I'd forgotten about that. It may well be fixed. I'll try it later today. Sorry for causing confusion! - I'll let you know whether it works. Jack

I've also had the same problem with that same bgl file for Kiev. Jack

Hi Brad, See this - viewtopic.php?f=5&t=923#p5661 Not a particularly old post! Hope this helps, Jack

Probably, yes. Did IVAO users always see all traffic before the latest EFB version? If so, perhaps the changes made to improve the visibility of traffic in the latest version has benefited VATSIM client users but not IVAO users. It might be a good point to switch to VATSIM, it's much better anyway! Thanks, Jack

Since the last build I haven't spotted any missing VATSIM traffic at all - even when flying the NGX, where previously I have had it show nothing at all. All working well for me Thanks, Jack

This is also something I'd like to know. I've seen it on so many occasions yet I don't know what its significance is. Jack

There's no need for it to be equal. I've always just left EFB's setting on unlimited and just changed vis ranges in FSInn. I vary the range set in FSInn depending on how much traffic is in the area. i.e. If I'm going long haul across the atlantic (at times other than Cross the Pond ) then I'll have it set to 100, but in a terminal environment I'll set it to 20/30. It's always nice to be kind to the VATSIM servers too, as I think officially they recommend leaving it at 20. Thanks, Jack

There seems to be a more serious problem here. Ticking the box for kph just appears to make the speeds look plausible, but they're still wrong. I'll be posting in the Beta Tester forums later with some findings. Thanks, Jack

Hi Todd, It's interesting that you mention that as I've also noticed this. In EFB's Online settings there's a tick box for when the pilot client provides the speed in kilometres per hour as opposed to knots. Ticking this option will solve the issue, and show the speed in knots once again. However, both FSInn and SB provide the speeds in knots anyway, so there shouldn't be the need to tick the box. In an earlier beta build of 1.3.2 there was an issue where it began to show altitudes in metres instead of feet, this was then fixed, but it's possible that when this bug was added that metric speeds were also implemented by accident. Urs, Could you look into this? Thanks, Jack

Hello, According to the forum rules please sign each post with your first name. FSX will only display online traffic if it's within FSInn/Squawkbox's visibility range. EFB only show's traffic that you can see in FSX. So you need to check that the visibility in your client is set and that the aircraft are showing in FSX, if this is the case with traffic then the aircraft should show in EFB. Thanks, Jack

Richard, EFB uses FSX's data for Aerodrome charts and approach charts, as opposed to various aircraft's use of AIRAC data. - This means that what EFB displays is FSX's actual situation, e.g. the scenery and magnetic variation in FSX will likely be out-of-date for many aerodromes and the EFB approach charts will reflect the actual frequencies and courses. Also if an airport has an added ILS which your scenery doesn't include, then this ILS will not show in EFB. Overall if you want to fly the runway's actual course as it is in FSX then fly what EFB lists, rather than what the AIRAC gives, as this is what the situation is at the RW aerodrome, which often won't be correct for your FSX scenery. Thanks, Jack

Hello, I use this, as it covers the whole world's airports. - https://pilotweb.nas.faa.gov/PilotWeb/ Below "NOTAM Retrieval" change the drop-down to "ICAO". Then just type the airports ICAO in the "Locations" box. For UK and UK GA flying I use this website, as it plots them onto a nice map. - http://www.notaminfo.com/ Thanks, Jack

Hello, It'd be problematic if it was stickied as whether you have the up-to-date runways or runway numbering depends purely on your scenery. For all airports that I fly to I'll look for some freeware scenery, a free AFCAD or if I feel I'll get my money's worth out of it and if there's one available then I'll buy a payware scenery. If somebody only had default scenery then you could sticky a file with gathered information only for to update the default scenery. This might cause confusion though. Thanks, Jack EDIT: Urs posted while I was typing. You've got two answers now

The installer should only create these folders where you've installed the DisplayUnit, not on the DataProvider's computer. Check again, but this time look on computer number 2. There is nothing wrong with not having those folders on your computer 1. As you specify that your computer running the DisplayUnit is on XP, then the folders should be located here: C:\Documents and Settings\[user Name]\ My Documents\AivlaSoft\EFB\UserData\... Thanks, Jack

Urs, I think you've misunderstood Clive's request and he's brought up something that I've also been wanting. The current library feature isn't aircraft specific meaning that you'll have to create your own sub-folders and all of the other documents, possibly specific to different aircraft will also show. What I believe Clive is recommending and what sounds like a good idea to me is to be able to click the "Checklists" button in the top-right hand corner (or with a new button) and to be able to access documents specific to your current aircraft which the user specifies. For example you could use the button and perhaps have access to the FCOM, QRH, FCTM and any other checklists or other documents in the PDF or other file format - this could be presented just as the checklists are currently, but leading to the documents instead. The current checklist feature using the XML files is great also, but this would be handy as an extra feature. Thanks, Jack

Yes, any changes to the activated scenery of FSX will require a re-scan in the DataProvider. It's required to show the correct chart when doing anything from adding a simple bgl file to the Addon Scenery folder through to ticking scenery in the Scenery Library dialogue or activating scenery in a separate applet, such as ORBX's. If you don't scan and visit the airports where you've changed the scenery you might well experience errors or crashes of EFB, and of course have the wrong data an details on the EFB charts. Thanks, Jack

Hi Will, Might be a silly question, but have you re-scanned the scenery folders in the DataProvider? - Through clicking on Data->FSX Scenery Data Update Jack

Jean-Louis, I've always known that yes, they're ICAO short coordinates. When I first saw them I found them quite confusing to get my head around. Your examples could also be written in the slightly longer form too, e.g. 49W08=49N108W. There are lots of ways to write coordinates Jack