-
P3Dv5.4 Download Gives Empty File
Hi Ray, Good to see you are still active! I have actually solved my problem, but NOT via the attempted download route (which still doesn't work). Looking into my downloads folder there was just the one entry for Prepar3D and I missed it (its a mighty big folder!) so I've learned the hard way to use "Search" in future. Having then repaired P3Dv5.4.9, I should have used the Search facility to find my PMDG B777X files as my B777 models were showing in the Aircraft Selection window, but with message "No preview available, and no visible aircraft when loaded. These were under a single entry which, unknown to me, was acting like a file folder, and contained both expansion apps for the ER versions of the B777. It was just frustration that made me click on this file. I thus had both B777-200ER and B777-300ER download apps ready and waiting to use. I used them both and now have my B777 fleet back up and running. The next problem was the scenery files: all the add-on sceneries showed as present in both the P3D Add-On window and the Scenery Library window (but greyed-out) when P3Dv5 was running. None of them was actually running. I tried a new re-install of UK2000 LHR Extreme v3. I am now slowly re-installing all my add-on sceneries as needed. I do not know what caused these simultaneous problems (my copy of ActiveSky for P3D wouldn't load, either!) as I had not added anything, or made any updates (including my nVidia graphics files).
-
roadrabbit149 started following Catastrophic Frame Rate , P3Dv5.4 Download Gives Empty File , FS2020 Shutdown Problem and 1 other
-
P3Dv5.4 Download Gives Empty File
Title says it all. Tried to download available Prepar3Dv54.9.28482 from prepar3d.com and received an "empty" .zip file which of course will not open. Also got 2 PART files,one of 3,328,605KB,the other of 204,256 KB, both in zip.part format. Please help.
-
FS2020 Shutdown Problem
Just to pour more oil on the fire: Beware of making Keyboard binding changes in Control Settings away from 'Default' setting. I tried to change the ESC function, which in Control Settings default are "Toggle Pause" and "Set Pause Off" - which have never functioned, so why they are there, who knows. In Control Settings there is no mention of the "Return to Higher Menu" function, which has worked up until now (as in previous versions of MS Flight Sim). If I alter any key bindings in Keyboard and then load aircreft/place, then I lose this ESC function. If things get messed up (surely not?!) then return Keyboard to 'Default'. The ESC function then returns. When setting up MSFS all windows show [ESC] (previous higher level menu item) at bottom left of lower 'in game' task bar. Repeated pressses lead to the 'safe' shutting down of MSFS2020 (and 2024). Do I need to know an original quote to further explain this functionality - no!
-
PMDG Odd Wheelbrake Behaviour
Using FSUIPC6 with the PMDG B777 usually works fine. However, today, it seemed like the wheel brakes were 'dragging' or even 'ON' no matter the input. Checking the reaction to inputs on FSUIPC Calibration all was working and indicating normal. Power needed to achieve forward speed was way more than normal - any suggestions?
-
Catastrophic Frame Rate
Gents All, Progress at last! I did the recommended clean re-install procedure and this time I did not enable any of the many add-ons I have when I restarted P3Dv5.4. I also made no alterations to the Scenario window and pressed <OK>. The result is, using <Shift-Z> to display frame rate, I now have 60.0 +/- fps. This confirms to me that I have a software glitch in (one of) my add-ons. I shall now add each one individually to try and isolate the faulty add-on(s). The problem add-on was a corrupted FSUIPC6. Suffice to say that since I re-installed FSUIPC6 the problem has completely disappeared. I am currently sitting in an FSLabs A320 IAE at the Glasgow airport (UK2000 Extreme scenery). having just re-assigned all controls via FSUIPC6. My frame rate continues at a fairly steady 60 fps within a range of 54 to 74 fps What has amazed me is how the frame rate has not noticeably altered at all, even when adjusting the various graphics settings.
-
Catastrophic Frame Rate
Before I do the recommended full uninstall/re-install described (for which many thanks) I opened the BIOS to look for the above Intel graphics unit. I searched everywhere but was unable to do so - exactly where is it?
-
Catastrophic Frame Rate
I was only using the nVidia In-Game Overlay to monitor fps in MS2020 (i.e NOT trying to boost performance). I had just not removed the overlay when I ran P3Dv5.4 and I saw the figures. I shall remove it from my next run of P3Dv5.4. The performance boost app you suggest looks interesting. I shall try it out when I have solved the current problems.
-
Catastrophic Frame Rate
To clarify: yes, the sim is loading the sim from P3Dv5.4 screen icon, then after 28 seconds the Scenario screen appears asking for aircraft/airport/weather/ date and time. This is the window I referred to as the data entry screen. The default aircraft (since I originally installed P3Dv5) has been an F35 at a US airbase in south central USA. I can change it, but I was always advised to leave the default aircraft to load up as given. Happy to take advice here. Files deleted for a clean install were four: P3Dv5 Scenery, P3Dv5 Content, P3Dv5 Client and P3Dv5 Professional. There was no 5th file as previously described. Regarding the N/A entries: these are what is displayed by the <nVidia In Game Overlay> when selected. When I select <Shift-Z> I get the actual readings of around 0.3 fps.
-
Catastrophic Frame Rate
Hi Ray, Monitor resolution = 3840 x 2160 (native) Refresh rate = 60 Hz VSync = enabled fps target = unlimited Jobscheduler (from Prepar3D.cfg file) = [JobScheduler] AffinityMask=65535 P3DCoreAffinityMask=65535 MainThreadScheduler=0 RenderThreadScheduler=2 FrameWorkerThreadScheduler=4 When loading from scratch data entry window came up after 28 secs (fastest ever!) and Overlay shows: FPS 35, GPU 1%, CPU 1%, LAT N/A. Once data is entered and OK pressed, Overlay drops immediately to: FPS N/A, GPU 5%, CPU 9%, LAT N/A. As always, grateful for any assistance 😀
-
Catastrophic Frame Rate
Yes - that was how I did the 'clean re-install'. I have looked in the nVidia App and I don't have a profile for Prepar3D. I did try and add P3D but I got message saying option was not available. I have now also updated my nVidia Game Ready Driver to version 572.47 For more info I used the nVidia Game Overlay to check performance. Here are the results: MS2020 FPS: 35/48 GPU: 72/80% CPU: 25/26% LAT: 53/72 ms Prepar3D ver 5.4 FPS: N/A GPU: 2% CPU: 6% LAT: N?A
-
Catastrophic Frame Rate
Firstly, since previous, I have uninstalled P3Dv5.4 and done a 'clean' re-install. No improvement or error messages. Have reset shaders, also deleted Prepar3D.cfg file. Have also carried out 'sfc /scannow check' with no error messages generated. What puzzles me is that MS2020 works fine and gives 65 fps. I really would like my P3D to work as I am very attached (!) to my PMDG fleet of B747-400, B777 and B787, not to mention other well-known airliners and light aircraft..
-
Catastrophic Frame Rate
I am not getting any error message.
-
Catastrophic Frame Rate
Just recently I started getting the dreaded BSOD at random times using both P3Dv5.4 and its chief rival platform. A clean-up of my computer and a re-seating (with renewed thermal paste) of my nVidia Geforce GTX 2080 Ti appeared to solve that problem. However, now the P3Dv5.4 frame rate drops to 0.4 fps from about halfway through loading. This is independent of aircraft chosen, from default and also either PMDG and FSLabs aircraft models. The rest of the loading takes place veeery sloooowly, with the Flight Computer Initialization running at about 18 to 22 seconds per subscreen second. Flying the rival platform (2020 version) I do not get any fps problem and get around 65 fps. I have tried doing "repairs" to both P3Dv5 Professional and also P3Dv5.d Client without success. I get the feeling that either I have a corrupt file somewhere within P3D (but why wasn't that corrected during the "repair" procedures?) or is there a setting somewhere within P3D that has somehow changed. As you can see, my thinking is rather simplistic at this stage and I would appreciate some good guidance.
- Fenix A320 - ECAM F/CTL L SIDESTICK FAULT
-
DWM.exe Crash to BSOD
I was recently plagued with the above crash (cause found by using Fortect) to Black Screen of Death with cooling fans running at max speed. The guidance and hints in most forums did not help. However the problem has been solved and I would like to share my experience. The problem started whilst running Prepar3Dv5.4.9 together with PMDG's B777 aircraft. So I started with that as baseline. Here are the steps I took with the results recorded for each step: 1. I ran the computer with no main apps running at all - so no P3D and no PMDG. The computer ran perfectly for 12 hours. 2. I did a comparison run with MSFS2020 running - again no failures at all after 7.5 hours. 3. I completed a "repair" of P3D (Having repaired P3D Professional, I actually had to re-download all 'content' files in order to repair P3D Content as well). When I next tried to load the PMDG B777 I got a message informimg me that I needed to activate the B777 Base Package. To do this I had to re-download the files from PMDG. However, I then ran into another problem: the downloads now work from a 'pop-up' (I was unaware of this - thank you Iwebber on this forum). I found that my browser pop-up blocker was active and blocking the download. I rectified this in my browser settings uner 'Security and Privacy'. I was also advised (Thanks to the good folks (thank you Chris M!) at PMDG) to go to "msc.services" and to ensure that "FlexNet Licensing Services 64" was set to 'Automatic' - mine was set to 'Disabled' (again, who knew?!). Having completed all the above, I then ran and completed a flight from EGLL to CYYZ successfully, with no hiccups. I believe the problem can occur with other computer 'games' and apps. If so, it should be possible to follow the generic approach suggested by the above to achieve a solution. Hopefully this will be of help to others who have experienced this DWM.exe failure/crash.