dts

have been flying online with ivao, no problems with the online traffic, that is with NGX latest SP and also latest EFB update

Traffic is an issue with the NGX, this is not just related to EFB, but also all AI programs and online clients so until PMDG sort this issue out, then there is not alot Urs can do i expect

this is a strange one, even after deleting all after the 4000, i still cant get it to show 4000 on the chart.

this makes me think that because it says EXPECT and not hard an fast this is why they dont enter into the arrivals

1, can i ask if the altitude constraints are in the airac for your FMC, 2, are all these in the US, 3, the other STARS are they for the same airport or a different one

I agree, i would say that 99.5% of the data is correct, and the issues I have come across tend to get fixed for the next airac cycle, and the thousands of lines of code that make up an airac cycle I dont expect 100% It happens in real like, my friend had to enter each flightplan by hand because the airac cycle that was on his FMC was incorrect, so this involved more time preparing for his flight as every waypoint had to be entered very tedious he informed me. So bearing in mind this is virtual, and we pay a mere fraction of the price for airac cycles i think we can accept small mistakes

No this is not normal, Navigraph will update them and should appear in the next airac update

This is a navigraph issue with a lack of detail for the approaches, below is what I believe it should look like when i amended the details. STAR BULLZ2 FIX BULLZ FIX TEDDY AT OR ABOVE 10000 FIX KRENA FIX COGSS FIX SOOLU FIX KURKK FIX VULCN AT OR ABOVE 7000 FIX HIMGO AT OR ABOVE 4000 FIX LOMEZ 4000 HDG 093 VECTORS seems that navigraph are missing a number of things out these days, but with the amount of data and the amount of different addons they supply i am not surprised, just put it on the forum and hopefully they will be able to update it. we seem to be adding to the list of things that need to be changed with the airacs for EFB, maybe we could give a link to navigraph for ONE post with the current AIRAC highlighting mistakes for them to fix rather than individuals posting on there forum.

yep very strange but that did seem to work,,, ummm I will keep testing to see if this continue to work

This is a NGX problem, but we seem to be seeing the effects with AI / Vatsim / Ivao traffic, hopefully PMDG will come up with some kind of solution or idea of what is actually happening.

thats what i was thinking

sorry i think i may have confused you , if for instance i had more than one standard company route but took me via different waypoints, the format that i use is the iata code s for the airfields and then a number or letter sequence behind it to determine the routing so for instance EGSS-LFMN i could go via CPT, SFD , DVR , LYD etc, so my code would be STN-NCE-XA {this would be the code for a cpt departure) STN-NCE-XB {this would be a SFD departure) an so on, this code would stand for all the different flightplans saved whether it is EFB PMDG or FSX flightplan, as this code would be the same for all of them. William, My idea for version 2 was to have a ATC briefing page within EFB, this is where you enter all your data and this then transfers as required to different flight handles, so that way you enter the data in once place and this is then transferred to the rest of the places when you save it, but also acts a a one stop place for weather info and sid /star info and so on , rather than having to write things down or look in different places for the info, it would all be there and

whilst we are on the subject of exporting flightplans, can we have a box that you can enter the flightplan name i use standard routes so by entering a coroute into my fmc i can bring up my flightplan, so for example todays flight i flew LIMJ-EGSS so i entered AOL-STN-XA so this tells me what flight route i will be using, but at the moment i have to change each file name in the save box, but a window giving me an option of what to save all the flightplans at the same time would be good. hope this makes sense. and this is for version 2 Urs, i dont want to stop you developing any longer

format for IVAO [FLIGHTPLAN] ID=RYR36BT RULES=I FLIGHTTYPE=S NUMBER=1 ACTYPE=B738 WAKECAT=M EQUIPMENT=ZSRWYP TRANSPONDER=S DEPICAO=EGSS DEPTIME=1012 SPEEDTYPE=N SPEED=352 LEVELTYPE=F LEVEL=190 ROUTE=CLN L620 REDFA DESTICAO=EHEH EET=0044 ALTICAO=EDLV ALTICAO2=EBCI OTHER=REG/EIEFL COM/TCAS RVR/200 OPR/RYANAIR DOF/110812 A/BLUE/WHITE/YELLOW ENDURANCE=0453 POB=86 MTL=B738RYRWL hopefully this could use as i suggested in my wishlist some more information viewtopic.php?f=4&t=562

I managed to edit it with ADE before i read this post and compiled it as a FSX BGL and all is fine, so I am guessing as you said there was something in there that FSX didnt recognise