freddy_

I am running EZDOK 3 (specifically v3.0.1.84) with P3D v4.5 HF3. As a user of P3D v4.5, I am unable to use a higher version of EZDOK, but the v3.0.1.84 works perfectly fine with my setup and gives me no issues whatsoever. I have had no issues wit EZDOK and the latest Windows Updates. Be aware there is a bit of a learning curve with EZDOK if you're not familiar with it, but the default settings work well enough if you don't want to dive right in. That said, once you get the hang of it, it is extremely flexible and you are able to get very realistic results with it.

"...not some garish multi colored mess stuffed with browser ads" I could not have said it any better. 🙂

Ha. You're welcome. 10 years later huh! 👍

@albar965 OK. It's disappointing, but it is also understandable and fair enough. 👍 Once again, thanks for a fantastic program. Keep up the excellent work!

Sorry for revisiting an old thread. I have only just discovered Little Navmap. Wow, I have been missing out. This is a fantastic program! As someone who works in the IT industry, I know how much work has gone in to this. Thanks Alex! I am also experiencing this hieroglyphs/corruption issue with my Majestic Dash 8 (Training Edition) v1.025a in P3D v4.5 with HF3. I am using Little Navmap 2.8.12. Intriguingly, the first time I used Little Navmap with my Dash 8, flight plans made with Little Navmap, using the supplied Navigraph Airac cycle 1801 which comes installed by default with Little Navmap, did load in to the Dash 8 perfrectly. A few days later, it made sense to update Little Navmap and my sim with the latest Navigraph Airac cycle ... that being 2401 at the time ... to get everything synchronized nicely ... and from that point, flight plans made with Little Navmap have had the hieroglyphs/corruption issue with the Dash 8. A week or so later, I updated the Navigraph Airac cycle again to 2402, but the same result persists ... flight plans made using Little Navmap continue to show this hieroglyphs/corruption issue when loaded in to the Dash 8. A quick experiment shows that if I create a direct flght plan with only a departure and arrival airport (ie, no navaid or waypoint routings in the plan), then the flight plan appears to load correctly in to the Dash 8 (but, just because I see no hieroglyphs/corruption in such a short flight plan, with no navaids or waypoints in the routing, I can't really be sure). That said, as soon as you add any navaid or waypoint routing in to that flight plan, the hieroglyphs/corruption issue occurs when you load the flight plan in to the Dash 8. Based on these obvservations, I assume this issue could have something to do with the Navigraph Airac data and how the navaids and waypoints are exported by Little Navmap in to the associated Dash 8 compatible .fpr file? At the moment, I am happy to use Little Navmap to create the flight plans, and then manually enter them in to the Dash 8. But, I look forward hopefully to any updates on this issue, or fixes which may come with one of the next versions.

A quick search of these forums will find you some information. And, of course, there is the FCOM ("PMDG-NGX-FCOMv2.pdf" is installed on your PC in the /PMDG 737 NGX/Flight Manuals folder). And, here's a few web pages which should also help to get you started: http://support.precisionmanuals.com/kb/a109/weather-radar-troubleshooting.aspx This one is "Boeing specific" but provides good information nonetheless: https://www.rockwellcollins.com/~/media/Files/Unsecure/Products/Product%20Brochures/Radar%20and%20Surveillance/Weather%20Radar/WXR-2100/MultiScan%20ThreatTrack%20Quick%20Reference%20Guide%20-%20Boeing.aspx http://www.smartcockpit.com/download.php?path=docs/&file=Collins_WXR-2100_Operators_Guide.pdf

Thankyou kevinh for the correction. Always learning, always learning. The FCOM says "At or above 10,000ft MSL, set LANDING light switches OFF". The Airbus FCOM is similar, and, from memory the Dash-8 as well. There are other checks performed at 10,000ft as per the FCOM(s) as well. But you can see why I mentioned the horn at 10,000ft as a reminder to switch off the external lights. As for the cabin altitude warning horn being different from the altitude alert C chord ... hmmm, the pitch of each of the sounds is quite similar ... I just assumed. Now that I think about it, yes, the altitude alert C chord probably is a little more subtle (I'm not in the cockpit right now to test, so I'm going from memory). And, yep, I think they are indeed named differently ("Cabin Altitude Warning" versus "Altitude Alert C Chord") in the FCOMs as well. As I said, always learning, always learning. :smile:

I think Ralgh has it correct. From what you describe, it is the altitude warning horn. A horn will sound (sounds like a car horn) when the cabin altitude goes over 10,000ft, AND also when you are approaching your preset autopilot altitude. At 10,000ft it is a reminder not only about cabin altitude, but also about external lights that are on after takeoff (such as takeoff lights) ... you're at 10,000ft so it's time to turn those lights off. The horn should sound once, and once only, each time an altitude is reached (ie, once at 10,000ft and then once at any subsequent preset autopilot altitudes). If the horn continues to sound, constantly, then that is a warning about a cabin pressure problem and indicates immediate action needs to be taken to rectify the problem. In this situation the flight crew would put on oxygen masks and then do the CABIN ALTITUDE WARNING OR RAPID DEPRESSURIZATION checklist.

No, you did not miss an update. If you are referring to the Navigation Display (ND) and the different colored shading that's showing in the YouTube video in the original post, then it is showing TERRAIN, not weather.

Kostas, Thanks for your (valued) input. "Predictive" versus "Reactive" windshear alerts. I was not aware of that. Always learning, always learning. Interesting. Based on what you've said here, it does sound like my suggestion above may not work. But, then again, might. Hmmm.

Locate the "C:\...Flight Simulator X\HiFi\ASNext_FSX\as_srv\Voice" folder on your PC. In there you will find a file called "pwsalert.wav". If you play that file you will hear that it is the ASN windshear alert sound. All you need to do is rename that file (in other words, keep that file as a backup) and then replace it with the one from the PMDG NGX. The one from the PMDG NGX is in the "C:\...\Flight Simulator X\Sound\PMDG\737NGX\CAWS" folder and is called "PMDG_737_egpws_sirwsh.wav". Copy the PMDG one to a temporary location such as the desktop, rename it to "pwsalert.wav" and then move it from your temporay location and put in to the "C:\...\Flight Simulator X\HiFi\ASNext_FSX\as_srv\Voice" folder. I haven't tested this, but I think that should do it.

Why is it used? I found this post in the Tech/Ops forum on the Airliners.net web page. I still don't fully understand ISA DEV, but this post does clear up some of the questions. Temperature Deviation (I apologise this is not a clickable link; but for some reason I am unable to get the "insert link" option working when posting.)

Another reason for starting engine 2 first is as follows ... If there has been a reason to use the APU for an extended period of time, then usual practice is to turn a LEFT fuel pump on to supply fuel under pressure to the APU to extend the service life of the APU fuel control unit. If the fuel quantity in the center tanks is sufficient, then the left CENTER tank fuel pump is used to prevent a fuel imbalance before takeoff. However, if the fuel quantity in the center tank is not sufficient, then the left AFT tank fuel pump is used. In that case, whilst the APU is running, a slight fuel imbalance would be created. Starting engine 2 first subsequently draws fuel from the opposite (RIGHT) tank(s) first, and therefore helps to correct the fuel imbalance before takeoff. Although, that said, using the APU for extended periods of time these days is something most airlines do not do (for economy reasons), and most airports also have set rules advising against it as well (I believe for noise abatement and probably pollution reasons).

Hilarious indeed! Excellent work! ROFL.

Question: During pushback, how does GSX handle the situation where ATC advises, "Orbit 737 hold position, caution other traffic" when maybe another AI plane or other airport vehicle is approaching? In such a situation, does GSX recognise this and momentarily stop the pushback to wait for the plane/vehicle to safely pass? Or, does it ignore it and continue regardless? Or, perhaps the pilot (me) has to do something to initiate a temporary stop? Etc etc.

I agree that the filename "uninstaller.exe" or "uninstall.exe" should be renamed. Here is a part-suggestion. Whenever you install something, you can look for the uninstall file and you can rename it to something more meaningful. Each time you install something, you find the uninstaller and rename it appropriately. Now whenever you look in the folder, you will see the (renamed) uninstallers and know which is which. HOWEVER, I said this was only a PART-suggestion. This will only work if the renamed uninstaller file knows which bits and pieces you want removed (ie, if it knows which program or software it is supposed to be uninstalling). Renaming the file merely changes the name, but the uninstall program may still uninstall the wrong software. If the uninstaller uses a text based config file (eg a .cfg or maybe .xml) file and you can find that file, then you can also rename that file appropriately. Whenever you do actually want to uninstall something, you would need to remember to rename the uninstaller AND its associated .cfg or .xml file back to the correct names, and, hopefully, it might all work. I'm not saying this is a good suggestion ... in fact, it's probably not even going to work. Nonetheless, it could be worth a try. Of course the best solution would be if the software writers, as per your appeal, did their jobs properly and correctly managed the files and folders they put on to your system.

I don't normally respond to these sorts of posts. However, in this case, I will. Opa has helped many. And, on many occasions, has also helped me. I learnt a lot from his posts to others and his responses to my own. As I write this, there is a lump in my throat and I feel like I am fighting back tears. Thanks Opa. You will be missed. I do hope threads such as these can be forwarded on to the family to give them a sense of how much their loved-one will be missed. My condolences.

Agreed. Like you, sometimes I can page through all the pages for an airport, but other times I am only able to look at 1 or 2 pages. Sometimes the PREV and NEXT buttons do not work (when this happens for me, one of the buttons does work fine, but the opposite one does not). Sometimes you press NEXT and the page count does not roll over back to page 1, but instead just keeps increasing and increasing, ad-infinitum, and you cannot go back. So, confirmed ... what you describe happens for me with Garrett's FMC as well. However, I don't have any problems getting the MENU, NAV DATA, AIRPORT IDENT features to work. All the features designed to search and display data work fine for me. (It's just that sometimes, once the data is displayed, the PREV and NEXT buttons do not always work 100%.) Whilst the FMC works for me for searching and displaying data (aside from the odd glitch with the PREV and NEXT buttons) ... I do have a pet hate ... that being that the pink flight plan line is not updated when you change from the enroute phase of the flight to the approach phase (selecting the desired approach and runway choice from the menus and then "activating" it). This is reflected in the Garmin GPS in the aircraft, with the pink flight path line changing to show the selected approach ... but the pink flight path line does NOT change in the FMC as it does in the GPS, instead it stubbornly continues to display the original enroute path straight to the airport without change. Other pet hates are the DTO function not allowing me to enter vertical navigation options for speed/altitude, and not being able to follow vertical navigation for an activated approach. It also does not do more than 6 pages for a flight plan making its use for long-haul flights quite restricted. There are also a few other obvious bugs and a number of various niggles providing the impression the work was not fully finished, or this is not the latest up-to-date complete version. However, despite this, Garrett's FMC can still be very useful ... and it is offered free.

On re-reading my own post, I see that it may have come across as though I was having a dig at some of the posts here. That wasn't my intention. I do apologise if that is the impression anyone got. The point I was making in my post is that I myself haven't had a bad experience with PC Aviator (Australia) and that I normally don't jump to any conclusions based on a bad experience that another person may have had.In your case altstiff, bad customer service, three months duration, no returned phone calls or emails, not even from Robert ... I agree that you have reason to complain ... I would too given those circumstances. Fair enough. Personally, I am still happy to deal with PC Aviator given the service I have had from them over the many years I've done business with them. However, if I had been on the receiving end of the experience you mentioned above, then I admit that I too would probably be reviewing that decision one way or the other as well.

I have been dealing with PC Aviator (Australia) since their establishment in 1990. I was lucky that, for me, they were only a short drive away and I could always actually go there, browse, talk, make an informed decision, and purchase. They moved from that location to a new location which was still at driving distance for me. With the exception of Flight Simulator itself, I have made ALL of my purchases through PC Aviatior ... joysticks, throttles, pedals, scenery packages, AI traffic software, etc. They have since moved from Melbourne to Brisbane, which of course is no longer driving distance for me unless I am REALLY dediated. Suffice to say I have not needed to purchase anything from them since that move. But, I have had correspondence with the Brisbane office (via email) and promptly received a reply and appropriate answer the next day.For me, PC Aviator has always been friendly, efficient and helpful. In the early days I dealt with Robert, until he moved to set up in the USA; these days, here in Australia, it is Dean. Both of them have always been informative, knowledgable, and a pleasure to deal with.In short, I never base my own decisions on one person's bad experience. In many cases that bad experience turns out to be a one-off, and usually has a logical and resonable explanation once the situation is investigated and/or resolved. I see no reason to jump ship based on a forum thread about a lost order and missing emails. Heck, how many times have people emailed me in the past, both at work or at home, only to have those emails get lost in the ether? It happens. Not returning phone calls, or lack of customer service skills is a different matter, and I can understand taking issue there. Fair enough. I do customer support for a living, and believe me, it is a difficult job, and an art and a skill to do it well. So I am usually happy to cut some slack on ocassions, depending on the circumstances and situation.As a long time customer, who has never had any issues whatsoever with PC Aviator, I will continue to deal with them. But, of course, my experience with them is based on the Australian store ... I've never dealt with the USA store.

Thanks Opa for the confirmation. I was just about to check, but noticed your post.

In the Virtual Cockpit (VC) there are two square buttons labelled "BRG" on the left hand side of the panel, below the clock.The top button toggles the flight display to show the VOR1 pointer, ADF pointer, or off.The bottom button toggles the flight display to show the VOR2 pointer, ADF pointer, or off.I don't use the 2D panel and I'm therefore not sure if these buttons are on that (and I'm also at work where I cannot check).

I don't specifically have the answer for you. However, you might like to check out the stock F/A-18 details and guides at the FSDreamteam web pages and forums.There, amongst other things, you will find a free "F/A-18 Printable Avionics Map" (PDF).There's also a great flight planning guide which discusses flight plan use specifically with the F/A-18 avionics.And a range of other handy material relating to the stock F/A-18.Links:FSDreamteam Forums: http://www.fsdreamteam.com/forum/FSDreamteam Unofficial F/A-18 Discussion Forum: http://www.fsdreamte...x.php?board=4.0 (This forum is where you will find the "F/A-18 Printable Avionics Map" etc).

Is the airport or navaid in the list HIGHLIGHTED AND FLASHING. If it is, ONLY THEN can the list be scrolled. It is a little hard to see in the screenshot below, but the second airport in the list is highlighted in light blue and is also blinking (although you obviously cannot see that in a still picture). To do this, you must first PUSH the knob to put the list in to CURSOR mode. To push the knob, your hand-pointer must be positioned over the knob but will NOT have a "+" or "-" in it. With the hand-pointer over the knob and no "+" or "-" in it, if you click the mouse, the knob will be pushed. Once in cursor mode, the airport or navaid will highlight and blink. Then you move the hand-pointer slightly ... to the edge of the knob (as shown here in the screenshot) and the "+" or "-" will appear depending on which side of the knob you are on. NOW you can scroll the list (either click the mouse or use the mouse-wheel). You scroll to what you want and then click the ENT button (or the CLR button if you change your mind and wish to simply return to normal operation).Getting the correct location of the hand-pointer can be tricky ... but it can be done. And once you've done it a few times, it almost becomes second nature such that you can do it without much thought at all.Keep at it, you'll get it.

I have the current version of AVG (2011 Free Edition) installed on my PC ... Windows 7 64-bit ... and have no problems at all with it. It has a neat new feature called "Game Mode" (found in the Tools menu, Advanced Settings). I have ALL the features switched on, including that one, AND I run FSX at the same time with all of that still switched on. With the PREVIOUS version of AVG, I needed to disable the resident shield whilst flying or else I would suffer a frame rate hit. But, with this new version of AVG and the "Game Mode" option I see no issue whatsover with loss of frame rates, even with resident shield still turned on. In fact, I tried a test with "Game Mode" switched on but turning off resident shield to check the frame rates ... and there was neither an increase or a decrease with resident shield on or off. No difference. In short, I have no issues whatsover running this latest version of AVG, even with ALL of the features turned on and running FSX at the same time. Regarding other posts in this thread, I have not had need to try to turn AVG off and therefore I cannot comment on that aspect of it. However, in closing, I do recognise this is *MY* particular experience ... and, for others, and different machines etc, mileage may certainly vary.