12-09-2012, 11:15 PM
Greetings,
I've been a very happy FsPassengers user for some time now. So far I've flown about 120-130 hours, most recently embarking upon an epic journey from
Belfast to San Francisco traveling east in my Jetstream 41, not going more than about 700 miles per leg. I've landed at dozens of airports and have
had a pretty flawless experience so far.
Recently, as I was arriving in the USA, I purchased the ORBX Pacific Northwest scenery. It was then that I started experiencing some problems.
Whenever an FSPS menu would pop up, say at the end of the flight, FSX would develop serious graphical glitches that would result in me having to
restart the program. It would begin with the bulk of the aircraft disappearing except for some of the buttons, and then develop into a full on
graphical nightmare. I wish I had some screenshots, but if you've ever seen a crash where dragging a dialogue box ends up reproducing the trailing
edge of that box over and over again, that's pretty much what this crash is like. This crash happened two more times, both at the end of a three hour
flight (annoyingly) and it always coincided with an FSPS dialogue box.
Having not experienced this problem for the previous 120 odd hours of use, I assumed it was ORBX causing the problem and I uninstalled it.
Immediately I loaded up a flight and did my utmost to replicate the error. Admittedly, this was a much shorter flight, from Seattle to Portland, but
the error disappeared. Today, after some highly annoying gusting issues resulting from REX's weather insertion, I switched to ActiveSky. With REX
disabled and ORBX uninstalled, but with a fresh install of ActiveSky, the error reappeared as soon as I ended my flight from Portland to San
Francisco. TL/DR, the error has now happened both with and without the most recent add-ons that I've installed to FSX.
I'm running 2x 3GB GTX590s, but I always run FSX with SLi disabled due to previous graphical issues. I always run it on a single core and this has
prevented any further issues from occurring (until now). I'm also running an Intel i7 2700K CPU @ 3.5GHz overclocked to 4.7GHz. I also have 8GB of
RAM on the machine. I'm running Windows 7 64 Home. Every add-on and every piece of software on my PC was purchased legitimately and I have zero
pirated software running with FSX.
I'm not necessarily expecting a solution to this problem, but hopefully someone out there has experienced a similar problem and may be able to offer
me some advice on how to fix it. The most puzzling thing is that it started up only when I began to fly in and out of US airports, as I have not had
this issue before in the UK, France, Germany, Russia or Canada. Indeed, my flights in and out of Alaska were also uneventful. Having uninstalled the
last piece of software I installed before the errors began, I'm even more baffled by the sudden onset of this problem.
Many thanks for taking the time to read this. Aside from this I love FsPassengers and am greatly looking forward to making my 142 hours so that I can
move up to the PMDG 737 NGX.
Pádraig.
I've been a very happy FsPassengers user for some time now. So far I've flown about 120-130 hours, most recently embarking upon an epic journey from
Belfast to San Francisco traveling east in my Jetstream 41, not going more than about 700 miles per leg. I've landed at dozens of airports and have
had a pretty flawless experience so far.
Recently, as I was arriving in the USA, I purchased the ORBX Pacific Northwest scenery. It was then that I started experiencing some problems.
Whenever an FSPS menu would pop up, say at the end of the flight, FSX would develop serious graphical glitches that would result in me having to
restart the program. It would begin with the bulk of the aircraft disappearing except for some of the buttons, and then develop into a full on
graphical nightmare. I wish I had some screenshots, but if you've ever seen a crash where dragging a dialogue box ends up reproducing the trailing
edge of that box over and over again, that's pretty much what this crash is like. This crash happened two more times, both at the end of a three hour
flight (annoyingly) and it always coincided with an FSPS dialogue box.
Having not experienced this problem for the previous 120 odd hours of use, I assumed it was ORBX causing the problem and I uninstalled it.
Immediately I loaded up a flight and did my utmost to replicate the error. Admittedly, this was a much shorter flight, from Seattle to Portland, but
the error disappeared. Today, after some highly annoying gusting issues resulting from REX's weather insertion, I switched to ActiveSky. With REX
disabled and ORBX uninstalled, but with a fresh install of ActiveSky, the error reappeared as soon as I ended my flight from Portland to San
Francisco. TL/DR, the error has now happened both with and without the most recent add-ons that I've installed to FSX.
I'm running 2x 3GB GTX590s, but I always run FSX with SLi disabled due to previous graphical issues. I always run it on a single core and this has
prevented any further issues from occurring (until now). I'm also running an Intel i7 2700K CPU @ 3.5GHz overclocked to 4.7GHz. I also have 8GB of
RAM on the machine. I'm running Windows 7 64 Home. Every add-on and every piece of software on my PC was purchased legitimately and I have zero
pirated software running with FSX.
I'm not necessarily expecting a solution to this problem, but hopefully someone out there has experienced a similar problem and may be able to offer
me some advice on how to fix it. The most puzzling thing is that it started up only when I began to fly in and out of US airports, as I have not had
this issue before in the UK, France, Germany, Russia or Canada. Indeed, my flights in and out of Alaska were also uneventful. Having uninstalled the
last piece of software I installed before the errors began, I'm even more baffled by the sudden onset of this problem.
Many thanks for taking the time to read this. Aside from this I love FsPassengers and am greatly looking forward to making my 142 hours so that I can
move up to the PMDG 737 NGX.
Pádraig.