Hardware Very low FPS

Wolf · Dec 24, 2009

Just installed Orbiter on a new PC but I get an avarage of 10fps (sometimes down to 5-6!).

System specs:

Intel Core i7
RAM 8G DDR3
NVIDIAb GeForce GT220 (1GB)
Windows 7

Monitor LCD 22" HD
Screen res 1680x1050x32

Setting lower screen res doesn't solve the problem

Any help?

Ok, it sems that changing res to 1600x1024 improves things: FPS is now between 20 and 35. Isn't it still quite poor compared to the system specs? is there any seting in the screen/grapphic card or Orbiter I should change to get max performance?

Woo482 · Dec 24, 2009

check you have the latest Drivers installed for your Graphics card, and if you haven't done so already try installing "VistaBoost 1.0" that can improve frames a lot on Vista / Windows 7

TSPenguin · Dec 24, 2009

In the video tab check "Always enumerate Devices" and then select the last entry in the list above. And use vistaboost as suggested above.

klink · Dec 24, 2009

why you bought a intel core 7 and only a low end video card and why you have 8gb Ram on a triple channel CPU?

Urwumpe · Dec 24, 2009

klink said:
why you bought a intel core 7 and only a low end video card and why you have 8gb Ram on a triple channel CPU?

Because he can.

Also a GT220 is hardly low end. While on the lower scale of the 200 series, it is of the latest NVidia chip generation.

dbeachy1 · Dec 24, 2009

TSPenguin said:
In the video tab check "Always enumerate Devices" and then select the last entry in the list above. And use vistaboost as suggested above.

To elaborate, be sure to choose a 3D device mode in the Launchpad that specifies "T&L HAL". As TSP said, that should be present as the last entry in the "3D Device" drop-down.

Wolf · Dec 30, 2009

Thanks for the tips guys, I have downloaded the latest INVIDIA drivers, vistaboost is enabled, and I have selected "Direct3D T&L and HAL": unfortunately I still have an average of 20 fps which I think is well below an acceptable FPS considering my system specs..
???

RisingFury · Dec 30, 2009

Well, Heilor posted a nice thread on the forum as to why the performance on Vista / Win7 is so bad. Look around, use the search button.

Also, make sure VistaBoost is enabled in the Modules tab, otherwise it's no good.

---------- Post added at 01:52 AM ---------- Previous post was at 01:44 AM ----------

Well, my mom's work computer... some slow dual core and integrated graphics chip is capable of 40 - 50 FPS on Vista in windowed 1280 x 960 Direct3D HAL mode, so you're probably doing something wrong...

TSPenguin · Dec 30, 2009

Could you post the orbiter.log after running a simulation?
Maybe we spot something in there.

Wolf · Dec 30, 2009

This what I have after a KSC landing simulation using ShuttleFleet with avarage FPS 20-25

**** Orbiter.log
Build Sep 29 2006 [v.060929]
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (NVIDIA GeForce GT 220)
==> Direct3D T&L HAL (NVIDIA GeForce GT 220)
Found 1 joystick(s)
Module AtlantisConfig.dll [API v.060425]
Module DGConfig.dll [API v.060425]
Module OrbiterSound.dll [API v.060425]
Module TrackIR.dll [API v.060425]
TrackIR module not found.
Module ScnEditor.dll [API v.060425]
Module Rcontrol.dll [API v.050206]
Module Meshdebug.dll [API v.060425]
Module Framerate.dll [API v.050206]
Module FlightData.dll [API v.050206]
Module ExtMFD.dll [API v.060425]
Module CustomMFD.dll [API v.060425]
Module GPCMFD.dll [API v.060425]
Module UniversalPointing.dll [API v.060425]
Module CamShake.dll [API v.050206]
Module AutoFCS.dll [API v.050206]
Module AttitudeMFD.dll [API v.060425]
Module RendezvousMFD.dll [API v.050206]
Module REDSHIFT.dll [API v.041022]
Module Attachment Manager.dll [API v.060425]
Module VistaBoost.dll [API v.060425]
VistaBoost 1.0: Font smoothing disabled to improve framerate; smoothing will be re-enabled when Orbiter shuts down.
VistaBoost 1.0: font smoothing re-enabled.

TSPenguin · Dec 30, 2009

That is what you have when you start the launchpad.
Try running the sim in windowed mode and copy the log while orbiter is running.
And please put the contents within [code]stuff goes here...[/code].

n72.75 · Dec 30, 2009

Make sure the video device is not set to RGB emulation.

Wolf · Dec 30, 2009

log.file saved running the scenario:

Code:

; === ORBITER Master Configuration File ===
; === Subdirectory locations
ConfigDir = .\Config\
MeshDir = .\Meshes\
TextureDir = .\Textures\
HightexDir = .\Textures2\
ScenarioDir = .\Scenarios\
; === Logical parameters ===
FlightModel = 1
DamageModel = 0
UnlimitedFuel = FALSE
InstrumentUpdateInterval = 1
GenericMFDSize = 6
PanelScale = 1
PanelScrollSpeed = 300
NumStar = 3000
FocusFollowsMouse = TRUE
StartPaused = FALSE
; === Physics engine ===
DistributedVesselMass = FALSE
NonsphericalGravitySources = FALSE
StabiliseOrbits = TRUE
StabilisePLimit = 0.05
StabiliseSLimit = 0.01
LinPropStages = 4
LinPropStage0 = 2 0.5
LinPropStage1 = 4 20
LinPropStage2 = 6 100
LinPropStage3 = 8
AngPropStages = 4
AngPropStage0 = 2 1 0.0174533
AngPropStage1 = 4 10 0.0698132
AngPropStage2 = 6 100 0.174533
AngPropStage3 = 8
AngPropSubsampling = 100 0.349066
AngPropLimits = 0.523599 62.8319
; === Visual parameters ===
AmbientLevel = 12
EnableShadows = TRUE
EnableVesselShadows = TRUE
EnableClouds = TRUE
EnableCloudShadows = FALSE
EnableNightlights = TRUE
EnableWaterReflection = TRUE
EnableSpecularRipples = FALSE
EnableHorizonHaze = TRUE
EnableSpecularReflection = TRUE
EnableReentryFlames = TRUE
EnableParticleStreams = TRUE
MFDTransparent = FALSE
PlanetMaxPatchLevel = 10
PlanetPatchRes = 1
PlanetHipatchAperture = 0.1
StarBrightness = 1
StarContrast = 1
NightlightBrightness = 0.7
Planetarium = 4330
Bodyforces = 60 1 1
CoordinateAxes = 4 1 1
; === Camera parameters ===
CameraPanspeed = 100
; === Joystick parameters ===
JoystickIndex = 1
JoystickThrottleAxis = 1
JoystickThrottleSaturation = 9500
JoystickDeadzone = 2500
IgnoreThrottleOnStart = TRUE
; === Demo parameters ===
DemoMode = FALSE
BackgroundImage = FALSE
BlockExit = FALSE
MaxDemoTime = 300
MaxLaunchpadIdleTime = 15
; === Record/play parameters ===
RecordTimewarp = TRUE
ReplayTimewarp = TRUE
SystimeSampling = TRUE
PlaybackNotes = TRUE
; === Font parameters ===
DialogFont_Scale = 1
DialogFont1_Face = Arial
; === Device settings ===
DeviceForceEnum = FALSE
DeviceIndex = 2 ; do not edit manually
ModeIndex = 27 ; do not edit manually
Fullscreen = TRUE
Stereo = FALSE
NoVSync = FALSE
StencilBuffer = FALSE
WindowWidth = 640
WindowHeight = 480
; === Multiplayer parameters ===
; === Active plugin list ===
ACTIVE_MODULES
  OrbiterSound
  transx
  TrackIR
  ScnEditor
  Rcontrol
  Meshdebug
  Framerate
  FlightData
  ExtMFD
  CustomMFD
  GPCMFD
END_MODULES

TSPenguin · Dec 30, 2009

That is not the log file... That is Orbiter.cfg

Wolf · Dec 30, 2009

ooops... sorry. there you go: btw, what is the error messege referred to?... maybe something's missing?...

Code:

**** Orbiter.log
Build Sep 29 2006 [v.060929]
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (NVIDIA GeForce GT 220)
==> Direct3D T&L HAL (NVIDIA GeForce GT 220)
Found 1 joystick(s)
Module AtlantisConfig.dll [API v.060425]
Module DGConfig.dll [API v.060425]
Module OrbiterSound.dll [API v.060425]
Module TrackIR.dll [API v.060425]
TrackIR module not found.
Module ScnEditor.dll [API v.060425]
Module Rcontrol.dll [API v.050206]
Module Meshdebug.dll [API v.060425]
Module Framerate.dll [API v.050206]
Module FlightData.dll [API v.050206]
Module ExtMFD.dll [API v.060425]
Module CustomMFD.dll [API v.060425]
Module GPCMFD.dll [API v.060425]
Module UniversalPointing.dll [API v.060425]
Module CamShake.dll [API v.050206]
Module AutoFCS.dll [API v.050206]
Module AttitudeMFD.dll [API v.060425]
Module RendezvousMFD.dll [API v.050206]
Module REDSHIFT.dll [API v.041022]
Module Attachment Manager.dll [API v.060425]
Module VistaBoost.dll [API v.060425]
VistaBoost 1.0: Font smoothing disabled to improve framerate; smoothing will be re-enabled when Orbiter shuts down.
**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Zbuffer: 32 bit
Render device: Window 1674 x 1022
Device has hardware T&L capability
Joystick throttle: Z-AXIS
No joystick throttle control detected
ERROR: DInput error DIERR_OBJECTNOTFOUND
       [C:\Source\Orbiter\Orbiter.cpp / 1624]
Module Sun.dll [API v.050206]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Earth.dll [API v.050206]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll [API v.041022]
ELP82: Precision 1e-005, Terms 116/829
Finished initialising world
Module Zarya.dll [API v.060425]
Module Shuttle.dll [API v.060425]
Module STSBAY.dll [API v.060425]
Module Unity.dll [API v.060425]
Module APFR.dll [API v.060425]
Module LC39.dll [API v.060425]
Module RL.dll [API v.060425]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state

orb · Dec 30, 2009

TSPenguin said:
That is not the log file... That is Orbiter.cfg

Well. Yes, but already tells something:

Code:

DeviceForceEnum = FALSE

"Always enumerate Devices" is unchecked.

Code:

DeviceIndex = 2 ; do not edit manually

"Direct3D T&L HAL" is selected. It would be set to 4 for "Direct3D T&L HAL (NVIDIA GeForce GT 220)"

Wolf said:
btw, what is the error messege referred to?... maybe something's missing?...

Try to run simulation with disabled joystick, and see if this error persists.

Wolf · Dec 30, 2009

orb said:
Well. Yes, but already tells something:

Code:

DeviceForceEnum = FALSE

"Always enumerate Devices" is unchecked.

Code:

DeviceIndex = 2 ; do not edit manually

"Direct3D T&L HAL" is selected. It would be set to 4 for "Direct3D T&L HAL (NVIDIA GeForce GT 220)"

this is very strange! I double checked twice before running the scenario that both "Always enumerate devices" and "Direct3D T&L HAL (NVIDIA GeForce GT220)" were actually checked (selected) in the video settings menu.
so why the logfile is not matching that....?

orb · Dec 30, 2009

Wolf said:
this is very strange! I double checked twice before running the scenario that both "Always enumerate devices" and "Direct3D T&L HAL (NVIDIA GeForce GT220)" were actually checked (selected) in the video settings menu.
so why the logfile is not matching that....?

If you "installed" Orbiter in Program Files then the actual config file could have been saved in your profile directory in "%USERPROFILE%\AppData\Local\VirtualStore\Program Files" or "Program Files (x86)".

Is it 64-bit version of Windows? In this thread VistaBoost didn't help much with improvement of performance in 64-bit Vista for Andy44.

Wolf · Dec 30, 2009

orb said:
If you "installed" Orbiter in Program Files then the actual config file could have been saved in your profile directory in "%USERPROFILE%\AppData\Local\VirtualStore\Program Files" or "Program Files (x86)"

I checked that out and like you said the actual config file gives me different video settings (3D device selected shows 2 instead of 4 and the "Always enumarate device" shows unchecked instead of checked) How can I fix this discrepancy?..

Is it 64-bit version of Windows? In this thread VistaBoost didn't help much with improvement of performance in 64-bit Vista for Andy44.

Yeap, it is a Win7 64-bit version.

Hielor · Dec 30, 2009

Wolf said:
I checked that out and like you said the actual config file gives me different video settings (3D device selected shows 2 instead of 4 and the "Always enumarate device" shows unchecked instead of checked) How can I fix this discrepancy?..

Yeap, it is a Win7 64-bit version.

Install Orbiter to somewhere other than Program Files (I use C:\Games, so C:\Games\Orbiter 2006), or disable UAC.

Orbiter 2024 has been released!

Hardware Very low FPS

Donator

Moderator

The Seeker

New member

Not funny anymore

O-F Administrator

Donator

OBSP developer

The Seeker

Donator

The Seeker

Seize the means of computation

Donator

The Seeker

Donator

New member

Donator

New member

Donator

Defender of Truth

Similar threads