Oolite Bulletins

For information and discussion about Oolite.
It is currently Tue Aug 21, 2018 12:46 pm

All times are UTC




Post new topic  Reply to topic  [ 13 posts ] 
Author Message
PostPosted: Thu Oct 05, 2017 9:31 pm 
Offline
Competent
Competent

Joined: Thu Oct 29, 2015 9:41 pm
Posts: 37
oolite might need more ram and gc overhead memroy since it still crashing i now have a very powerfuel computer that can take full advancge of oolites potenal i have installed alot a oxz and have the max detail set and it runs at 50-60 fps but almost every time the garabige collector runs the game crashs and i got LIKE 8GBs of ram and the game don't even use like 5% of it oolite needs a ram and gc overhead incrase to run properly on mid to high end hardware that even a small smart phone has at least 3-4 GBs of ram these days


Top
   
PostPosted: Thu Oct 05, 2017 9:34 pm 
Online
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral

Joined: Wed Feb 28, 2007 7:54 am
Posts: 5207
Right, can you please post a log after one of those crashes?


Top
   
PostPosted: Thu Oct 05, 2017 10:20 pm 
Offline
Competent
Competent

Joined: Thu Oct 29, 2015 9:41 pm
Posts: 37
the log dosen't record when the game GC run out of ram to use the log don't work


Top
   
PostPosted: Thu Oct 05, 2017 10:20 pm 
Offline
Competent
Competent

Joined: Thu Oct 29, 2015 9:41 pm
Posts: 37
the log just gets cut off becuse the computer just kills the game to fast becuse 500 MBs don't work if my computer HDD and ram just smashes the games poor code to death trying not crush it like an ant made out of dust


Top
   
 Post subject: Re: OXP Performance tips
PostPosted: Thu Oct 05, 2017 10:25 pm 
Offline
Competent
Competent

Joined: Thu Oct 29, 2015 9:41 pm
Posts: 37
well most use muticore possing as a requrment and anthing lower and 64 bit java is now requred to avoid crashes in real times games for even the smallst of games to even run on most computers bulit past 2012


Top
   
 Post subject: Re: OXP Performance tips
PostPosted: Thu Oct 05, 2017 10:29 pm 
Offline
Competent
Competent

Joined: Thu Oct 29, 2015 9:41 pm
Posts: 37
i have 8 GB's of ram and your games overhead is 500 MBs and my computer has like 4 cores and my computer tends to cause crashs if the cores are not being used or when a app has less then 1-2 GBs or ram being used for a game with a gpu its even worse if it's all the above that if a even try to load two save games in a row my kernal would just kill the game becuse the 500 MB overhead just gets smashed by just loading to game save files in one sesion


Top
   
 Post subject: Re: OXP Performance tips
PostPosted: Thu Oct 05, 2017 10:34 pm 
Offline
Competent
Competent

Joined: Thu Oct 29, 2015 9:41 pm
Posts: 37
so technaly my computer is techany like the hulk trying to pick a lock two times but the pick just brake when the secound file qury happens to cause the game engine inmplode


Top
   
 Post subject: Re: OXP Performance tips
PostPosted: Thu Oct 05, 2017 10:37 pm 
Offline
Competent
Competent

Joined: Thu Oct 29, 2015 9:41 pm
Posts: 37
plus i can't log the crash becuse the game GC overhead just impodes to fast becuse the kenral and shear POWER of my computer killed the engine before the log even gets any data from the game it crashes that fast


Top
   
PostPosted: Thu Oct 05, 2017 10:51 pm 
Offline
Competent
Competent

Joined: Thu Oct 29, 2015 9:41 pm
Posts: 37
so if i dont want the game to crash i would have to use my 2008 mac book pro for it and i don't want to go back to that cunker so oolite super small code dosn't get GC buy my computers bulit in GC in the kernal overdoing it


Top
   
PostPosted: Thu Oct 05, 2017 11:50 pm 
Offline
Competent
Competent

Joined: Thu Oct 29, 2015 9:41 pm
Posts: 37
well the 1.85 uses more ram automaticly if it runs out out GC so the crash won't happen in 1.85 thank goodness i just tested that


Top
   
 Post subject: Re: OXP Performance tips
PostPosted: Sat Dec 16, 2017 12:57 am 
Offline
---- E L I T E ----
---- E L I T E ----
User avatar

Joined: Tue Apr 11, 2006 1:47 am
Posts: 1565
Location: Somewhere in the great starry void
Quote:
well most use muticore possing as a requrment and anthing lower and 64 bit java is now requred to avoid crashes in real times games for even the smallst of games to even run on most computers bulit past 2012
I hate to break it to you, but that's not true. Most games, even these days, are single-threaded. Oolite certainly is. It's still a rare thing to see a game, even modern AA rated titles, use more than one thread for it's rendering engine (though granted the more demanding ones could go a lot better with some multithreading.) And java isn't a requirement either; Sure Oolite uses javascript in a lot of oxps, but it'll run just fine without java installed. Same with a lot of other games.

As for needing a powerful high performance PC? Naaaw! Oolite's resource demands are so low it can run smoothly on a 90's computer; a potato with an Athalon XP and a Geforce 3 is still almost too much computer.

Now to your issue. More than likely you're looking at some bad memory, and/or a barely stable overclock that's causing the crashes. Oolite itself tends to be right stable; even the test builds are hard to crash.

_________________
Running Oolite buttery smooth & rock stable w/ tons of eyecandy oxps on:
ASUS Prime X370-A
Ryzen 5 1500X
16GB DDR4 3200MHZ
128GB NVMe M.2 SSD (Boot drive)
1TB Hybrid HDD (For software and games)
EVGA GTX-1070 SC
1080P Samsung large screen monitor


Top
   
PostPosted: Thu Feb 15, 2018 1:54 pm 
Offline
Average
Average
User avatar

Joined: Fri Jan 26, 2018 1:11 pm
Posts: 10
My computer has 8Gb ram too but it still runs smoothly when I play Oolite. Must be another reason for crashing rather than just RAM. Btw, can you put some commas and full stops to your post please? it gave me a headache when reading...

_________________
"How you played in yesterday's game is all that counts." Jackie Robinson


Top
   
PostPosted: Thu Feb 15, 2018 2:04 pm 
Online
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral

Joined: Wed Feb 28, 2007 7:54 am
Posts: 5207
The reason for the crash ashtiboy was going on about is well known and fixed in 1.86. It was a simple case of a null pointer dereference in the code. Just a normal bug; certainly nothing to do with any of that "GC in the kernal" stories.


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 13 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Powered by phpBB® Forum Software © phpBB Limited