General Category > General Discussion
Couatl crashing P3Dv3.3.5
virtuali:
--- Quote from: jeffreymg on February 21, 2017, 11:09:54 pm ---I have never had a problem also till today and had a crash using P3D 3.4
--- End quote ---
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSXit_Xpoi_fr2'
{'User Pos': (25.798839457493614, -80.27883486668968, 6.35564 m, 3.91764 m, 235.50999534635113)}[/quote]
This problem, which has been already fixed in the latest version, can be fixed by removing the following folder:
FSX\fsdreamteam\Couatl\XPOI
Or, by applying the current Live Update.
Emi:
--- Quote ---You are assuming the problem is the Addon Manager, but it's not.
--- End quote ---
But it works if I remove the Addon Manager.
On 5 flights with the Addon Manager enabled I had 5 crashes.
On 5 subsequent flights with the Addon Manager uninstalled I did not have a single crash.
On another 3 flights with the Addon Manager reinstalled again I had another 3 crashes.
Points into a clear direction if you ask me.
--- Quote ---for example, a simple memory exhaustion caused by a memory hungry airplane running on a 32 bit application ?
--- End quote ---
That's easy, I keep monitoring my memory all along the flight and it does never exceed 3.5GB enroute and 3.7GB after landing. So plenty of memory left.
When the crashes happened my VAS was at about 3.3GB (my usual value enroute).
Furthermore I have previously flown the FS Labs A320 which uses about 500mb more memory than any of the PMDG aircraft.
But for the sake of testing, I also flew the PMDG 777 previously without crashes, which uses an equal amount of memory as the 747 does.
--- Quote ---One month ago, there wasn't any PMDG 747, for example. How you can be so sure the crash is *caused* by the Addon Manager
--- End quote ---
Another simple answer: It first appeared after updating Couatl and the Addon Manager. It remained ever since.
Thus my request in my last post if you could provide me the files from about one or two months ago, so that I could install and test these.
This would easily give us a clear indication whether or not one of the recent updates introduced such crashes.
virtuali:
--- Quote from: Emi on February 22, 2017, 06:00:46 pm ---But it works if I remove the Addon Manager.
--- End quote ---
Have you tried with another airplane, instead ?
Have you tried running the sim with ONLY the FSDT modules running ?
If you don't do this, you cannot say "it's the Addon Manager". At most, you could say there might be a NEW *conflict* between the Addon Manager and some other module that for some reason started only now.
If you can provide me with a replicable case of P3D crashing JUST with the Addon Manager installer, then we could find something to start with. Don't you think that if WE had any crashes, we would have found and fixed them ALREADY ???
--- Quote ---That's easy, I keep monitoring my memory all along the flight and it does never exceed 3.5GB enroute and 3.7GB after landing. So plenty of memory left.
--- End quote ---
PLENTY ??? That's VERY close to memory exhaustion instead. You DO NOT have the whole 4GB available, that's only the maximum theoretical amount of VAS for a 32 bit process, but you cannot use it all. In fact, it's a very well known fact that FSX/P3D will start to risk crashes when approaching 3.7 GB.
Emi:
--- Quote ---Have you tried with another airplane, instead ?
--- End quote ---
Yes, I tried the FSL A320, but with the same result.
--- Quote ---Have you tried running the sim with ONLY the FSDT modules running ?
--- End quote ---
Apart from FSUIPC (the older version) yes.
Trying without FSUIPC is impossible at the moment because all my addon planes depend on it.
--- Quote ---If you don't do this, you cannot say "it's the Addon Manager". At most, you could say there might be a NEW *conflict* between the Addon Manager and some other module that for some reason started only now.
--- End quote ---
All I can say is that it crashes with the Addon Manager. And it does not crash without the Addon Manager.
So it is related and so I ask for your support to solve the issue.
--- Quote ---Don't you think that if WE had any crashes, we would have found and fixed them ALREADY Huh
--- End quote ---
I'd never say that, experience in customer support shows that developers (and beta testers) can miss issues though.
No program is perfect, regardless how much effort went into it and that's nothing to be ashamed of.
--- Quote ---PLENTY Huh That's VERY close to memory exhaustion instead. You DO NOT have the whole 4GB available, that's only the maximum theoretical amount of VAS for a 32 bit process, but you cannot use it all. In fact, it's a very well known fact that FSX/P3D will start to risk crashes when approaching 3.7 GB.
--- End quote ---
VERY close can be relative. From a pilots point of view it is a safe bet in Prepar3Dv3 that you will make your landing without any crashes and even still do a go around and diversion. At least that's what experience shows from my pilots point of view. From your developers point of view it may look different, no doubt. All I can say is that it works for me.
Keep in mind the crashes happen enroute in the middle of nowhere, where the VAS usage is about 3.2-3.3GB. So at least during the crashes we can agree that there is plenty of VAS left, can we?
virtuali:
--- Quote from: Emi on February 22, 2017, 08:06:08 pm ---Yes, I tried the FSL A320, but with the same result.
--- End quote ---
An even more memory hungry airplane, as you said yourself
--- Quote ---Apart from FSUIPC (the older version) yes. Trying without FSUIPC is impossible at the moment because all my addon planes depend on it.
--- End quote ---
You don't understand. I'm NOT saying you must configure your sim like that *permanently*. It's JUST A TEST!
So yes, disable everything, including FSUIPC, try with a default airplane, so you can provide a case we could try to replicate.
--- Quote ---All I can say is that it crashes with the Addon Manager. And it does not crash without the Addon Manager.
--- End quote ---
You still cannot say that. You might say it crashes with the Addon Manager and lots of other stuff. Until you can replicate a crash with ONLY the Addon Manager, you cannot be sure of the Addon Manager being the cause.
--- Quote ---I'd never say that, experience in customer support shows that developers (and beta testers) can miss issues though. No program is perfect, regardless how much effort went into it and that's nothing to be ashamed of.
--- End quote ---
Which is why, I asked for your help, in providing a test case that we can replicate. Being able to replicate it, it's the only way to hope for a fix, assuming a fix is needed.
--- Quote ---Keep in mind the crashes happen enroute in the middle of nowhere, where the VAS usage is about 3.2-3.3GB. So at least during the crashes we can agree that there is plenty of VAS left, can we?
--- End quote ---
Which is precisely the moment the Addon Manager is not doing ANYTHING. If you are just flying over some place, the only thing the Addon Manager does, is to check your position and see if you are entering in the area of an FSDT airport. That's the only thing it does, when you are flying outside an airport.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version