Archived

This topic is now archived and is closed to further replies.

red259

CTD

Recommended Posts

After a cross country flight from kjfk to klax (no acceleration used) I was turning on to my final approach and the 777 CTD. I don't have this problem with any other plane, although I have had a number of problems with the 777. 737ngx is fine and so is the q400. This tend to occur on long flights with the 777. I was able to do kjfk to klas with the 737 two nights ago without incident. I'm not sure what to do at this point. I was on vatsim and I just lost an entire afternoon. I have ftx global and the klax is fsdt. In the past I have gotten OOM indicators, but this time that did not occur (I have disabled ut2 and since I was on vatsim I was not running voxatc).

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

if it was not OOM related then it is difficult to say what went wrong.

Especially if you can not reproduce the CDT.

 

You can monitor VAS use as described in the PMDG intro manual to make sure it is ot VAS.

Share this post


Link to post
Share on other sites

if it was not OOM related then it is difficult to say what went wrong.

Especially if you can not reproduce the CDT.

 

You can monitor VAS use as described in the PMDG intro manual to make sure it is ot VAS.

Yea, I had downloaded the program to monitor vas, but didn't have it running when this happened. Just from the start fsx is putting up something like 3,500,000. I'm guessing this number includes the addon airport I am at along with the pmdg jet and ftx global? Opus shows up way down the list as another item for weather. The acars program for my virtual airline is at like 900.000. 

Share this post


Link to post
Share on other sites

You need to follow your Vas readings as mentioned. If your anywhere near 3800 then you need to save your flight, only takes a few seconds and then you can relax.

 

When fsx reloads it will be a lower vas

Share this post


Link to post
Share on other sites

(...) Just from the start fsx is putting up something like 3,500,000. (...)

 

 

That's way too much on startup: You'll have to think about your textures sizes, graphics settings and disabling (photo)sceneries and not-used airports for the flight.

Share this post


Link to post
Share on other sites

That's way too much on startup: You'll have to think about your textures sizes, graphics settings and disabling (photo)sceneries and not-used airports for the flight.

It is a lot yes. But when I leave default FSX airport KJFK towards Aerosoft Manhattan X I am looking at 3.8Gb VAS (also have GEX and UTX and FSGenesis mesh). If I have fair weather that is! With grey and rainy or TS I will probably OOM :-(.

 

This was to be expected to be honest and there is no point crying about it in my opinion.

 

If I ever OOM out at Manhattan I will disable this scenery when I fly the PMDG777.

Too bad but you only see Manhattan for a little while anyway if you fly an aircraft like this.

Share this post


Link to post
Share on other sites

I too have been getting CTDs (non OOM) I have opened a support  ticket and have sent the details to support)

 

Are you guys saying that you don't have any CTDs with 777?  (other than OOM which is really not a 777 issue)

Share this post


Link to post
Share on other sites

 

 


You need to follow your Vas readings as mentioned. If your anywhere near 3800 then you need to save your flight, only takes a few seconds and then you can relax.

 

Even better is setting FSUIPC to autosave your flight every 15 mins or so, that's what I do nowadays as FSCaptain supports flight restoring and now I don't have to worry about the extreme rage that not being able to finish a flight due to CTD after hours of flying gave me before. 

 

Not sure if you need the paid version for that feature though but in any case it's great.

 

Regards

 

Joona L

Share this post


Link to post
Share on other sites

Even better is setting FSUIPC to autosave your flight every 15 mins or so, (...)

Not sure if you need the paid version for that feature though but in any case it's great.

 

Regards

 

Joona L

 

 

Yep: Payware version only.

Share this post


Link to post
Share on other sites

I too have been getting CTDs (non OOM) I have opened a support  ticket and have sent the details to support)

 

Are you guys saying that you don't have any CTDs with 777?  (other than OOM which is really not a 777 issue)

That is correct, no CTDs here.

Share this post


Link to post
Share on other sites

For me, the only way to have no ctd is not use PLN mode with the nav mode selected on the touch screen!

It seem there is problem with the PLN mode in this version (confirmed by dev team when i send a ticket for this problem).

Answer was it will be corrected in th next version.

Share this post


Link to post
Share on other sites

For me, the only way to have no ctd is not use PLN mode with the nav mode selected on the touch screen!

It seem there is problem with the PLN mode in this version (confirmed by dev team when i send a ticket for this problem).

Answer was it will be corrected in th next version.

Ah yes, that one is a known bug. I dont use PLN so I do not have CTDs.

Share this post


Link to post
Share on other sites

I too have been getting CTDs (non OOM) I have opened a support  ticket and have sent the details to support)

 

Are you guys saying that you don't have any CTDs with 777?  (other than OOM which is really not a 777 issue)

So far, the only CTD for me was while flying a longer flight from Bermuda to EGLL.  On approach to EGLL, I just dropped to the desktop with an ntdll.dll error.  Never had this before with the NGX, so perhaps there is some issue that I can't identify that is already being worked on.   No OOM.  It's version 1.0, so I'm confident that through the next couple SPs, they will work it out to be as stable as the NGX is.

 

John

Share this post


Link to post
Share on other sites

 

 

So far, the only CTD for me was while flying a longer flight from Bermuda to EGLL.  On approach to EGLL, I just dropped to the desktop with an ntdll.dll error.

 

Make sure you are running the latest FSUIPC DLL, and check all scenery for landclass, as they leak memory, causing the problem you report.

 

Best regards,

Robin.

Share this post


Link to post
Share on other sites

For me, the only way to have no ctd is not use PLN mode with the nav mode selected on the touch screen!

It seem there is problem with the PLN mode in this version (confirmed by dev team when i send a ticket for this problem).

Answer was it will be corrected in th next version.

What are you referring to?

Make sure you are running the latest FSUIPC DLL, and check all scenery for landclass, as they leak memory, causing the problem you report.

 

Best regards,

Robin.

How do I check scenery for landclass? The only scenery I have is ftx global and airpots along with gsx/aes airport services. 

Share this post


Link to post
Share on other sites
The only scenery I have is ftx global

 

Yikes! OK - that is going to be a big job then. There could be a lot of them in that scenery, and they all want moving.

 

Basically the steps are:

 

* Find the landclass files for a particular scenery (e.g. MyScenery)

* Create a new scenery area (e.g. MySceneryLC)

* In the new scenery create a folder called scenery

* Do **NOT** create a texture folder!

* MOVE the landclass files to the newly created scenery folder

* Add the area to the FSX database, and ensure it appears below the scenery it came from

 

This will prevent the memory leak.

 

Best regards,

Robin.

Share this post


Link to post
Share on other sites

Yikes! OK - that is going to be a big job then. There could be a lot of them in that scenery, and they all want moving.

 

Basically the steps are:

 

* Find the landclass files for a particular scenery (e.g. MyScenery)

* Create a new scenery area (e.g. MySceneryLC)

* In the new scenery create a folder called scenery

* Do **NOT** create a texture folder!

* MOVE the landclass files to the newly created scenery folder

* Add the area to the FSX database, and ensure it appears below the scenery it came from

 

This will prevent the memory leak.

 

Best regards,

Robin.

Robin, areyou sure about that?

 

I have never heard about that procedure.

 

1) If a product has a memory leak then as far as I know it is best to uninstall and not use it.

 

2) would what you are advising not create an FSX scenery mess?

I mean would it not be better, before you move all that landclass somewhere, FIRST remove it from the FSX library?

Then move it and then add it to the library again.

 

3) How do we even know his CTD are cause by a memory leak?

 

4) if FTX is suspected of causing a memory leak just unclick it from the FSX library and test. And if FTX is causing memory leaks, would it not be all over the forums?

Make sure you are running the latest FSUIPC DLL, and check all scenery for landclass, as they leak memory, causing the problem you report.

 

Best regards,

Robin.

And with this, are you saying ALL landclass ALLWAYS leaks memory?

Share this post


Link to post
Share on other sites