Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

ps1flyer

Members
  • Joined

  • Last visited

  1. For China, there is a recent new addition to the payware market. Check out "REAL CHINA BASE EXTENDED" by the FS Real China Team. It is available for rought 10 Euros or Dollar at Simmmarket, see http://secure.simmarket.com/fs-real-china-team-fs-real-china-base-extended-fsx-fsxse-p3d-all-versions.phtml The description of the product at simmarket is correct, it adds a huge amount of roads, rivers, coastlines and possibly landclass. I bought it yesterday and I think it changes the ground appearance of a default FSX quite a lot when within Chinese airspace. Considering the price, I would rate it as a very good buy. Hope this helps, Markus
  2. I only notice now, that I have created an annoying amount of multiple posts. My sincere apologies for that; maybe an adminstrator can take care of that. It happened because on each try to post this message, I got a "service unavailable" message and did not notice that the message was posted although I got an error indication saying the forum is not available. Sorry again, Markus
  3. Hi all, I have spent quite a few hours with the PMDG 777 now and I am still delighted by this magnificient aircraft. So first of all, it's time to say thanks from my side for creating this impressive simulation. On of the aspects I really love about the latest PMDG aircraft is the EGPWS simulation. Back, in old Aerowinx PS1 days, I made myself familiar with loads of technical details on EGPWS and I still love this system. That's why I would like to discuss a few things I noticed. I think I found two bugs and a few things which do not "feel" correct. Read on for more, please. 1) First of all, let me start with an issue I found comparing the PMDG 777 EGPWS display with real world photos (simulating them in PMDG). Generally, the 777 compares very well but: This particular image shows the first issue quite well - note the high and low values from the PEAKS MODE display just below the TERR announciation. (Numbers 143 and 000). You might remember: this indicates the highest (14.300') and lowest terrain points shown on the ND. Now, let's switch off the Water Display in CYAN: Note that the figure indicating the lowest terrain figure on the ND terrain display has changed from 000 to 072, indicating the lowest terrain point has an elevation of 7.200'. I think, there is a bug - namely the value showing 000 with water display turned on. Whenever Water in CYAN is switched on and water is visible the lowest terrain value is 000. This is not correct. While I understand this from software programmers point of view - the lowest point IS indeed 000 (and shown in blue) - it does not make sense from the EGPWS logic point of view - the pilot is still interested in the terrain and not in the sea level elevation. In the real world, even with sea level water in CYAN display, the aircraft shows 073 on the peaks mode display, see here. (My apologies for showing an Airbus cockpit. :lol: ). Of course, you'll note the excellent agreement between simulation (PMDG) and real world (Honeywell EGPWS). By the way, the position shown in the images should be obvious. 2) My second "bug" results from pure chance and not from systematic observation. Recently I was flying the ILS34 approach into Wellington, New Zealand (NZWN) (before Wordlflight 2013 and during WF.) Two issues here: on the approach, I got a spurious TERRAIN PULL UP warning and an obviously incorrect terrain display. To demonstrate this, I'll show a couple of screenshots from the approach on the ILS34. First image: on ILS34, at 560', 1.8 DME out. You can already see that I have received a PULL UP warning although I am well established on the ILS. This may be something worth looking into - the warning is false. But notice - again - the SEA WATER display in CYAN is on and shown correctly. Second Image: A few seconds later, on the ILS at 0.4 DME and 110'. I still have the TERRAIN message and the PULL UP warning on the PDF, but notice that the sea level display in CYAN is gone and replaced by all yellow colour. This is clearly not correct. Just to show that the incorrect 'all yellow' display of the sea level is not related to the TERRAIN message, here is the ND during taxi into the ramp. Again, sea level display in CYAN is not shown were it should be shown. Okay, this concludes my first section on things where I think that something is wrong. 3) In this third section, I will show a few things where I think that the EGPWS terrain display is not entirely correct. But is more like a "feeling" - I cannot really prove nor do I have images or documentation to show that something is wrong. I initially discovered this next issues while flying on airway L888 from KCA in Western China towards SANLI. This is an airway which runs directly across the Tibetian plateau over terrain of typically 15.000' or more (with peaks up to 20.000') and with sector minimum altitudes in the 25.000' to 29.000' range. Approaching LUVAR intersection, I noticed this display by the EGPWS computer. Now, this looks strange to me because: - it clearly shows that EGPWS is in a PEAKS MODE display (only green) - the highest terrain figure (198) indicated the highest terrain of 19.800' is clearly well below the airplane cruising at FL370 - the terrain elevation below the aircraft is about 14.500' (and not 107) - and the display is all green This is very confusing to the pilot and kind of violates the principle of the EGPWS Peaks Mode display to show only the highest peak elevations (e.g. mountain tops) around and not flat terrain. From a situational awareness point of view, this does not look correct. As far as I know, there is no image anywhere in the literature, on the web, in a DVD/Blueway which shows an all green terrain display from EGPWS (from WX radar of course, but not from EGPWS). My feeling is that a lowest terrain elevation of something like 15.500' would be more appropriate and thus show peaks only. The bottom line of this section is: I think that an entirely green EGPWS terrain display is not shown on a real world aircraft. Obviously, this image changes when the ND range is changed and I could continue showing images with different ranges. It looks better and different with a high ND range, but with a low (10 or 20 NM) ND range, I again get an all green display. There is probably no point in showing these images. Just one for the moment being... the issue of an all green display is not limited to the special case of flying along airway L888 over Tibet. Earlier on the same flight, around LASDO intersection (N46.5, E076 in Kazakhstan), I noticed a similar behaviour over essentially flat terrain. Here the low figure is 1100' (011) and the high figure is 1500' (015) of PEAKS display, which is basically a very flat desert. Or another example (without image), the same behaviour (all green) over flat terrain over Argentina, just 10 miles west of RYD VOR (approx. S34, W065). To conclude, I think that I have found a few issues within the EGPWS terrain display of the 777 (and possibly the 737NGX; my forum search has shown a similar post for the 737). I would appreciate some feedback, possibly from PMDG as well and wonder if this could be adressed in any upcoming service update for this great aircraft. Thanks a lot, Markus
  4. Hi all, I have spent quite a few hours with the PMDG 777 now and I am still delighted by this magnificient aircraft. So first of all, it's time to say thanks from my side for creating this impressive simulation. On of the aspects I really love about the latest PMDG aircraft is the EGPWS simulation. Back, in old Aerowinx PS1 days, I made myself familiar with loads of technical details on EGPWS and I still love this system. That's why I would like to discuss a few things I noticed. I think I found two bugs and a few things which do not "feel" correct. Read on for more, please. 1) First of all, let me start with an issue I found comparing the PMDG 777 EGPWS display with real world photos (simulating them in PMDG). Generally, the 777 compares very well but: This particular image shows the first issue quite well - note the high and low values from the PEAKS MODE display just below the TERR announciation. (Numbers 143 and 000). You might remember: this indicates the highest (14.300') and lowest terrain points shown on the ND. Now, let's switch off the Water Display in CYAN: Note that the figure indicating the lowest terrain figure on the ND terrain display has changed from 000 to 072, indicating the lowest terrain point has an elevation of 7.200'. I think, there is a bug - namely the value showing 000 with water display turned on. Whenever Water in CYAN is switched on and water is visible the lowest terrain value is 000. This is not correct. While I understand this from software programmers point of view - the lowest point IS indeed 000 (and shown in blue) - it does not make sense from the EGPWS logic point of view - the pilot is still interested in the terrain and not in the sea level elevation. In the real world, even with sea level water in CYAN display, the aircraft shows 073 on the peaks mode display, see here. (My apologies for showing an Airbus cockpit. :lol: ). Of course, you'll note the excellent agreement between simulation (PMDG) and real world (Honeywell EGPWS). By the way, the position shown in the images should be obvious. 2) My second "bug" results from pure chance and not from systematic observation. Recently I was flying the ILS34 approach into Wellington, New Zealand (NZWN) (before Wordlflight 2013 and during WF.) Two issues here: on the approach, I got a spurious TERRAIN PULL UP warning and an obviously incorrect terrain display. To demonstrate this, I'll show a couple of screenshots from the approach on the ILS34. First image: on ILS34, at 560', 1.8 DME out. You can already see that I have received a PULL UP warning although I am well established on the ILS. This may be something worth looking into - the warning is false. But notice - again - the SEA WATER display in CYAN is on and shown correctly. Second Image: A few seconds later, on the ILS at 0.4 DME and 110'. I still have the TERRAIN message and the PULL UP warning on the PDF, but notice that the sea level display in CYAN is gone and replaced by all yellow colour. This is clearly not correct. Just to show that the incorrect 'all yellow' display of the sea level is not related to the TERRAIN message, here is the ND during taxi into the ramp. Again, sea level display in CYAN is not shown were it should be shown. Okay, this concludes my first section on things where I think that something is wrong. 3) In this third section, I will show a few things where I think that the EGPWS terrain display is not entirely correct. But is more like a "feeling" - I cannot really prove nor do I have images or documentation to show that something is wrong. I initially discovered this next issues while flying on airway L888 from KCA in Western China towards SANLI. This is an airway which runs directly across the Tibetian plateau over terrain of typically 15.000' or more (with peaks up to 20.000') and with sector minimum altitudes in the 25.000' to 29.000' range. Approaching LUVAR intersection, I noticed this display by the EGPWS computer. Now, this looks strange to me because: - it clearly shows that EGPWS is in a PEAKS MODE display (only green) - the highest terrain figure (198) indicated the highest terrain of 19.800' is clearly well below the airplane cruising at FL370 - the terrain elevation below the aircraft is about 14.500' (and not 107) - and the display is all green This is very confusing to the pilot and kind of violates the principle of the EGPWS Peaks Mode display to show only the highest peak elevations (e.g. mountain tops) around and not flat terrain. From a situational awareness point of view, this does not look correct. As far as I know, there is no image anywhere in the literature, on the web, in a DVD/Blueway which shows an all green terrain display from EGPWS (from WX radar of course, but not from EGPWS). My feeling is that a lowest terrain elevation of something like 15.500' would be more appropriate and thus show peaks only. The bottom line of this section is: I think that an entirely green EGPWS terrain display is not shown on a real world aircraft. Obviously, this image changes when the ND range is changed and I could continue showing images with different ranges. It looks better and different with a high ND range, but with a low (10 or 20 NM) ND range, I again get an all green display. There is probably no point in showing these images. Just one for the moment being... the issue of an all green display is not limited to the special case of flying along airway L888 over Tibet. Earlier on the same flight, around LASDO intersection (N46.5, E076 in Kazakhstan), I noticed a similar behaviour over essentially flat terrain. Here the low figure is 1100' (011) and the high figure is 1500' (015) of PEAKS display, which is basically a very flat desert. Or another example (without image), the same behaviour (all green) over flat terrain over Argentina, just 10 miles west of RYD VOR (approx. S34, W065). To conclude, I think that I have found a few issues within the EGPWS terrain display of the 777 (and possibly the 737NGX; my forum search has shown a similar post for the 737). I would appreciate some feedback, possibly from PMDG as well and wonder if this could be adressed in any upcoming service update for this great aircraft. Thanks a lot, Markus
  5. Hi all, I have spent quite a few hours with the PMDG 777 now and I am still delighted by this magnificient aircraft. So first of all, it's time to say thanks from my side for creating this impressive simulation. On of the aspects I really love about the latest PMDG aircraft is the EGPWS simulation. Back, in old Aerowinx PS1 days, I made myself familiar with loads of technical details on EGPWS and I still love this system. That's why I would like to discuss a few things I noticed. I think I found two bugs and a few things which do not "feel" correct. Read on for more, please. 1) First of all, let me start with an issue I found comparing the PMDG 777 EGPWS display with real world photos (simulating them in PMDG). Generally, the 777 compares very well but: This particular image shows the first issue quite well - note the high and low values from the PEAKS MODE display just below the TERR announciation. (Numbers 143 and 000). You might remember: this indicates the highest (14.300') and lowest terrain points shown on the ND. Now, let's switch off the Water Display in CYAN: Note that the figure indicating the lowest terrain figure on the ND terrain display has changed from 000 to 072, indicating the lowest terrain point has an elevation of 7.200'. I think, there is a bug - namely the value showing 000 with water display turned on. Whenever Water in CYAN is switched on and water is visible the lowest terrain value is 000. This is not correct. While I understand this from software programmers point of view - the lowest point IS indeed 000 (and shown in blue) - it does not make sense from the EGPWS logic point of view - the pilot is still interested in the terrain and not in the sea level elevation. In the real world, even with sea level water in CYAN display, the aircraft shows 073 on the peaks mode display, see here. (My apologies for showing an Airbus cockpit. :lol: ). Of course, you'll note the excellent agreement between simulation (PMDG) and real world (Honeywell EGPWS). By the way, the position shown in the images should be obvious. 2) My second "bug" results from pure chance and not from systematic observation. Recently I was flying the ILS34 approach into Wellington, New Zealand (NZWN) (before Wordlflight 2013 and during WF.) Two issues here: on the approach, I got a spurious TERRAIN PULL UP warning and an obviously incorrect terrain display. To demonstrate this, I'll show a couple of screenshots from the approach on the ILS34. First image: on ILS34, at 560', 1.8 DME out. You can already see that I have received a PULL UP warning although I am well established on the ILS. This may be something worth looking into - the warning is false. But notice - again - the SEA WATER display in CYAN is on and shown correctly. Second Image: A few seconds later, on the ILS at 0.4 DME and 110'. I still have the TERRAIN message and the PULL UP warning on the PDF, but notice that the sea level display in CYAN is gone and replaced by all yellow colour. This is clearly not correct. Just to show that the incorrect 'all yellow' display of the sea level is not related to the TERRAIN message, here is the ND during taxi into the ramp. Again, sea level display in CYAN is not shown were it should be shown. Okay, this concludes my first section on things where I think that something is wrong. 3) In this third section, I will show a few things where I think that the EGPWS terrain display is not entirely correct. But is more like a "feeling" - I cannot really prove nor do I have images or documentation to show that something is wrong. I initially discovered this next issues while flying on airway L888 from KCA in Western China towards SANLI. This is an airway which runs directly across the Tibetian plateau over terrain of typically 15.000' or more (with peaks up to 20.000') and with sector minimum altitudes in the 25.000' to 29.000' range. Approaching LUVAR intersection, I noticed this display by the EGPWS computer. Now, this looks strange to me because: - it clearly shows that EGPWS is in a PEAKS MODE display (only green) - the highest terrain figure (198) indicated the highest terrain of 19.800' is clearly well below the airplane cruising at FL370 - the terrain elevation below the aircraft is about 14.500' (and not 107) - and the display is all green This is very confusing to the pilot and kind of violates the principle of the EGPWS Peaks Mode display to show only the highest peak elevations (e.g. mountain tops) around and not flat terrain. From a situational awareness point of view, this does not look correct. As far as I know, there is no image anywhere in the literature, on the web, in a DVD/Blueway which shows an all green terrain display from EGPWS (from WX radar of course, but not from EGPWS). My feeling is that a lowest terrain elevation of something like 15.500' would be more appropriate and thus show peaks only. The bottom line of this section is: I think that an entirely green EGPWS terrain display is not shown on a real world aircraft. Obviously, this image changes when the ND range is changed and I could continue showing images with different ranges. It looks better and different with a high ND range, but with a low (10 or 20 NM) ND range, I again get an all green display. There is probably no point in showing these images. Just one for the moment being... the issue of an all green display is not limited to the special case of flying along airway L888 over Tibet. Earlier on the same flight, around LASDO intersection (N46.5, E076 in Kazakhstan), I noticed a similar behaviour over essentially flat terrain. Here the low figure is 1100' (011) and the high figure is 1500' (015) of PEAKS display, which is basically a very flat desert. Or another example (without image), the same behaviour (all green) over flat terrain over Argentina, just 10 miles west of RYD VOR (approx. S34, W065). To conclude, I think that I have found a few issues within the EGPWS terrain display of the 777 (and possibly the 737NGX; my forum search has shown a similar post for the 737). I would appreciate some feedback, possibly from PMDG as well and wonder if this could be adressed in any upcoming service update for this great aircraft. Thanks a lot, Markus
  6. Hi all, I have spent quite a few hours with the PMDG 777 now and I am still delighted by this magnificient aircraft. So first of all, it's time to say thanks from my side for creating this impressive simulation. On of the aspects I really love about the latest PMDG aircraft is the EGPWS simulation. Back, in old Aerowinx PS1 days, I made myself familiar with loads of technical details on EGPWS and I still love this system. That's why I would like to discuss a few things I noticed. I think I found two bugs and a few things which do not "feel" correct. Read on for more, please. 1) First of all, let me start with an issue I found comparing the PMDG 777 EGPWS display with real world photos (simulating them in PMDG). Generally, the 777 compares very well but: This particular image shows the first issue quite well - note the high and low values from the PEAKS MODE display just below the TERR announciation. (Numbers 143 and 000). You might remember: this indicates the highest (14.300') and lowest terrain points shown on the ND. Now, let's switch off the Water Display in CYAN: Note that the figure indicating the lowest terrain figure on the ND terrain display has changed from 000 to 072, indicating the lowest terrain point has an elevation of 7.200'. I think, there is a bug - namely the value showing 000 with water display turned on. Whenever Water in CYAN is switched on and water is visible the lowest terrain value is 000. This is not correct. While I understand this from software programmers point of view - the lowest point IS indeed 000 (and shown in blue) - it does not make sense from the EGPWS logic point of view - the pilot is still interested in the terrain and not in the sea level elevation. In the real world, even with sea level water in CYAN display, the aircraft shows 073 on the peaks mode display, see here. (My apologies for showing an Airbus cockpit. :lol: ). Of course, you'll note the excellent agreement between simulation (PMDG) and real world (Honeywell EGPWS). By the way, the position shown in the images should be obvious. 2) My second "bug" results from pure chance and not from systematic observation. Recently I was flying the ILS34 approach into Wellington, New Zealand (NZWN) (before Wordlflight 2013 and during WF.) Two issues here: on the approach, I got a spurious TERRAIN PULL UP warning and an obviously incorrect terrain display. To demonstrate this, I'll show a couple of screenshots from the approach on the ILS34. First image: on ILS34, at 560', 1.8 DME out. You can already see that I have received a PULL UP warning although I am well established on the ILS. This may be something worth looking into - the warning is false. But notice - again - the SEA WATER display in CYAN is on and shown correctly. Second Image: A few seconds later, on the ILS at 0.4 DME and 110'. I still have the TERRAIN message and the PULL UP warning on the PDF, but notice that the sea level display in CYAN is gone and replaced by all yellow colour. This is clearly not correct. Just to show that the incorrect 'all yellow' display of the sea level is not related to the TERRAIN message, here is the ND during taxi into the ramp. Again, sea level display in CYAN is not shown were it should be shown. Okay, this concludes my first section on things where I think that something is wrong. 3) In this third section, I will show a few things where I think that the EGPWS terrain display is not entirely correct. But is more like a "feeling" - I cannot really prove nor do I have images or documentation to show that something is wrong. I initially discovered this next issues while flying on airway L888 from KCA in Western China towards SANLI. This is an airway which runs directly across the Tibetian plateau over terrain of typically 15.000' or more (with peaks up to 20.000') and with sector minimum altitudes in the 25.000' to 29.000' range. Approaching LUVAR intersection, I noticed this display by the EGPWS computer. Now, this looks strange to me because: - it clearly shows that EGPWS is in a PEAKS MODE display (only green) - the highest terrain figure (198) indicated the highest terrain of 19.800' is clearly well below the airplane cruising at FL370 - the terrain elevation below the aircraft is about 14.500' (and not 107) - and the display is all green This is very confusing to the pilot and kind of violates the principle of the EGPWS Peaks Mode display to show only the highest peak elevations (e.g. mountain tops) around and not flat terrain. From a situational awareness point of view, this does not look correct. As far as I know, there is no image anywhere in the literature, on the web, in a DVD/Blueway which shows an all green terrain display from EGPWS (from WX radar of course, but not from EGPWS). My feeling is that a lowest terrain elevation of something like 15.500' would be more appropriate and thus show peaks only. The bottom line of this section is: I think that an entirely green EGPWS terrain display is not shown on a real world aircraft. Obviously, this image changes when the ND range is changed and I could continue showing images with different ranges. It looks better and different with a high ND range, but with a low (10 or 20 NM) ND range, I again get an all green display. There is probably no point in showing these images. Just one for the moment being... the issue of an all green display is not limited to the special case of flying along airway L888 over Tibet. Earlier on the same flight, around LASDO intersection (N46.5, E076 in Kazakhstan), I noticed a similar behaviour over essentially flat terrain. Here the low figure is 1100' (011) and the high figure is 1500' (015) of PEAKS display, which is basically a very flat desert. Or another example (without image), the same behaviour (all green) over flat terrain over Argentina, just 10 miles west of RYD VOR (approx. S34, W065). To conclude, I think that I have found a few issues within the EGPWS terrain display of the 777 (and possibly the 737NGX; my forum search has shown a similar post for the 737). I would appreciate some feedback, possibly from PMDG as well and wonder if this could be adressed in any upcoming service update for this great aircraft. Thanks a lot, Markus
  7. Hi all, I have spent quite a few hours with the PMDG 777 now and I am still delighted by this magnificient aircraft. So first of all, it's time to say thanks from my side for creating this impressive simulation. On of the aspects I really love about the latest PMDG aircraft is the EGPWS simulation. Back, in old Aerowinx PS1 days, I made myself familiar with loads of technical details on EGPWS and I still love this system. That's why I would like to discuss a few things I noticed. I think I found two bugs and a few things which do not "feel" correct. Read on for more, please. 1) First of all, let me start with an issue I found comparing the PMDG 777 EGPWS display with real world photos (simulating them in PMDG). Generally, the 777 compares very well but: This particular image shows the first issue quite well - note the high and low values from the PEAKS MODE display just below the TERR announciation. (Numbers 143 and 000). You might remember: this indicates the highest (14.300') and lowest terrain points shown on the ND. Now, let's switch off the Water Display in CYAN: Note that the figure indicating the lowest terrain figure on the ND terrain display has changed from 000 to 072, indicating the lowest terrain point has an elevation of 7.200'. I think, there is a bug - namely the value showing 000 with water display turned on. Whenever Water in CYAN is switched on and water is visible the lowest terrain value is 000. This is not correct. While I understand this from software programmers point of view - the lowest point IS indeed 000 (and shown in blue) - it does not make sense from the EGPWS logic point of view - the pilot is still interested in the terrain and not in the sea level elevation. In the real world, even with sea level water in CYAN display, the aircraft shows 073 on the peaks mode display, see here. (My apologies for showing an Airbus cockpit. :lol: ). Of course, you'll note the excellent agreement between simulation (PMDG) and real world (Honeywell EGPWS). By the way, the position shown in the images should be obvious. 2) My second "bug" results from pure chance and not from systematic observation. Recently I was flying the ILS34 approach into Wellington, New Zealand (NZWN) (before Wordlflight 2013 and during WF.) Two issues here: on the approach, I got a spurious TERRAIN PULL UP warning and an obviously incorrect terrain display. To demonstrate this, I'll show a couple of screenshots from the approach on the ILS34. First image: on ILS34, at 560', 1.8 DME out. You can already see that I have received a PULL UP warning although I am well established on the ILS. This may be something worth looking into - the warning is false. But notice - again - the SEA WATER display in CYAN is on and shown correctly. Second Image: A few seconds later, on the ILS at 0.4 DME and 110'. I still have the TERRAIN message and the PULL UP warning on the PDF, but notice that the sea level display in CYAN is gone and replaced by all yellow colour. This is clearly not correct. Just to show that the incorrect 'all yellow' display of the sea level is not related to the TERRAIN message, here is the ND during taxi into the ramp. Again, sea level display in CYAN is not shown were it should be shown. Okay, this concludes my first section on things where I think that something is wrong. 3) In this third section, I will show a few things where I think that the EGPWS terrain display is not entirely correct. But is more like a "feeling" - I cannot really prove nor do I have images or documentation to show that something is wrong. I initially discovered this next issues while flying on airway L888 from KCA in Western China towards SANLI. This is an airway which runs directly across the Tibetian plateau over terrain of typically 15.000' or more (with peaks up to 20.000') and with sector minimum altitudes in the 25.000' to 29.000' range. Approaching LUVAR intersection, I noticed this display by the EGPWS computer. Now, this looks strange to me because: - it clearly shows that EGPWS is in a PEAKS MODE display (only green) - the highest terrain figure (198) indicated the highest terrain of 19.800' is clearly well below the airplane cruising at FL370 - the terrain elevation below the aircraft is about 14.500' (and not 107) - and the display is all green This is very confusing to the pilot and kind of violates the principle of the EGPWS Peaks Mode display to show only the highest peak elevations (e.g. mountain tops) around and not flat terrain. From a situational awareness point of view, this does not look correct. As far as I know, there is no image anywhere in the literature, on the web, in a DVD/Blueway which shows an all green terrain display from EGPWS (from WX radar of course, but not from EGPWS). My feeling is that a lowest terrain elevation of something like 15.500' would be more appropriate and thus show peaks only. The bottom line of this section is: I think that an entirely green EGPWS terrain display is not shown on a real world aircraft. Obviously, this image changes when the ND range is changed and I could continue showing images with different ranges. It looks better and different with a high ND range, but with a low (10 or 20 NM) ND range, I again get an all green display. There is probably no point in showing these images. Just one for the moment being... the issue of an all green display is not limited to the special case of flying along airway L888 over Tibet. Earlier on the same flight, around LASDO intersection (N46.5, E076 in Kazakhstan), I noticed a similar behaviour over essentially flat terrain. Here the low figure is 1100' (011) and the high figure is 1500' (015) of PEAKS display, which is basically a very flat desert. Or another example (without image), the same behaviour (all green) over flat terrain over Argentina, just 10 miles west of RYD VOR (approx. S34, W065). To conclude, I think that I have found a few issues within the EGPWS terrain display of the 777 (and possibly the 737NGX; my forum search has shown a similar post for the 737). I would appreciate some feedback, possibly from PMDG as well and wonder if this could be adressed in any upcoming service update for this great aircraft. Thanks a lot, Markus
  8. Hi all, I have spent quite a few hours with the PMDG 777 now and I am still delighted by this magnificient aircraft. So first of all, it's time to say thanks from my side for creating this impressive simulation. On of the aspects I really love about the latest PMDG aircraft is the EGPWS simulation. Back, in old Aerowinx PS1 days, I made myself familiar with loads of technical details on EGPWS and I still love this system. That's why I would like to discuss a few things I noticed. I think I found two bugs and a few things which do not "feel" correct. Read on for more, please. 1) First of all, let me start with an issue I found comparing the PMDG 777 EGPWS display with real world photos (simulating them in PMDG). Generally, the 777 compares very well but: This particular image shows the first issue quite well - note the high and low values from the PEAKS MODE display just below the TERR announciation. (Numbers 143 and 000). You might remember: this indicates the highest (14.300') and lowest terrain points shown on the ND. Now, let's switch off the Water Display in CYAN: Note that the figure indicating the lowest terrain figure on the ND terrain display has changed from 000 to 072, indicating the lowest terrain point has an elevation of 7.200'. I think, there is a bug - namely the value showing 000 with water display turned on. Whenever Water in CYAN is switched on and water is visible the lowest terrain value is 000. This is not correct. While I understand this from software programmers point of view - the lowest point IS indeed 000 (and shown in blue) - it does not make sense from the EGPWS logic point of view - the pilot is still interested in the terrain and not in the sea level elevation. In the real world, even with sea level water in CYAN display, the aircraft shows 073 on the peaks mode display, see here. (My apologies for showing an Airbus cockpit. :lol: ). Of course, you'll note the excellent agreement between simulation (PMDG) and real world (Honeywell EGPWS). By the way, the position shown in the images should be obvious. 2) My second "bug" results from pure chance and not from systematic observation. Recently I was flying the ILS34 approach into Wellington, New Zealand (NZWN) (before Wordlflight 2013 and during WF.) Two issues here: on the approach, I got a spurious TERRAIN PULL UP warning and an obviously incorrect terrain display. To demonstrate this, I'll show a couple of screenshots from the approach on the ILS34. First image: on ILS34, at 560', 1.8 DME out. You can already see that I have received a PULL UP warning although I am well established on the ILS. This may be something worth looking into - the warning is false. But notice - again - the SEA WATER display in CYAN is on and shown correctly. Second Image: A few seconds later, on the ILS at 0.4 DME and 110'. I still have the TERRAIN message and the PULL UP warning on the PDF, but notice that the sea level display in CYAN is gone and replaced by all yellow colour. This is clearly not correct. Just to show that the incorrect 'all yellow' display of the sea level is not related to the TERRAIN message, here is the ND during taxi into the ramp. Again, sea level display in CYAN is not shown were it should be shown. Okay, this concludes my first section on things where I think that something is wrong. 3) In this third section, I will show a few things where I think that the EGPWS terrain display is not entirely correct. But is more like a "feeling" - I cannot really prove nor do I have images or documentation to show that something is wrong. I initially discovered this next issues while flying on airway L888 from KCA in Western China towards SANLI. This is an airway which runs directly across the Tibetian plateau over terrain of typically 15.000' or more (with peaks up to 20.000') and with sector minimum altitudes in the 25.000' to 29.000' range. Approaching LUVAR intersection, I noticed this display by the EGPWS computer. Now, this looks strange to me because: - it clearly shows that EGPWS is in a PEAKS MODE display (only green) - the highest terrain figure (198) indicated the highest terrain of 19.800' is clearly well below the airplane cruising at FL370 - the terrain elevation below the aircraft is about 14.500' (and not 107) - and the display is all green This is very confusing to the pilot and kind of violates the principle of the EGPWS Peaks Mode display to show only the highest peak elevations (e.g. mountain tops) around and not flat terrain. From a situational awareness point of view, this does not look correct. As far as I know, there is no image anywhere in the literature, on the web, in a DVD/Blueway which shows an all green terrain display from EGPWS (from WX radar of course, but not from EGPWS). My feeling is that a lowest terrain elevation of something like 15.500' would be more appropriate and thus show peaks only. The bottom line of this section is: I think that an entirely green EGPWS terrain display is not shown on a real world aircraft. Obviously, this image changes when the ND range is changed and I could continue showing images with different ranges. It looks better and different with a high ND range, but with a low (10 or 20 NM) ND range, I again get an all green display. There is probably no point in showing these images. Just one for the moment being... the issue of an all green display is not limited to the special case of flying along airway L888 over Tibet. Earlier on the same flight, around LASDO intersection (N46.5, E076 in Kazakhstan), I noticed a similar behaviour over essentially flat terrain. Here the low figure is 1100' (011) and the high figure is 1500' (015) of PEAKS display, which is basically a very flat desert. Or another example (without image), the same behaviour (all green) over flat terrain over Argentina, just 10 miles west of RYD VOR (approx. S34, W065). To conclude, I think that I have found a few issues within the EGPWS terrain display of the 777 (and possibly the 737NGX; my forum search has shown a similar post for the 737). I would appreciate some feedback, possibly from PMDG as well and wonder if this could be adressed in any upcoming service update for this great aircraft. Thanks a lot, Markus
  9. Hi all, I have spent quite a few hours with the PMDG 777 now and I am still delighted by this magnificient aircraft. So first of all, it's time to say thanks from my side for creating this impressive simulation. On of the aspects I really love about the latest PMDG aircraft is the EGPWS simulation. Back, in old Aerowinx PS1 days, I made myself familiar with loads of technical details on EGPWS and I still love this system. That's why I would like to discuss a few things I noticed. I think I found two bugs and a few things which do not "feel" correct. Read on for more, please. 1) First of all, let me start with an issue I found comparing the PMDG 777 EGPWS display with real world photos (simulating them in PMDG). Generally, the 777 compares very well but: This particular image shows the first issue quite well - note the high and low values from the PEAKS MODE display just below the TERR announciation. (Numbers 143 and 000). You might remember: this indicates the highest (14.300') and lowest terrain points shown on the ND. Now, let's switch off the Water Display in CYAN: Note that the figure indicating the lowest terrain figure on the ND terrain display has changed from 000 to 072, indicating the lowest terrain point has an elevation of 7.200'. I think, there is a bug - namely the value showing 000 with water display turned on. Whenever Water in CYAN is switched on and water is visible the lowest terrain value is 000. This is not correct. While I understand this from software programmers point of view - the lowest point IS indeed 000 (and shown in blue) - it does not make sense from the EGPWS logic point of view - the pilot is still interested in the terrain and not in the sea level elevation. In the real world, even with sea level water in CYAN display, the aircraft shows 073 on the peaks mode display, see here. (My apologies for showing an Airbus cockpit. :lol: ). Of course, you'll note the excellent agreement between simulation (PMDG) and real world (Honeywell EGPWS). By the way, the position shown in the images should be obvious. 2) My second "bug" results from pure chance and not from systematic observation. Recently I was flying the ILS34 approach into Wellington, New Zealand (NZWN) (before Wordlflight 2013 and during WF.) Two issues here: on the approach, I got a spurious TERRAIN PULL UP warning and an obviously incorrect terrain display. To demonstrate this, I'll show a couple of screenshots from the approach on the ILS34. First image: on ILS34, at 560', 1.8 DME out. You can already see that I have received a PULL UP warning although I am well established on the ILS. This may be something worth looking into - the warning is false. But notice - again - the SEA WATER display in CYAN is on and shown correctly. Second Image: A few seconds later, on the ILS at 0.4 DME and 110'. I still have the TERRAIN message and the PULL UP warning on the PDF, but notice that the sea level display in CYAN is gone and replaced by all yellow colour. This is clearly not correct. Just to show that the incorrect 'all yellow' display of the sea level is not related to the TERRAIN message, here is the ND during taxi into the ramp. Again, sea level display in CYAN is not shown were it should be shown. Okay, this concludes my first section on things where I think that something is wrong. 3) In this third section, I will show a few things where I think that the EGPWS terrain display is not entirely correct. But is more like a "feeling" - I cannot really prove nor do I have images or documentation to show that something is wrong. I initially discovered this next issues while flying on airway L888 from KCA in Western China towards SANLI. This is an airway which runs directly across the Tibetian plateau over terrain of typically 15.000' or more (with peaks up to 20.000') and with sector minimum altitudes in the 25.000' to 29.000' range. Approaching LUVAR intersection, I noticed this display by the EGPWS computer. Now, this looks strange to me because: - it clearly shows that EGPWS is in a PEAKS MODE display (only green) - the highest terrain figure (198) indicated the highest terrain of 19.800' is clearly well below the airplane cruising at FL370 - the terrain elevation below the aircraft is about 14.500' (and not 107) - and the display is all green This is very confusing to the pilot and kind of violates the principle of the EGPWS Peaks Mode display to show only the highest peak elevations (e.g. mountain tops) around and not flat terrain. From a situational awareness point of view, this does not look correct. As far as I know, there is no image anywhere in the literature, on the web, in a DVD/Blueway which shows an all green terrain display from EGPWS (from WX radar of course, but not from EGPWS). My feeling is that a lowest terrain elevation of something like 15.500' would be more appropriate and thus show peaks only. The bottom line of this section is: I think that an entirely green EGPWS terrain display is not shown on a real world aircraft. Obviously, this image changes when the ND range is changed and I could continue showing images with different ranges. It looks better and different with a high ND range, but with a low (10 or 20 NM) ND range, I again get an all green display. There is probably no point in showing these images. Just one for the moment being... the issue of an all green display is not limited to the special case of flying along airway L888 over Tibet. Earlier on the same flight, around LASDO intersection (N46.5, E076 in Kazakhstan), I noticed a similar behaviour over essentially flat terrain. Here the low figure is 1100' (011) and the high figure is 1500' (015) of PEAKS display, which is basically a very flat desert. Or another example (without image), the same behaviour (all green) over flat terrain over Argentina, just 10 miles west of RYD VOR (approx. S34, W065). To conclude, I think that I have found a few issues within the EGPWS terrain display of the 777 (and possibly the 737NGX; my forum search has shown a similar post for the 737). I would appreciate some feedback, possibly from PMDG as well and wonder if this could be adressed in any upcoming service update for this great aircraft. Thanks a lot, Markus
  10. Hi Steven, that is already the correct answer. You need to enter J1 - or alternatively J189. Both airways share a common path here. Regards, Markus Vitzethum
  11. ps1flyer replied to a post in a topic in PMDG General Forum
    > Is this a special airline option? Is is not possible to have> HDG up in MAP mode due to program limitation or any other> reason?HDG up vs. TRK up in ND Map Mode is an airline option. Markus
  12. Actually, I have never stopped flying PS1.3 during the last 6 year. ;-) And like many other PS1 users, I am looking forward to the PMDG version of a 747-400 and I would love to compare those two simulators. Markus
  13. Hi Glen,>Do you know if anyone has contacted Virgin Atlantic to see if>a copy of the flight plan is available?do my best knowledge, no flight plan from Virgin Atlantic is available or known.However, the producer (Nick Grindley, of ITVV) assured that the flight was not filmed on several legs but during a single flight from London to San Francisco. The discussion about the flight plan goes really back for a long time in the Aerowinx forum. You might want to do some further reading here, but please do not be confused by the frequent references to the Winnipeg "overflight". This solved has, apparently, been solved and my theory that the F/O's comment referes to the Winnipeg FIR airspace seems to be accepted now.Here are the links:http://aerowinx.com/archive04.cgi/read/8599http://aerowinx.com/archive04.cgi/read/8600http://aerowinx.com/archive00.cgi?review=1877Markus
  14. It should be correct that the flight was close to the great circle distance.When lookinging closely there is much more information about the route in the movie e.g. FMC crossing times and crossing time predictions, wind information, the data shown while the crew browses through plan mode (again, look at the times.).Actually, that very same topic has been discussed in the Aerowinx forum for ages. ;-)See e.g. http://aerowinx.com/archive12.cgi?review=9073 for a thorough analysis.Markus

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.