October 5, 201510 yr Undertook the 737ngx 800 WL in taxi trials at Stansted (UK2000Xtreme) Aircraft had no issue with gauges/controls etc, however, when I closed Prepar3D down an error message that the pmdg 737 900 had generated errors was generated to check the P3D v3 log. Among some minor errors, a log of some 600 lines had been generated for the 737-900. At no time had I loaded this aircraft. I should mention that no errors were generated during runtime or the performance effected for the 737-800 Any probable causes for this error [error.165]error=Duplicate Section Name File: E:\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\PMDG 737-900NGX WL\aircraft.cfg Section: SMOKESYSTEM down to[error.654]error=Duplicate Section Name File: E:\Lockheed Martin\Prepar3D v3\SimObjects\Airplanes\PMDG 737-900NGX WL\aircraft.cfg Section: SMOKESYSTEM steve S
October 5, 201510 yr Per Robert Randazzo of PMDG: "Launch Prepar3D v3, then go to OPTIONS, SETTINGS, GENERAL. On the top left quadrant, you will see two check-boxes: "Scenario Error Logging" and "Content Error Logging." Uncheck both of these boxes." The error-logging system of P3D is causing your crash on exit with the SMOKESYSTEM errors. This logging function was really only intended for use by developers, but LM has it enabled by default when you initially install P3D V3. Uncheck the boxes, and you should have no further problems. Jim BarrettLicensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.
October 5, 201510 yr Per Robert Randazzo of PMDG: "Launch Prepar3D v3, then go to OPTIONS, SETTINGS, GENERAL. On the top left quadrant, you will see two check-boxes: "Scenario Error Logging" and "Content Error Logging." Uncheck both of these boxes." The error-logging system of P3D is causing your crash on exit with the SMOKESYSTEM errors. This logging function was really only intended for use by developers, but LM has it enabled by default when you initially install P3D V3. Uncheck the boxes, and you should have no further problems. But the messages are stating real problems with the software. - David Lee
October 5, 201510 yr Thanks Jim, I'll do that, as David mentions a problem must exist to generate an error message. I'm not concerned, it didn't affect my flight. steve
October 5, 201510 yr Gents- We have reviewed this and the conclusion is as follows: You can ignore it. There is one error here that we will correct in a future update (the duplicate SMOKE SYSTEM entry in the 900WL aircraft.cfg file). It is harmless and does not consume any resources. The remainder of the errors logged are the result of Lockheed Martin setting a logging parameter that picks up on a technique that we use to instance gauge processes that take place in multiple places around the cockpit. (Lighting, etc.) I'm not sure why they flag it as an error- it isn't. As we recommended with FSX- if you aren't a developer we recommend turning that logging off. It creates more false instances than it does useful information. David and Steve, The above is a quote from Robert Randazzo and should answer your questions regarding it being an actual error in the software - it's from a closed thread entitled "PMDG 737NGX and Prepar3D V3 Error" (the thread was closed due to the answer being placed in a Sticky instead). The thread can be found here if you want to read through the full exchange.
October 5, 201510 yr You can manually fix most of the errors listed (cover all the 777 variants and 737 variants) ... I've done this and there are no ill effects. Or you can ignore them per Robert. Not exactly sure what Robert is talking about on the technical side, but I had no issues after correcting the reported errors. The 777 performance is outstanding in V3 ... can't believe what I got away with GSX, ASN, 3rd party airport, extremely high graphics settings and locked at 30 FPS (30Hz), very smooth flight. Cheers, Rob.
Create an account or sign in to comment