My 707 developed a strange issue recently: in VC view the screen shows flickering, random artifacts which are really annoying. I didnt change my video driver or any setup option recently. Running Win7 64bit and a nvidia GTS250 1 GB videocard.

any ideas on this?

Are you talking about the black bar that runs through the VC?

A reinstall might fix it...

Also, this happens on weaker graphics drivers, but if you have the GTS 250 that shouldn't be a problem.

Using ACE, select Flight Deck Only. That will ease the load on your Graphics Card.

Mark

OK I did some testing: bufferpools around 500 000 000 solves this problem, however, FSX starts to develop crazy...well....x-rated errors with this after a while:

http://img4web.com/view/8FS78E


but lowering the bufferpools to 400 000 000 brings back the flashing spikes and polygons in cockpit view.

@markoz
are you telling me to fly on less details with an OCed 4 Ghz CPU and 8 Gigs of RAM?

Do I really have to consider to go for a 300 € + Video Card with around 2 GB to have everything running fine?

It sometimes happens with me and I just reload the 707 and it usually goes away.
I didn't know what your system was as you never mentioned it. I just thought that might have been the problem.

Mark

I know, sorry ;)

reloading the aircraft is not really possible when in a flight with fspassengers. But well, it happend to me every time since, only way to fix it seem the bufferpool entry, a too high value leads to the artifacts seen in the picture, too low and the flickering starts......

You're right. Another thing, with v1.3, every time you reload the aircraft too many things get reset. It makes it difficult if you have everything nicely set. :(

Mark

Well however, I set the bufferpools to 0, that worked to solve the strange-object-transformation issue, which wasnt a CS related problem, and also gave me a huge performance leap, but now for some reason the flickering textures in the VC of the 707 returned.

@ Captain Sim: my PC should be able to take the 707 with Flight Deck and cabin view ON, I also found various threads of other customers regarding that issue. It seems there is a problem with the 707's virtual cockpit and cabin for some users like me WHO SPENT A LOT OF MONEY PURCHASING THIS PLANE!
Right now, the bird is unusable to me.

So please, fix it!

thanks!


Here is, once again, my system: Phenom II x4 965 @ 3,9 Ghz, 8 GB DDR2 RAM, nvidia GTS250 1 GB DDR3, Win7 64bit, FSX Acceleration....

as well as my current fsx.cfg settings:


Code (][Display):

ChangeTime=2.000000 TransitionTime=2.000000 ActiveWindowTitleTextColor=255,255,255 ActiveWindowTitleBackGroundColor=0,28,140,64 NonActiveWindowTitleTextColor=255,255,255 NonActiveWindowTitleBackGroundColor=24,33,87,64 InfoUpperRightTextColor=255,0,0 InfoUpperRightBackGroundColor=0,0,0,0 InfoLowerLeftTextColor=255,255,255 InfoLowerLeftBackGroundColor=255,0,0,128 InfoLowerRightTextColor=255,255,255 InfoLowerRightBackGroundColor=255,0,0,128 InfoBrakesEnable=False InfoParkingBrakesEnable=True InfoPauseEnable=False InfoSlewEnable=True InfoStallEnable=False InfoOverspeedEnable=False BLOOM_EFFECTS=0 SKINNED_ANIMATIONS=1 TEXTURE_BANDWIDTH_MULT=70 UPPER_FRAMERATE_LIMIT=0 WideViewAspect=False [GRAPHICS] HIGHMEMFIX=1 ALLOW_SHADER_30=1 SHADER_CACHE_VERSION=11 STALE_BUFFER_THRESHOLD=2147483647 SHADER_CACHE_PRIMED=1693500683 TEXTURE_MAX_LOAD=4096 NUM_LIGHTS=8 AIRCRAFT_SHADOWS=1 AIRCRAFT_REFLECTIONS=1 COCKPIT_HIGH_LOD=1 LANDING_LIGHTS=1 AC_SELF_SHADOW=1 EFFECTS_QUALITY=2 GROUND_SHADOWS=0 TEXTURE_QUALITY=3 IMAGE_QUALITY=0 See_Self=1 Text_Scroll=1 SHADER_CACHE_PRIMED_10=1693500683 D3D10=0 [TERRAIN] LOD_RADIUS=4.500000 MESH_COMPLEXITY=100 MESH_RESOLUTION=22 TEXTURE_RESOLUTION=29 AUTOGEN_DENSITY=5 DETAIL_TEXTURE=1 WATER_EFFECTS=7 TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1500 TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=4000 [BufferPools] PoolSize=0

Hi, I have that same flicker in the virtual cockpit and cabin which makes this plane useless to me >:(. If I do virtual cockpit only it goes away, however I purchased the 707 Captain v1.3 only because of the cabin :'(! Resetting the aircraft or even the computer don't help ::). All my other Captain Sim aircraft work fine (727,767, etc.) ;). The 707 being the only one to have a check box in ace to turn off the cabin proves there is a problem :-?.

And there is no way it's because of my system 8-): i7 975 Extreme cpu :P, 2 X 6990 video cards 4GB's each (thats 8GB's of video memery) tell me thats not enough :D), 16GB's of the fastest RAM and SD Hard Drives ;D!!!

Does anyone know of a fix :-/? Or can Captain Sim create v1.4 to address this bug :-X! This has to be there best aircraft and it would be a shame to delete it :o.

I tryed adding this to the bottom of my fsx.cfg :D:

[BUFFERPOOLS]
Poolsize=250000000

Did'nt do a thing :(!

Another problem with the cabin loaded is when you do a replay, everthing in the FSX world flickers :-?!

I have room for 4 more of those 6990 video cards ;D, I just don't have the $3000.00 :-/.

O'well, even if I can't use the best FSX airplane cabin ever made :'(, with the nice card tables :'(, etc :'(, etc. :'(, I still love Captain Sim :). There planes are the best, period ;)!!! There great work is what had me build a good computer 8-).

All my other Captain Sim aircraft work fine (727,767, etc.)
Sorry, but the above statement is wrong. The CS767 ACE does have that option (see image). The reason is because the amount of extra textures and polygons are very demanding on the computer, lesser computers will struggle. The main difference with the 707 is that it is using HD textures that require a lot more processing power by both the CPU and GPU.

Another problem with the cabin loaded is when you do a replay, everthing in the FSX world flickers
The same reason above, with regards to the textures and power needed to view, applies.

Hope this helps

---

Sorry about that, your right the 767 does have this option too :-[. However, if you look at the obove mentioned spec's of my system, I should have enough hardware for running the 707 cabin ;). All my other addons run like fluid 8-).

However, if you look at the obove mentioned spec's of my system, I should have enough hardware for running the 707 cabin
Sorry, I somehow missed your computer specs.

You should definitely have enough "grunt" to run the 707 easily. It runs fine with the cabin on mine, but does require an aircraft reload if I get the problem. And that is the thing for me, it doesn't happen all the time, but I can get rid of it if it does.

Mark

Hi Mark, Thanks for the quick replys. I have tried the aircraft restarts and had no luck. The only way I can stop the cabin flicker is to turn off the cabin in ACE. It hurts becaues the 707 cabin is the best cabin I have ever seen (from the screen shots on the web). I like to relax in the cabin and have a drink and smoke before departure and the card table in the 707 looks like the perfect place just for that!

Can't Captain Sim create cabin texture files that are not HD for us not so cabin lucky captains? I would pay $50. towards the research. And If that's impossible to do can they put a card table in the up comming 737 :( :-[ :-/ ?

i have same issue. external view is very clear but i can't even read the most of the gauges in the vc. how can i get rid that flickers?

http://i1138.photobucket.com/albums/n528/cenkcnk/comparsion/2011-8-11_20-23-21-117.jpg

I just spent $3000.00 on an new system (3770K CPU, 16GB 1600 RAM, GTX 680 2GB GPU, 2 x 240GB SATA III SSD's) just to get the 707 VC flicker to stop and it's still doing it >:(!!! It has been a year and a half and you guys still have not addressed this problem yet >:(. I'm very disappointed in Captain Sim >:( >:( >:(. I have 2 friends that also have this CS707 bug and it's because I only have 2 friends that have the CS707.

As you can see by my computer specs in my signature below, I have an i7 3770K CPU and 16GB of 1600 RAM (G.Skill Ripjaws), but I l don't have any SSD's or a GTX680 2GB GPU (only a two year old GTX470 1GB). I don't get any flickering in the VC.
On my computer, it looks sharp, it's smooth and I have no graphics problems at all with the CS 707.

It doesn't make sense that you get the flickering, while I don't. :-/

I have seen this VC flicker on 5 different systems, none of which had any parts in common. I guess your very lucky. You guys need to test on more then just one computer. I'm not the only one with this problem. Why don't any of my other Captain Sim planes do this :-X.

I guess if we want all the bells and whistles,even with the highest end rigs,we can still get flickering.Like Mark, I can get rid of most of it by setting the ACE to flight deck only.I know that does'nt help you,so maybe this bird needs some some work still on the software.
Whether this is commercialy feasible from CS's  perspective is another story.Maybe a survey is required,with respondents indicating their system specs and whether they have flickering with cabin enabled and not. the specs should also indicate the MB manufacturer
Ron

Captain A wrote on Nov 20^th, 2012 at 8:45am:

I have seen this VC flicker on 5 different systems, none of which had any parts in common. I guess your very lucky. You guys need to test on more then just one computer. I'm not the only one with this problem. Why don't any of my other Captain Sim planes do this :-X.

I've had the 707 on 3 different computers (all of them built by me) since the 707 was first released. On the old Core 2 Duo Quad 9550 with 4GB RAM and a 512MB 9800 GTX+ I was getting the flickering happening often, but not all the time! Either reloading the 707, or restarting FSX, always fixed it.

On the i7 870 with 8GB DDR3 1600 RAM and the GTX 470 1GB graphics card, I saw it a lot less often. And now I don't see it at all on my new computer.

I have always preferred to have the Pax Cabin showing, but removing it did lessen the flickering (on the two early computers). Using the "lite" VC, only gives me much better fps on the 707 on this computer, but currently getting around 25-30 fps with the Pax Cabin included, I have no need to use the "lite" interior. Those frame rates are what I get at KSEA with my sliders set to either maximum, or the notch below maximum. I do not have any airport traffic at all and the cars, ships, ferries and leisure boats traffic sliders (all 3) are are at 5%. My Airliner and GA traffic sliders are set to 1%, but I use Ultimate Traffic in place of them, and it is set at 30% for both GA and Airliner traffic.

Flickering or 'tearing' is not a model problem but a sign of a system that cannot cope with the graphic loads, CPU first Graphic card second. What to do about this is not so comforting but not that hard. First I run a bog standard HP 4GB DDR3 Dual Core Processor with a standard Intel
Graphic Chipset of about 2 GB. The processor speed is nothing special at about 3.0 GHZ. The O/S system is WIN 7 64 bit.

Can I say I have learnt the hard way and I have done several complete rebuilds of FSX, every time I have learnt something new about FSX the program and how to work with it not against it, so just throwing memory and high speed graphic cards may work but not as well as most expect. I have also discovered over time that most flight simmers are obsessed with FPS rates which is basically irrelevant as far as the eye can see and FPS does not equate with CPU processing capacity.

My guess is that system you have will run CS stuff, mine does flawlessly and now and then with high loads ( I will come to that) it gets a little stuttery or lags but not badly or in a manner I cannot live with it, this always and I repeat always, occurs in scenery areas with complex and detailed scenery, such as any major city in the world. There are lots of things happening here with the graphics that relate to what you want it to show, what you have set the system to try and show and what the system is doing, eventually with MS FSX the whole shebang gets behind and you get tearing and out of memory problems.

A common problem with all simmers is that they allow various scenery addons to self install or rely on installation scripts etc to do this, with few exceptions this leads to a big mess in the scenery files in terms of layers and file orders this means that the FSX program is running all over the place trying to match the layers and programs runtime calls and driver demands. Lesson number one you need to get all of your scenery into a separate folder outside of FSX's main directory and you unfortunately have to learn how to add and layer scenery, once you master this and it will take a little while you will find the whole program runs very smoothly and you will find the FSX scenery library tools and management process works as intended. I will post links to very useful guides on how to do this.

Again you might consider a rebuild of FSX with no model or new aircraft added in but only FSX SP1 and SP2, again there are very good tutorials elsewhere on how to get this done properly. Before you do anything else, any changes to sliders or settings  you need to have a look at what FSX does with your system when it configures itself on intial install, it will set the optimal grahpics. FPS etc that it is programmed to do with the hardware and O/S version you have. That then becomes a starting point.

Third you need to get rid of any tweaks and forget about automation core. dll's get rid of them they don't really work and are covering up the fact that your basic FSX architecture and layering is mismatched with your hardware.

Once you have this basic data and set up you can begin to make fine adjustments to scenery, traffic etc and fine tune your system using the tools FSX provides via the user settings interface dialogue boxes, they actually do work and that is why they are provided.

Finally some tips, the big killer of graphic smoothness etc is AI traffic of any sort, level of scenery density and autogenerated scenery object density and clouds, the amount of processing time FSX is using to do the graphic changes is quite phenomenal.

Once you have this sorted out in the way you approach FSX then load in your Captain Sim model and begin to play with various adjustments to see what it does to your system performance and graphics. I think you will be surprised at the improvements.

So My Iron Rules:

No FSX cfg tweaks (there are two exceptions graphic file size only) and no automation core dll files.
No scenery addons into FSX keep them outside in separate directories and layer scenery correctly.
Keep all AI traffic down to a minimum of 16% or lower, you won't notice anyway.
Keep water resolutions low, you wont notice the difference.
Take out uneccessary enhancements such as shadows, cockpit tool tips, flare etc. You won't miss these either.
Ensure your DX settings for filtering are appropriate to your video driver and card.

I also have this issue with the 707.  I bought it on release and have upgraded my PC twice since then.  Still, the issue is the same.  The post above this is somewhat misleading, as the flickers produced in the VC of this aircraft, are NOT the same as the flickers produced by an overwork PC or video card.

I guess because it doesn't happen to everyone, CS decided it wasn't worth fixing.  Sadly, that is so with some developers.

I haven't been able to fly my CS 707 'seriously' since purchase;-(

This flicker problem actually a directX driver problem. It can be triggered by switching the active windows, starting addons like SquawkBox or (most common in my case) switching from full screen to windowed mode. Sometimes i have this bug. Never in DX10 mode. I use GTX470 card. drivers later than ver 285 to ver 301 had extremely bad reputation. Now im on 306.23 WHQL. Pretty stable.
It happens with default birds too, but not so often.
It can be one of FSX hidden "feature".

Another apearance of this crap - is when your VC just becomes transparent. - its same problem.

Well I really wanted this 707 and downloaded the demo version and I also have the black line in the cockpit. I am afraid to buy the full version if, as I am learning here, they have not fixed it yet.

My computer is not the problem. I7 at 4.4, Three Gtx 980's in SLI at 4 ram each. Nothing gives me a problem graphically in FSX except the 707. So fix it so I can give you money,  ok!

Please note the Demo limitations: http://www.captainsim.com/products/x707/demo.html

teisco wrote on Jul 21^st, 2015 at 2:49pm:

Well I really wanted this 707 and downloaded the demo version and I also have the black line in the cockpit. I am afraid to buy the full version if, as I am learning here, they have not fixed it yet. My computer is not the problem. I7 at 4.4, Three Gtx 980's in SLI at 4 ram each. Nothing gives me a problem graphically in FSX except the 707. So fix it so I can give you money,  ok!

My computer is less powerful than yours, and when I get this problem with the 707, which isn't very often, I just reload the 707 and it disappears. The only time I don't reload the 707, is when it happens at the end of a flight!

Has there been a solution for this problem? I have the latest version of the 707 and I'm getting some pretty bad flickering at the windshield in front of me when I'm in VC.
I have a pretty powerful computer with a GTX 970 and 64Gigs of RAM.
I don't really believe it can have anything to do with the computer. I can fly any airliner that is made with no problems like this.
I will try turning off the cabin in ACE and see if that helps.
If anyone has any other suggestions I would appreciate it.

The 707 needs to be patched badly and made P3D compatible ;)

There are no solutions for now other than disable the cabin via ACE  :'(

speck wrote on Oct 5^th, 2015 at 5:19pm:

The 707 needs to be patched badly and made P3D compatible ;) There are no solutions for now other than disable the cabin via ACE  :'(

Yes, I had to disable my cabin in order for the flickering to stop.  At least I can fly my 707 now, but it's sad that I cannot enjoy the most beautiful cabin ever created for an airliner in flight simulator.
I certainly hope that Captain Sim will consider fixing this problem for us.
I'm using FSX right now, but I've purchased P3Dv3 and will be installing it as soon as developers make new installers to work with it.

Looks like I now have the same problem.  Never had any flickering until I got a new SSD and had to reinstall B707. I'll report back if anything comes up.

Why there are 20 Updates for the 727 and 0.nothing for the 707?  ::)

CS HAVE TO take care also for the other great planes  ;)

Mustang1977 wrote on Nov 20^th, 2015 at 6:45pm:

Why there are 20 Updates for the 727 and 0.nothing for the 707?  ::) CS HAVE TO take care also for the other great planes  ;)

Seeing as Captain Sim have a small staff, which means a small development team, and are currently working hard to get the 777, L-1011, 737, and 727, working better, so the 707 will have to wait its turn.

Of course, but with the time they should range the priorities, means not every stupid switch in the 727 to fix, instead of take care to the major problems in the other planes like the 707.

The screen flickering ist not the only problem, the bug in one of the altimeter-gauge is also still present. There is a special thread here which list all the current bugs ...

I don't actually understand why it works, but all i did was shut down my computer, restart and it all works just fine; cabin ticked on and no flickering now!  8-)

Kipendale wrote on Nov 22^nd, 2015 at 11:38pm:

I don't actually understand why it works, but all i did was shut down my computer, restart and it all works just fine; cabin ticked on and no flickering now!  8-)

All I ever have/had to do to stop the flickering, was to reload the 707 into FSX. That was it until the next time I loaded it. Now that I have a 4GB GTX 770 OC, it rarely, if ever, flickers. :-/

EDIT. Once I upgraded to the i7 3370k, 32GB RAM, and the 4G GTX 770 OC, it rarely, if ever flickered. So I think that the more powerful the computer, the less likely it is to flicker.