|
|
Post by leen on Aug 15, 2015 15:45:29 GMT -5
I have been running windows 10 for a week and had not problems with fsx or fscaptain. However, today when I tried FSX I got an error message that fsx has a problem with an addon. FScaptain.dll. fsx will load if I say not to use it. Also FScaptain is no longer in the fsx addon menu. The DLL.XML shows the FScaptain.dll entry, and it is also in the fsx modules folder. FSX cfg lists it as trusted. Attachments:fsx error.docx (1009.57 KB)
|
|
|
|
Post by peter on Aug 15, 2015 17:52:42 GMT -5
Hi Leen, this may be really bad news. A few months ago I encountered the same problem. In my case, it wasn't triggered by FSCaptain at all, but FSX crashed violently after I loaded a specific flight plan for a payware airplane (I verified that it was that flight plan and no other issue). FSCaptain just happened to be open at the time and somehow Windows henceforth insisted that FSCaptain.dll was not to be trusted. FSCaptain is not the only addon that may be affected because this is actually a Simconnect problem, see forum.simflight.com/topic/68382-fsx-fails-to-run-after-fsuipc4-first-installed/To make a long story short, after about 300 FSX restarts and three weeks of trying to solve this problem I had to concede defeat and moved on to P3D. That was actually a blessing in disguise because P3D has a lot of nice features, I am quite happy with the switch. As Pete Dowson wrote, you may or may not solve the problem. If not, FSX-SE may be an option. Sorry that I do not have better news. Peter |
|
|
|
Post by Travis on Aug 15, 2015 20:50:42 GMT -5
I've seen such dialog boxes, some of which even pointed a finger at FSUIPC!!!
None of them ever pointed a finger at a utility/add-on that I didn't know of. So I've always forged ahead... saying "YES / GO AWAY" to whatever they've asked.
If you have "untrusted" FSCaptain with your simulator then I don't know the mechanism that would restore trust (even if there is one).
|
|
|
|
Post by andlaz on Aug 16, 2015 5:39:11 GMT -5
|
|
|
|
Post by leen on Aug 16, 2015 8:46:04 GMT -5
I was able to fix the problem by doing a restore to the day before the problem. I should have done that before removing and reinstalling fscaptain as I am now
on a new career. Don't know what caused the problem, as everything was where it should be as per my first post. The only thing that changed was an update to
windows 10 and windows defender. Uninstalled them but still same.Andlaz, I saw that article and my trust policy was as it should be, so not that. Just some
crazy thing that windows10 must have done. Anyway I am back in business on a new career. tks for your time and input. Keep on flying.
|
|
|
|
Post by peter on Aug 16, 2015 11:19:56 GMT -5
Hi Leen, that's great news, I am really glad that you were spared my fate  @ Andlaz: thanks for this suggestion. It is great to have additional hints in this thread because they might work for some people who run into this annoying problem. In my case the 0x23c00 trick didn't work (  ), but that doesn't mean it may not work for someone else. Best, Peter |
|
|
|
Post by leen on Aug 17, 2015 10:18:30 GMT -5
My problem has returned. I think it must be a problem with windows 10. I installed the new fixpack this morning, and loaded FSX. It said that it didn't trust Fscaptain.dll and gave me a choice of using it or not. When I said yes, it crashed .
Loaded it again and this time said NO. It then did what it should by asking me to run FScaptain and then to trust. Then I did the same for the guages, and then it crashed. Loaded again and said NO and it loaded and I was able to start the
FCDU guage and complete flying. The only thing in event viewer is exception code: 0xc0000005, faulting application name FSX.exe, faulting module path: unknown. Very curious to see if anybody else running Windows 10 has had
the same problem?
|
|
|
|
Post by leen on Aug 17, 2015 12:58:30 GMT -5
It looks like the only thing not being allowed is the Fscaptain.dll and also Fscaptain is not in the fsx addon menu. The guages are being accepted. Fscaptain appears in every location including being trusted in FSX.CFG file. Tried
compatability mode but so far no go. Meant to ask previously about when you load the fixpack or full install it say there are write protected files. Is this right?
|
|
|
|
Post by Travis on Aug 17, 2015 14:34:42 GMT -5
This is another story that keeps me well satisfied with Win7....  Lee, if you ever get stuck again with an untrusted FSCaptain try this old trick. Open your fsx.cfg file and manually remove all references to FSCaptain.dll and your gauges from the [Trusted] section. This should force FSX to ask once again to "trust" FSCaptain (twice actually; once for the dll and once for the gauge). |
|
|
|
Post by leen on Aug 17, 2015 14:48:27 GMT -5
Way ahead of that one. Deleted FScaptain.dll from all locations, and removed Fscaptain.dll and fcdu gauges from fsx.cfg. Then installed the latest fix pack and it
still doesn't recognize the Fscaptain.dll and won't give me fscaptain in the fsx menu add on. It does exist in the modules under FSX. Am able to fly if I tell it not
to use fscaptain.dll when FSX loads. Will wait to see if anybody else has seen this with windows 10.
|
|
|
|
Post by peter on Aug 17, 2015 16:35:44 GMT -5
Hello Leen,
I do not think that this is a Win 10 issue at all. I am using Win 10 and so far everything works great except for one (unrelated) addon. For me, the issue appeared under Win 8 and a loong time after I started using it. Judging from Pete Dowson's remarks this is a bug in FSX/Simconnect, not a Win X problem. If I am not mistaken, the FSCaptain.dll in FSCaptain/bin installs the menu in FSX, so if the dll doesn't run then it is natural that you won't see the menu.
I really tried hard to find a solution but there are only a few resources out there that mention this problem at all.
Just to try to figure out under what conditions this problem occurs: when this first happened to you, can you recall whether you had any other addons running? If yes, which ones?
Best,
Peter
|
|
|
|
Post by leen on Aug 18, 2015 14:24:42 GMT -5
Peter, not sure which aircraft I had been flying, but I completed the flight and closed FSX and ASNext out. The next day I loaded ASNnet (current version) and the FSX. As FSX was loading, I got the FSX detected a problem with third party
add on. company unknown. fscaptain/bin/fscaptain.dll. I do have QW757 , and a freeware A380 installed. As I said FSX never get past the loading screen when the fauld comes up.
|
|
|
|
Post by peter on Aug 19, 2015 3:28:34 GMT -5
Hi Leen, thanks for the information, which I find very interesting. When the crash happened to me, I loaded a PFPX-generated flight plan EGSS->UUEE into the FMC of the QW 146. I also had ASN and FSCaptain running at the same time, so that may be a clue. That flight plan killed FSX intantly, and after the first occurence I was able to repeat this every time, even without any other addons running besides the QW 146. I contacted QW support and they had no issues with that flight plan at all. However, since that first crash I cannot use FSCaptain in FSX anymore Pete Dowson's post indicates that this is a timing problem in Simconnect, so maybe QW, ASN and FSCaptain together have some unfortunate timing?! On the other hand, you and I are the only two cases I know where this problem occured (with any addon), so this is just a speculation. Still, I will discuss with Dutch and Travis what we can possibly do. I hope you will have more luck than I had. Peter |
|
|
|
Post by peter on Aug 19, 2015 3:46:20 GMT -5
Important update: 2-3 weeks ago I upgraded to Win 10 (everything works great except for Aivlasoft EFB). I hadn't started FSX since then, but your post inspired me to give it a try. Result: FSX displayed the usual "detected a problem with third party software" message at the beginning, but when I clicked yes, it worked normally. I can run FSX with FSCaptain again! As not much is known about this problem, I don't have an idea why it works now. Maybe because I didn't try for a while, maybe because I switched operating systems. It is strange that this is exactly the opposite phenomenon that appeared to you when installing Win 10. I guess perseverance is the key, as Pete Dowson wrote. Good Luck, Peter |
|
|
|
Post by leen on Aug 20, 2015 11:06:52 GMT -5
Peter, Travis. I want to thank you for your concern about this issue. I am able to run the program all be it without the addon menu. everything works okay as long as on the opening screen I say not to run the third party addon "fsx/fscaptain/bin/fscaptain.dll. It is strange, that when I delete fscaptain.dll from the fsx.cfg trusted area, and start FSX and when the third party thing comes up I say yes, and then it asks me if I want to run (yes) and then (trust) FSX
crashes. Open again and say no and everything works except addon menu. FSX.CFG does then show FScaptain.dll in the trusted section. Anyway everthing else works.
|
|
). Note those e zeros, not O letters.
), but that doesn't mean it may not work for someone else.