Oolite problem at SSC [Solved]

For test results, bug reports, announcements of new builds etc.

Moderators: winston, another_commander, Getafix

Post Reply
User avatar
Cody
Sharp Shooter Spam Assassin
Sharp Shooter Spam Assassin
Posts: 16081
Joined: Sat Jul 04, 2009 9:31 pm
Location: The Lizard's Claw
Contact:

Oolite problem at SSC [Solved]

Post by Cody »

A guy came into the Oolite embassy at SSC with a little problem getting Oolite to run... any ideas?
I would advise stilts for the quagmires, and camels for the snowy hills
And any survivors, their debts I will certainly pay. There's always a way!
User avatar
Eric Walch
Slightly Grand Rear Admiral
Slightly Grand Rear Admiral
Posts: 5536
Joined: Sat Jun 16, 2007 3:48 pm
Location: Netherlands

Re: Oolite problem at SSC

Post by Eric Walch »

El Viejo wrote:
A guy came into the Oolite embassy at SSC with a little problem getting Oolite to run... any ideas?
He should update to a current oolite version. In version 1.75 that line from his bug-report reads:

Code: Select all

assert(surface != NULL);
But 1.76 already has different code at that spot. No longer any assert command nearby either. So, it probably solved in 1.76 upwards :wink:
another_commander
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 6634
Joined: Wed Feb 28, 2007 7:54 am

Re: Oolite problem at SSC

Post by another_commander »

Actually, the 1.76 source has the assert in line 220 of MyOpenGLView.m. It appears that SDL is failing to initialize the splash screen.

A possible solution could be the -nosplash switch. Alternatively, we need to know what screen resolution setting is being attempted and whether that was an attempt to go full screen or window (probably it's going to be window, if it was a first try, but just to be sure).

If all else fails, it might be worth trying with a nightly build, where the SDL setup parameters have been adjusted to newer graphics cards.
User avatar
Cody
Sharp Shooter Spam Assassin
Sharp Shooter Spam Assassin
Posts: 16081
Joined: Sat Jul 04, 2009 9:31 pm
Location: The Lizard's Claw
Contact:

Re: Oolite problem at SSC

Post by Cody »

Thanks to the Admiralty... I'll link this thread back to the Oolite embassy.
I would advise stilts for the quagmires, and camels for the snowy hills
And any survivors, their debts I will certainly pay. There's always a way!
User avatar
Eric Walch
Slightly Grand Rear Admiral
Slightly Grand Rear Admiral
Posts: 5536
Joined: Sat Jun 16, 2007 3:48 pm
Location: Netherlands

Re: Oolite problem at SSC

Post by Eric Walch »

another_commander wrote:
Actually, the 1.76 source has the assert in line 220 of MyOpenGLView.m. It appears that SDL is failing to initialize the splash screen.
You are right. I only looked at my local 1.76 maintenance. There it has been changed. In the 1.76 release code on berlios it was still there :oops: .
another_commander
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 6634
Joined: Wed Feb 28, 2007 7:54 am

Re: Oolite problem at SSC

Post by another_commander »

I cross checked with maintenance and indeed it looks it's fixed there. So from what it looks like, the problem is that the Radeon HD 6770 has problems setting up 16-bit OpenGL contexts. Trunk and maintenance fix this by switching the start up initialization to 32-bit OpenGL contexts with fallback to 16-bit in case things don't go as expected. Chances are trunk nightlies will run fine.
User avatar
Cody
Sharp Shooter Spam Assassin
Sharp Shooter Spam Assassin
Posts: 16081
Joined: Sat Jul 04, 2009 9:31 pm
Location: The Lizard's Claw
Contact:

Re: Oolite problem at SSC

Post by Cody »

All sorted - the -nosplash switch fixed it. I looked at that error message and didn't even think of that option.
... now just gotta learn how to play this badboy ... thanks a lot cody. you da man.
<howls> I think that is the first time I have ever been called da man <wanders off, chuckling quietly>
I would advise stilts for the quagmires, and camels for the snowy hills
And any survivors, their debts I will certainly pay. There's always a way!
Post Reply