jrw4

Members
  • Content Count

    58
  • Joined

  • Last visited

Community Reputation

4 Neutral

About jrw4

  • Birthday 07/26/1944

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    No

Recent Profile Visitors

382 profile views
  1. jrw4

    Question about RNAV approach

    With regard to the original post, what may be happening is that you have set the MCP altitude to the MDA and left it there after passing the FAF and instead of changing it to the altitude required by the missed approach procedure as noted by several of the other posters. That causes the autothrottle to spool up the engines as the a/c approaches the MDA, etc. Believe me, I made the same mistake several times before watching how it is actually done on a tutorial video. With regard to the suggestion that these approaches be flown by hand, the FCTM states on page 5.27 that the autopilot should be used for non-ILS approaches. Of course, no one is actually watching, so go for it if you like!
  2. jrw4

    DXGI_ERROR_DEVICE_HUNG

    I rolled the driver version back to 397.31 and that ended it. Still on P3D v4.2....... It also first appeared after first running the new A320-X. It was not happening with PMDG a/c, so yes, better let them know in the other vendor's forum.
  3. Ah yes, I see this has been addressed previously. There it was noted, in response to the question of whether it was possible to select an option that would result in the NGX not losing sound on lost focus, that the answer was "no". However (and this was confusing me) the PMDG-737 NGX Introduction and Use manual (mine is dated 2011-2015) states on page 92 with reference to the P3D sound options I take it that this is incorrect, at least in P3D v4.2. Many thanks for any clarification.
  4. A recent post on the 737NGX forum concerning the loss of sound in that aircraft when clicking outside the PMDG window was solved when the OP was instructed to unclick the Mute on Lose Focus button on the Sound option page of P3D v4.2. I had earlier had a similar problem in the PMDG 737 and PMDG 777 a/c, so I happily saw this as an opportunity to bring back the sound. Unfortunately, when I went to the Options page, I saw that the button was, in fact, unchecked. When I tested the sound behavior with default aircraft, as well as with the FSL A320-X, I was surprised to see that they performed as expected, namely the cockpit sounds remained audible when the focus shifted to a non P3D window. I'm using the latest versions of W10 (including the "Spring" update), P3D, and PMDG. Nothing unusual about the sound system, as I'm using the default sound system configuration, etc. Has anyone seen a similar problem or is this one of those unique learning opportunities we sometime stumble across in flightsim land?
  5. jrw4

    Still problems with ASUS Motherboards?

    No problems with an ASUS Z270M with i7-7700K CPU in a micro-ATX case. The CPU is lightly overclocked to 4.6 GHz since cooling is limited in the small case, but that's sufficient to run P3D v4.2 (and our favorite family of study level add-on aircraft) very smoothly VSync'ed to 30Hz with a GTX970 GPU.
  6. Just an update on how I fixed this. Because I use Backblaze to back up my flightsim computer, I was able to download from them a copy of the ShadersHLSL folder as it was prior to downloading PTA. I replaced the four shader files and that allowed PTA to process the shader directory correctly. It would seem that even rudimentary error checking prior to making changes to the shader files (e.g., "Can I write to the the BACKUP folder? If no, then throw error code without further processing") would solve problems for at least some new users. Having solved that problem does anyone know of useful presets as starting points for further exploration. I tried the SASS preset, but it yields a garish rendition on my system that made it very hard to read the flat panel displays in an FSL A320-X. Many thanks in advance.
  7. Whenever I try to apply a preset, I get errors like this Applying preset C:\Users\johnw\Desktop\Flight Sim Support\PTA tweak\default.ini... ERROR applying preset: source file C:\Users\johnw\Desktop\Flight Sim Support\PTA tweak\SHADERS_BACKUP\Cloud.fx not found ERROR applying preset: source file C:\Users\johnw\Desktop\Flight Sim Support\PTA tweak\SHADERS_BACKUP\General.fx not found ERROR applying preset: source file C:\Users\johnw\Desktop\Flight Sim Support\PTA tweak\SHADERS_BACKUP\GPUTerrain.fx not found ERROR applying preset: source file C:\Users\johnw\Desktop\Flight Sim Support\PTA tweak\SHADERS_BACKUP\FuncLibrary.fxh not found Preset has been applied with errors. See log above Shaders cache cleared If I try to restore original P3D shaders, I get this error ERROR: backup of shader file C:\Users\johnw\Desktop\Flight Sim Support\PTA tweak\SHADERS_BACKUP\Cloud.fx not exists ERROR: backup of shader file C:\Users\johnw\Desktop\Flight Sim Support\PTA tweak\SHADERS_BACKUP\General.fx not exists ERROR: backup of shader file C:\Users\johnw\Desktop\Flight Sim Support\PTA tweak\SHADERS_BACKUP\GPUTerrain.fx not exists ERROR: backup of shader file C:\Users\johnw\Desktop\Flight Sim Support\PTA tweak\SHADERS_BACKUP\FuncLibrary.fxh not exists Shader backup C:\P3D\ShadersHLSL\GPUTerrain.fxh has been restored to C:\Users\johnw\Desktop\Flight Sim Support\PTA tweak\SHADERS_BACKUP\GPUTerrain.fxh Shader backup C:\P3D\ShadersHLSL\PostProcess\HDR.hlsl has been restored to C:\Users\johnw\Desktop\Flight Sim Support\PTA tweak\SHADERS_BACKUP\PostProcess\HDR.hlsl Shader backup C:\P3D\ShadersHLSL\PostProcess\FXAAResolve.hlsl has been restored to C:\Users\johnw\Desktop\Flight Sim Support\PTA tweak\SHADERS_BACKUP\PostProcess\FXAAResolve.hlsl Shaders cache cleared I'm just guessing here, but I get the sense that PTA never backed up the shaders originally. I think this may have been caused by my running PTA from the zip file download. It seemed to work, but maybe it couldn't figure out where to back up the shaders. Worst of all, having failed to make backups it merrily went ahead and did the modifications which it now doesn't recognize. Does anyone have any ideas how to fix this? If I'm right about this (and I really hope I'm wrong) this seems like sloppy error checking by the software. John Wiesenfeld
  8. jrw4

    Disc A/P @ 1000 feet for landing... tips?

    Just for reference, controllers in FAA-land cannot issue speed adjustments inside of the FAF. A typical approach clearance including the speed constraint (for 31R at KJFK, for example) would then be "ABC123, eight miles from ZULAB, turn left heading 340, maintain 3000 until established, cleared ILS runwy 31R approach. Maintain 170 knots until ZULAB". That last is critical because all previous speed adjustments are cancelled when the approach clearance is issued. I guess 31R has a fairly typical ILS path (but someone else might have different info), so the FAF is at 5.3 DME and 1888 AGL. At a typical descent rate of 800 fpm on the GS, the crew only has about a minute to stabilize the approach while simultaneously deploying the gear, lowering the flaps to 30, and reducing airspeed by 25-30 kts. I wouldn't be surprised if this is a bit more than most desktop captains can do reliably, but there's no harm in cheating by having the gear down and flaps at 15 at the assigned airspeed prior to the FAF. Yes, it burns extra fuel and creates more noise, but then all you need do at the FAF is lower the flaps two notches and crank back the airspeed to Vapp. Issuance of airspeed adjustments on final isn't a magic sauce for increasing a runway's landing rate, since the a/c need to slow down to land and taxi off of the runway, but it does help a controller maintain even spacing. Since the time is short between issuing the approach clearance and the FAF, one can't make up for gross disparities in spacing this way. In the real world, I have landed a C172 in front of a flight of Air National Guard F4s. Tower told me to keep my speed up (hah!), but those guys must have been doing S-turns halfway across the state.
  9. jrw4

    Still problems with ASUS Motherboards?

    Also a Prime Z270/i7700K and also no problems, other than the usual mistakes induced by yours truly.....
  10. Thanks everyone for the thoughtful advice. I did carry out the update using the LM instructions (client only this time around) and it seems to have worked flawlessly, Now if only my piloting skills matched that description..... Cheers, John
  11. I may have lost track of this due to recent travels, but is there any particular advantage for those of us successfully using P3D v4.0 to update the client packages to v4.1? I have read the LM readme page, but there doesn't seem to be anything there that makes the update a "must do" item for me and my 737ngx/777-200LR install. What have I missed? Many thanks in advance.
  12. jrw4

    SELCAL ON 777

    Just to expand a bit on Olympic260's comment. you input your desired SELCAL code into the vPilot Connect dialog. In addition, you should include the code in the remarks section of your flight plan. I'm not sure if both of the major VATSIM ATC clients would automatically extract the code from the pilot client connect window, but they both claim to do so from the remarks section. It looks like you should only enter the four characters, not the dash. Hope this helps.
  13. jrw4

    A New Sim x64

    I come to P3D originally from XPlane 9 and 10, via FSX. It was always very frustrating in FSX and P3D to observe my CPU utilization using Task Manager: One thread was pinned at 100% and the rest were humming along a bit above idle. That is no longer the case. I'm just doing an approach to KIAD with the default scenery, ORBX Global and Vector, and ChasePlane. I'm running an i7-7700K lightly overclocked at 4.6 GHz, and a GTX970 GPU. Thread 1 is still pinned at 100%, but now six of the remaining seven hyperthreads are running at utilization levels well in excess of 50%, with the overall CPU utilization around 75%. Task Manager indicates that virtually all of that is P3D. The GPU utilization is around 50%. LM has done more with v4 than convert to 64 bit architecture. This seems to be a very different creature than was v2.5, my earlier installation. Those individuals waiting on the fence or elsewhere might want to take a very close look at v4. I don't have access to the source code of either P3D v4 or XP11 and doubt that I could understand them anyway, but both of these products now seem able to take effective advantage of modern computer architectures.
  14. jrw4

    PMDG and Dynamic Lights

    Unless the ORBX website is out of date, their LOWI scenery is not P3D v4 compatible. Is that correct? I tried a similar experiment at default LOWI and there was no discernible impact on frame rate locked at 30 fps at night using 4xMSAA and no observable shimmering either. Has ORBX announced a schedule for updating their airports? Does DL impact FPS at fields that have been certified as V4 compatible?
  15. jrw4

    PMDG and Dynamic Lights

    That would be excellent. It seems that (as has largely been the case with FSX in the past) these problems don't always show up on everyone's system. It would be good to have a clear demonstration that interested parties could try to reproduce. Thanks so much.