Oolite Bulletins

And still around if a little quiet (busy with RL) the last few weeks - I will make time to pick up on some Oolite stuff this weekend.

I was looking back at your similar problems here https://bb.oolite.space/viewtopic.php?f=3&t=9669&p=157205&hilit=Program+received+signal+SIGSEGV%2C+Segmentation+fault.#p157205 which suggested the Graphics Driver was implicated in the crash. Are your graphics drivers as up to date as they...

You'd have to step me through the process to do that. :( Follow these posts?: https://bb.oolite.space/viewtopic.php?f=8&t=5943 Yep but at stage 3 do make debug=yes https://bb.oolite.space/viewtopic.php?f=8&t=10800 Yep. :) Assuming I did those correctly, here's what I got: Program received s...

Yes, I think I was. How about adding, to the this.escapePodSequenceOver handler (or a pod launched handler, if there is one) code to cancel your timed reminder? But you'd need to restart/recreated the timer if and when the ship both launched and hadn't had the drive repaired. Version 1.3 of Breakab...

Can you run a debug build with GDB? I've still got a copy of OMEGA you sent me a while back and have spent a while pootling around in perpetual cloak, misjumping, following ships through wormholes etc, but no crashes.

Version 1.3.3 of the standalone and oxpConfig versions is available for download.

Version 1.3.3 and 1.3.3oxpC: 30/06/12

Fixed timer clean up mechanism to avoid unrooted timer errors when flicking rapidly to and from the long range chart.

I just did some testing of this on my old Win XP machine (256MB ATI x700) compared to my Win 7 machine (HD3000 can use up to 1.7GB of system memory for video). On the XP machine 1.76.1 runs fine. 1.77 prior to revision 5042 loads fine, but the frame rate turns to sludge (4fps) on looking at the shor...

Hi sdrubble - Eric made the changes so can answer with more authority, but it looks like that prior to 1.76.1 (including all 1.75.x) weapon_range and weapon_energy shipdata keys in turret definitions were being ignored and default hardcoded values used instead (25 for weapon_energy, 6000 for weapon_...

Tricky wrote:

That patch works.

Thanks for testing - I'll tidy that up properly (there's already some timer clean up code elsewhere in the script which I'll adapt to use) and update the OXP in the morning.

An interesting bug indeed.

Thanks for the report Tricky. I've just done a very quick test to see if I could crash Oolite in this way and not so far. I'll try again in the morning and also fix the potentially unrooted timer issue to see if that does make any difference for you. No luck in crashing r5036 under Windows 7 with u...

Thanks for the report Tricky.

I've just done a very quick test to see if I could crash Oolite in this way and not so far. I'll try again in the morning and also fix the potentially unrooted timer issue to see if that does make any difference for you.

Thargoid wrote:

Could something suitable be added to 1.77 please, for both materials and shaders? Presumably to dump out a dictionary of current settings, similar to what you'd feed back with setShaders/setMaterials if you wanted to apply them again?

See https://bb.oolite.space/viewtopic.ph ... 85#p175585

From https://bb.oolite.space/viewtopic.php?f=4&t=3243&p=172766&hilit=+materials#p172767 Could something suitable be added to 1.77 please, for both materials and shaders? Presumably to dump out a dictionary of current settings, similar to what you'd feed back with setShaders/setMaterials ...

Capt. Murphy wrote:

Following that with...

Code: Select all

player.ship.setShaders(x)

returns true but does not apply the changes.

setShaders() is fixed in trunk with revision 5032.

Will definitely be making use of that when I can get a .dat and texture files out of the wings file. Are you following the instructions from [wiki]OXP_howto_model[/wiki]. Should work fine. Double check with version of Python you've installed - the scripts are for Python 2.x not for 3.x. You have to...