Found it. ( my previous post )

Problem solved! More changes to my .cfg file found on another forum thread http://forum.avsim.net/topic/389953-cure-for-flashing-when-changing-views-in-ngx/

not only completely solved my texture loading problem when switching views, but has allowed me to max out my sliders and get BETTER PERFORMANCE!!! Not only that, but my GPU utilization has jumped up to 61% although VRAM usage is about the same. Here is my .cfg now:

 

// This file was tweaked on Nov 01, 2012 at 01:42 GMT using Bojote's automated FSX Tweaking & Tuning Service

// Your 'original' fsx.CFG file was backed up at http://www.venetubo.com/fsx/e289dc063783997b3781778933c337cf/backup/fsx_backup.cfg

// This file is optimized as follows: 4 core(s), CPU speed 4, HT 0, GPU 4, PREF 2

// You can visit Bojote's FSX Tweaking & Tuning service at http://www.venetubo.com/fsx.html

[DynamicHeadMovement]

HeadMoveTimeConstant=1.000000

LonAccelOnHeadLon=-0.020000

LonAccelOnHeadPitch=-0.010000

MaxHeadAngle=5.000000

MaxHeadOffset=0.300000

RollAccelOnHeadLat=0.010000

RollAccelOnHeadRoll=0.100000

YawAccelOnHeadLat=-0.100000

[REALISM]

AutoCoord=False

AutoTrim=False

CrashDetection=False

CrashTolerance=0.000000

CrashWithDyn=False

GEffect=False

General=0.000000

GyroDrift=False

GyroEffect=0.000000

ManualLights=False

PFactor=0.000000

RealMixture=False

StressDamage=False

Torque=0.000000

TrueAirspeed=False

UnlimitedFuel=True

[Weather]

AdjustForMagVarInDialog=1

CLOUD_COVERAGE_DENSITY=8

CLOUD_DRAW_DISTANCE=4

DETAILED_CLOUDS=1

DisableTurbulence=0

DownloadWindsAloft=0

DynamicWeather=0

MaxGustRampSpeed=200

MaxGustTime=500

MaxVarRampSpeed=75

MaxVarTime=50

MinGustRampSpeed=1

MinGustTime=10

MinVarRampSpeed=10

MinVarTime=5

THERMAL_VISUALS=0

TurbulenceScale=0.500000

WeatherGraphDataInDialog=0

WeatherServerAddress=fs2k.zone.com

WeatherServerPort=80

WindshieldPrecipitationEffects=1

[Misc]

Com_Rate=7

[Main]

FIBER_FRAME_TIME_FRACTION=0.16

HideMenuFullscreen=1

HideMenuNormal=0

Location=440,130,1480,908,\\.\DISPLAY1

Maximized=2

SimObjectPaths.0=SimObjects\Airplanes

SimObjectPaths.1=SimObjects\Rotorcraft

SimObjectPaths.2=SimObjects\GroundVehicles

SimObjectPaths.3=SimObjects\Boats

SimObjectPaths.4=SimObjects\Animals

SimObjectPaths.5=SimObjects\Misc

User Objects=Airplane, Helicopter

ProcSpeed=16583

PerfBucket=7

[VirtualCopilot]

VirtualCopilotActive=1

[Trusted]

E:\FSX\GAUGES\LVLD\B767Afds.GAU.reqbtwhceaoeiuchobilzwurwqlrowolqltkbbzt=2

E:\FSX\GAUGES\LVLD\B767FMC.GAU.rkbbztuuolaioqtooihlluuonbloncahcalhtkca=2

E:\FSX\GAUGES\LVLD\B767Overhead.GAU.narbzeozqziccuntlbnianwlioabahlckbnhzwtz=2

E:\FSX\GAUGES\LVLD\B767Radios.GAU.tahurlcwhubolwrtutkarqieoahwkthwcuctrucr=2

E:\FSX\GAUGES\LVLD\B767at.GAU.harhqnkhzerqqqzqnzleaiknttbeortecbriiueb=2

E:\FSX\GAUGES\LVLD\B767eadi.GAU.rawwibicwarrhnurtnzzibieuboiqthazebbklkw=2

E:\FSX\GAUGES\LVLD\B767ehsi.GAU.runouqrbbeeqrluohucqranrurownwwlwizhtalo=2

E:\FSX\GAUGES\LVLD\B767eicas.GAU.rbwbtwawlhiznwaarkkaqeqbunqrolcnhbcoqlnt=2

E:\FSX\GAUGES\LVLD\B767leicas.GAU.krluoqtqlqubkclhuiaarincznqcuaeoneulwrkl=2

E:\FSX\GAUGES\LVLD\B767main.GAU.kirhtotackcbqnwaiaezwncnakottctoaaekiknw=2

E:\FSX\GAUGES\LVLD\B767oh.GAU.kiiikouwcnabhcqaerwirblokintboeuwnbwciqo=2

E:\FSX\GAUGES\LVLD\B767pedestal.GAU.ooauwklizezllntbaaqrklboocwbiewqkkqwhaaq=2

E:\FSX\GAUGES\PMDG_737NGX.DLL.wthznknlachoclitwhweetuhzzrquitleoqbkohh=2

E:\FSX\GAUGES\PMDG_737NGX_3.DLL.eacataubtoocrlrkebetbzuhzznllwnbawkqlchz=2

E:\FSX\Modules\FSCopilot.dll.tebkhrukbzaizaokwleoabtllnnweeackqoocbqa=-1

E:\FSX\Modules\FSUIPC4.dll.qhwhqcbikracqaqlhznaltekahkzenrrwwzqtoaw=1

E:\FSX\Modules\LVLD.dll.ounkbwchnkiktwawikiuorncnawreiiruauhbnlu=1

E:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll.kzabhitoelnlwkkrlrakkrzbewiitkaoohurzehc=1

[sOUND]

AmbientUI=0

AmbientUIMusic=FSX01

AmbientUIMusicVolume=-6.000000

PrimaryDevice={DEF00000-9C6D-47ED-AAF1-4DDA8F2B5C03}

SOUND=1

SOUND_FADER1=0.500000

SOUND_FADER2=0.500000

SOUND_FADER3=0.500000

SOUND_FADER4=-0.500000

SOUND_LOD=1

SOUND_QUALITY=2

UISound=1

VoiceDevice={DEF00002-9C6D-47ED-AAF1-4DDA8F2B5C03}

[uSERINTERFACE]

Map_Orientation=2

OpenATCOnCreate=0

PAUSE_ON_LOST_FOCUS=0

PROMPT_ON_EXIT=0

PageID=1

SHOW_MISSION_CAPTIONS=0

SITUATION=FLIGHTS\OTHER\FLTSIM

SelectAircraftManufacturer=All

SelectAircraftPublisher=All

SelectAircraftType=All

ShowAllACPaintSchemes=1

[slewTextInfo.1]

AirSpeed=1,5

Altitude=1,3

Heading=1,4

Latitude=1,1

Longitude=1,2

[TextInfo.2]

FrameRate=1,1

FuelPercentage=1,4

GForce=1,3

LockedFrameRate=1,2

[sIM]

SYSCLOCK=1

[AContain]

LabelColor=FFFF0000

LabelDelay=1000

ShowLabelAirline=0

ShowLabelAirlineAndFlightNumber=0

ShowLabelAirspeed=0

ShowLabelAltitude=1

ShowLabelContainerId=0

ShowLabelDistance=1

ShowLabelFlightPlan=0

ShowLabelHeading=0

ShowLabelManufacturer=1

ShowLabelModel=1

ShowLabelTailNumber=1

ShowLabels=1

ShowUserLabel=1

[bUFFERPOOLS]

RejectThreshold=98304

[ATC]

AutoOpenAirTrafficWindow=1

COMM_MSG_AI_ATC_COLOR=FFFF7840

COMM_MSG_ATC_AI_COLOR=FF00FF00

COMM_MSG_ATC_USER_COLOR=FFB6FFB6

COMM_MSG_NONE_COLOR=FFFFFFFF

COMM_MSG_USER_ATC_COLOR=FFFFD21B

PilotVoice=0

ShowATCText=1

UsePilotVoice=1

[TextInfo.1]

AirSpeed=1,5

Altitude=1,3

Heading=1,4

Latitude=1,1

Longitude=1,2

WindDirectionAndSpeed=1,6

[Display]

ActiveWindowTitleBackGroundColor=0,28,140,64

ActiveWindowTitleTextColor=255,255,255

BLOOM_EFFECTS=0

ChangeTime=4.000000

InfoBrakesEnable=True

InfoLowerLeftBackGroundColor=255,0,0,128

InfoLowerLeftTextColor=255,255,255

InfoLowerRightBackGroundColor=255,0,0,128

InfoLowerRightTextColor=255,255,255

InfoOverspeedEnable=True

InfoParkingBrakesEnable=True

InfoPauseEnable=True

InfoSlewEnable=True

InfoStallEnable=True

InfoUpperRightBackGroundColor=0,0,0,0

InfoUpperRightTextColor=255,0,0

NonActiveWindowTitleBackGroundColor=24,33,87,64

NonActiveWindowTitleTextColor=255,255,255

SKINNED_ANIMATIONS=1

TEXTURE_BANDWIDTH_MULT=2800

//default was 40

TextureMaxLoad=6

//default was 30

TransitionTime=4.000000

UPPER_FRAMERATE_LIMIT=31

WideViewAspect=False

[iNTERNATIONAL]

ASLAT=2

ASLON=1

MEASURE=0

[CONTROLS]

Controls_Current=Standard

Controls_Default=Standard

KBDAIL=64

KBDELEV=64

KBDRUD=64

[slewTextInfo.3]

AirSpeed=1,5

Altitude=1,3

FrameRate=2,1

Heading=1,4

Latitude=1,1

LockedFrameRate=2,2

Longitude=1,2

[sTARTUP]

DEMO=0

LoadWindow=1

SHOW_OPENING_SCREEN=1

STARTUP_DEMO=0

[PANELS]

DEFAULT_VIEW=0

IMAGE_QUALITY=1

PANEL_MASKING=1

PANEL_OPACITY=100

PANEL_STRETCHING=1

QUICKTIPS=0

UNITS_OF_MEASURE=0

[FACILITIES]

CITY=

COUNTRY=

GTL_BUTTON=1244

STATE=

[DISPLAY.Device.NVIDIA GeForce GTX 660 Ti.0]

Mode=1920x1080x32

Anisotropic=1

[TextInfo.3]

AirSpeed=1,5

Altitude=1,3

FrameRate=2,1

FuelPercentage=2,4

GForce=2,3

Heading=1,4

Latitude=1,1

LockedFrameRate=2,2

Longitude=1,2

WindDirectionAndSpeed=1,6

[PointOfInterestSystem]

CycleSetting=0

[slewTextInfo.2]

FrameRate=1,1

LockedFrameRate=1,2

[TERRAIN]

SWAP_WAIT_TIMEOUT=2

TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1800

TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=700

DETAIL_TEXTURE=1

MESH_COMPLEXITY=100

MESH_RESOLUTION=23

TEXTURE_RESOLUTION=29

WATER_EFFECTS=4

AUTOGEN_DENSITY=2

LOD_RADIUS=4.500000

[JobScheduler]

AffinityMask=14

[sCENERY]

DAWN_DUSK_SMOOTHING=1

IMAGE_COMPLEXITY=3

LENSFLARE=1

MAX_ASYNC_BATCHING_JOBS=3

SmallPartRejectRadius=4.0

[GRAPHICS]

AC_SELF_SHADOW=0

AIRCRAFT_REFLECTIONS=1

AIRCRAFT_SHADOWS=0

ALLOW_SHADER_30=1

COCKPIT_HIGH_LOD=1

D3D10=0

EFFECTS_QUALITY=2

GROUND_SHADOWS=0

HIGHMEMFIX=1

IMAGE_QUALITY=0

LANDING_LIGHTS=1

NUM_LIGHTS=8

See_Self=1

TEXTURE_MAX_LOAD=1024

TEXTURE_QUALITY=3

Text_Scroll=1

SHADER_CACHE_PRIMED_10=1693458432

SHADER_CACHE_PRIMED=1693458432

[TrafficManager]

AIRPORT_SCENERY_DENSITY=0

AirlineDensity=0

FreewayDensity=10

GADensity=0

IFROnly=0

LeisureBoatsDensity=0

ShipsAndFerriesDensity=0

[MULTIPLAYER]

condAccoutPassword=0

VoiceVolume=-1.000000

 

I never needed to weak my .cfg this much with my ATI card, but now it definitely looks and performs better. Thanks for all your feedback!

Yes I expected someone to home in on core multi threaded stuff that must obviously change to go with current hardware, gave me a great laugh.

Let's not be rude Paul, if the hardware had not improved there's little need for another sim.

Sorry, but those are even less meaningful then your original "software hasn't changed in 20 years" post.

 

If you have difficulty dealing with concurrency, you don't need to feel too bad about it, many people have problems with it at first, and some people just never grasp it.

I've got no problems with concurrency Paul, I didn't say "software hasn't changed in 20 years". Some people seem to have trouble understanding me, sorry about that.

I got a mail last week asking about moving up to FSX and getting the PMDG737, does it all work? I adviised them to go ahead. The worry was that FSX is not programmed correctly and Win7 causes problems (they have XP/FS9). It is my belief that people like Paul here, who believes concurrency came in since multicore, are causing confusion. I say get FSX, it is well written for its day.

I am starting to wonder if the 192 bit memory bus is part of the problem on my 660 Ti. My 5850 had a 256 bit memory bus.

 

Glad to hear your problems are solved! I was going to pull the trigger on 660TI superclocked to replace my 560TI, after seeing the 192 bit memory bus my plan has now been to order the 670.

 

Well your last post has go tme a little confused now I am wondering if I should go for the 660TI since my rig is for FS only. Could anyone comment on the difference in performance between the two in FS9/FSX? this machine is built primarily for the PMDG 777, CPU is a I52600K clocked at 4.9ghz. FSX actually run's great on the 560TI

 

Cheers

I would spend the extra $70 and get the 670 but I highly recommend using a non-reference cooler design such as Asus, Gigabyte, or MSI because cooling is better. If you can wait a few weeks for Black Friday you'll probably be able to buy one for what I paid for my 660ti ($299).

Cheers mate, i'll go for the 670, I leave the UK in a week so I need to get this sorted before then.

 

Regards

i have this prםblem

Nope, the 20 year old code you speak of is written the same today...

...I didn't say "software hasn't changed in 20 years".

?

...Some people seem to have trouble understanding me...

You don't say...

I got a mail last week asking about moving up to FSX and getting the PMDG737, does it all work? I adviised them to go ahead. The worry was that FSX is not programmed correctly and Win7 causes problems (they have XP/FS9). It is my belief that people like Paul here, who believes concurrency came in since multicore, are causing confusion. I say get FSX, it is well written for its day.

I am sorry, but again, I have no idea what you are trying to say. Is FSX better the FS9? Yes. Is Win7 better then XP? Yes. Is there a lot of rubbish talked about both? Yes. And saying things like concurrency is related to multicore, or suggesting that I am saying that, is simply adding to the confusion. As I said, you don't need to feel too bad about your lack of knowledge about concurrency, as it is something that most people, including many so called computer experts, know remarkably little about. To try and put it simply, concurrency (by definition) involves more then one thing happening at the same time. It should not be confused with multithreading which is all about running two or more tasks on a single processor (or core), and though multithreading can be thought of as a subset of concurrency, concurrent programming (often called parallel programming) has been going on since the sixties, long before Intel and AMD came up with hyperthreaded or multicore chips for the retail market. Multithreading can be thought of as having one program try to do two jobs at the same time. Concurrent programming is having two programs running at the same time (and you don't know or care what the other one is).

 

What the predecessors of FSX got wrong, and why this is an issue today, is that they assumed that Moores law would be maintained by delivering ever more powerful (i.e. faster) processors. This was what had happened with mainframes and mini computers, so it was considered a safe enough bet with PC's. The original 4.77MHz IBM PC of 1983, should have been running at 4.77GHz in 1999. Ok, it went from 8bit, thru 16 and 32 to 64 bit. so add another 3 cycles of 18months and that brings you to 2005. And even when FS9 was released, Intel was shipping P4's at 3.6GHz and people were already talking about overclocking well past 4GHz, so it was still not unreasonable to expect history to continue as it had.

 

Then came an unexpected paradigm shift. Intead of making processors faster, they made more of them. The rest of the game industry grabbed this with both hands since as a model, multicore processing really suits gaming probably better then any other area of computing. 1+ core for logic, 1+ for graphics, 1+ for physics and 1+ for sound. However, the Flight franchise was so dominant, that it had no real competition, and it was too big and cumbersome to be refactored to exploit multicore. The rest, as they say, is history.

 

Just to set the record straight. FSX is not, and never was, well written. That did not stop it becoming the dominant flight simulator to the degree that when the computing world changed from monolithic processing to multicore processing, there was nothing on the market that could step into its place, not even when Microsoft closed it down. The authors of X-plane can justifiably claim theirs is a far better written product, however, they still have not had the commercial success to encourage the add-on creators to support their platform, and that means we all suffer.

i have this prםblem

Did you add the HIGHMEMFIX=1 line to your fsx.cfg like the instruction manual told you to do?

If you don't mind me asking, what's your experience\background Paul? You sound very knowlegeable, have you written a DX renderer or anything like that? Do you work with 3D math? By the way, I'm working on parallel processing the physics of N complex assemblies.

Did you add the HIGHMEMFIX=1 line to your fsx.cfg like the instruction manual told you to do?

 

Yes, I did, and still have the problem.

Is there anything else I can do?

 

 

 

[GRAPHICS]

AC_SELF_SHADOW=0

AIRCRAFT_REFLECTIONS=1

AIRCRAFT_SHADOWS=0

COCKPIT_HIGH_LOD=1

D3D10=0

EFFECTS_QUALITY=2

GROUND_SHADOWS=0

IMAGE_QUALITY=0

LANDING_LIGHTS=1

NUM_LIGHTS=8

See_Self=1

SHADER_CACHE_PRIMED=1693458432

TEXTURE_MAX_LOAD=512

TEXTURE_QUALITY=3

Text_Scroll=1

HIGHMEMFIX=1

I added this line to my [DISPLAY] Section : TEXTURE_BANDWIDTH_MULT=2800

 

 

Also, my TextureMaxLoad=6 as opposed to the 512 in yours. See if that helps you. It really improved my texture loading.

After reaching what I found to be good performance I decided to change some of my Inspector settings. Specifically, I upped my Antialiasing to Super VCAA_64x_8v8 and was impressed with the visual improvement. My frame rates did not drop a bit, but using the Inspector monitor while flying around KLGA with AS2012 running I noticed my GPU usage went up to 90% and VRAM used was 1380. It also really sharpened my textures all around. This is the only thing that has really pushed my 660ti so far.