Error - Printable Version +- FsPassengers Forums (http://www.fspassengers.com/forum) +-- Forum: Flight Simulators (http://www.fspassengers.com/forum/forumdisplay.php?fid=7) +--- Forum: Prepar3D General (http://www.fspassengers.com/forum/forumdisplay.php?fid=8) +--- Thread: Error (/showthread.php?tid=18226) |
Error - Jari95 - 21-11-2017 Hi all, I just bought fspassengers for p3d V3.4. I use it together with the FSLabs 320 and GSX on some payware scenery airports (like EDDM, LSZH, EGLL,...). Since a recent update to windows 10 I've been having multiple issues with child windows (Error creating child window resulting in me not being able to use either GSX or FSP). With FSP however it gives me an extra error message called error 34 "unable to subclass mini report gauge". Anyone have any ideas? RE: Error - Joeflyer - 21-11-2017 Jari, sounds like this topic on the LM forums: http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=126667 RE: Error - Jari95 - 21-11-2017 Well it was, so I uninstalled this 'security' update and the problem seemed fixed untill my stupid FSLabs 320 started crashing the whole sim again. Now i re-installed that thing. If i take the standard piper and I run GSX together with FSP i experience 0 Problems. It's just when I add that over-priced buggy 320 that the same bug occurs. On FSP it occurs when i press the OK-Load Flight option in the Start Flight menu. So to clarify. FSP runs perfectly with the standard piper, even together with GSX. I just receive the Child window error when i run the FSLabs 320. On top of that error i get the aforementioned Error 34 in FSP itself. RE: Error - Joeflyer - 23-11-2017 So, the FS Labs A320 is actually the culprit. Not much FsP can do about a problematic addon aircraft. RE: Error - Jari95 - 23-11-2017 Nope, it was actually a bug in windows. It kept auto-updating. Thank you for the help. RE: Error - Joeflyer - 26-11-2017 You indicated that the A320 is buggy, so why is that a "nope"? |