| Zeus0moose | Date: Friday, 26.08.2011, 07:44 | Message # 1 |
 Observer
Group: Users
United States
Messages: 10
Status: Offline
| I'll put the edits that I know for sure work first
Main.cfg edits
A good way to reduce framerate issues is to lower the resolution. I recommend windowing it to keep it looking nice.
Reduce or get rid of anisotropic filtering, 0 is none, 16 is the highest I believe
Go to the planetdetail<sun/gasgiant/terra> section. Lower these significantly. I've lowered some to many, many zeroes before the first one shows up, and the Planets still look decent.
I know these ones work. However, there are a couple that I'm not sure of, but seem to have helped.
Maximpostors lowered, 2-4 at lowest. No ill effects that I've seen, might have helped.
If you ever turned on Reverse Planet loading, turn it off. I'm not sure, but it may cause textures to load, the de-load, then load again. This obviously can cause longer load times. Once I turned this off it seemed to fix this.
Do NOT lower the TRimpresolution, if you do this, I've noticed that looking at galaxies edge on becomes a blurry mess, put it even lower and Framebuffer objects stop working.
This has definitely worked for me, as I have WAY less than 512 VRAM but I am currently getting over 100 FPS everywhere but on or near planets with atmospheres, and even then it will be more than playable unless I visit a planet with an exceptionally dense atmosphere.
And just a side tip, if loading is getting annoying while trying to position yourself on a planet, go to the place you want to take the picture from and turn until you've come around 360 degrees and loaded all the textures and meshes. Now you can move the camera within this area without excessive load times.
Also, I recommend making a backup of the configs before editing if you don't think you'll remember the original values.
Edited to get rid of CubemeshLOD edits and gave a better impostor value.
"Somewhere, something incredible is waiting to be known." ~ Carl Sagan
Edited by Zeus0moose - Friday, 26.08.2011, 16:07 |
| |
| |
| SpaceEngineer | Date: Friday, 26.08.2011, 10:09 | Message # 2 |
 Author of Space Engine
Group: Administrators
Russian Federation
Messages: 4800
Status: Offline
| No, do not change CubeMeshLOD and SphereMeshLOD! It may break landscape subdivision algorithm. You can change planet detail, but do not change it!
Do not turm MaxImpostors to zero. Impostors are used to render galaxies and nebulae that are mid distance from camera. If you turn it to zero, they become too laggy. Have at least 2-4 impostors.
To improve general framereate, it is better to reduce star magnitude. Or even disable procedural stars (and the procedural planets). In F4 menu uncheck Stars-Procedural and Planets-Procedural, but leave Planets-Procedural_on_catalog_stars. This allows you to fly around with the catalog stars in Milky Way and also visit its procedural planets, this will preserve a lot of memory that procedural stars use.
To improve framerate on the planets, disable eclipse shadows and multiple lighting (planet shine). The last is great for planets with atmospheres. And of course, reduce planet LOD to -3. This gives a blurry landscape, but improves generation time.
*
|
| |
| |
| Zeus0moose | Date: Friday, 26.08.2011, 16:09 | Message # 3 |
|
Observer
Group: Users
United States
Messages: 10
Status: Offline
| Okay, edited the main post to take out CubemeshLOD and recommended 2 impostors at the lowest. Thanks for the info!
"Somewhere, something incredible is waiting to be known." ~ Carl Sagan
|
| |
| |
ENG
New site
United States 
Russian Federation