Tailstrike

Going to try Seattle tonight to see if it's consistent.

Update, I disabled Orbx PNW yesterday flying out of CYVR to sort through another problem I'm having and to my suprise, SB4 when running from Windows didn't show the error message. I reloaded Orbx PNW and started FSX and the NGX in CYVR and I got the pop up so there's an element in Orbx that when coupled with NGX doesn't like SB4. Man, can't we all just get along in there! LOL.

Yes, everytime I fly with SB4 from the Start menu the "SB has encountered a problem" alert pops up. Your point on proximity to other A/C is true, it typically only happens when I'm approaching an airport or if someone logs in at the airport I'm departing from. I have been running SB4 from Windows and not FSX, I dont get the C++ error but I do get a window saying "SB has encountered a problem" but I can continue to run as long as I dont acknowledge it. Still works fine but my PTT is disabled on my yoke.

Good point Don, I'm doubting it's a PC resources issue though as I thought of that too so the next flight I kept the resource monitor open to see if I'm over-tasking. The highest spike was 32% CPU and 45% RAM when it happened, might be missing something though. I have a Sandy Bridge machine OC'd to 4.8Ghz and FSX with Orbx/REX doesn't put too big of a dent into it. The NGX is the only aircraft I see the problem error message pop up when running SB from Windows. It's weird though, if I don't acknowledge the alert, everything keeps on ticking. Just the error message stays up which certainly isn't ideal to run with but I can live with it as I can hide it on my second monitor or Ipad behind the FMC when using AirDisplay. The only issue with that though is the push to talk button on my yoke doesn't work anymore, have to use the keyboard which I guess in the big picture is a minor annoyance when communicating to ATC in a busy cockpit environment. I'll tinker and surf other forums, if not I'll figure out FSInn.

Meaning if you're not comfortable or don't understand how to unassign/disable throttle axis in FSX and re-assign/calibrate using FSUIPC, do a google search. There are many step by step tutorials on numerous forums. Sorry for the confusion. Rob

That's great news!

Even though you are using FSUIPC for fine tuning your yoke, you may want to either google this or do some Flight Sim forum searches for details but killing all axis assignments in FSX's setting's panel and soley using FSUIPC's axis assignment/calibration tool, you'll find a much more realistic and smooth axis function. Do this with your rudder pedals as well as any throttle quads you may be using too, you'll see a significant improvement on control surface precision meaning it'll eliminate all control spiking. Rob

I gave it a try Tom and I noticed no performance increase, it actually got buggy and CTD'd on the second try.

Has been pretty stable for me, however I've noticed screen tearing to be a bit more exagerated when in windowed mode.

Funny comment Wilbert, I feel your pain.

I've been playing with core designation in FS9 and FSX. FS9 I've noticed a processor resource improvement when isolating a core to FS9 but it's not 100% consistent. In FSX, isolating the program to a single core improves processor performance but it effects scenery in areas where 3rd party textures have been installed such as Orbx, when I allow FSX to run on all 4 cores, the visuals are excellent but the over-all processor performance is poor (High CPU Usage %) Flyboy, you might want to look into NickN's tweaking tips for Win7, you'll need to read through it carefully though to make sure FS9 is applicable.http://www.simforums.com/forums/topic34141_post198187.html#198187RobF