Hi Jim,

 

Glad you've got things working okay. Yes, I must read the manual sometime. :wink:

 

Four and a half hours ago I departed KIAD for KLAX. Once at cruise I came downstairs and watched "Cold Mountain" whilst keeping a eye on FS Earth running on my laptop which shows the current aircraft position. I figured if it crashes, it crashes and I've lost no time.

 

But if I can get to LAX (in about 1.5 hours) then I will have proved to myself that I can fly longish flights with reasonable confidence.

 

Although Burkhard didn't say so I think that error I got when compiling the schedule could cause a crash if the Antonov was required by FSX. Fingers crossed that nothing happens on this flight. I'll know soon enough.

 

 

so I think that error I got when compiling the schedule could cause a crash if the Antonov was required by FSX

 

So far I have not compiled any schedules and I don't see anything in the manual where I need to.  They are there if you want them.  Maybe if I was plane spotting I would install a schedule.  Believe the installation program installs a schedule and that works for me.  Did another flight after my PM nap and still not crashes but my average fps for the flight was 28 but I was locked at 35 most of the way.  Very smooth.  I can honestly say for a fact that I did not do anything else but uninstall MTX and my ntdll/stackhash CTD's/freezes went away.  I'm going to wait reinstalling 5.4c until I'm sure it is stable.  Tired of crashing (too much of it going on here in the CTD Forum!) :lol:

 

Best regards,

I'll reply in full tomorrow Jim but just to let you know I landed in LAX 20 mins ago. Where's the sushine? So pleased not to have had any crashes today. Must have flown over 3000 miles! :biggrin:

 

 

So far I have not compiled any schedules and I don't see anything in the manual where I need to. They are there if you want them. Maybe if I was plane spotting I would install a schedule. Believe the installation program installs a schedule and that works for me.

 

If I hadn't chosen to recompile a schedule I would never have spotted that problem with the Antonov. And although Burkhard said it would only have prevented that aircraft from being loaded I feel there might have been a possibility it could cause a crash. It does no harm to recompile and could be beneficial in identifying problems with the install.

 

After choosing the 2013 schedule I noticed a great reduction in the number of Ai despite the setting in FSX remaining unchanged. It was only after reverting to the 2012 one the aircraft returned.

 

 

 

Did another flight after my PM nap and still not crashes but my average fps for the flight was 28 but I was locked at 35 most of the way. Very smooth. I can honestly say for a fact that I did not do anything else but uninstall MTX and my ntdll/stackhash CTD's/freezes went away. I'm going to wait reinstalling 5.4c until I'm sure it is stable.

That's good. Stay with what is stable. I still have 5.4c installed and having identified and fixed two problems with MTX I now feel it's more stable. Only time and flights will tell.

 

 

After choosing the 2013 schedule I noticed a great reduction in the number of Ai despite the setting in FSX remaining unchanged. It was only after reverting to the 2012 one the aircraft returned.

 

I saw that too in my previous install of 5.4c.  Thought that was normal but when I installed MTX without employing any of the schedules, I had tons of aircraft at the airports.  It was like I had a brand new toy and I've had MTX all the way back into the FS9 days.

 

Best regards,

Hi Jim,

 

Seems we're both happy with our setups at the moment. I flew EGCC-KIAD in a Posky 777-200 today - 3100 miles. Had to speed it up to x4 to get there before dinner but no problems whatsoever. Well, apart from the rubbish weather in your capital! :wink:

 

I did have one issue. Lots of Ai entries in the menu bar. After searching for the cause it seems it only happens when the number of Ai exceeds 1000. I guess that means the total number in a flight rather than all at once! It's a bug in FSX but has no consequences.

 

So to summarise after opening this thread a couple of weeks ago I am very happy with the Gigabyte mobo and after resolving a couple of bad / missing textures in MTX things seem to have settled down nicely.

Hi Ray,

 

Yes, it looks we are both knocking on wood.  Glad to hear things are now going well.  Happy Flying!

 

Best regards,

Ray and Jim, great thread. Learned a few things, thanks guys. I have had a stable system for over 2 years now, since switching to a Gigabyte board. My Asus board failed after about 6 months, but it took several heart stopping weeks to find out it was the board.

 

As for MTX, I have been reluctant to switch to 54c because of the ntdll errors. So do you think It would be worth trying 54C again ?

Hi Julian,

 

I did have a ntldll.dll error with the Gigabyte board but clearly there wasn't a link. What was annoying me was the inability of Asus to identify and fix the frozen bios clock problem. Fortunately, Scan UK were willing to swap the mobo and rebuild my system. I'm sure plenty of people are satisfied with Asus but in future I'm sticking with Gigabyte.

 

Regarding the FSX crashes I appear to have solved mine by rebuilding the schedule and choosing 2012 Autumn. Lots of aircraft disappeared with the Summer 2013 one but Burkhard cannot identify why.

 

The benefit of rebuilding your schedule is that it forces MTX to check the validity of all texture files. I would never have found that Antonov problem had I not done so. So yes, I'd try the 5.4c update but choose the Autumn 2012 schedule and definitely run the schedule check in MTX Configurator.

Flew KIAD-KATL this afternoon. One more flight with no CTDs. That's over 6,000 miles now with no problems. :good:

 

Dare I press that Mark Solved button? Tempting fate I think so I won't.

Hi Ray,

 

I plan on referencing this topic if anyone gets the NTDLL.dll or StackHash errors in the CTD Forum.  Yes, it's a long read but I think it goes a long way in resolving many FSX issues!  It really is great to be able to fly now without an error.  In fact, today, I moved my LOD_Radius up to 7.5 (per recommendation of MSE V2 developers).  If I get a NTDLL.dll or StackHash or OOM error, I'll at least know the culprit.  Hope your issues stay gone.

 

Best regards,

Hi Jim,

 

I'm convinced those errors were related to My Traffic X corrupt textures. Fix those and the errors go away. I've seen other advice regarding deleting the contents of folders but that doesn't ring true to me because I've tried that several times and the crashes come back.

 

I may tweak the LOD radius but it will probably eat into available VAS so keep an eye on that if you do.

I did have one issue. Lots of Ai entries in the menu bar. After searching for the cause it seems it only happens when the number of Ai exceeds 1000. I guess that means the total number in a flight rather than all at once! It's a bug in FSX but has no consequences.

Hi Ray, sorry for late reply, (Avsim Outage ) will give 54C a try. BTW, as to your AI exceeds,  download this http://library.avsim.net/search.php?SearchTerm=aidupe&CatID=root&Go=Search

 

Have been using it for yonks, and goes into your modules folder. I noticed one day (MTX) there were double BA flights @ EGLL, so Installed AI Dupe, and it fixed the fsx bug of duplicate ai.

I will dig out the dll.xml entry for you, as it can be a bit niggly to install.

 

Edit:

DLL.XML entry

 

<Launch.Addon>

    <Name>AIDupe</Name>

    <Disabled>False</Disabled>

    <Path>D:\fsx\Modules\AIDupe.dll</Path>  //////Choose your path

  </Launch.Addon>

 

 

I may tweak the LOD radius but it will probably eat into available VAS so keep an eye on that if you do.

 

I raised mine from 6.5 to 7.5 and it brought my system nearly to its knees.  Single digits at KORD with MSE Chicago Hi-Res.  I may have another problem as I have never seen this before and I've been as high as 9.5 with good fps (until the OOM :lol: ).

 

Best regards,

Hi Ray,

 

Before you wake up and see my previous post (should be about 2:30 am your time as I write this), I fixed my single-digit problem.  It was MyTrafficX configuration.  I have my LOD_Radius at 7.5 and Texture_Max_Load 2048 (HD) and lowered my slider for MyTrafficX to 20 as recommended by the developer (he actually recommends 16).  Still single digit fps with almost all gates filled at KORD.  Read the manual.  Changed MyTrafficX configuration as shown in Page 24 of the MTX Manual.  Disabled Exits for Ground Animation and Effect Lights and ticked Use simplified aircraft models and textures and models for wide screen.  Immediately after loading to KORD, the fps were near my max of 40 and stayed there.  Almost every gate at the airport had aircraft and they all looked nice.  Only thing I don't have is the strobes for the AI and jetways don't come out for the AI.  What a difference!!  I'm going to leave LOD at 7.5 for a while to see how fast I can get an OOM.  I only enable the scenery I'm flying over though so I may be okay.

 

Best regards,