FSDreamTeam forum
Products Support => Memphis KMEM Support FSX/P3D => Topic started by: demio on December 11, 2016, 08:29:33 pm
-
Hello everyone,
I have a problem with KMEM and the iFly 737 and 747. Approaching KMEM with the 747 a few days back, I had a CTD with the g2d.dll error. I found this thread:
http://www.fsdreamteam.com/forum/index.php/topic,13623.0.html (http://www.fsdreamteam.com/forum/index.php/topic,13623.0.html)
...but unfortunately, a) it's locked, and b) no one was talking about the iFly.
The crash with the 747 is 100 % reproduce-able. When in the VC and anywhere near KMEM, I get a CTD. With the 737, it's slightly different: If I load up the 737 with KMEM, there is no crash, but also no KMEM - the scenery objects aren't created.
I "emptied" the dll. and exe.xml files from all but the Addon Manager entries, and sure enough, I could load up the 747 and KMEM, but then the 747 doesn't work (black screens, no gear, no function).
Is there any advice available on this? Thank you!
Edit: I use FSX "Classic" with the X-Pack, I believe.
-
That thread finally proved, after so many different tests
- The G2D.DLL crash is always caused by other addons. There, it was mostly the usage of outdated version EZDOK camera, but of course it's possible there might be similar issue with other 3rd party modules out there.
I "emptied" the dll. and exe.xml files from all but the Addon Manager entries, and sure enough, I could load up the 747 and KMEM, but then the 747 doesn't work (black screens, no gear, no function).
I think this test of yours proved the crash was caused by another 3rd party module. It's not sure, however, if it's the iFly modules, because you said you removed "everything". Now, you should re-enable all modules, one by one, which is the only way to find which is the offending one.
-
Thank you for your reply.
Since it doesn't happen with other aircraft (I tested the default 172 and PMDG's MD-11), AND the problem doesn't occur with the iFly aircraft on any other airport (although I'd have to test your KORD), I'm pretty sure it's the combination of KMEM and iFly. For the sake of argument, let's say I'm right with that assumption: What do I do now? You say it's not your product. I will bring the issue to iFly's attention, but iFly will maybe say the same thing. I'm assuming you don't have the 737 or 747 available for testing?
-
For the sake of argument, let's say I'm right with that assumption: What do I do now?
Since you said your crash was so easily reproducible as soon as you approach KMEM with that plane, I guess the only possible reply is: "thank God FSDT has a Trial".
The main point of offering a Trial, is precisely to let users test our product with their own combinations of addons before purchasing it and according to your description, this problem should have been obvious while testing.
I'm assuming you don't have the 737 or 747 available for testing?
No, I don't. Do they have a Trial version ?
In any case, I would like to know if the problem happens at KMEM only, or in other FSDT sceneries. KORD would be a good test and, if you can KIAH (which of course, can be freely downloaded too). If KORD works and KIAH doesn't, that *might* give some indications of the reason.
-
This chap did bring his problem to iFly and I (I'm part of the support team) was unable to reproduce it with any FSDT airport. So he is now going through the dismal process of going through the add-ons in an attempt to find the magic combination. Flight1, of course, does have the equivalent of demo versions in that they offer a 30 day, money back, guarantee for their products.
Regards,
DJ
-
This chap did bring his problem to iFly and I (I'm part of the support team) was unable to reproduce it with any FSDT airport.
That's good to hear. In fact, I was quite sure there was no conflict specific to iFly, since nobody reported it so far.
So he is now going through the dismal process of going through the add-ons in an attempt to find the magic combination.
I'll be interested to know more. One thing to check (although our recent installers automatically fix this), is if the FSX.CFG has the (dangerous) Poolsize = 0 command in the settings, which is an almost sure recipe for G2D.DLL crashes, which is another thing that came out in the thread related to crashes.
-
So, I'm in the process of testing. So far, I've moved the entries in dll and exe.xml to the end, but then I get 3 errors on FSX startup:
No 1 states "The procedure entry point SimConnect_Text could not be located in the dynamic link library simconnect.dll"
No 2 and 3 are Windows error message boxes:
"Problem signature:
Problem Event Name: BEX
Application Name: fsx.exe
Application Version: 10.0.61637.0
Application Timestamp: 46fadb14
Fault Module Name: StackHash_66f0
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 00000000
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 66f0
Additional Information 2: 66f06d06f844bd5c49b97c88d6c514cb
Additional Information 3: 7235
Additional Information 4: 723561e9eaa5467048b1b8de149bbcea"
"Problem signature:
Problem Event Name: APPCRASH
Application Name: fsx.exe
Application Version: 10.0.61637.0
Application Timestamp: 46fadb14
Fault Module Name: API.DLL
Fault Module Version: 10.0.61637.0
Fault Module Timestamp: 46fadb58
Exception Code: c0000005
Exception Offset: 000533bf
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 7d79
Additional Information 2: 7d795e2d464162c1163def7d89a0a7c7
Additional Information 3: a3f5
Additional Information 4: a3f5984416be245658c62513142a14c0"
By the way: The first time I've seen two of those from one crash, and I'm an IT admin...
I have SimConnect v10.0.61259.0 installed and working. Oh, and no "Poolsize = 0".
After a lot of tries, each time moving the bglmanx.dll a bit further up, FSX will finally fire up to the start screen if the bglmanx.dll is ABOVE the iFly737NG.dll (but still below the iFly744.dll). KMEM and 747 still crashes. KORD and 747 works. I'll test KIAH next...
-
KIAH doesn't crash...
-
Last test for today: dll and exe.xml with entries only for Addon Manager and the 747. Result: Crash...
-
So, I'm in the process of testing. So far, I've moved the entries in dll and exe.xml to the end, but then I get 3 errors on FSX startup:
No 1 states "The procedure entry point SimConnect_Text could not be located in the dynamic link library simconnect.dll"
This has been discussed many times on the forum. The problem is caused by another add-on that use an outdated (the one from the initial FSX release) Simconnect version, that doesn’t include the Simconnect_text function required by our products, so the sim is forced to load an the outdated version, and is stuck with it for some reason.
It should be possible to fix it as explained here:
http://www.fsdreamteam.com/forum/index.php/topic,13029.msg97823.html#msg97823
No 2 and 3 are Windows error message boxes:
Application Name: fsx.exe
Fault Module Name: StackHash_66f0
Application Name: fsx.exe
Fault Module Name: API.DLL
By the way: The first time I've seen two of those from one crash, and I'm an IT admin...
These are very common instead, and since API.DLL IS Simconnect, clearly indicates you DO have a problem with Simconnect libraries.
I have SimConnect v10.0.61259.0 installed and working
Your error messages clearly indicates it's not working. More precisely, ANOTHER addon is loading the outdated version first (the RTM version)
Oh, and no "Poolsize = 0"
That would cause the G2D.DLL error.
After a lot of tries, each time moving the bglmanx.dll a bit further up, FSX will finally fire up to the start screen if the bglmanx.dll is ABOVE the iFly737NG.dll (but still below the iFly744.dll). KMEM and 747 still crashes. KORD and 747 works. I'll test KIAH next...
This seems to indicate the module that was compiled with the old SDK is the iFly.
However, while moving it might seem to solve the initial loading problem, if you have a problem with the Windows Side-by-side system, which allows TWO different .DLLs to be loaded and executed in the same address space, is not working properly, there WILL be crashes.
-
Last test for today: dll and exe.xml with entries only for Addon Manager and the 747. Result: Crash...
This is not what you said initially:
I "emptied" the dll. and exe.xml files from all but the Addon Manager entries, and sure enough, I could load up the 747 and KMEM, but then the 747 doesn't work (black screens, no gear, no function).
So, either you haven't really cleaned up the XML files, or you must have done something else in the meantime which has caused other problems to Simconnect.
And, as reported by ubersu, which said he's part of iFly support:
This chap did bring his problem to iFly and I (I'm part of the support team) was unable to reproduce it with any FSDT airport.
Seems to confirm there's no problem between iFly and FSDT modules, at any FSDT airport (I assume that with "any", he included KMEM too).
-
That was a different test. To clarify: "Initially" I removed all entries but the bglmax.dll. Result: No crash, but no functional 747. Yesterday I removed all entries but bglmanx and ifly747, so as to narrow it down. Result: g2d.dll crash.
Seems to confirm there's no problem between iFly and FSDT modules, at any FSDT airport (I assume that with "any", he included KMEM too).
Yes, well, in my case, there seems to be a problem. Any ideas on how to proceed? Re-install the Addon Manager? Will I have to activate my FSDT products again if I do that?
-
That was a different test. To clarify: "Initially" I removed all entries but the bglmax.dll. Result: No crash, but no functional 747. Yesterday I removed all entries but bglmanx and ifly747, so as to narrow it down. Result: g2d.dll crash.
Which I guess translates into "No crash at KMEM with any other plane", right ?
Yes, well, in my case, there seems to be a problem. Any ideas on how to proceed? Re-install the Addon Manager? Will I have to activate my FSDT products again if I do that?
I don't think it would change much. However, I'd try by downloading and installing the GSX Public Beta, which contains an updated Addon Manager/Couatl that haven't been officially released yet. Don't think it would make any difference, but doesn't hurt trying.
As explained so many times on the forum, you will NEVER lose your activation by simply uninstalling/installing. The ONLY time you must be concerned about reactivating, is when:
- You reinstall Windows from scratch
OR
- You change major hardware components
Uninstalling/reinstalling without doing any of this, can be done an unlimited amount of times.
-
That was a different test. To clarify: "Initially" I removed all entries but the bglmax.dll. Result: No crash, but no functional 747. Yesterday I removed all entries but bglmanx and ifly747, so as to narrow it down. Result: g2d.dll crash.
Which I guess translates into "No crash at KMEM with any other plane", right ?
Almost. With the MS' C172 and PMDG's MD-11 there is to crash. With iFly's 737, there is no crash, but also no KMEM: The objects aren't created, I have an empty airport.
I don't think it would change much. However, I'd try by downloading and installing the GSX Public Beta, which contains an updated Addon Manager/Couatl that haven't been officially released yet. Don't think it would make any difference, but doesn't hurt trying.
I'm thinking the same. I'll try it and post the results.
As explained so many times on the forum, you will NEVER lose your activation by simply uninstalling/installing. The ONLY time you must be concerned about reactivating, is when:
- You reinstall Windows from scratch
OR
- You change major hardware components
Uninstalling/reinstalling without doing any of this, can be done an unlimited amount of times.
Sorry, new to the forum. Thanks for the info.
-
Almost. With the MS' C172 and PMDG's MD-11 there is to crash. With iFly's 737, there is no crash, but also no KMEM: The objects aren't created, I have an empty airport.
That's a different and new version of your report. That started saying the problem happened only with iFly products (something that iFly support was never able to reproduce, it seems).
What crash you get with the default C-172 ?
-
Sorry, I misspelled. That was supposed to read "With the MS' C172 and PMDG's MD-11 there is no crash."
-
So, re-installed the Addon Manager, but the CTD remains.
Umberto, does the installer delete the [BUFFERPOOLS] section from the fsx.cfg?
Edit: By the way, I'm not the only one with this problem. In the iFly forum, someone else reported the same thing.
-
Umberto, does the installer delete the [BUFFERPOOLS] section from the fsx.cfg?
Yes, since the setting has been proven to be dangerous, and it's the first cause of G2D.DLL crashes.
Edit: By the way, I'm not the only one with this problem. In the iFly forum, someone else reported the same thing
Than nobody better than iFly support guys should be able to help you with this, but they said they cannot replicate it...how are we supposed to, if they even them cannot ?
-
Yes, since the setting has been proven to be dangerous, and it's the first cause of G2D.DLL crashes.
I see, but I'd like to be asked before someone makes such a change. And yes, I tried to remove the section (I run a large amount of buffer pools), but it still crashes.
Than nobody better than iFly support guys should be able to help you with this, but they said they cannot replicate it...how are we supposed to, if they even them cannot ?
I understand the problem you are facing - I really do. Is there some kind of logging I can activate in the Addon Manager?
-
I see, but I'd like to be asked before someone makes such a change. And yes, I tried to remove the section (I run a large amount of buffer pools), but it still crashes.
Both PoolSize and a too large buffer pools settings are equally dangerous (one would risk GD2.DLL crashes, the other OOMs), and we cannot afford for KMEM to be mistakenly accused to cause crashes, if it's running with settings that have been proven dangerous by the community at large.
The safest setting is default: which means no setting. That doesn't obviously mean FSX doesn't use any bufferpools: it just use a reasonable number.
It's just a setting which can be easily restored: there are 3rd party installers out there ( I won't name them, but we know there are ), which silent patch your FSX .DLLs, or patch your FSX.EXE, or corrupt your XML files. We only restore it to its correct default value.
Most of the issues with FSX, is from "miracle" tweaks, which don't really do anything, other then increasing the risk of crashes, we were in the FSX Beta since 2007 when the Acceleration/SP2 was releases (heck, we even WORKED on the Acceleration Pack!!), and the default values were carefully chosen for some reason.
If you really want to change something and have a more reliable product, switch to P3D instead. No miracle tweak can really fix a 10-years old sim.
I understand the problem you are facing - I really do. Is there some kind of logging I can activate in the Addon Manager?
You are still missing the point. The Addon Manager is NOT crashing. If it did, you would see a crash in bglmanx.dll. It's your FSX which is crashing and it's NOT crashing (according to your latest report), with any other airplane than the iFly.
How you could expect we would ever be able to "log" a crash happening only when another program is running ? Again, the only ones that can help you are iFly guys, assuming you could be able to help them replicate the problem.
-
I understand what you're saying, but it's my system, and I'd like to be informed. Or else what happens is I notice the missing section, don't know why it's gone and go looking for other missing sections - hunting ghosts, if you so will, and that's a huge waste of time.
How you could expect we would ever be able to "log" a crash happening only when another program is running ? Again, the only ones that can help you are iFly guys, assuming you could be able to help them replicate the problem.
The iFly is also not crashing at any other airport, just KMEM, and I've been flying it in and out of other taxing aftermarket sceneries like EDDF V2 and KMIA. Plus, the 737 from iFly is also causing problems at (and only at) KMEM.
Okay, I'll have a look at my configuration, and I'll talk to the other guy that's having the same problem, and the I'll get back to you.
-
The iFly is also not crashing at any other airport, just KMEM
According to YOUR own report, no other plane crashes at KMEM so, it's clearly not a problem of the scenery. Again, it MIGHT be a conflict, but (as I've said), if eve the iFly support guys cannot reproduce it, how WE are supposed to ?
So, the most likely explanation, is that there's a problem on YOUR system only, which cause a conflict between KMEM and iFly that normally shouldn't happen.
-
On my system, until now, yes, only the iFly aircraft 747 has produced a CTD, and the 737 causes KMEM not to show up. But, as I mentioned, someone else in the iFly forum has the same problem. Actually, his is even bigger, and I quote:
I can definitely say after dealing with this issue over the last day, the problem is not really in the IFly 744. FSDT KMEM is just inherently unstable. The iFly 744 is the only aircraft that causes a CTD every time, but I have had a CTD with the FSX default 744 and even the Bell 206. The iFly 744 is just complex enough to push FSX over the edge every time without fail.
I'm trying to narrow down with him, but it will take some time.
-
Saying that KMEM is "inherently unstable", just because the iFly ALWAYS crashes, and he also had "some" crashes with other planes, doesn't indicate in any way that KMEM is the cause.
It only indicates that:
- The iFly put an higher strain on HIS system
AND
- He's probably already close to the FSX memory limit even with default planes, just no always.
Nowhere there's any indication KMEM is the *cause*. As explained, so many times, it's the COMBINATION of everything that is running at any certain moment, which eats away memory, and will cause crashes at some point so, the only possible solution, is simply lower the settings and don't use too many addons at the same time.
-
So, I have just tried...
- setting minimal settings
- switching from DX10 to DX9
- deactivating ORBX openLC and Vector
...but I keep getting the same error.
Running out of things to rule out. Any ideas?
-
Running out of things to rule out. Any ideas?
Try to remove ALL the other 3rd party modules from the DLL and EXE XML, except bglmanx and couatl and the iFly module. At least, you would know if the conflict might be caused by an interaction of *several* modules, not just these two.
Otherwise, it wouldn't explain why the iFly support guys weren't able to reproduce it.
-
Try to remove ALL the other 3rd party modules from the DLL and EXE XML, except bglmanx and couatl and the iFly module. At least, you would know if the conflict might be caused by an interaction of *several* modules, not just these two.
That was actually one of my first tests, but I just did it again. Crashed then, crashed just now. It's on that basis I've been focusing on those two products. And don't forget the problem with the iFly 737. Different, but still a problem.