Cody wrote:Jumped into my nova system again (the sun is still at a survivable distance), and this popped-up:
Code: Select all
13:19:47.390 [script.javaScript.exception.unexpectedType]: ***** JavaScript exception (Oolite Pirate Freighter AI 1.81): TypeError: system.mainPlanet is null
13:19:47.390 [script.javaScript.exception.unexpectedType]: Resources/Scripts/oolite-priorityai.js, line 4502.
The sun problem should be fixed now, though anyone who saved their game on a recent nightly won't get the benefit of that fix without manually editing their save file. Upgrades from 1.80 to 1.82 will work, though.
Testers who want to make the edit manually, you need to find the bit like this in your savegame - it may be considerably longer than this if you have a lot of OXPs. Replace "~3 168~" with the appropriate values for your nova system.
Code: Select all
<key>scripted_planetinfo_overrides</key>
<dict>
<key>org.oolite.oolite~|~3 168~|~corona_flare~|~2</key>
<string>0.105626</string>
<key>org.oolite.oolite~|~3 168~|~corona_hues~|~2</key>
<string>0.800000</string>
<key>org.oolite.oolite~|~3 168~|~market~|~2</key>
<string>none</string>
<key>org.oolite.oolite~|~3 168~|~sun_gone_nova~|~2</key>
<string>true</string>
</dict>
Then add
Code: Select all
<key>org.oolite.oolite~|~3 168~|~sun_radius~|~2</key>
<string>680000</string>
(Strictly, what you should do is look up the sun_radius for the system and add 600000 to it, but it's not going to make that much difference)
The AI problem ... I'm not entirely sure how the freighter got there in the first place, but probably there's a general AI problem that they don't react sensibly to being in a nova system. I'll add that to my list of things to fix.
Venator Dha wrote:Suddenly lost sound on latest build, needed to quit to reset.
That error message is going to be difficult to track down the cause of. I would guess that "out of memory to allocate buffer" is unlikely if you have 12Gb (assuming you haven't severely restricted how much of that Oolite can request), and there shouldn't be other resource limits being relevant either. There's a limit of 1024 simultaneous buffers on OS X, but you shouldn't be getting anywhere near that limit in normal operation.
Could you see if you can reproduce it with some sort of reliability (e.g. continuously play normally for X minutes or do something that triggers lots of sounds at once)? If you can, could you post a list of the sound-related OXPs you have installed and see if it still happens in Strict mode?
It looks like it took four hours to happen, from the log file, so maybe something in Core or an OXP is keeping references to sound buffers around for much longer than it needs to, or creating multiple copies of the same sound.
![[EliteWiki]](/images/elitewikismall.png){kind=small}
New Cargoes
. I was in a fire fight at the time so there's a lot of laser fire & hits to my shields going on. The only OXP I have running that affects sounds in any way that I know of is audible docking clearance otherwise I only have the core sounds running.
