Author Topic: FS2004 Default Terminal 2/3 .bgl  (Read 79005 times)

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50691
    • VIRTUALI Sagl
Re: FS2004 Default Terminal 2/3 .bgl
« Reply #15 on: August 06, 2012, 09:51:57 am »
There's a switch in your settings which might potentially affect fps a lot, the "Transform & Lighting" is switched off, try to turn it on. And, turn the number of hardware lights to the maximum too.

I get much better fps (as you can clearly see in my screenshots) with *everything* maxed out to the right...so your system clearly has problems.

And, of course, when trying to understand the fps of a *SCENERY* ALWAYS use a default airplane.

gmcg

  • Jr. Member
  • **
  • Posts: 71
Re: FS2004 Default Terminal 2/3 .bgl
« Reply #16 on: August 06, 2012, 06:17:04 pm »
I already tried transform lighting...... I guess I could try it again with the lights maxed out and see what happens.

Whether you want to believe me or not, my computer literally just came out of the shop and had a diagnostic check with a clean bill of health.

Who cares about default aircraft? I too can probably get 60+ FPS in the default 777. Doesn't do me any good since I only use the LDS757/767 and that should be the true benchmark  :o

What is your opinion on my graphics card? Again, its a GeForce 210 (I'm 50% positive its not the best for gaming).
« Last Edit: August 07, 2012, 12:43:26 am by gmcg »

gmcg

  • Jr. Member
  • **
  • Posts: 71
Re: FS2004 Default Terminal 2/3 .bgl
« Reply #17 on: August 24, 2012, 11:42:01 pm »
OK what now  ???

I just installed a NVIDA 9800 GTX+ 1GB and am still getting only 23FPS (Locked at 28) in some places in the middle of the B/C concourse. And this is with Term2/3 not installed.

Some might say 23 in only "some" parts is playable but I don't want to give up that easily after spending $120 on a used 9800 GTX+

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50691
    • VIRTUALI Sagl
Re: FS2004 Default Terminal 2/3 .bgl
« Reply #18 on: August 25, 2012, 09:56:49 am »
First, nobody suggested that your video card wasn't good enough or that your problem was caused by your video card.

Since the screenshots I've posted from my system (which is now has a lesser video card than your new one) shows an higher fps, it's fairly obvious the problem is not your video card, or the scenery, but something else in your system.

And, you are wrong stating that "I only use the LDS757/767 and that should be the true benchmark", because this way you have lost the ability to assess performances, because you can't possibly know if the problem is the airplane or the scenery.

As I've said, FIRST test with a default airplane and THEN (in exactly the same spot) test with the airplane you are using most, and check the DIFFERENCE, so you can at least understand WHY you are losing fps.

You might also try to UNLOCK the fps, and 28 it's a number that doesn't make any sense anyway, because fps should be locked to a number that is aligned to the screen refresh rate so, for a standard 60 hz refresh rate, it would be better locking at 30 fps (or 20 fps). And, some users prefer to leave the fps unlocked in Flight sim, and use an external utility to lock the fps.
« Last Edit: August 25, 2012, 09:59:31 am by virtuali »

gmcg

  • Jr. Member
  • **
  • Posts: 71
Re: FS2004 Default Terminal 2/3 .bgl
« Reply #19 on: October 01, 2012, 10:58:34 pm »
Put a new CPU in...... works fine.

My next question though now is stuff in the distance sort of looks jittery when I make a turn. Its almost like my screen lags even though the computer is holding its FPS no problems. Like its "tearing" the image in half making it look like its lagging. Any ideas what could be causing this? In addition, my taxi lines look like crap. So I'm wondering if there is a setting(s) I could change within Nvidia Inspector that could fix both b/c I really feel the two are related.

I hope I'm explaining if well. But its like a wave that develops when I make sharp turns and makes the buildings in the distance looking like they are lagging behind and unclear. I even tried 30FPS since my monitor refresh rate is 60Hz and get this "slicing wave" issue.

Please help and thanks!

http://imageshack.us/a/img231/4030/capture1zm.jpg
Terrible, blocky looking taxi lines

http://imageshack.us/a/img525/5607/capture4gp.jpg
Nvidia Settings  
« Last Edit: October 02, 2012, 01:15:14 am by virtuali »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50691
    • VIRTUALI Sagl
Re: FS2004 Default Terminal 2/3 .bgl
« Reply #20 on: October 02, 2012, 01:19:08 am »
Like its "tearing" the image in half making it look like its lagging. Any ideas what could be causing this?

Tearing is the correct term, and it means you don't have VSync enabled. Sometimes is tricky to have it enabled, sometimes it works only in full screen mode, and it's dependent on driver settings, releases and tweaks applied.

Quote
In addition, my taxi lines look like crap. So I'm wondering if there is a setting(s) I could change within Nvidia Inspector that could fix both b/c I really feel the two are related.

No, they aren't. Jagged lines are due to a lack of antialiasing, try to set the video card to "Force" the Antialiasing, instead of "set by the application"


Quote
I even tried 30FPS since my monitor refresh rate is 60Hz and get this "slicing wave" issue.

That's vsync not enabled, and you shouldn't lock your fps. Enable vsync and keep the fps unlimited.

gmcg

  • Jr. Member
  • **
  • Posts: 71
Re: FS2004 Default Terminal 2/3 .bgl
« Reply #21 on: October 04, 2012, 07:49:31 am »
Will try

gmcg

  • Jr. Member
  • **
  • Posts: 71
Re: FS2004 Default Terminal 2/3 .bgl
« Reply #22 on: October 07, 2012, 05:28:56 am »
Alright I'm literally driving myself nuts...... I need to get the FPS up in these few areas with the LDS767 panel. That is the only way I can enjoy it. I had them up and locked for a while with my old fs9.cfg file but the changes I made are only suppose to improve performance, not downgrade it.

Any suggestions? Could FSDT release a "lighter" texture or a lighter .bgl version? I would be whiling to re-buy the product, if I knew it would preform like Hawaii does for me, at this point since I'm literally going bonkers  :o

I don't believe my configuration is off since ORD is the only issue. Everything else is smooth as silk. Here is my FS9.CFG and Nvidia settings. I need to get the performance up all over the airport.... I'd even been cool with like 28 locked at 30 in these areas at this point if we can't get all 30 back (I don't see why we can't though with my rig and settings) Please help :'(

[PANELS]
IMAGE_QUALITY=1
UNITS_OF_MEASURE=0
QUICKTIPS=0
PANEL_MASKING=1
PANEL_STRETCHING=1
[Weather]
WindshieldPrecipitationEffects=1
MinGustTime=10
MaxGustTime=500
MinGustRampSpeed=1
MaxGustRampSpeed=200
MinVarTime=5
MaxVarTime=50
MinVarRampSpeed=10
MaxVarRampSpeed=75
TurbulenceScale=1.000000
DefaultVisibility=0
DynWx_MedianDewPointSpread=10.000000
DynWx_ProbCloudFormForMedianDewPoint=0.000500
DynWx_MaxDewPointSpread=50.000000
DynWx_ProbCloudFormForMaxDewPoint=0.000125
DynWx_ProbCloudFormForMinDewPoint=0.100000
DynWx_DryTempLapsePer1000Meters=9.000000
DynWx_ProbCloudFormForDryTempLapse=0.000500
DynWx_MoistTempLapsePer1000Meters=3.300000
DynWx_ProbCloudFormForMoistTempLapse=0.040000
DynWx_MaxProbCloudChangePerMinute=0.040000
DynWx_MultiplierForDynamicWeatherLevelMild=0.500000
DynWx_MultiplierForDynamicWeatherLevelNormal=1.000000
DynWx_MultiplierForDynamicWeatherLevelHigh=3.000000
DynWx_MultiplierForDynamicWeatherLevelExtreme=10.000000
DynWx_TempChangePercentageForOvercastClouds=0.750000
DynWx_TempChangePercentageForMinDewPoint=0.700000
DynWx_MaxTempChangePerMinute=0.060000
WeatherServerAddress=fs2k.zone.com
WeatherServerPort=80
WeatherGraphDataInDialog=0
DynamicWeather=2
LOADWEATHER=1
MAX_UNLIMITED_VIS=96560
CLOUD_DRAW_DISTANCE=4
3D_CLOUD_PERCENT=90
DETAILED_CLOUDS=1
CLOUD_COVERAGE_DENSITY=6
CloudsImpostorRingRadius=57600.000000
[INTERNATIONAL]
ASLAT=2
ASLON=1
MEASURE=0
[MISC]
COM_RATE=7
LOG_TIME=0
FOREIGN_TRANSLATOR=0
LOG_FILE=
[STARTUP]
DEMO=0
LOADSIM=1
LOADWINDOW=1
SHOW_OPENING_SCREEN=1
STARTUP_DEMO=
[GRAPHICS]
FULL_SCREEN=0
PERFORMANCE_MODE=0
DEF_PERF_MODE=6
TEXT_SCROLL=0
AUTO_LOD=0
DETAIL_TEXTURE=2
WATER_EFFECTS=1
TERRAIN_USE_VECTOR_MAP=1
TERRAIN_USE_VECTOR_OBJECTS=1
EFFECTS_QUALITY=0
GROUND_SHADOWS=0
SMOOTH_VIEW=1
IMAGE_SMOOTHING=1
TEXTURE_MAX_LOAD=256
COCKPIT_HIGH_LOD=0
AIRCRAFT_SHADOWS=0
LANDING_LIGHTS=1
IMAGE_QUALITY=0
TEXTURE_BLDG=1
TEXTURE_GND=1
TEXTURE_WATER=1
AIRCRAFT_TEXTURE=1
SEE_SELF=1
TEXTURE_QUALITY=3
LOD_TARGET_FPS=21
NUM_LIGHTS=6
[REALISM]
INDASPD=0
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=False
CrashWithDyn=False
CrashDetection=0
[CONTROLS]
KBDAIL=64
KBDELEV=64
KBDRUD=64
PAN_RATE=900
[USERINTERFACE]
MAP_ORIENTATION=2
PAUSE_ON_LOST_FOCUS=0
PROMPT_ON_EXIT=1
SelectFlightLevel=0
SelectFlightTitle=0
PageID=3
OpenATCOnCreate=0
SITUATION=
DisplayFuelAsWeight=1
[SOUND]
SOUND=1
SOUND_FADER1=0.500000
SOUND_FADER2=0.100000
SOUND_FADER3=0.300000
SOUND_FADER4=0.800000
SOUND_FADER5=0.500000
SOUND_FADER6=0.800000
SOUND_QUALITY=1
[DISPLAY.Device.NVIDIA GeForce 9800 GTX/9800 GTX+.0]
Mode=1680x1050x32
TriLinear=1
[DISPLAY]
UPPER_FRAMERATE_LIMIT=30
TEXTURE_BANDWIDTH_MULT=55
TextureMaxLoad=10
runway_lights_surface_scalar=0.9
runway_lights_vasi_scalar=0.5
runway_lights_approach_scalar=0.5
runway_lights_strobe_scalar=0.9
[TERRAIN]
TERRAIN_ERROR_FACTOR=50.000000
TERRAIN_MIN_DEM_AREA=10.000000
TERRAIN_MAX_DEM_AREA=100.000000
TERRAIN_MAX_VERTEX_LEVEL=19
TERRAIN_TEXTURE_SIZE_EXP=8
TERRAIN_AUTOGEN_DENSITY=4
TERRAIN_USE_GRADIENT_MAP=1
TERRAIN_EXTENDED_TEXTURES=1
TERRAIN_DEFAULT_RADIUS=3.500000
TERRAIN_EXTENDED_RADIUS=4.000000
TERRAIN_EXTENDED_LEVELS=232
[SCENERY]
IMAGE_COMPLEXITY=4
DYNAMIC_SCENERY=0
DYN_SCN_DENSITY=0
DAWN_DUSK_SMOOTHING=1
SUNGLARE=1
LENSFLARE=0
[AIRtoCONTAINER]
SIM1=Cessna Skylane 182R RG
SIM2=Learjet 45
SIM3=Schweizer 2-32 Sailplane
SIM4=Sopwith Camel
SIM5=Extra 300S
SIM6=Boeing 737-400
[APL]
CACHE_WAV_FILES=1
[TrafficManager]
TrafficDensity=0
IFROnly=0
EnableAirline=0
EnableGeneralAviation=0
[AContain]
ShowLabels=0
ShowUserLabel=0
ShowLabelManufacturer=0
ShowLabelModel=0
ShowLabelTailNumber=0
ShowLabelDistance=0
ShowLabelAltitude=0
ShowLabelAirline=0
ShowLabelAirlineAndFlightNumber=0
ShowLabelFlightPlan=0
ShowLabelContainerId=0
ShowLabelAirspeed=0
ShowLabelHeading=0
LabelDelay=1000
LabelColor=FFFFFFFF
[SLEW]
MaxLateralRate=40000.000000
MaxVerticalRate=1000.000000
MaxPitchRate=360.000000
MaxBankRate=360.000000
MaxHeadingRate=360.000000
[VirtualCopilot]
VirtualCopilotActive=0
[MAIN]
Location=-1604,22,-130,994
Maximized=1
HideMenuNormal=0
HideMenuFullscreen=1
[MULTIPLAYER]
ALWAYS_SHOW_INITIAL_DIALOG=1
SESSION_NAME=SquawkBox (valued-e37f3f8a)
PLAYER_NAME=ABX903
GUARANTEED_MESSAGES=0
MAX_PLAYERS=8
MAX_OBSERVERS=0
TICKS_PER_SYNC=90
PACKETS_PER_SEC=4
COLLISION_SECS=2
FOLLOWING_MULTIPLIER=5
ALLOW_PLANE_MODEL_SEND=0
ALLOW_PLANE_MODEL_RECEIVE=0
ALLOW_TEXTURE_SEND=0
ALLOW_TEXTURE_RECEIVE=0
MAX_SEGMENT_SIZE=100
MAX_SEGMENTS_PER_SEC=1
CONNECTION_TYPE=0
PROTOCOL_SELECTION=0
ALLOW_DESCRIPTIVE_SEND=1
ALLOW_DESCRIPTIVE_RECEIVE=1
AUTOPILOT_LOCK=0
DISTANCE_DISPLAY=0
ADF_TRACK=0
ALLOW_NAME_TAG_DISPLAY=1
CLIENT_CONNECT_USE_CUSTOM_PORT=0
CLIENT_CONNECT_PORT=23456
CLIENT_HOST_USE_CUSTOM_PORT=0
CLIENT_HOST_PORT=23456
HOST_CONNECT_USE_CUSTOM_PORT=0
HOST_CONNECT_PORT=23456
[SIM]
SYSCLOCK=1
[ATC]
AutoOpenAirTrafficWindow=0
UsePilotVoice=0
ShowATCText=0
PilotVoice=1
[FACILITIES]
COUNTRY=
STATE=
CITY=
GTL_BUTTON=6225
[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=0
SHOW_WEATHERSYSTEMS=0
SHOW_DATATAGS=1
SHOW_TERRAIN=1
show_flight_history=1
[DISPLAY.Device.NVIDIA GeForce 9800 GTX/9800 GTX+.1]
Mode=800x600x16
[KEYBOARD_MAIN]
SELECT_1=49,8
SELECT_2=50,8
SELECT_3=51,8
SELECT_4=52,8
MINUS=189,8
PLUS=187,8
ZOOM_1X=8,8
SOUND_TOGGLE=81,8
ENGINE=69,8
SIM_RATE=82,8
XPNDR=84,8
SLEW_TOGGLE=89,8
EGT=85,8
SMOKE_TOGGLE=73,8
STROBES_TOGGLE=79,8
PAUSE_TOGGLE=80,8
PAUSE_TOGGLE#1=19,8
ATC=192,8
ATC#1=145,8
ADF=65,8
VIEW_MODE=83,8
HEADING_GYRO_SET=68,8
DME=70,8
GEAR_TOGGLE=71,8
ANTI_ICE_TOGGLE=72,8
JET_STARTER=74,8
JOYSTICK_CALIBRATE=75,10
ALL_LIGHTS_TOGGLE=76,8
SITUATION_SAVE=186,8
VIEW_WINDOW_TO_FRONT=222,8
AP_MASTER=90,8
FREQUENCY_SWAP=88,8
COM_RADIO=67,8
VOR_OBS=86,8
BAROMETRIC=66,8
NAV_RADIO=78,8
MAGNETO=77,8
BRAKES=190,8
SPOILERS_TOGGLE=191,8
SITUATION_RESET=186,10
FLAPS_UP=116,8
THROTTLE_FULL=115,8
THROTTLE_INCR_SMALL=114,8
THROTTLE_DECR=113,8
FLAPS_DOWN=119,8
THROTTLE_CUT=112,8
VIEW=111,8
ELEV_TRIM_DN=36,8
ELEV_DOWN=38,8
INCREASE_THROTTLE=33,8
AILERONS_LEFT=37,8
CENTER_AILER_RUDDER=12,8
AILERONS_RIGHT=39,8
ELEV_TRIM_UP=35,8
ELEV_UP=40,8
DECREASE_THROTTLE=34,8
VIEW_FORWARD=38,41
VIEW_FORWARD_RIGHT=33,41
VIEW_RIGHT=39,41
VIEW_REAR_RIGHT=34,41
VIEW_REAR=40,41
VIEW_REAR_LEFT=35,41
VIEW_LEFT=37,41
VIEW_FORWARD_LEFT=36,41
VIEW_DOWN=12,41
RUDDER_LEFT=45,8
RUDDER_RIGHT=135,8
BRAKES_LEFT=122,8
BRAKES_RIGHT=123,8
AP_ATT_HOLD=84,10
AP_LOC_HOLD=79,10
AP_APR_HOLD=65,10
AP_HDG_HOLD=72,10
AP_ALT_HOLD=90,10
AP_WING_LEVELER=86,10
AP_BC_HOLD=66,10
AP_NAV1_HOLD=78,10
EXIT=67,10
ABORT=3,10
READOUTS_FLIGHT=90,9
PANEL_TOGGLE=219,9
VIEW_MODE_REV=83,9
PANEL_LIGHTS_TOGGLE=76,9
LANDING_LIGHTS_TOGGLE=76,10
PARKING_BRAKES=190,10
MINUS_SHIFT=189,9
PLUS_SHIFT=187,9
FLAPS_INCR=118,8
FLAPS_DECR=117,8
PROP_PITCH_LO=115,10
PROP_PITCH_INCR_SMALL=114,10
PROP_PITCH_DECR=113,10
PROP_PITCH_HI=112,10
MIXTURE_RICH=115,11
MIXTURE_INCR_SMALL=114,11
MIXTURE_DECR=113,11
MIXTURE_LEAN=112,11
SCRIPT_EVENT_1=219,10
SCRIPT_EVENT_2=221,10
YAW_DAMPER_TOGGLE=68,10
CENTER_NT361_CHECK=57,11
CLOSE_VIEW=221,8
NEW_VIEW=219,8
NEW_MAP=221,9
NEXT_VIEW=9,10
PREV_VIEW=9,11
VIEW_TYPE=83,10
VIEW_TYPE_REV=83,11
RADIO_VOR1_IDENT_TOGGLE=49,10
RADIO_VOR2_IDENT_TOGGLE=50,10
RADIO_DME1_IDENT_TOGGLE=52,10
RADIO_ADF_IDENT_TOGGLE=53,10
GEAR_PUMP=71,10
SPOILERS_ARM_TOGGLE=191,9
PITOT_HEAT_TOGGLE=72,9
AP_AIRSPEED_HOLD=82,10
AUTO_THROTTLE_ARM=82,9
AUTO_THROTTLE_TO_GA=71,11
LANDING_LIGHT_UP=38,11
LANDING_LIGHT_DOWN=40,11
LANDING_LIGHT_LEFT=37,11
LANDING_LIGHT_RIGHT=39,11
LANDING_LIGHT_HOME=12,11
PAN_RESET=46,9
KNEEBOARD_VIEW=121,8
MP_PLAYER_CYCLE=84,11
MP_PLAYER_SNAP=70,11
MP_GO_OBSERVER=79,11
MP_CHAT=221,11
MP_ACTIVATE_CHAT=13,8
PANEL_1=49,9
PANEL_2=50,9
PANEL_3=51,9
PANEL_4=52,9
PANEL_5=53,9
PANEL_6=54,9
PANEL_7=55,9
PANEL_8=56,9
PANEL_9=57,9
AP_MACH_HOLD=77,10
VIEW_FORWARD_UP=38,42
VIEW_FORWARD_RIGHT_UP=33,42
VIEW_REAR_RIGHT_UP=34,42
VIEW_REAR_UP=40,42
VIEW_REAR_LEFT_UP=35,42
VIEW_FORWARD_LEFT_UP=36,42
VIEW_UP=12,42
INVOKE_HELP=191,10
INVOKE_HELP#1=191,11
TOGGLE_AIRCRAFT_LABELS=76,11
ENGINE_AUTO_START=69,10
INC_COWL_FLAPS=86,11
DEC_COWL_FLAPS=67,11
USER_INTERRUPT=27,8
AILERON_TRIM_LEFT=37,10
AILERON_TRIM_RIGHT=39,10
RUDDER_TRIM_LEFT=45,10
RUDDER_TRIM_RIGHT=135,10
TOGGLE_FLIGHT_DIRECTOR=70,10
TOGGLE_AFTERBURNER=115,9
TOGGLE_MASTER_BATTERY_ALTERNATOR=77,9
TOGGLE_AIRCRAFT_EXIT=69,9
PANEL_HUD_TOGGLE=87,8
SNAP_TO_PANEL=45,41
MARKER_SOUND_TOGGLE=51,10
TOGGLE_WATER_RUDDER=87,9
TOGGLE_PUSHBACK=80,9
KEY_CHASE_VIEW_NEXT=87,10
KEY_CHASE_VIEW_PREV=87,11
HEADING_BUG_SELECT=72,11
ALTITUDE_BUG_SELECT=90,11
CHASE_VIEW_TOGGLE=81,10
EYEPOINT_UP=13,9
EYEPOINT_DOWN=8,9
EYEPOINT_RIGHT=13,11
EYEPOINT_LEFT=8,11
EYEPOINT_FORWARD=8,10
EYEPOINT_BACK=13,10
EYEPOINT_RESET=32,8
AIRSPEED_BUG_SELECT=82,11
TOGGLE_TAILWHEEL_LOCK=71,9
ROTOR_BRAKE=66,9
ROTOR_CLUTCH_SWITCH_TOGGLE=190,9
ROTOR_GOV_SWITCH_TOGGLE=188,9
VIRTUAL_COPILOT_TOGGLE=88,11
VIRTUAL_COPILOT_ACTION=88,10
[KEYBOARD_SLEW]
SLEW_TOGGLE=89,8
SLEW_ALTIT_UP_FAST=115,8
SLEW_ALTIT_UP_SLOW=114,8
SLEW_ALTIT_FREEZE=113,8
SLEW_ALTIT_DN_FAST=112,8
SLEW_ALTIT_PLUS=81,8
SLEW_ALTIT_MINUS=65,8
SLEW_PITCH_DN_FAST=119,8
SLEW_PITCH_DN_SLOW=118,8
SLEW_PITCH_FREEZE=117,8
SLEW_PITCH_UP_FAST=116,8
SLEW_PITCH_PLUS=57,8
SLEW_PITCH_MINUS=48,8
READOUTS_SLEW=90,9
SLEW_BANK_MINUS=36,8
SLEW_AHEAD_PLUS=38,8
SLEW_BANK_PLUS=33,8
SLEW_LEFT=37,8
SLEW_FREEZE=12,8
SLEW_RIGHT=39,8
SLEW_HEADING_MINUS=35,8
SLEW_AHEAD_MINUS=40,8
SLEW_HEADING_PLUS=34,8
SLEW_RESET=32,8
TOGGLE_AIRCRAFT_LABELS=76,11
EYEPOINT_UP=13,9
EYEPOINT_DOWN=8,9
EYEPOINT_RIGHT=13,11
EYEPOINT_LEFT=8,11
EYEPOINT_FORWARD=8,10
EYEPOINT_BACK=13,10


http://img.techpowerup.org/121006/nvidia_20121006_232612.png
Settings 1(2)

http://img.techpowerup.org/121006/nvidia_20121006_232657.png
Settings 2(2)
« Last Edit: October 08, 2012, 12:21:17 pm by virtuali »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50691
    • VIRTUALI Sagl
Re: FS2004 Default Terminal 2/3 .bgl
« Reply #23 on: October 07, 2012, 12:30:51 pm »
Alright I'm literally driving myself nuts...... I need to get the FPS up in these few areas with the LDS767 panel.

I'm sorry but, you said yourself in your last message, the fps went up, the only problem was image tearing. If the fps is high with a default airplane, is not a problem of the scenery.

gmcg

  • Jr. Member
  • **
  • Posts: 71
Re: FS2004 Default Terminal 2/3 .bgl
« Reply #24 on: October 07, 2012, 03:20:35 pm »
My computer should be able to handle this no issues; the FPS hold was really only 28 locked at 30 in the "Us" of terminal 2/3. I will not accept that answer, sir, about no issue with the scenery with default aircraft. Who cares about default aircraft  :o

Is there any Nvidia settings I could try? I'm not that big into things looking nice so long as the sim is smooth. Please give me more insight then the default aircraft junk! There should be no reason that I can't get the same performance @ ORD like I do at HNL  :-\

Not trying to be rude but lets work this out  8)
« Last Edit: October 07, 2012, 03:43:53 pm by gmcg »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50691
    • VIRTUALI Sagl
Re: FS2004 Default Terminal 2/3 .bgl
« Reply #25 on: October 07, 2012, 05:15:48 pm »
There should be no reason that I can't get the same performance @ ORD like I do at HNL  :-\

KORD is surely not slower than PHNL. You said yourself the problem was fixed and the only remaining problem was image tearing. Image tearing is lack of vsync ( in the video card NOT in FS9!!! ), and it's nothing related to the scenery.

gmcg

  • Jr. Member
  • **
  • Posts: 71
Re: FS2004 Default Terminal 2/3 .bgl
« Reply #26 on: October 07, 2012, 11:00:31 pm »
You're not reading what I'm writing. The problem is NOT fixed. The FPS drop is still there. Vsync helped with the tearing. So two SEPARATE issues.

KORD is surely not slower than PHNL.
Why do you keep beating around the bush? I've tested and tested and tested. I get 35+ FPS per second in the most complex of areas at PHNL yet struggle to 25 FPS in the complex areas of KORD. Stop saying stuff like this; it isn't helping and its basically calling a customer a liar in the process.
« Last Edit: October 07, 2012, 11:44:40 pm by gmcg »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50691
    • VIRTUALI Sagl
Re: FS2004 Default Terminal 2/3 .bgl
« Reply #27 on: October 08, 2012, 12:19:25 pm »
You're not reading what I'm writing
.

I obviously have, and the only meaningful thing you wrote, was the problem WAS fixed at SOME POINT. It doesn't really matter, at all, if you say it's not fixed NOW, but this clearly proves the scenery wasn't the problem to begin with.

Quote
The FPS drop is still there. Vsync helped with the tearing. So two SEPARATE issues.

That exactly what I've said, they are entirely different issues and, none of them caused by the scenery, because you HAD the "low fps" problem fixed at some point, and the tearing it's obviously a video card problem.

Quote
Stop saying stuff like this; it isn't helping and its basically calling a customer a liar in the process.

You are obviously wrong: nobody called you "a liar", I BELIEVE you have a lows fps problem but, you are wrong keep saying you pretend it has to be high using the Level-D airplane, because the only way to test if a low fps problem is *caused* by the scenery, it's obviously with a default airplane.

Once you have proof the scenery works well with a default airplane, it will then be your choice using it with a complex airplane, but you can't blame the scenery if half of your frame rate is already eaten by the airplane, you just can't expect the scenery would magically *increase* the frame rate of a complex airplane.

In any case, the real issue is that you are using FS9, which has the problem of not scaling well with better hardware and, at a certain point, you'll have diminishing returns on hardware increases, since FS9 doesn't support better CPU (no multicore) and better videocards (not much shaders usage).

FS9 users usually think they are better served putting fast PCs with FS9, but it doesn't work like that: FS9 is much better than FSX on a single or dual-core with an average video card but, when you start adding CPU cores and faster cards, FS9 will not use them (FS9 only gets better with more mhz, but cpu clocks haven't increased in the last years, only the number of cores has), while FSX can use multicore better and CAN use modern video cards that run shaders faster so, at a certain point, FSX becomes faster than FS9 AND it tolerates load much better.

And just to prove it, have a look at the following screenshots in FS9 and FSX


gmcg

  • Jr. Member
  • **
  • Posts: 71
Re: FS2004 Default Terminal 2/3 .bgl
« Reply #28 on: October 08, 2012, 04:13:19 pm »
It was never fixed.... By fixed I meant maybe 28 locked at 30. Again, based on my Nvidia settings, do you see anything I can try differently. That is all I'm asking.

I'm sorry if I sound weird or anything but there has to be a fix out there.

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50691
    • VIRTUALI Sagl
Re: FS2004 Default Terminal 2/3 .bgl
« Reply #29 on: October 08, 2012, 05:16:07 pm »
It was never fixed.... By fixed I meant maybe 28 locked at 30. Again, based on my Nvidia settings, do you see anything I can try differently. That is all I'm asking.

This sentence is not clear: are you saying that you reached 28-30 fps at some stage ? That's a very usable frame rate. And, it would be best if you unlock the frame rate.