Русский New site

Advanced search

[ New messages · Forum rules · Members ]
Page 12 of 13«1210111213»
Forum » SpaceEngine » Archive » Troubleshooting SpaceEngine 0.94 (FROM CATEGORY "TROUBLESHOOTING AND SOLUTIONS")
Troubleshooting SpaceEngine 0.94
SpaceEngineerDate: Thursday, 17.11.2011, 03:03 | Message # 166
Author of Space Engine
Group: Administrators
Russian Federation
Messages: 4796
Status: Offline
Wow, posting this amount of images is a bad idea. I have a limit of only 500Mb for the site on the server, so I must remove old pictures soon.

Please do not do this again in the future smile

About the bug - it looks like incorrect working of memory manager. It even calculates star node size as negative value...

*





 
SekseDate: Thursday, 17.11.2011, 03:03 | Message # 167
Observer
Group: Newbies
United States
Messages: 5
Status: Offline
2 Things about this error. 1: If you are getting it, turn down the landscape LOD, a LOD of 0 produces great looking planetary terrain still, but won't crash.

2: For a developer suggestion, it seems the problem is in the LOD system. I noticed a few things that may be a factor:
1 - the program still seems to be trying to load textures and generate meshes for position x after I have moved to position Y
2 - the program seems to be keeping the meshes and textures in memory rather than dumping them to make room for more
3 - the program seems to render high detail terrain all over the place when the landscape LOD is set too high, so I am stuck watching the rest of the world start looking good in the distance while the section closest to me still looks low quality, leaving me waiting for 15 minutes before it gets finished (again with LOD set to max). With LOD set to 0 everything works great, I get a runtime crash every so often but nothing else really. No Out Of Memory crashes or anything.

As for PC specs, I am running an Alienware laptop with dual core CPU, 8GB RAM and a 1GB Nvidia GFX card (And maxed out LOD still slows me to 9 FPS lol)
 
SpaceEngineerDate: Thursday, 17.11.2011, 03:03 | Message # 168
Author of Space Engine
Group: Administrators
Russian Federation
Messages: 4796
Status: Offline
About the black screen start-up bug:

Try to disable HDR mode: Open 'user.cfg' and set EnableHDR to false.

*





 
NeonDate: Thursday, 17.11.2011, 03:03 | Message # 169
Explorer
Group: SE team
Australia
Messages: 205
Status: Offline
The way it works, is say the first 2 images, and the last 2, sometimes it will fix within
a few minutes, other times, it won't get fixed. This appears when you first go to the
selected object.

I will create a completely different installation in a new folder,
and see if that fixes anything. Will let you know.

Ok, I just did a test and I think I may have found the problem with the
textures, and why you don't show the problem. I think it's because of how
it's installed. Vers 93 had a SE folder in the archive, 94 doesn't. I think
people have been either overwriting vers .93 with .94, or not deleting
.93. This is what I did originally. I just tested 0.94 it using a completely different
folder and it worked fine, though theres still something wrong with the fullscreen
option. It gives the black screen bug.

I'll post the fix in the troubleshooting forum.

*
 
NeonDate: Thursday, 17.11.2011, 03:03 | Message # 170
Explorer
Group: SE team
Australia
Messages: 205
Status: Offline
I also get load times like this on the surface if Landscape LOD is set to full. I usually
have it on 0, but I still have to wait for it to load for about 10 seconds. Sometimes
I get beautiful topography, other times I get virtually no topography, or minimal.

It would be nice to have a topographical map to find interesting spots eventually.
Maybe a cockpit display for later.

So far no crashes on Landscape LOD set to max, tho I'm only just testing that. Framerate
drops to 6-9, and takes a long time to load, comparable to what Sekse said.
 
SpaceEngineerDate: Thursday, 17.11.2011, 03:03 | Message # 171
Author of Space Engine
Group: Administrators
Russian Federation
Messages: 4796
Status: Offline
I realize that I must make SE automatically delete cache folder when the new version runs for the first time. This will fix a lot of bugs that people are having. Installing new version will overwrite old and not delete the cache folder.

*





 
GabrielDate: Thursday, 17.11.2011, 03:03 | Message # 172
Space Tourist
Group: Users
Australia
Messages: 20
Status: Offline
Yeah sorry about those images haha, they're hosted off-site though so don't worry. If you need any more information about the memory bug please ask, I'll discuss the black screen bug further in Neon's thread because the images I posted are annoying :P
 
SpaceEngineerDate: Thursday, 17.11.2011, 03:03 | Message # 173
Author of Space Engine
Group: Administrators
Russian Federation
Messages: 4796
Status: Offline
Quote (Sekse)
2 Thing about this error, 1: If you are getting it, turn down the landscape LOD, a LOD of 0 produces great looking planetary terrain still, but won't crash.


Set LOD to minimum (-3), and there no OUT OF MEMORY smile Do not set it to maximium (+3), because even 1Gb of VRAM is not enough to load full landscape with full LOD on procedural planets. LOD +3 works fine on Earth and other real planets, because there are a maximum of 7 levels of texture, but on procedural planets it is up to 13.

Quote (Sekse)
1 - the program still seems to be trying to load textures and generate meshes for position x after I have moved to position Y


Right, loader queue is filled with requests from your old position, and the loader won't start to generate textures and patches from your new position until it generates all of it in the queue.

Quote (Sekse)
2 - the program seems to be keeping the meshes and textures in memory rather than dumping them to make room for more


Right, program caches all generated data. This is not a bug. You can land on surface, then rotate around until all textures and meshes are generated, and then loader queue will be empty and all will render smoothly. You can 'walk' slowly and have no data load at all, because it's all already cached. You can fly away and then come back, and cached data is still loaded there. If data get deleted immediately then landscape node leaves view field, then the loading process never stops. A similar system is used for procedural stars. So when you stop moving and rotate yourself around, all visible stars are generated and you can fly away smoothly at slow speed (i.e. at a planetary system), with no new stars generated.

Quote (Sekse)
3 - the program seems to render high detail terrain all over the place when the landscape LOD is set too high, so I am stuck watching the rest of the world start looking good in the distance while the section closest to me still looks low quality, leaving me waiting for 15 minutes before it gets finished (again with LOD set to max).


Yes, this is because for high LOD the so-called "LOD metric value" is equivalent for all distances - SE tries to create per-pixel detail geometry. For low LOD (lower than 0) the LOD metric is depend on distance - for nearest parts it is per-pixel, for far away parts it is lower (so distant mountains can have terrible low details, but this saves memory and loading time).

*





 
NeonDate: Thursday, 17.11.2011, 03:03 | Message # 174
Explorer
Group: SE team
Australia
Messages: 205
Status: Offline
Yeh I'm sure eventually you'll probably make an install program for it,
but it's really not necessary at the moment. Once people get the idea
of deleting the cache it shouldn't cause too many more problems. Mine
is working fine now. Except I can't have full screen.... I can live with that
for awhile.

btw I love some of the places in the places.cfg, only just discovered that lol.

*
 
NeonDate: Thursday, 17.11.2011, 03:03 | Message # 175
Explorer
Group: SE team
Australia
Messages: 205
Status: Offline
Thanks, that'd help alot. smile

Keep discussing it here, cause yours seem to be a different problem
to the fix I mentioned. You did try it right? I might delete the
images though because they make it very difficult to read
the entire thread.

I'll just delete the images, repost them here if you resize them
to keep within one screen width. wink lol
 
GabrielDate: Thursday, 17.11.2011, 03:03 | Message # 176
Space Tourist
Group: Users
Australia
Messages: 20
Status: Offline
Ah sure. If any of them are needed for troubleshooting let me know and I'll resize and repost them. I've reduced my settings down to 0 from max (+3) and the texture issue seems to still be happening. SpaceEngineer said maybe it's an issue with the memory manager?

It's not too serious because it only occurs when I fly right down to a planet and let it cache textures until they're good quality. If I just fly around and don't spend too much time looking at detailed mountain ranges and things like that on planets it doesn't happen. So at least I can still play smile
It's a shame though because that's one of the coolest things about Space Engine sad

If this is an issue with the memory manager, maybe it's related to the GL_OUT_OF_MEMORY crash reported in another thread...? I think I should just wait until a newer version with that issue fixed as maybe it'll fix this too.


Edited by Gabriel - Monday, 13.06.2011, 10:35
 
SpaceEngineerDate: Thursday, 17.11.2011, 03:03 | Message # 177
Author of Space Engine
Group: Administrators
Russian Federation
Messages: 4796
Status: Offline
Gabriel, oh, you are getting this bug while using +3 LOD? Try to use -3 LOD (minimum detail).

BTW, if you upload images directly to forum, they must be re-sized to fit within predefined width.

*





 
NeonDate: Thursday, 17.11.2011, 03:04 | Message # 178
Explorer
Group: SE team
Australia
Messages: 205
Status: Offline
You did delete the cache when you installed the new version right?
 
SpaceEngineerDate: Thursday, 17.11.2011, 03:04 | Message # 179
Author of Space Engine
Group: Administrators
Russian Federation
Messages: 4796
Status: Offline
Cache does not affect that. The Cache folder is where generated shaders of planets are saved. Not deleting cache before new installation, will cause visual artifacts on planets, rings and atmospheres, but not on 'blinking' landscapes, out of memory, or black screen.

*





 
GabrielDate: Thursday, 17.11.2011, 03:04 | Message # 180
Space Tourist
Group: Users
Australia
Messages: 20
Status: Offline
I just tried on -3 detail. The issue does not happen at all when I am in fullscreen on -3 detail. At all other settings, it happens more frequently the higher the detail and the more I fly around on the surface of a planet.
Here is a screenshot of it happening when set to -1 detail (resized haha). Before this the planet was displaying fine. It doesn't happen frequently on -1 though, it took me a bit of flying around before this happened.
As an aside - you should check out that planet, HD 100335 2. Looks a bit like home! Edit - attached a screenshot of the planet displaying okay just so you can take a look, I like it! Nice view of the binary sun too - a good place for a holiday maybe smile

Attachments: 1159700.jpg(66Kb) · 0646539.jpg(76Kb)


Edited by Gabriel - Tuesday, 14.06.2011, 05:55
 
Forum » SpaceEngine » Archive » Troubleshooting SpaceEngine 0.94 (FROM CATEGORY "TROUBLESHOOTING AND SOLUTIONS")
Page 12 of 13«1210111213»
Search: