I noticed this in the cabin of the 707 yesterday. my computer is plenty fast enough to run it, seeing as though I get 20 FPS+.
I've tried defragging and clearing temp files, changing settings, shuttown AVs, using GameBooster

---

We do not see this artifact on our systems. Anyone else to confirm this issue please?

If you had bought the full version of CS 707 you're screen would look much better!  :D

http://home.comcast.net/~lou.lynn/pole.gif

I had a similar problem:

---

LOU, that was the highlight joke of the day. I found that after defragging, cleaning temp files, restarting and NOT running firefox or any background apps I got it to go away. It seems somewhat common though. I refuse to fly without the cabin though, lol. Can't get to the bottom of this.

Guys over at CS, let me have a crack at this and I'll see what I can do.

I THINK I GOT IT!

Captain Sim, do you ever hear FSX sound pops/clicks when sounds loop?
707Captain, do you ever ever hear it?

I do. I have problems with PCI Latency, and I think it may be connected to this. It's absolutely connected to the sound pops.

**PCI latency is the amount of time the computer "holds" the video/sound card before it can be used by another program.

i think its a high speed monorail beating the speed out of your old 707 :P

Never seen that black line anywhere in the 707 and I have not heard any pops/clicks when the sound loops either.

Mark

precisely. I think they're connected. Acceptable PCI latency=no pops, no line, Thanks Markoz, you just helped to support my theory.

I found that if you defrag your computer, and do this
type %temp% in the search bar on vista/7 or the start/run box on XP, and delete all the files inthere, then restart the computer. Then open FSX without minimizing it during loading and WITHOUT firefox running, it does away. I would appreciate anyone who can try and back this up. Thanks!

Collin

I'm sorry that I can't contribute anything useful but I really have to say that I laughed my a.. off after Lou's post.
Best one of 2011 so far.  ;D

Ah, maybe one comment. Could it be that the latency or whatever related graphics corruption has the same source as the former artifacts and flashes on the 707 which were ruled out by 1.2?
Some systems experienced them, others not.
I've read about sound problems when going for bufferpools tweaks as they seem to stress the bus load which is the only transfer line for all CPU to GPU, SATA and Sound actions. Increased and time sensible load there might trigger some things to drop. Seems like the sound is one of the obvious and first ones then and acts as a clear sign for too much load there with other symptoms to follow.

I think Bojote explained the increased bus load coming with his bufferpools tweak.
I don't know if you run those tweaks but a test without them might help to clear things and error sources then.

Actually, I've tried it with and without the bufferpools, and recieved the same results. It seemed unconnected to my pools settings. However, the sound pops are somewhat connected to it, but they alone cannot stop it.

SO

I noticed that my computer was fragmented more often than normal, only after installing the 707. That was my first clue. Then I noticed how low the FPS got after turning on the weather radar. Second Clue. I now make sure to turn off the weather radar before closing the sim.

SO part 2
I deleted my FSX.cfg and logbook.bin files and had my computer rebuild them. No fragmentation, no graphics pole. I think that the weather radar may be incorrectly using the computer's resources. That supports my earlier comment that cleaning the temp files and restarting solved it. That would reset any logs/temp holds that FSX.exe uses.

So please, everyone try this to help me rule this once and for all, I need backup.

type this in to the search bar on Vista/7 or the Start/Run box on XP.

%appdata%\Microsoft\FSX and open that folder
then rename fsx.cfg to fsx.cfg.old
now go to your Documents\Flight Simulator X Files
and delete the logbook.bin file **CAUTION AS THIS WILL CLEAR ANY MISSION REWARDS AND THE TIME LOG**
now type %temp% into the search/run box
delete all the files in that folder, allowing continuation when prompted for administrative access. Ignore any "file in use" warnings and just skip that file
now restart the computer
then open FSX
is there a graphics error?

Make sure to have the WX radar off when closing FSX

that should have done it!

also note that you don't have to rebuild the FSX.cfg everytime, but it's good to do it once a month to avoid corruption.

VISTA/7 USERS THIS IS CRUCIAL

Make Sure to add the following lines to the NEW fsx.cfg after loading and closing fsx
put them under the graphics [GRAPHICS] section


HIGHMEMFIX=1
STALE_BUFFER_THRESHOLD=2147483647

credit to Jose on the another company forums for that, but be sure to install this to save headaches later on

~PLEASE REPORT BACK HERE AND TELL ME HOW IS GOES~

Collin Biedenkapp

Have seen a vertical line once - hmmm, hang on was that in the 707 or the 757? Might have to retest