April 20, 20206 yr 2 minutes ago, daelight said: Using the majestic and getting CTD. Probably because using addon airports. Sliders to the middle, not using hi-res textures. i7 8700k 1080ti. If anyone is successful flying it with add-on p3dv4 airports it would be good to know. Noticed the sound from inside the passenger cabin was broken too (short clipping loop) It may not be the majestic, I've found that sometimes when I run v5 and make an adjustment, about 50% of the time after initialization v5 just shuts down. try a second time and it will run, sometimes it takes 3 tries Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz (8 cores) Hyper on, Evga RTX 3060 12 Gig, 32 GB ram, Windows 11, P3D v6, and MSFS 2020 and a couple of SSD's
April 20, 20206 yr 2 minutes ago, cwburnett said: What kind of CTD? Out of VRAM or other? I have only installed scenery with v5 installers. I have ORBX Base, NA LC, NorCal, Socal and PNW installed. LVFR KMIA, LVFR KEYW, LVFR KSNA, Flightbeam KSFO and KPDX. ORBX KSAN, KPSP. Oh, and FB SEQM. That's where I've flown it so far... Not VRAM as only 4GB used (4.3GB total inc windows) So likely the Technobrain airports I am flying to and from are tripping it (generic kernalbase error) Will try defaults-only flight later.
April 20, 20206 yr 10 minutes ago, daelight said: Not VRAM as only 4GB used (4.3GB total inc windows) So likely the Technobrain airports I am flying to and from are tripping it (generic kernalbase error) Will try defaults-only flight later. In case it matters on the settings tab in the MJC84 control panel I have my graphics quality and refresh rate set at medium. Don't know if that matters, but you could try that if you're still not having any luck. Oh and using Queue Timer and FDE sync enabled. Edited April 20, 20206 yr by cwburnett 5800X3D | Radeon RX 6900XT
April 20, 20206 yr 16 minutes ago, cwburnett said: In case it matters on the settings tab in the MJC84 control panel I have my graphics quality and refresh rate set at medium. Don't know if that matters, but you could try that if you're still not having any luck. Oh and using Queue Timer and FDE sync enabled. Thanks for that info, will adjust to match
April 20, 20206 yr Tried to install the Q into V5 but got blurry/pixilated displays. P3D 4.3, Windows 10/64 bit, Intel 6700k @ 4.7 air-cooled, NVidia 2080 Ti Founders Edition, ASUS Rog Maximus VIII Ranger, 16GB G.Skill Ripjaws DDR4 @3200, Phanteks Anthoo Pro Series Case, Samsung 950 Pro M.2 500GB, Sandisk 1TB SATA, Seagate 2TB Hybrid Drive, Cooler Master 700W, 40-inch Samsung 4k TV
April 20, 20206 yr 20 minutes ago, bbain1187 said: Tried to install the Q into V5 but got blurry/pixilated displays. check your prepar3d.cfg in VC texture resolution make sure is 4096. After CTD this file is messed up. Ramon De Valencia AMD 9950X3D / 64GB DDR5 6000MHz / RTX 5090 / 1200 watt PSU MSFS 2020 and 2024
April 20, 20206 yr It seems there’s something in v5 causing these pixelated glass displays, here’s something you can try. Dave Current System (Running at 4k): ASUS ROG STRIX X670E-F, Ryzen 7800X3D, RTX 5090, 55" Samsung Q80T, 64GB DDR5 6000 RAM, EVGA CLC 280mm AIO Cooler, Brunner CLS-E NG Yoke, Thrustmaster Warthog HOTAS & Stick, Thrustmaster TCA Quadrant & Add-on, VirtualFly Ruddo+, TQ6+ and Yoko+, GoFlight MCP-PRO and EFIS, Skalarki FCU and MCDU
April 20, 20206 yr 10 hours ago, ttbq1 said: check your prepar3d.cfg in VC texture resolution make sure is 4096. After CTD this file is messed up. This was not the issue, but thanks for the suggestion. 47 minutes ago, regis9 said: It seems there’s something in v5 causing these pixelated glass displays, here’s something you can try. Bingo! Thank you!!! I just changed every 'pixel_size=1024' entry in the panel.cfg to 4096 and now have super-crisp displays in the Q400! 2048 was an improvement as well, but opted for the higher setting with my 4k display. P3D 4.3, Windows 10/64 bit, Intel 6700k @ 4.7 air-cooled, NVidia 2080 Ti Founders Edition, ASUS Rog Maximus VIII Ranger, 16GB G.Skill Ripjaws DDR4 @3200, Phanteks Anthoo Pro Series Case, Samsung 950 Pro M.2 500GB, Sandisk 1TB SATA, Seagate 2TB Hybrid Drive, Cooler Master 700W, 40-inch Samsung 4k TV
April 20, 20206 yr Short report: it runs very well for me in P3D v5. I know it since it was released (first FSX, then P3D v4), and fly it regularly. To me, the handling feels exactly as before. Some minor things: the APU bleed sound is not there, and some sawtooth artifacts are under the speed placards. The cockpit is a bit darker, and PFD, ND and MFD are more reflective. All visuals are sharp. What puzzles me is the message "This gauge must be used under Prepar3D V4.0 or higher" when loading it. I have to click o.K., then the flight loads. Does someone know what this message means? Michael Michael Thesen MSFS, HP Reverb G2, Gigabyte B760 32Gb, Samsung 970 EVO, Geforce RTX 4070-TI, Win11, i7-14700KF, Thrustmaster T16000M, Saitek Pro Flight Rudder Pedals
April 20, 20206 yr 30 minutes ago, michaelth said: Short report: it runs very well for me in P3D v5. I know it since it was released (first FSX, then P3D v4), and fly it regularly. To me, the handling feels exactly as before. Some minor things: the APU bleed sound is not there, and some sawtooth artifacts are under the speed placards. The cockpit is a bit darker, and PFD, ND and MFD are more reflective. All visuals are sharp. What puzzles me is the message "This gauge must be used under Prepar3D V4.0 or higher" when loading it. I have to click o.K., then the flight loads. Does someone know what this message means? Michael I think the gauge is just seeing a version that doesn't comply with what it is looking for, so throwing the message, but isn't creating a problem. EDIT: I was wrong, there are no sound files that had to be moved. Maybe double check your sound settings in the MJC84 Control Panel app? Or even just reset them so that the INI file reinitializes them to the correct sound device. Edited April 20, 20206 yr by cwburnett Sound file correction 5800X3D | Radeon RX 6900XT
Archived
This topic is now archived and is closed to further replies.