Yeah, there's a bug with FSX Xpack (and SP2_ not sure about this one)... When starting engines once you put the fuel cutoff switches and N2 (and N1) starts to rise to normal idle values but at about +40 % those parameters drop back to 18-15% N2 without apparent reason... and the engine stars a second time.It's a known bug by Level-D team.

Ouch... If that's the case, recommending the LDS767 to somebody who own the Acceleration pack is sort of impossible... Then I'd say go with Captain Sim. It's not a bad aircraft or anything, it just doesn't do panel saving, is all (and is significantly harder on frame rates for all I could see).

Ouch... If that's the case, recommending the LDS767 to somebody who own the Acceleration pack is sort of impossible... Then I'd say go with Captain Sim. It's not a bad aircraft or anything, it just doesn't do panel saving, is all (and is significantly harder on frame rates for all I could see).

I have fsx+accel and the lds767 works great. What do you mean it is sort of impossible. Am i missing something

I have fsx+accel and the lds767 works great. What do you mean it is sort of impossible. Am i missing something

I also think it works great for the most part and despite my rants I really like it. Personally though I think that many people who use the Level-D 767 really enjoy and appreciate the accurate systems and procedures. Those poeople could probably live without bugs that make you not being able to follow the standard checklists. The thing that bothers me is that those issues are likely trivial to fix, but still, customers are being told time after time to wait until the 757 is out.

...The thing that bothers me is that those issues are likely trivial to fix, but still, customers are being told time after time to wait until the 757 is out.

I think the thing that hurts about being told to wait until after the 757 is the great uncertainty about if the 757 is even coming out ever. Every now and then, a member of the Level-D team (always the same one I believe) shows up online and replies "of course it still coming". Otherwise we've heard nothing in the 4 years since FSX came out or even the couple years before that when they announced the 757 for FS9. Even traditionally closed mouth companies like PMDG will show up every 3-6 months with some brief updates on their projects.I see the LDS 767 struggling once the 737NG with FS2Crew is available. The only reason I've put up with the bugs so far (the Acceleration bugs are tolerable, the instability/CTD aren't really) is that I want a nice simulation of a Boeing with failures (yes, I actually use them). Once the NG is out, I can fill the niche elsewhere very nicely in FSX.

Hi,Well, I do not believe its Level-D causing the Instability & CTD's. I suffered from countless critical errors (CTD's) on a regular basis and found a fix.Keep in mind my system is a 'Flight Simulator Only Computer", it is not used for any other purpose!I was so fed up with FSX and the constant CTD's that I was just about ready to give up flightsim altogether and sell thousands of dollars in hardware. I then tried one last option that has removed my CTD's to this day.==================================================I removed the following file (UIAutomationCore.dll) from three locations==================================================1. Removed it from my FSX directory (Note: I copied one into this directory, thought it would fix the problem like many have stated, it did not fix the problem).2. Removed the file from my Windows/SysWOW64 folder3. Removed the file from my Windows/System32 folderThe UIAutomationCore.dll file no longer exists on my computer, it has been completely removed, I have yet to have a critical error or CDT. There is no doubt in my mind that this one file caused all my instability/CTD problems.There are programs that require this file. If your system is not a flightsim only setup, you run the risk of needing this file and not having it if you removed the file from your computer.All I can suggest for those of you who use your computer for purposes other than FS, keep a backup of the file(s), if needed when not flight simming, copy the file back into your windows system32 and SysWow64 sub folders and reboot. When the opportunity arises to jump into the sim, remove the files, reboot and load up FSX.Some will say you do not have to reboot, but I'm what you would consider dense :( , if it were me and I had to have the files on my system for other programs, I'd reboot after removal of the UIAutomationCore.dll file.Keep in mind YMMV, what has worked for me may do nothing for you. Also keep in mind you will have to take ownership of these files before you will be allowed to remove them.The easy way to take ownership and delete/rename these files.============================================Right Mouse Click on the file and select propertiesGo to securitySelect your group or user namePress editSelect your group or user nameNow give yourself full controlPress apply and OK============================================Side effects-------------------There is only one reported side effect with this solution:"If you exit FSX completely while in flight your windows desktop may become dysfunctional and you will have to restart your computer. If you first end your flight and then exit FSX you should have no problem." I have not seen nor experienced this problem, but don't be surprised if it happens to you.

The only reason I've put up with the bugs so far (the Acceleration bugs are tolerable, the instability/CTD aren't really) is that I want a nice simulation of a Boeing with failures (yes, I actually use them). Once the NG is out, I can fill the niche elsewhere very nicely in FSX.

The guy mentioning the panel state save of the Captain Sim:Its implemented, just save your flight and see your CS 767 come alive right where you left her. There's no menu for this, but every flight saving saves the panel state of that situation too.So your long haul flights can and will work if saving in between.Never had CTDs with Level D or Captain Sim so far, using FSX+X-Cel.

Hi,Well, I do not believe its Level-D causing the Instability & CTD's...

I'm sorry, but it's pretty compelling evidence that I've never had a CTD or even a freeze of my current flight simulator installation/setup with any aircraft other than the LDS 767. And these CTD's don't happen out of the blue. They happen with things like pushing the ground call button, a well known bug with the LDS and Windows 7. I have hundreds of hours with the PMDG MD-11, 744, JS4100 and Leonardo Maddog without problems. IT IS the LDS 767 in my case.

Hi,I suffered from numerous FSX lockups whenever I pressed the ground call button while using the Level-D 767 and I spend 99.9% of my flight sim time in this aircraft. However, I have not had one freeze/lockup/CTD since I removed the UIAutomationCore.dll file from my system. I now have the ability to press the ground call button without fear of a system freeze/lockup, the problem is gone.

I'm sorry, but it's pretty compelling evidence that I've never had a CTD or even a freeze of my current flight simulator installation/setup with any aircraft other than the LDS 767. And these CTD's don't happen out of the blue. They happen with things like pushing the ground call button, a well known bug with the LDS and Windows 7. I have hundreds of hours with the PMDG MD-11, 744, JS4100 and Leonardo Maddog without problems. IT IS the LDS 767 in my case.

Hi,I suffered from numerous FSX lockups whenever I pressed the ground call button while using the Level-D 767 and I spend 99.9% of my flight sim time in this aircraft. However, I have not had one freeze/lockup/CTD since I removed the UIAutomationCore.dll file from my system. I now have the ability to press the ground call button without fear of a system freeze/lockup, the problem is gone.

May I ask why the ground call button is so important? I've NEVER use it IRL on the 767 because IF the guy down there has connected his headset he can hear me taking anyway and if he's sitting in his car he can't hear the ground call at all. So I have to use the taxi light switch to get his attention.

@ Tim Capps, what file needs to be changed from a 1 to a 0 in the CS 767?

Topic SummaryB777ER Posted Today, 07:20 AM@ Tim Capps, what file needs to be changed from a 1 to a 0 in the CS 767?

can we keep that to pm's or on the captain sim forum, or another topic :)cheers brah

Level-D is clearly the more in depth simulation with better systems and flight dynamics.I don't own, nor will I the CS 767...

Then how can you say LDS one is better if you have not tried Captain Sim's one? :)

Captain Sim :)A developer of a very complex FSX addon once said that "only 2% of his costumers use the failure generator and are interested in the system depth that is necessary to get this feature running". So you have 100% arguing with "great system depth and simulation" and only rough 2 of those 100 are really using it.I know, a real simmer cares for hydraulic circuits, checks if ailerons point downwards if no pressure is applied and always verifies his virtual circuit breakers. He then goes for the exact calculation of his speed bug settings, gets lost, when ATIS told him the wrong winds and usually flies in outdated optics (VC) or even 2D.I can see two big Pros on the 767 from Level D: The FS2Crew Voice addon (which is a big one, no question) and the speed tape in the PFD (which the CS lacks of).Rest? You won't find missing pages in the FMC or none working switches in the cockpit of the CS if you use it like those 98% of simmers do. You will get very nice optics, sounds, animations which those 98% surely recognize. You also get additional models (which, of course, you have to pay for) where Level D only goes 767-300 all the time.I also like the integrated weather radar in the ND of the Captain Sim. It adds some great atmosphere.I also found the VNAV working better on the CS, while LNAV seems to be better on the Level D.I'm aware that mentioning those magic words "Level D" kicks you right into the pro level of simming whereas "Captain Sim" seems to lower you (especially in forums), but if you don't care about what others think and just go for the experience (yes, I own both addons), you'll surely recognize that some things are really overrated in case of the Level D and underestimated in the Captain Sim's.So the really essential point of it is personal choice, that's what counts.You won't fall behind Level D simmers online, you won't fail on flying SIDs and STARs, you don't loose TOPCAT support (if you want to use it), you'll find "real pilots" involved in both products, you'll see reviews where "sharp and pointy" describes the real 767 flying and other where the opposite is stated and you will find a huge amount of forums automatically! replying "Level D" ... so make up your mind and your choice.Again: The FS2Crew Voice addon is a big, big Pro towards Level D, I must admit.

+ 1 here, just could not have said it better.

Hi,I suffered from numerous FSX lockups whenever I pressed the ground call button while using the Level-D 767 and I spend 99.9% of my flight sim time in this aircraft. However, I have not had one freeze/lockup/CTD since I removed the UIAutomationCore.dll file from my system. I now have the ability to press the ground call button without fear of a system freeze/lockup, the problem is gone.

If you read my previous posts you would see that I've already done this. I've tried removing it, replacing it and changing it. For me it vastly reduced the CTD's, but it did not remove them.

May I ask why the ground call button is so important? I've NEVER use it IRL on the 767 because IF the guy down there has connected his headset he can hear me taking anyway and if he's sitting in his car he can't hear the ground call at all. So I have to use the taxi light switch to get his attention.

In the LDS, the ground call is the way to bring up the menu for ground communications. This is where you get to connect the ground power, external air, etc. As it is now, I basically just run off the APU for an entire preflight since I can't reliably access this menu. Not unrealistic, but not typical either.

Then how can you say LDS one is better if you have not tried Captain Sim's one? :)

That is why I did not comment at length on appearances, functions, etc. However, it is clear from mulitple reviews and user feedback that the Level-D excells in these two areas. If nothing else, Level-D has fialures (whether you uses them or not) and CS does not...these are more in depth systems. As for flight dynamics, Level-D has been matched against real world data for things like derated takeoffs, climb rate for weight, etc. and has come out very close to real world figures while CS has been quite a bit further away. I have never, no will ever, fly a 767 just like most simmers so these comparisons to real world numbers are all I will ever have to tell me if it handles similarly to a real 767.

I have fsx+accel and the lds767 works great. What do you mean it is sort of impossible. Am i missing something

Yes, The rest of the thread... What I said was a reaction to what somebody else said. You can't really take my post out of context and understand why I said what I said...CoolP: didn't think it'd be that easy, honestly... Thanks! Means I can use the CS767 without problems :-)