I did have same problem  I uninstalled 707 1.1 and reinstalled 707 1.0,then installed 707 1.1 and clicked on Repair.
Problem solved, I hope this helps you.

Now noticing that if I or my friends start at the pre-set Seattle flight from CS there is no flashing and all is well

However the minute I change to another airport the flashing returns with a vengence.

and we still have the occasional LOAD WITHOUT WHEELS issue

so.............................................................

There is a post regarding CTDs and in that post a discussion about the flashing textures in the VC.

I would like to post my reply here also so that people who are encountering this problem will see that others are posting about it and will speak up.

I wouldn't even post if this add-on were a typical $30.00 or even $40.00 expense but that is not the case at all.

There is something fundamentally unstable with the update that was not present in the original.

and going down the path of blaming settings or an individuals machine environment IS NOT tHE ANSWER.

This is a software issue just as the another company JS4100 issue was the software and making machine excuses is just a form of HIDE AND SEEK.

So here's the post:

"There is a fundamental error in the software that was not present in the original release and that error is not machine related.

If the CS pre-set flight at Seattle is loaded than the flashing textures are not there but the second that the plane is moved to any other location or a flight is started at another location the flashing reappears.

These are not spikes or ground texture whiteouts or black outs as one would expect to see if buffer pools were set out of the video cards range or beyond its capacity and if it were a pure texture issue than it would occur in the default flight as well.

If this was happening to only me than I could see the idea of a machine specific related error but that is not the case at all

If this were a $30.00 purchase it would be a lot easier to accept but it is not.

This is an expensive add-on and something is wrong and it needs to be addressed."

SOONER NOT LATER

ramsa329

www.fs-gs.com

ramsa329, how come you think that YOUR problem is a fundamental one while many others are flying crash- and problemfree?
Tho forums would be full of people if the crashes or flashing were a mayor problem, don't you think?

Do you think your "this is an expensive addon" sentence helps anyone around in the support staff? Everyone is aware about the price and usually support workers can't work harder on high priced things, because the already do work hard independent from the fact of how much money was spent. Nice attribute I think.
Please try to calm down and deliver some values to work with.

As you could see before, the guys from Captain Sim are listening to customers around but it won't help if one of them goes lunatic and posts something about "fundamental error" all over the place.
First thing might be to answer their questions.
Seems like they are already on it, fellow Captain.

It's sad to read that your installation does not run fine, mine does, so at least there are two opposites existent which shows that there might be anything else but "fundamental error"  

Captain Sim wrote on Oct 3^rd, 2010 at 10:47am:


CS:
Thanks for the fast reply. I reinstalled the update, changed all planes to 'flight deck only', and the flashing seems to be fixed. I need to test this more as it's only been a few minutes now, but I did check in both single and multiplayer. Of course I have some strange views cycling through the cabin, but I can live with that for now.

Since you are aware of this by pointing us in that direction, is there a fix coming? Even though I dont smoke Marlboro's, I  love having a smoking section  

CP:
Ramsa isnt the only one with the issue or being a bit upset about it. I'm sure you would be too if it was happening to you.

Ok as of now with my, and others initial testing, have found that the flashing stops when every plane is set to VC only in ACE.

So now we have a work-around and are pointed in the right direction for a fix.

Thanks to everyone at Captainsim and in the forums for such a swift response.

To Mark:

The fix for the another company JS4100 is in their configuration utility and is associated to the VC.

Simply change "Virtual Cockpit Model Options" to medium.

To CoolP:

As I said before if it was one system than maybe I would consider machine related conditions but it wasn't as the work-around clearly shows.

It was and is now, as it was before, an issue with the software.

No amount of SNAPPING AT ME  will change the fact that we (who were encountering the problem) now have a work-around to what was happening.

I tried to narrow down the HIDE and SEEK factor which so often happens in forums so that those who could would more easily be able to isolate the problem and could do so without being distracted by random solutions and guesses.

I was not attacking CS I was looking for a solution or at least an interim work-around. I am a supporter of theirs and always have been even when many others were not.

In any case:

Again a big THANK YOU to CS for such a great plane, for the support and for the work-around.

Now I'm going to go fly

ramsa329

www.fs-gs.com
 

ramsa329, and once again: I don't have any flashing here, Cabin on or off so it wasn't, isn't and won't be a general issue.
I don't know what you mean with "snapping" but I usually hop in if somebody explains the world something wrong (meaning "general problem" which is a wrong statement as seen) and correct it.
Call this whatever you like and enjoy your plane.

Mark, exactly your experience with the other plane.
They state that this will be fixed in SP2 and until then, the workaround is stated in their forums or spoken here (don't ask me why other guys repeat the advice).