Slime Salad

Master K wrote:

Hey, I think that photo of this piece of art was taken here in Auckland about a year back. You can see Rangitoto in the background.

Exporting from the same game from which you successfully exported previously? I actually forgot to push the new version to gitorious, so nothing's changed. I've done that now (do "git pull origin"). I can't understand how that error could happen, but could you try with the new version? Fai...

I've never heard of such a bug before. The music is really loud. Whenever the music loops back over again, SW Synth returns to the default volume, whether it was turned down or not. By "default volume", do you mean "the default loud volume", or "the volume becomes quieter&qu...

I can't wait to hear of how you generated those screens using a spreadsheet!

nohrio also has some support for MXS and the other graphics formats. Looking at nohrio/3rdparty/colouruse.py should help, though it's obsolete. I'll pass on this one.

I guess that makes me the only source of information, and ultimately to blame for rumours... aside from Jabber spread FUD in favour of switching to OpenAL!

Can do. I'll just reschedule our next release for June 2102, but you know how schedules slip...

OK. You're hitting Ctrl+C and Ctrl+V on the "Slice Collection #" line, just as I did. In Zenzizenzic this causes the slice ID to be copied and pasted rather than a slice! In nightlies, this is fixed.

CASE CLOSED!

Does copying and pasting work elsewhere? What version are you using? But, thanks, "copying the slice collection's name" turned out to be the explanation of the crash I saw! I hit Ctrl+C while the "<Slice>" line was selected. I realised what was up when happening upon the cryptic ...

Actually, that's 42 characters. By the way, if you're using the full 36 characters, make sure you're using a nightly since the 20th of April; before then only 34 to 35 characters were supported. Opps, I didn't notice that it actually throws an error on strings that are too long rather than truncatin...

But yes, it would be nice if we could control volume better. That will have to wait for a better sound backend. It won't be too much work to implement in all the existing sound/music backends. Half the work is actually in fixing the music backend API, which is awful and wrapped in additional useles...

Are you sure about that? It can appear that that's what's happening when in fact it's working correctly, because the newly created slice looks identical to the old one. Especially confusing because there's no scroll bar in the slice editor, so you might not notice the list of slices getting longer a...

I was thinking of using strings to do that, but I was concerned that with the amount of data I have going through the scripts, the text wouldn't remain the same once I ran out of strings, but perhaps I may just be reading the string limitations incorrectly. I'm not sure what you mean. The only limi...

Not yet. It's definitely badly needed. Your only option is to use an external editor.

Also unfortunately on Windows MIDI volume is totally separate to other volumes.

Looks good. I wouldn't worry about speed, but I'll note that it's much simpler to store the item ID in a menu item extra data slot (setmenuitemextra, getmenuitemextra) instead of checking the menu item's caption. Also, you can write "craftingstage += 1" instead of "increment(craftings...

Err, yes, just listen to BMR and ignore me. I figured I would screw that up, because when was the last time I actually used text box chains? 2003? Edit: What everyone seems to recommend for sound editing is Audacity . Or you could just use 'Sound Recorder' on Windows; that can clip bits off the end ...