October 16, 20178 yr Hello, I have tried everything but can't find the solution. Even on a clean P3D v4 with only Orbyx FTX Global and regions but without any other scenery add-ons, whenever I launcg a PMDG plane (777/737/747) my P3D crashes after I few seconds when all other aircrafts do work. The P3D error reporting shows nothing except ; [error.0] error=Payload station indexes should be between 1 - Number of Stations [error.1] error=Payload station indexes should be between 1 - Number of Stations [error.2] error=Payload station indexes should be between 1 - Number of Stations [error.3] error=Payload station indexes should be between 1 - Number of Stations [error.4] error=Payload station indexes should be between 1 - Number of Stations [error.5] error=Payload station indexes should be between 1 - Number of Stations [error.6] error=Payload station indexes should be between 1 - Number of Stations [error.7] error=Payload station indexes should be between 1 - Number ....... Does anyone have the same issue ? \Thank you, Greg too much, too soon....
October 16, 20178 yr Commercial Member 7 hours ago, pao said: Does anyone have the same issue ? You using any external programs to adjust the load on the aircraft? Some sort of passenger or VA application? Kyle Rodgers
October 17, 20178 yr Author HI, I actually I performed a clean instal of P3D thinking that would solve the issue so beside some ORBX texture and regions + Fsuipc updated for P3Dv4, there is nothing. No add-ons, no sceneries... The funny thing is that the crash only happens with PMDG aircrafts. too much, too soon....
October 17, 20178 yr Recommend reading through the entire thread. Three recent Win 10 updates are now all carrying a bug that can cause some crashes with a number of aircraft in P3D (3.x - 4.0 - 4.1). 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
October 18, 20178 yr Commercial Member 9 hours ago, pao said: any chance PMDG could bring us a patch ? No. Microsoft's update affects the core of your operating system. Everything is built on top of that. If the core of your OS is corrupted by bad code, asking everyone to stop what they're doing to work on a patch that may or may not be able to sidestep the issue isn't entirely reasonable. Please take note that this affects many developers. It isn't a PMDG issue. Kyle Rodgers
October 18, 20178 yr Commercial Member 17 minutes ago, pao said: So it means that W10 latest update is not compatible with PMDG then ? There is an issue with one of the latest KBs, which is noted in a few threads here in the forum. As I noted earlier, though, the error itself is something that you may want to research, because it may not be related to the Win 10 update. Looks like yours may be related to Visual C++ Runtime issues (and quite an old one at that). Also: the way you phrased it is not correct. Microsoft released an update that caused troubles for all kinds of devs - not just us. Kyle Rodgers
October 19, 20178 yr Author Ok thanks Kyle for your explanations. .... and thank you Microsoft ! too much, too soon....
Archived
This topic is now archived and is closed to further replies.