March 15Mar 15 I started having a loading issue with P3dv5.4 last week. I was getting a start up but the sim loaded a BLACK SCREEN. I did a myriad of things to fix this: I uninstalled Client, Content, and Scenery and reinstalled same; I looked at all recent addons and tried to determine if anything could have caused this so-called "crash". P3d was loaded, but there was no image on the monitor. So, I actually uninstalled P3d and all of my painstaking installations of planes, scenery, utilities, etc. I reinstalled it and started fresh. I called Jetline (my computer manufacturer) and spoke to them about it. They got into my computer with ANY DESK and deleted many temp files and did other cleanup types of things. They did delete the Cfg and let the sim load up a new one. That worked! However, I've done that many times, and it does work. However, after setting up a start scenario with perhaps an Airbus or CRJ (my favorite plane), I was back to the black start up screen. I uninstalled some ORBX files and reinstalled them, verified them, etc. Jetline today texted me and said that you are definitely supposed to use the DEFAULT screen with the Jet Fighter at whatever airport it's at ALWAYS. You can then load up any scenery or aircraft you want once you're in the sim. I've been doing that all day, and it does work. Absolutely no crashes! Since when can't you have a "saved scenario" of your choice of plane and airport to start the sim. I've always used P3d with my own startup screen and had no real problems. I was told that I got away with it for quite a while but as my P3d grew with addons, the startup screen was not able to load efficiently and that the P3d default screens would always work for me. Do most of you use the Default startup in P3d, or does your sim load fine with a custom startup you put together? Just curious if you've ever had this issue.
March 15Mar 15 Default, always. Since the early days of ESP-based sims (FS9 and later), the default scenario sets/resets state variables behind the scenes, some of which appear to persist from the last flight and which I suspect have never been available or visible via the SDK. All sorts of odd unhappiness has been resolved by loading up a default flight first before building a scenario at the beginning of a session. With P3D, through v5 at least, I've found that having a default acft and airfield load at startup into the scenario GUI is enough (e.g. you don't need to actually start a flight with the default scenario). Generally just having the F-35 pre-load at KRND by having it set as the default flight has sufficed. Bob Scott | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
March 15Mar 15 Author 21 minutes ago, Bob Scott said: Default, always. Since the early days of ESP-based sims (FS9 and later), the default scenario sets/resets state variables behind the scenes, some of which appear to persist from the last flight and which I suspect have never been available or visible via the SDK. All sorts of odd unhappiness has been resolved by loading up a default flight first before building a scenario at the beginning of a session. With P3D, through v5 at least, I've found that having a default acft and airfield load at startup into the scenario GUI is enough (e.g. you don't need to actually start a flight with the default scenario). Generally just having the F-35 pre-load at KRND by having it set as the default flight has sufficed. Yes. That's right. I let the F-35 pre-load and literally NEVER fly it. I then go to my Saved flights and pull something that's there or start a new flight. Thanks.
March 15Mar 15 Moderator @spilok, ouch! All that work for nothing. 😟 As Bob has said always, but always, start P3D with a default aircraft. I fly Concorde, PMDG 737/777 and a few other 3rd party aircraft but my startup is a Piper Cub. At the Scenario screen I select my aircraft. Make sure you have the Scenario menu visible. You can then select airport and time of day too. Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
March 15Mar 15 This has always been standard for me. Let P3d load the default selection screen and then choose what you want. Intel i7 6700K @4.3. 32gb Gskill 3200 RAM. Z170x Gigabyte m/b. 28" LG HD monitor. Win 10 Home. 500g Samsung 960 as Windows home. 1 Gb Mushkin SSD for P3D. GTX 1080 8gb.
March 15Mar 15 I have always loaded my preferred scenario without issues. But I will try the default start and then switch to my usual scenario. I know that “if it ain’t broke don’t fix it “ but this is worth a try based on what most of you are doing sherm
Create an account or sign in to comment