max-texture-size
setting in the .GNUstepDefaults
file to 1024 or even to 512. This should reduce the load when large textures are used.Moderators: winston, another_commander, Getafix
max-texture-size
setting in the .GNUstepDefaults
file to 1024 or even to 512. This should reduce the load when large textures are used.Thanks to Gimi, I got an eBook in my inbox tonight (31st May 2014 - Release of Elite Reclamation)!Gimi wrote:Maybe you could start a Kickstarter Campaign to found your £4500 pledge.drew wrote:£4,500 though! <Faints>
Cheers,
Drew.
I see the same thing with my ATI Mobility Radeon X2300 laptop. I don't think it's a RAM swapping issue.. from everything I've read to date, I'm inclined to think it's due to ATIs incomplete implementation of OpenGL.another_commander wrote:The description of the problem seems to indicate that there is not enough and that RAM swapping might be taking place.
I have also noticed that in your first post you mention Intel graphics, but further down it is ATI Mobility Radeon HD 2400. I think this needs to be clarified a bit.
<has a flashback to three years ago> Those bloody ATI/AMD drivers - arghh!Diziet Sma wrote:... I'm inclined to think it's due to ATIs incomplete implementation of OpenGL.
VSync off?CommRLock78 wrote:Interestingly, I haven't any problems with my Radeon HD 5450's driver (essentially - there's some slight tearing that I haven't been able to get rid of). A roll back might just help though, as another_commander suggested.
Nothing about V-Sync that I can see, but there is a V-refresh which is cranked up because Tear Free requires it to be so (Catalyst AI I just re-enabled yesterday trying to see if I could fix the tearing, which seems to be occurring about 1/3 of the way down the screen particularly when I'm yawing in Oolite fullscreen (windowed doesn't have the tearing, but graphics seem sluggish)).Svengali wrote:VSync off?CommRLock78 wrote:Interestingly, I haven't any problems with my Radeon HD 5450's driver (essentially - there's some slight tearing that I haven't been able to get rid of). A roll back might just help though, as another_commander suggested.
This is weird - I thought I had maxed out all the settings, but I realized the basic Anti-Aliasing 'method' was not maxed. After setting it from "Wide Tent" (which gives 8X samples) to "Edge-Detect" (which gives 12X samples), now oolite crashes.El Viejo wrote:From memory of my old ATI - CatalystAI off and V-Refresh on. Is there a setting anything like Triple Buffering? If so, toggle it on. All other settings (anti-aliasing etc) max!
Yeah, all reverted to the way it was - AI is back off. Ah well... thanks for the help anyway EV and Svengali . I'll have to play around with it some more. It's weird that 12X didn't work...El Viejo wrote:Ah... well, my ATI-foo is old and stale. Back to 8x, methinks.
Code: Select all
{
NSGlobalDomain = {
};
oolite = {
autosave = YES;
display_height = 800;
display_refresh = 0;
display_width = 1280;
fullscreen = YES;
"max-texture-size" = 512;
"procedurally-textured-planets" = YES;
"reduced-detail-graphics" = NO;
"shader-mode" = 3;
"sky-render-inset-coords" = YES;
"use-texture-lod-bias" = YES;
"wireframe-graphics" = NO;
};
}