Jump to content

NBouc

Members
  • Content Count

    24
  • Joined

  • Last visited

Community Reputation

3 Neutral

About NBouc

  • Rank
    Member
  • Birthday May 9

Profile Information

  • Gender:
    Male
  • Location:
    Montreal, Canada - CYUL
  1. My Central backup folder for AUv2 contains 1.54GB of files (36 files) all dated the day I installed the service pack update.
  2. I have it too about 8nm east of KAQW. I have Global Vector and OLC NA installed. It could very well be a vector issue.
  3. Hi Larry, I understand the logic behind your choice. If the simulator has no problem seeing YRC and CYRC as two different airports in the same country, then there is no problem. I only mentioned it because I did not know if the simulator could differentiate the two idents. Keep up the good work !
  4. Hi Larry, If YRC is to be the "identifier" that you use for Refuge Cove in your scenery, just be advised that there already is a CYRC airport in Canada (Chicoutimi/St-Honore, Qc). I mention it in case it would cause conflict for the users. Your scenery looks very good BTW. Best regards,
  5. Hi Tozzifan, I don't know what the source of the problem you encountered might be, but just to confirm that it is not an ORBX issue, I just flew the ILS RWY 05 at ORBX NSTU with PMDG NGX in Prepar3D 4.1 and it is perfectly aligned with the runway center line. I let AUTOLAND do the job to make sure and it was "bang on". I use AIRAC 1801 and updated MAGVAR 2017. I hope you find a solution some day. Best regards.
  6. The LOC-DME-H (LDA-H) approach to PAVD is indeed a little offset from the runway and it is like this in real life (Loc course is 057, runway heading is 064). On the approach plate, all the minimums apply to CIRCLING, meaning that the approach is not intended to take you directly along the extended runway centerline, but rather close enough to the airport for a visual landing. I can understand that one may think of a possible "alignement" problem since the localizer is "almost" aligned with runway 06. So don't worry, what you observed is all good.
  7. I don't have a solution for you Peter, but just want to let you know that I fly a similar route to LDDU a few times a week in P3Dv4.1 from either LGAV or LGKR ( ... L611 LOKRU - LOKR1A) using PMDG NGX, ASP4 and ASCA, and never had a crash (day or night). In addition to LDDU scenery, I have FTX Global Base, FTX Global Vector and FTX Global OLC EU, as well as FreeMeshX covering that area. My guess is that something is interfering with your scenery that makes P3D CTD. Someone just have to figure out what it is. In the LDDU control panel, I have all options ON, with the following options: - Vector compatibility: ON - Airport vegetation season switch: Automatic - APX Static aircraft: With Static I hope you find the cause of your CTD, but at least you know that LDDU can work fine.
  8. Thank you Philip for the confirmation. You did a great job with ESSA BTW, I love that scenery.
  9. Can someone confirm that at ESSA, there isn't any taxiway edge lights (blue lights) ? Only green leading lights on the taxiways ? I just want to make sure that I am not missing any detail because this is the first airport I see without the blue taxiway lights at night. Best regards,
  10. Hello Roger, If you plan for a fresh install of P3D and assuming you have downloaded the complete package from Lockheed Martin, then simply run the "Setup.exe" from your P3D download. This will install all P3D components (Client, Content and Scenery). P3D installation comes in 3 different components for providing an easy way of updating a specific component of an existing installation of P3D. So when someone refers to "Client", they mean the "Install_Client.msi" file for P3D. Sometimes, a new version of P3D may only make changes to the "Client" component and not the others. When that is the case, we can update (remove previous client and install new client component) instead of re-installing the whole thing. My guess is that the "Client" contains the main P3D software, the "Content" probably the vehicles, etc.. and the "Scenery", well ... the scenery files.
  11. This is the ICAO format to represent a speed and/or altitude change enroute. It is included in the filed route when it differs from the filed speed and/or altitude. M means Mach number (% of the speed of sound). It must be expressed using 3 digits after the M. N means Knots. It must represent the True Airspeed (TAS) in knots, using 4 digits after the N. F means Flight Level, expressed using 3 digits (F360 means 36,000 ft with altimeter settings 29.92). After IDOTO, the flight is planning a speed of Mach 0.77 (M077) and Flight Level 360 (F360) After SATNA, the flight is planning a speed of 452 TAS (N0452) remaining at Flight Level 360 (F360) Regards, Normand.
  12. I haven't flown online for quite a while but when I did, I used 2 sound cards (1 built-in and 1 PCI). I found it very usefull to direct the COM to the 2nd card so that I could adjust the headset volume without interfering with the environment sound of the simulator. I would'nt say it is a must, but it makes things a lot more enjoyable (and a lot less "please say again" on my part).
  13. I recently replaced my NVIDIA 8800GTX 768 MB with an ATI HD5850 1 GB, thinking the 8800 was slowly dying. In turned out that it was simply kept underpowered by Windows 7 "balanced" power saving option. Once I realized that, I switched to "High performance" power saving option and tried both cards under the same parameters. Even though the 5850 performed very well, I cannot say it outperformed the 8800GTX. To some extent, both cards seem to perform as well as the other, with occasional slightly higher FPS with the 5850. I used a pristine FSX.CFG with both cards (rebuilt after switching card). Setup: Drivers for 8800GTX: Nvidia Vista-64 182.50 (better image quality than the Win7 drivers) Drivers for HD5850: ATI Catalyst 10.1 Window 7 64-bit AA and Anisotropic set inside FSX. AA 4x and Anisotropic 16X set in the drivers (override application). VSync forced to ON. Display settings - Scenery: Target FPS 60 Detail radius: Large Mesh complexity: 100 Mesh resolution: 10 m Texture resolution: 7cm Water effects: Low 2x Scenery complexity: Very Dense Autogen density: Normal Special effects detail: High My flight departs YPEC (All Orbx FTX regions and sceneries installed) in the Aerosoft Piper Cheyenne II during a fair weather day (Broken 5/8 cumulus at 12500 ft, 30 miles vis) for a quick tour of the bay and returns landing, with weather theme change to Major Thunderstorm half way into the flight. Resulting FPS might sometimes seem low to some of you, but keep in mind that I am running 3 monitors through a Matrox TH2G digital 3840x1024x32 (3 times 1280x1024). This easily lowers the FPS under 2/3 of what a single monitor would display. All readings taken inside the 3D cockpit because that is where I sit when I fly. Starting location, YPEC parking 1: HD5850 18-20 FPS, 8800GTX 17-18 FPS Aligned on runway 25: HD5850 13 FPS, 8800GTX 11-12 FPS Overhead the power station: - looking left towards Warnevale: HD5850 14-15 FPS, 8800GTX 13-16 FPS - looking front-right towards YCNK: HD5850 28-30 FPS, 8800GTX 24-26 FPS - looking at the tip of the right wing: HD5850 20-24 FPS, 8800GTX 18-23 FPS Weather changed to Major Thunderstorm - inside the clouds at 8000 ft with precipitations: HD5850 15-22 FPS, 8800GTX 15-20 FPS - under the cloud layer at 2200 ft with precipitations: HD5850 10-15 FPS, 8800GTX 11-13 FPS - left downwind for runway 25, facing the sea: HD5850 30 FPS, 8800GTX 27-30 FPS - on final runway 25 over the beach: HD5850 9-10 FPS, 8800GTX 8-10 FPS If I was replacing something like a 8400GS, I would be very pleased for sure. But the reality is that I probably just exchanged 4 quarters for a dollar. Despite this fact, I can appreciate the value of the 5850 (which costs me half the price of the 8800GTX some years ago). The image quality is as good as with the 8800GTX, ATI rendering the textures with a bit more vivid colors, but the 8800GTX doing it with a more natural look. I would like you to take this "comparative test" with subjectivity. It is in no way a scientific test and some factors I did not think of might have played a role in the results. Best regards to all readers,
×
×
  • Create New...