cyyt47

Micheal - I tried playing with the situation file but went back to the way it was (with spaces) as leaving the spaces out caused startup errors. As for the *default.fmxl, mine has the underscore. Recent update - Whenever the error occurred, the event viewer showed "Driver ACPI returned invalid ID for child device". To me, that's sounds like a system error. After a bit of googling, I found a site that suggested changing the Windows Driver Foundation Service from Manual to Automatic which I did. Since making the change, I've logged about two hours of sim time and, so far anyway, no errors. Time will tell if it is indeed fixed but I'm optimistic as previously I couldn't get anymore than a few minutes into a flight before the error would occur. Coincidence or not, right now, I'm happy. Will post back if the situation changes. Thanks much, guys. ....Lloyd

Thanks, guys. First of all a quick intro; My name is Lloyd Noel. I've been an avid simmer since way back to the Sub-Logic flight sim days. Over the years I've been active fixing other folks problems on flightsim.com hardware forum. Now I'm the one looking for help and it looks like I've come to the right place. As for gear, I build my own rigs. Currently running an Intel 6700K at 4.7GHz on an ASUS Maximus Hero VIII mobo with 16GB RAM and a GTX970 video card. OS is 64-bit Win7 Pro on a 480GB SSD. P3D is on its own 240GB SSD. I'm using CH Products Pro Pedals, Yoke and Throttle Quad plus Saitek Multi, Radio and Switch panels. To the problem at hand... Micheal - The situation line in my P3D.cfg file points to this file: B58 at KHQM.fxml (my saved default flight). Rob - Thanks for chiming in. System details above and tomorrow when the last of my Christmas guests depart I will get back with Event Viewer errors and/or ContentErrors log. Best rgds, Lloyd

Thanks, Micheal. Checked and found that my Prepar3D_Default.FXMLt file is exactly as you said it should be (including the underscore). I read through the link you posted in your reply but, unless I am missing something, I don't see any reference to the child window creation error. I also searched this forum and came across one of your posts containing a link to a LM forum post about the problem. I had been following that thread on the LM forum when I was attempting to fix the child window error with v3. That thread contained a "work around" which said to disable controllers in P3D and use FSUIPC (registered version) to calibrate the controllers. This is the way I calibrate my controllers anyway but it had no bearing on my child window error. BTW - Not using EMT and have not yet installed my PMDG products This problem is making P3D unusable for me so if you or anyone else can help further it would be greatly appreciated.

Before the v3.1 release I was constantly plagued with "Error Creating Child Window". I was hoping the update would fix this but it has not. Anyone else having the same problem? If so, is there a fix?