melb00m

It works now... I uninstalled and reinstalled twice, now it looks okay and frames are indeed better! Thank you.

Hello *******,let me first say a huge thank you for all your work on this and the other FSX tweaks! I've just switched to FSX an it has been very helpful!I also just tried your Shader 3.0 mod, but unfortunately, it gives me trouble. I do in fact get (a lot) higher FPS than before, but the water movement effects are extremely fast. After removing the mod everything was back to normal. Is this a known issue? I have an ATI 6970M video card with 1 GByte of memory.Thank you,Martin

I second Thralnis opinion about the iMac screen... it's simply gorgeous!As I said, I'm going to buy the MD11 for FSX the next days and then I'll go for another test ride and post some results and frames here. I only own MD11 for FS9 so far. Does anyone have a good page with recommendations for FSX tweaks? I found the sticky post on the AVSIM forums, and it helped me quite a bit, but I'd love to read some more so I can be sure my configuration is right.Martin Buchheim

Just letting you know that I received my iMac today, and made a couple first tests with FS X under BootCamp Windows 7 x64. I don't want to get into details yet, I have to install a lot of additional addons and test more, but I tried to fly around FS DreamTeams O'Hare with a default aircraft and ActiveSky Enchanced weather. The results are good with pretty high settings. Good enough so I think I'll finally switch to FSX, and will buy the MD11 (and the NGX...) for FSX soon to start another round of tests. My iMac specs are:Intel Sandy Bridge i5 @ 4x3.1 GHzATI 6970M 1 GByte12 GByte DDR3 1333I have yet to find an AMD supplied driver for this GPU, I'm using the one BootCamp came with, but have no options to configure Antialiasing in the driver. With very dense clouds and AA enabled, FPS drop a little bit at the native 2540x1440 resolution, but it looks pretty good without AA at this resolution as well. Does someone know what sort of AA is applied with the checkbox within FSXs settings?Martin Buchheim

I don't think they're using the mobile CPUs for the iMac, given the power consumption under load. But as you said, they do use mobile graphic cards, although the one in the largest model (6970M) should be sufficient for FSX. Heck, this GPU can run Crysis 2 very well, which is a completely different beast (graphics-wise).One problem is the very high resolution of the 27" display, probably you can't run FSX in native resolution with this GPU. Oh no, certainly not. If you're buying a machine mostly for flight simulaton, don't get a Mac. For me it's the other way round, I need a Mac for iOS development and other things, and I need windows ONLY for FSX.Maybe I'll get a separate gaming rig later, but for now I don't want to invest that kind of money for FSX alone.I'll let you know how the iMac works in the coming weeks, I'll get it on Monday.

I've ordered the new Sandy Bridge iMac as well, but with the Quadcore i5 3,1 Ghz CPU. I plan to use it for FSX as well, and I guess it will be sufficient if you don't need to crank all sliders up... Apart from Flight Simulator, I don't have any other use for Windows, and I'm not buying a second PC just for FSX. And yes, BootCamp is native, no virtual machine required any more as Macs run on Intel processors now for a few years already.

No it's not stupid. They already had the 757, and as this one is quite similar to the 767 all they needed to do was to create a new model... Especially as CS is not the kind of addon developer that really cares much to "get it right", as you'd expect from PMDG or Level-D. The 767 is even supposed to have the same bugs as the 757...I don't like how Captain Sim works neither, but from an economic point of view the 767 propably does make sense. Especially simmers that are into fancy graphics will buy it.And back to topic: My biggest wish right now would be that PMDG decides to release the 737NG for FS9 as well. That would be amazing news for me.

I checked my control settings and joystick raw numbers many times, there's really nothing more I can do. Are you using FS9 or FSX? Maybe there are multiple factors that lead to that bug on my configuration, but as long as it does work using my own panel-state, I am happy...Cheers,Martin

Just wanted to give another status update, perhaps there're other ones who experience the same trouble.I did some more testing on this issue, and found out that the problems really seem to be related to the panel states. Not just "Cold&Dark" as I thought before, but pretty much every panel state that is pre-defined from PMDG causes the ABS system to fail when loaded.I managed to get ABS working by simply creating my own cold&dark-preset, and as far as I can tell so far everything seems to work as it should. Mabe those panel-states were created before the update, and aren't 100% compatible?!... but that's just speculation.Hope that helps,Martin Buchheim

I already checked for spiking, but that's not the reason. Consequently, setting a nullzone doesn't do any good either (I've tried that, too). :( I do, too! Apart from that ABS flaw everything works very well.Martin Buchheim

Chris, thanks for the input. Did you use FSUIPC to configure your pedals, or did you do it via the FS9 configuration settings? Maybe you could make a screenshot of the sensitivity settings for your pedals, that would be very much appreciated.I talked to a friend with a similar hardware setup like the one I have, and he experiences the exact same problem: no autobrakes for him either on the eleven.I'm pretty sure there isn't anything wrong on my side, I also double checked that no unwanted brake inputs occur by looking at the raw (numeric) data from the brake pedals. I also saw the "auto_brakes=0" setting in the aircraft.cfg file and tried using 1 instead. That makes the autobrakes work but they can't be turned back off then once they were applied (and I'm also pretty sure PMDG had a reason to set this to 0...).I don't know what else I could do to fix this, so I'll stick with manual brakes for now and hope for a patch. If I come across a solution for this, I'll let you know. Cheers,Martin Buchheim

Dan, thanks for your suggestion. I just did another flight with my own panel configuration. Again, no brakes on touchdown. I'll try configuring the brake pedals using FSUIPC again now, maybe that will be a (temporary?) solution.Cheers,Martin Buchheim

I bought the MD-11 for FS9 a few days ago, and so far I'm very impressed. Well done!However, I also often encounter situations where, desipte everything being set up correctly, autobrakes simply don't have any effect whatsoever.Most of the time they do work for RTO, but they almost never do after touchdown. As I said, I double checked everything is set up correctly (autobrakes switch set as required, ground spoilers armed, anti-skid active and so on).I noticed there might me some connection to the panel state that was loaded before flight. "Cold & Dark" almost always results in ABS not working for me.I have CH Pro-Pedals, which I configured for left and right toe-brakes using the according options within the FS9 settings menu. I read somewhere on this forum that one solution might be to try using FSUIPC for braking assignments, but I couldn't manage to set it up correctly (breakes where always applied). Can someone with a similar setup explain to me in a little more detail how to do it?Any help would be greatly appreciated! And keep up the amazing work (still hoping for 737 NGX in FS9 though... ;) ).Sincerly,Martin Buchheim

Some basic rules on the CS757 in it

If the autopilot is able to do it, you should be, too.Did you check your takeoff trim setting?