Messages

Hey gang, I've been off on vacation off the grid!  Is there any way I could get this extended to Friday/Saturday?

Btw Monkey424, that's an awesome picture!

*GASP!*

Ben is a nice name....

So far I found that when you call SayAt the "width" parameter must be >= width of speech frame, because it actually limits both text AND portrait size.

If it's less, it causes all kinds of weird results, eventually trying to create an overlay bitmap of many-GB in size.

Alright, I got it.  Good call on the speech frame portrait size.  What I had done was swapped the blank frame from loop 0 of View 1 to a character sprite in order to place it precisely in the room (thus playing with the character attributes, making me suspect that that was the cause).  However, I forgot that the reason View 1 has empty sprites in all 4 views is not an oversight but was actually my invisible portrait frames for my custom speech bubble TalkAt function.  As soon as I swapped the blank sprite back into View 1 the game ran normally -1000 thank yous!  

I wonder if this is what I inadvertently did last time....  I'm pretty sure I have a back up of the "corrupted" file: I should go check.

Could you post the code or a line number that you think is causing the weird results?  I'm not saying that leaky code might not be a possibility here (and that's why I posted in this same thread), but it is definitely suspicious that I had the same crash last summer with different code, and that the speech bubbles were all working fine last week.

[@Crimson Wizard:]

Upon reflection, I see another common thread to this error.  Both times it occurred after I changed the character view while both the character tab was open and the same character was the focus in the room I was working on.  Can it be that the editor can't handle updating the properties of one while the other is open at the same time?

@Crimson Wizard: PMed!

Gah!  Memory problems.  I had them before, once, and was convinced that it was a corrupt room file.  However, deleting the room didn't solve the problem so I had to go back to a previous build of my game and rebuild.  Which implies that it wasn't a corrupt room file at all, but a broader mysterious problem that was never solved.

Anyway, now I'm getting this:


Apparently this has been a problem for other developers recently, and it happens for me now when speech starts, which can not be a coincidence.  But I haven't altered any of the speech code since I established that it worked a couple weeks back, and I have tested the width of my speech bubble by displaying it before the bubble is called, and it is always positive (I commented out a bunch of speech to try out random lines, but they all crash the game now).  It seems like it must be a corrupt room file again -or at least the mysterious corruption again- but why does it always crash on speech....?  My speech bubble function uses Sierra with Background speech with SayAt commands: it's too much of a coincidence.

What have I changed since getting the speech bubble function to work a few weeks back?  Just added another background to the same room, some objects, and a couple of new speech views.  I cannot even remember opening the global script since the speech bubble function worked....

So, since I haven't changed anything with the working code, this seems to be a recurrence of the random room file mystery corruption that I suffered from last summer.  But... why does the game always crash now during speech?  Why am I getting virtually the same error Dave was getting when his SayAt width was negative?  Why was he able to fix his game so easily?!?   Does anyone have any ideas, or is it back to square one for me (again....)?

Ah America.... inventor of the mankini.  Who could ever make fun of that?

only cows use latex gloves as condoms

Now who's going to draw that smiley?

[gloves]

That's why doctors recommend using latex gloves for your brains, Baron.

Kinda like a brain condom?  Yeah, I could use one of those about now.

Where do you find such coins, Baron?

Garage sales and antique stores mostly....  Just look in the discount bin. 

I've got a small collection.  There are two criteria for coins to interest me:

1) Coins must be at least 200 years old
2) Coins must have almost no current monetary value

...So basically this limits me to severely worn/damaged coins, but it's still cool to contemplate how many lives a tiny lump of metal in your hand has passed through in the past 2000 years.  If only money could talk!  Wait....

So.... rhymthmic hips and flawless armpits aside, when exactly do the rights of the Bake Sale games relapse to their owners?

Well, peeing was one of the things I was going to do to him, yes.  Me power!

Aaaaaaaaaargh!

Fun, although often taking the riskiest and sure-to-kill-you option is the surest way to survive.   In the spirit of "choose your own adventure" novels, I would have appreciated some more serious options, just to feel a little bit in control of my fate, but I suppose that would compromise the zany heart-in-your-throat comedic action-packed blitz-fun vibe that you were going for....  Anyway, as I say, it was fun.

I'm pretty sure there was plenty of blood, sweat, and tears in that game of mine you have on file.  Of course, there were many collaborators on that project, so the resulting clone might have one attribute of each of us....  ...like some sort of Franken-clone!  With the monocle of the Baron, but the rhythmic hips of the Ponch!  And the left ear lobe of Frodo!  And the armpit of kconan!  And the squeaky clean mouse-clicking finger of Tabata herself!!!  Now truly that would be a beast to behold.

As it stands now, I'm not sure why your are complaining about your army of cloned tomatoes.  They will be much more obedient and rather less flatulent than an army of Baron clones....

[brain!]

I also secrete a nice liquid starch which comes in handy when it's time to break out the ironing board.

The soap... it doesn't work on my brain!

You know, P, now that it's been brought up....  I'm having a hard time remembering exactly what I "agreed" to.    Could we establish a concrete date so that there's no more confusion?  Thanks.