...without smooth gradient

There are a number of flyers who set "1/3 frame Rate" in Inspector, and set "20" fps in FSX - it's quite smooth, and will allow some higher slider settings.

I'm one of them. Frame rates aren't the Holy Grail ... *smoothness* is. My DX10+Fixer runs beautifully smoothly on a very modest system.

I used to work in film - where 24fps was considered perfectly adequate for cinema -albeit we're talking about either projectors or CRT screens (in those day) that held the phosphors longer.

Adam.
 
Thak you Poul and Adam. I'll try your suggestions... however my expactations were bigger after changing GPU. Hmm, maybe I'll try rise CPU clock...

Best regards,
Lucas
 
Thak you Poul and Adam. I'll try your suggestions... however my expactations were bigger after changing GPU. Hmm, maybe I'll try rise CPU clock...

Best regards,
Lucas


Good idea, my friend! With some water cooling and some patience - your proc should see 4.5 or 4.6, and you WILL notice that!

All the Best,

pj
 
Hi Poul,

…do you think that 4.5 GHz OC needs water cooling? One of my friends raise i5 2500K to 4.4 (or even 4.5) only by increasing multiplier and he has traditional cooler (not stock of course).

Ok, anyway, I would like to share my settings and performance… I think that I will not invent anything else. I also must admit that I'm disappointed because I don't see improvement with new GPU :( - 2 x more memory, 2 x faster core ...and nothing.

Ok, Inspector:


FSX.CFG:
[JOBSCHEDULER]
AffinityMask=14

[BUFFERPOOLS]
Usepools=0

[SOUND]
AmbientUIMusicVolume=-6.000000
SOUND_FADER1=0.100000
SOUND_FADER2=0.800000
SOUND_FADER3=0.200000
SOUND_FADER4=0.500000
AmbientUIMusic=FSX01
SOUND=1
SOUND_QUALITY=2
SOUND_LOD=0
UISound=1
AmbientUI=0
PrimaryDevice={DEF00000-9C6D-47ED-AAF1-4DDA8F2B5C03}
VoiceDevice={DEF00002-9C6D-47ED-AAF1-4DDA8F2B5C03}

[Display]
ChangeTime=4.000000
TransitionTime=4.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=True
InfoParkingBrakesEnable=True
InfoPauseEnable=True
InfoSlewEnable=True
InfoStallEnable=True
InfoOverspeedEnable=True
BLOOM_EFFECTS=1
SKINNED_ANIMATIONS=1
TEXTURE_BANDWIDTH_MULT=80
UPPER_FRAMERATE_LIMIT=0
WideViewAspect=False

[Main]
FIBER_FRAME_TIME_FRACTION=0.20
DisablePreload=1
User Objects=Airplane, Helicopter
SimObjectPaths.0=SimObjects\Airplanes
SimObjectPaths.1=SimObjects\Rotorcraft
SimObjectPaths.2=SimObjects\GroundVehicles
SimObjectPaths.3=SimObjects\Boats
SimObjectPaths.4=SimObjects\Animals
SimObjectPaths.5=SimObjects\Misc
HideMenuNormal=0
HideMenuFullscreen=1
HideInfoText=1
ProcSpeed=16774
PerfBucket=7
Location=120,104,1160,880,\\.\DISPLAY1
Maximized=2

[PANELS]
IMAGE_QUALITY=1
QUICKTIPS=1
PANEL_OPACITY=100
PANEL_MASKING=1
PANEL_STRETCHING=1
UNITS_OF_MEASURE=0
DEFAULT_VIEW=0

[Weather]
WindshieldPrecipitationEffects=1
MinGustTime=10
MaxGustTime=500
MinGustRampSpeed=1
MaxGustRampSpeed=200
MinVarTime=5
MaxVarTime=50
MinVarRampSpeed=10
MaxVarRampSpeed=75
TurbulenceScale=1.000000
WeatherServerAddress=fs2k.zone.com
WeatherServerPort=80
WeatherGraphDataInDialog=0
AdjustForMagVarInDialog=1
DynamicWeather=0
DownloadWindsAloft=0
DisableTurbulence=0
CLOUD_DRAW_DISTANCE=4
DETAILED_CLOUDS=1
CLOUD_COVERAGE_DENSITY=8
THERMAL_VISUALS=0

[DISPLAY.Device.NVIDIA GeForce GTX 660 Ti.0]
Mode=1280x1024x32
Anisotropic=1
AntiAlias=1

[CONTROLS]
Controls_Default=Standard
Controls_Current=Standard
KBDAIL=64
KBDELEV=64
KBDRUD=64

[GRAPHICS]
HIGHMEMFIX=1
SHADER_CACHE_PRIMED=1693458432
TEXTURE_MAX_LOAD=1024
NUM_LIGHTS=8
AIRCRAFT_SHADOWS=0
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=1693458432
D3D10=1
MultiSamplesPerPixel=4
MultiSampleQuality=0

[TextInfo.1]
Latitude=1,1
Longitude=1,2
Altitude=1,3
Heading=1,4
AirSpeed=1,5
WindDirectionAndSpeed=1,6
[TextInfo.2]
FrameRate=1,1
LockedFrameRate=1,2
GForce=1,3
FuelPercentage=1,4
[TextInfo.3]
Latitude=1,1
Longitude=1,2
Altitude=1,3
Heading=1,4
AirSpeed=1,5
WindDirectionAndSpeed=1,6
FrameRate=2,1
LockedFrameRate=2,2
GForce=2,3
FuelPercentage=2,4
[SlewTextInfo.1]
Latitude=1,1
Longitude=1,2
Altitude=1,3
Heading=1,4
AirSpeed=1,5
[SlewTextInfo.2]
FrameRate=1,1
LockedFrameRate=1,2
[SlewTextInfo.3]
Latitude=1,1
Longitude=1,2
Altitude=1,3
Heading=1,4
AirSpeed=1,5
FrameRate=2,1
LockedFrameRate=2,2
[DynamicHeadMovement]
LonAccelOnHeadLon=-0.020000
LonAccelOnHeadPitch=-0.010000
RollAccelOnHeadLat=0.010000
YawAccelOnHeadLat=-0.100000
RollAccelOnHeadRoll=0.100000
MaxHeadAngle=5.000000
MaxHeadOffset=0.300000
HeadMoveTimeConstant=1.000000
[VirtualCopilot]
VirtualCopilotActive=0
[USERINTERFACE]
PageID=1
OpenATCOnCreate=0
SHOW_MISSION_CAPTIONS=0
PAUSE_ON_LOST_FOCUS=0
PROMPT_ON_EXIT=1
SITUATION=FLIGHTS\OTHER\FLTSIM
Map_Orientation=2
ShowAllACPaintSchemes=1
SelectAircraftManufacturer=Wszystkie
SelectAircraftPublisher=Wszystkie
SelectAircraftType=Wszystkie
DisplayFuelAsWeight=1
[ATC]
ShowATCText=0
COMM_MSG_NONE_COLOR=FFFFFFFF
COMM_MSG_ATC_USER_COLOR=FFB6FFB6
COMM_MSG_USER_ATC_COLOR=FFFFD21B
COMM_MSG_ATC_AI_COLOR=FF00FF00
COMM_MSG_AI_ATC_COLOR=FFFF7840
AutoOpenAirTrafficWindow=0
UsePilotVoice=0
PilotVoice=0
[PointOfInterestSystem]
CycleSetting=0

[SCENERY]
LENSFLARE=0
DAWN_DUSK_SMOOTHING=1
IMAGE_COMPLEXITY=5

[TrafficManager]
AirlineDensity=0
GADensity=0
FreewayDensity=5
ShipsAndFerriesDensity=5
LeisureBoatsDensity=5
IFROnly=0
AIRPORT_SCENERY_DENSITY=1

[TERRAIN]
LOD_RADIUS=4.500000
MESH_COMPLEXITY=80
MESH_RESOLUTION=23
TEXTURE_RESOLUTION=27
AUTOGEN_DENSITY=2
DETAIL_TEXTURE=1
WATER_EFFECTS=5

[AContain]
ShowLabels=1
ShowUserLabel=0
ShowLabelManufacturer=0
ShowLabelModel=0
ShowLabelTailNumber=1
ShowLabelDistance=0
ShowLabelAltitude=0
ShowLabelAirline=0
ShowLabelAirlineAndFlightNumber=0
ShowLabelFlightPlan=0
ShowLabelContainerId=0
ShowLabelAirspeed=0
ShowLabelHeading=0
LabelDelay=1000
LabelColor=FFFF0000
[INTERNATIONAL]
ASLAT=2
ASLON=0
MEASURE=0
[REALISM]
PFactor=1.000000
Torque=1.000000
GyroEffect=1.000000
CrashTolerance=1.000000
General=1.000000
UnlimitedFuel=False
TrueAirspeed=False
AutoCoord=False
RealMixture=True
StressDamage=False
GEffect=True
ManualLights=True
GyroDrift=True
CrashWithDyn=False
CrashDetection=False
AutoTrim=False
[SIM]
SYSCLOCK=1
[STARTUP]
DEMO=0
SHOW_OPENING_SCREEN=1
STARTUP_DEMO=
LoadWindow=1
[FACILITIES]
COUNTRY=
STATE=
CITY=
GTL_BUTTON=1338
[Misc]
Com_Rate=7

[Trusted]
F:\FSX\Modules\FSUIPC4.dll.bqozccnatnzlukzurlnhrlquankhullcqizqutcu=1
F:\FSX\as_srv\as_btstrp.dll.zzueiueohnzeaqrequtnhhreklbhnlikkizutzcr=1
F:\FSX\Modules\FSCopilot.dll.ehllltkocelrwzbtzaerqkaabnhhoqibikwtceww=1
F:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll.lkktnhaatuwzlunbbncqrlnltiilhiqehqoqqiui=1
F:\FSX\GAUGES\PMDG_737NGX.DLL.wlzqowlqwcthabbiueqzhwkrkclbtcqnhqqlruoh=2
F:\FSX\GAUGES\PMDG_737NGX_3.DLL.izerhlcknihullnkuotchqnhhclrhhlwzhhnzbhn=2
F:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll.aukrlkkbkqcoqbeqzaztqkahnwnleqclierknuor=1
F:\FSX\GAUGES\PMDG_737NGX.DLL.rulhlziwwurutuekroweeaoraktlrtcwitieowzr=2
F:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll.wwwzziaubohbetizootzzkrrouhezqlukbtwnltt=1
F:\FSX\GAUGES\PMDG_737NGX.DLL.hnakleiwuunlcqrztnzrbieottqltethltuhqill=2
F:\FSX\GAUGES\PMDG_737NGX_3.DLL.tktwnebwczhwrcztlcarbooqtinnkrltbuuwlhqt=2
F:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll.hewioznlaabuirrzckeanqruriqebbrwercannze=1
F:\FSX\GAUGES\PMDG_737NGX.DLL.tktwzbchlowneuwbtbqnziooqacahwwnwkqcwabu=2
F:\FSX\PMDG\DLLs\PMDG_Interface.dll.uoibazarrqobuoketcccrwcwaawawzazeqoeutrn=1
F:\FSX\RAASPRO\RAASPRO.dll.haieaerewrhzotaokoonubobtwcbattulczubkhu=1
F:\FSX\GAUGES\PMDG_777X.DLL.cbentruuqbbrntrenkukwnohbqecnharankntuuq=2
F:\FSX\GAUGES\PMDG_777X_3.DLL.zbhzrbocowkhtntbloeethwkiabiinaintkoheor=2
F:\FSX\GAUGES\PMDG_BAe_JS4100_3.DLL.liaeqwlzliaeclabtbeekhareltrruinwieobarz=2
F:\FSX\GAUGES\PMDG_BAe_JS4100.DLL.qtkaiueckoewtklorlwtlwewuiowanaaqtlbklwo=2
F:\FSX\GAUGES\RadioC210.DLL.nuhnwrilhhaelqueoorhabzbkwbeeqnwaktohhei=2
F:\FSX\GAUGES\CCTC2.DLL.nczbznlcwollhakrrttaauuqqaoorowuznkarkrq=2
F:\FSX\fsdreamteam\couatl\couatl.exe.iehqktiotzziwlinzultnzceihzokllkhcbkchkl=1
F:\FSX\bglmanx.dll.quttbkueietklieczzqeuwnbnzttuuozqcnbhwtb=1
F:\FSX\FSCaptain\bin\FSCaptain.dll.anluwoqqzhkuhawrrlqbrocoqzzritbaanelntln=1
F:\FSX\GAUGES\FCDU.GAU.ltzobhcaelrnrlazbhbouzebhhrenqatiwweebrb=2
C:\Program Files (x86)\EZCA\EZCA.exe.qnckurrokleewbwblqtrteuiecnazzrlzuzrrkeb=1
F:\FSX\GAUGES\XGauge.DLL.clrhoteotohzkkhllwtrwlierbbqqbqioooicniu=2
F:\FSX\GAUGES\737-400.DLL.cenclhrqcuikqeleolnhzwbocnowiizrroienwue=2

[DISPLAY.Device.NVIDIA GeForce GTX 660 Ti.0.0]
AntiAlias=1
Mode=1280x1024x32
Anisotropic=1

[MAPVIEW_MAP]
SHOW_AIRPORTS=1
SHOW_VORS=1
SHOW_NDBS=1
SHOW_APPROACHES=1
SHOW_INTERSECTIONS=0
SHOW_VICTOR=0
SHOW_JET=0
SHOW_AIRSPACE=1
SHOW_FLIGHTPLAN=1
SHOW_WEATHERSTATIONS=1
SHOW_WEATHERSYSTEMS=1
SHOW_DATATAGS=1
SHOW_TERRAIN=1
show_flight_history=1
[MULTIPLAYER]
condAccoutPassword=0


(yes, I’m stubborn [a little ;)] and leave LOD_RADIUS=4.5, because I don’t want to sharp textures only straight below the aircraft ..and 'yes' limited frames by Inspector because I steel think that I have a little more fps via this way).
Also, I didn't see differences between AAx2 and x4 set in Fixer, so I leave x4.

However… in my case, textures time sharpening could be shorter in external view (sometimes I have to wait about 10 sec. or more) -> do you think that should I change FFTF or TBM paramtres?

Ok, Poul, and one more question – does WINOWED Vsync have impact to fps? I know that full-screen-flying is better way (= more smoother and higher fps) but I usually fly on Vatsim and have to change between different programs while flight.
(and yes, I know that I have to use „pseudo full screen” and „aero” in case windowed vsync :) )

Regards,
Lucas
 

Hi Poul,

…do you think that 4.5 GHz OC needs water cooling? One of my friends raise i5 2500K to 4.4 (or even 4.5) only by increasing multiplier and he has traditional cooler (not stock of course).

Ok, anyway, I would like to share my settings and performance… I think that I will not invent anything else. I also must admit that I'm disappointed because I don't see improvement with new GPU - 2 x more memory, 2 x faster core ...and nothing.

FSX.CFG:

[Display]
BLOOM_EFFECTS=1
UPPER_FRAMERATE_LIMIT=0

[Main]
FIBER_FRAME_TIME_FRACTION=0.20

[Weather]
CLOUD_DRAW_DISTANCE=4
DETAILED_CLOUDS=1
CLOUD_COVERAGE_DENSITY=8

[SCENERY]
IMAGE_COMPLEXITY=5

[TrafficManager]
FreewayDensity=5
ShipsAndFerriesDensity=5
LeisureBoatsDensity=5
AIRPORT_SCENERY_DENSITY=1

[TERRAIN]
LOD_RADIUS=4.500000
WATER_EFFECTS=5

[DISPLAY.Device.NVIDIA GeForce GTX 660 Ti.0.0]
Mode=1280x1024x32
AntiAlias=1
Anisotropic=1

(yes, I’m stubborn [a little ;)] and leave LOD_RADIUS=4.5, because I don’t want to sharp textures only straight below the aircraft ..and 'yes' limited frames by Inspector because I steel think that I have a little more fps via this way).
Also, I didn't see differences between AAx2 and x4 set in Fixer, so I leave x4.

However… in my case, textures time sharpening could be shorter in external view (sometimes I have to wait about 10 sec. or more) -> do you think that should I change FFTF or TBM paramtres?

Ok, Poul, and one more question – does WINOWED Vsync have impact to fps? I know that full-screen-flying is better way (= more smoother and higher fps) but I usually fly on Vatsim and have to change between different programs while flight.
(and yes, I know that I have to use „pseudo full screen” and „aero” in case windowed vsync)


AsRock P67 Pro3 | i5 2500K 4.3GHz | 4 x 2GB RAM | Gigabyte GTX660 Ti OC 2GB | 2 x 1TB (SATAIII) | Vista 64

FSX (SP2), DX10SF, SweetFX, UTX Europe, XClass World, AS Next, REX4, GSX






1). "Do I think that a 4.5 gig proc needs watercooling??"
I can't answer that question, Lucasz.
What information would you think I need in order to answer that question?


2). "new GPU - 2 x more memory, 2 x faster core ...and nothing." On May 4th, in this thread, post #20, I said that:-



In your case - at 4.3 gig - any of those cards will work - even a 560Ti is ok, but the 660 is a 3rd-grade card, so you would be better to wait and save up to get a good card - the 680 - as this will match the proc, and will even allow you to move the proc speed up tp 4.6 gig - then your FSX would begin to fly!


- so you knew that when you purchased the card.



3). "
do you think that should I change FFTF or TBM paramtres?" May 4th -> lucasz_fsx_660.txt but only when using 30 fps locked INSIDE the flight sim. TBM doesn't work at all when using unlimited.

4). "p
seudo full screen” and „aero” in case windowed vsync" In my very brief tests with Aero - the sim appeared even smoother - and also at more consistent frame rates. Windowed or fullscreen should both be ~same.

5). (yes, I’m stubborn [a little ;)] and leave LOD_RADIUS=4.5, and " I have a little more fps via this way" (unlimited frames)--->>>> "sometimes I have to wait about 10 sec. or more)" True. Unlimited frames can cause this, because then all system time is devoted to fsx, and eventually this causes the system to pause fsx, so that it can do it's "housekeeping".

# 5 is your problem, Lucasz. Expectations. To get a smooth sim, with nice graphics and a high (30fps) frame rate then you have two choices: you either get a faster system - say 4.8 - 5.2GHz, with an x80-series gpu, or you lower your expectations. You can be as stubborn as you like - your pc is not going to suddenly behave as if it were a high-end pc. I've suggested good settings for a low-end pc in a re-vamped fsx.cfg on May 14th, in this thread, and you've ignored most of them, and I have posted a list of the known frame-killers. If you choose not to make use of that, or to ignore what others suggest, then you have to find your own way - ok!

All the Best,

PAUL J





DX10 Setup Guide - Frame Killers in the fsx.cfg - DX10 SF Manual - AA Settings Table - FSX Graphics Buffering

2600K@5.0gig on Water, P8P67 DL; GTX 780; 8gig Vngnc C8@1600; Win 7-64; FSX - DX10, TH2G w/3x19"

 
1). "Do I think that a 4.5 gig proc needs watercooling??" I can't answer that question, Lucasz.
What information would you think I need in order to answer that question?

I was suggested your above words:

„With some water cooling and some patience - your proc should see 4.5 or 4.6”

…so asked you about water cooling, but I understand that you cannot give me simply answer – no problem.

* * *

I said that:-

In your case - at 4.3 gig - any of those cards will work - even a 560Ti is ok, but the 660 is a 3rd-grade card, so you would be better to wait and save up to get a good card - the 680 - as this will match the proc, and will even allow you to move the proc speed up tp 4.6 gig - then your FSX would begin to fly!

- so you knew that when you purchased the card.


# 5 is your problem, Lucasz. Expectations. To get a smooth sim, with nice graphics and a high (30fps) frame rate then you have two choices: you either get a faster system - say 4.8 - 5.2GHz, with an x80-series gpu, or you lower your expectations. You can be as stubborn as you like - your pc is not going to suddenly behave as if it were a high-end pc. I've suggested good settings for a low-end pc in a re-vamped fsx.cfg on May 14th, in this thread, and you've ignored most of them, and I have posted a list of the known frame-killers. If you choose not to make use of that, or to ignore what others suggest, then you have to find your own way - ok!

Ok, Poul, yes - you exactly wrote this, but you also wrote:

Post #10:
„A 660 will give much better performance than the 560 - even the 560Ti is much better, so - yes if it's available and you can afford it..... and will allow the use of: [BufferPools] UsePools=0”

Post #15:
- my question: „Do you think with 660 will be big performance improve in relation to my 560?”
- your answer: “Yes it will: the 560 is a low-end card, even when compared to the 560Ti.”

Post #18
[…] but the 660 (or 660Ti) has many features which put either into the "next grade" above the 560. I'm sure you'll do the right thing....”

After all these words I was sure that superiority 660Ti over 560 will be visible, so this is why I’m disappointed now - I hope that you understand me.
Of course I know that ‘x80’ card is far better, unfortunately I don’t have money for it, however after your words I expected improvement even with 660.
Ok, nothing happened… don't misunderstand me, I’m not angry on you …still very thankful for time spent for me and a lot of help from you.

Regards,
Lucas
 
Post #10:

„A 660 will give much better performance than the 560 - even the 560Ti is much better, so - yes if it's available and you can afford it..... and will allow the use of: [BufferPools] UsePools=0”


Post #15:
- my question: „Do you think with 660 will be big performance improve in relation to my 560?”
- your answer: “Yes it will: the 560 is a low-end card, even when compared to the 560Ti.”



Please don't blame me for you ignoring the settings which I've posted twice for you to use. And cherry-picking one sentence out of context mixed in with two (or more) long posts regarding your problem is not going to score any points, either.

Your problem is a slow processor and system in general, and you are expecting much better performance with just a gpu change. At the same time you are killing the system with FSX settings which are too high.


And my name is not "Poul"
.


pj
 
I'm sorry that I made a mistake in your name.

* * *

Ok, nothing happened… don't misunderstand me, I’m not angry on you …still very thankful for time spent for me and a lot of help from you.
Again... I don't blame you! (that was my choice) I'm only disappointed (I think that I have a right to be disappointed) that with THE SAME SETTINGS in simulator, Inspector, etc. FSX's performance is the same with both cards, although one is much better then the second.

Ok, there is no sense to continue this subject. I didn't expect such your reaction. I hope this will not have affect on our acquaintance.

All the best,
Lucas
 
These are most of my personal rules, Lucasz:-

Given that Flight Simulator X is processor-bound:

If you increase your cpu speed - you will get better performance.

If your gpu is not capable of matching that performance - you will only get the same performance - maybe a hair better, or smoother. The 660 has better performance than the 560Ti.

If you move your cpu to 4.6GHz with the 660 - you will get better performance.

If your cpu and gpu are improved, you need to bring the rest of the system up with them.

I use this cooling system, chosen by knowing (before I purchased it) - that it would take care of the heat from any proc I could overclock.

I only buy the *80 - series Nvidia gpu's. I have then taken care of the gpu bottleneck.

I use Alacrity to stop all un-necessary processes.

I have FSX on it's own dedicated SSD.

I only load areas and airports where I'm going to fly.

I have different fsx.cfg's for each "type" of flight that I make. GA - VFR or IFR: Airliner: Helicopter: each has it's own cfg file.

The fsx.cfg and Inspector settings are only two members of the team. The "system" has to work efficiently and in harmony.
Some of this is also outlined in Nick's "Bible" - particularly the hardware choice for FSX.

OK!

All the Best.

pj
 
Hi Paul,

thanks for detailed info.

Yestarday I applied your proposed settings and did some tests, then changing this and that ... and I observed that the big impact on performance (in my case) has WATER_EFFECT=5 and IMAGE_COMPLEXITY=5, so I decreased them by 1 -> there is much better now. I also set limit of frames in FSX.
Other settings from [TERRAIN] section and cloud settings ('coverage density' and 'detailed cloud') I decided to leave – I think they have no impact (or very marginal) on performance (in my case).

Now, I’m going to do some tests with set windowed VSYNC (some people said that it increase smoothness) -> please tell me one thing: I know that I have to start Aero after run FSX but is it necessary to use “pseudo full screen” or is it visual effect tweak only?

Best regards,
Lucas ;)
 
Good Morning Lucasz;

, I’m going to do some tests with set windowed VSYNC (some people said that it increase smoothness) -> please tell me one thing: I know that I have to start Aero after run FSX but is it necessary to use “pseudo full screen” or is it visual effect tweak only?


Pseudo-FullScreen is a visual effect, allowing FSX to be in "windowed-mode", but looking as if it were in "full-screen mode". This is a requirement for most dual or multi-monitor flyers who want their GPS - FMC - PlanG, etc., on the second monitor, but want to fly in the "normal" full screen mode.


Regarding:-

cloud settings ('coverage density' and 'detailed cloud') I decided to leave – I think they have no impact (or very marginal) on performance (in my case).


From your fsx.cfg, May 4th:-

CLOUD_DRAW_DISTANCE=6
DETAILED_CLOUDS=1
CLOUD_COVERAGE_DENSITY=8

I recommended, on the same date:-

CLOUD_DRAW_DISTANCE=3 // 6
DETAILED_CLOUDS=0 // 1
CLOUD_COVERAGE_DENSITY=7 // 8

These settings have a very large impact on frame rates, and will prevent other, perhaps more desirable effects to not perform as you think they should.

Regards,

pj
 
Good Morning Lucasz;

, I’m going to do some tests with set windowed VSYNC (some people said that it increase smoothness) -> please tell me one thing: I know that I have to start Aero after run FSX but is it necessary to use “pseudo full screen” or is it visual effect tweak only?
Pseudo-FullScreen is a visual effect, allowing FSX to be in "windowed-mode", but looking as if it were in "full-screen mode". This is a requirement for most dual or multi-monitor flyers who want their GPS - FMC - PlanG, etc., on the second monitor, but want to fly in the "normal" full screen mode. We use Aero to provide the vSync in this case, as it does not normally work in windowed mode.


Regarding:-

cloud settings ('coverage density' and 'detailed cloud') I decided to leave – I think they have no impact (or very marginal) on performance (in my case).

From your fsx.cfg, May 4th:-

CLOUD_DRAW_DISTANCE=6
DETAILED_CLOUDS=1
CLOUD_COVERAGE_DENSITY=8

I recommended, on the same date:-

CLOUD_DRAW_DISTANCE=3 // 6
DETAILED_CLOUDS=0 // 1
CLOUD_COVERAGE_DENSITY=7 // 8

These settings have a very large impact on frame rates, and will prevent other, perhaps more desirable effects to not perform as you think they should.

Regards,

pj
 
Back
Top