guswhite3 Posted July 15, 2010 Report Posted July 15, 2010 I recently loaded Win7 64 bit on a new drive, then loaded FSX (w/updates), reloaded FSInn/CoPilot (latest ver), reloaded latest ver of FSUIPC, and some add on aircraft (PMDG 747, Cap Sim 757, QualityWings 757, etc.). The Captain Sim and QualityWings 757's run fine until I load up FSInn (remote or local), then FSX runs for about 5 minutes and then it freezes and crashes. The problem is related to FSInn because everything runs great until I try to go online with FSInn. I have researched this problem with no joyany ideas where to look? I have read and followed Larry James posts with no luck. I thought I would switch to SB4, which works fine, except I can't see any other online aircraft. Here is is the error: "FSUIPC error #12 FSUIPC_ERR_SENDMSG, error sending message to FSUIPC." Help is appreciated... :) Gus UAL1169
guswhite3 Posted July 15, 2010 Author Report Posted July 15, 2010 OKneed to add that the FSX w/FSInn only has a problem with the CaptSim and QualityWings aircraft (both 757s). PMDG 747 & B1900, LVLD 767, and any stock aircraft perform just fine. I have not tried my Wilco/FeelThere aircraft (CRJ). What is it about the two addon aircraft that FSInn (or FSUIPC) doesn't like? Is it a setting I'm missing? :(
guswhite3 Posted July 15, 2010 Author Report Posted July 15, 2010 Update: My FeelThere/Wilco aircraft (777, Airbus, CRJ) also work just fine, so it is just CaptainSim and QualityWings.
JSkorna Posted July 16, 2010 Report Posted July 16, 2010 Hi, You might want to see what the FSInn folks have to say about this. It looks like the error is from their program.
Pete Dowson Posted July 25, 2010 Report Posted July 25, 2010 Here is is the error: "FSUIPC error #12 FSUIPC_ERR_SENDMSG, error sending message to FSUIPC." What program gives you this message, and what actually crashes FS? If the number 12 is quoting the standard FSUIPC interface error number in the program concerned, then it simply means that the "SendMessageTimeOut" call, used to send requests to FS's main Window, timed out (i.e. failed) on several retries. This call should only be used by External programs, not internal DLLs or Gauges, so it is likely that after FSInn (or FSCopilot, which I think it uses?) somehow caused FS to crash, an external program (EXE) you are running simply could not talk to FS because it had crashed. If this is the case, and it sounds like it, then the true culprit is not the one suffering Error #12. I don't think either FSInn or FSCopilot use FSUIPC. You need to refer your problem to FSInn support. Regards Pete
guswhite3 Posted July 26, 2010 Author Report Posted July 26, 2010 Thanks, Pete. I actually temporarily solved the QualityWings 757 aircraft problem with an ignore line in the fsx.cfg so that FSInn doesn't see that addon. The downside is that my aircraft shows as a Cessna to other flyers on VatSim. I can fly now with no crashes.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now