Archive for the ‘Code Stuffs’ Category

Yes it is dynamic, and yes, the math involved wasn’t fun at all. 😛

I should probably wait for a wider adoption of “Bake on Mesh” before I actually go further than the “prototype stage” with this.

I quickly modeled a little “menu card” to serve as a holder/giver for the notecard that contains all the drinks you can make.

I’ve also:

• Fixed a bunch of bugs.
• Added some missing drinks (Engine degreaser, Sunshine Cloud).
• Added proximity checking.
• Updated all the drinks.
• Added machine config options for the owner to restrict users, disallow drink dropping, and whether they want to use temp-on-rez or not.
• Updated the taste for all the fixed recipes.
• Custom drinks now have taste for ice & aging.
• Successful drinks are timed (just as a personal challenge).
• The machine doesn’t produce anything when the mixing handle isn’t held for the minimum time.

There is only a couple of things I still have to do (specular map for the machine, wiki, product pics…)

Otherwise It’s pretty much ready!

I modeled two more glasses for the MixMaster. It is now able to make 12 drinks.

I also wrote more code to get recipes to check that the preparation has been followed (ice/age/mix/blend) but I’m gonna have to scrap this part. My intent was to give a hint that you didn’t quite make the right drink, and that’s currently what it does.

Result: ‘Sugar rush’ and ‘Sparkle Star’ have the same ingredients, so one of the two recipes overrides the other.

I have two options:

1. Keep it as it is and change the sugar rush or sparkle star recipe?
2. Make the preparation part of the recipe, but then I lose flexibility with drinks that have preparation errors.

Regardless, I also need to make two new bento hand poses, the hand opening is too small for the rocks glass and too big for the test tube.

I’ve spent an absurd amount of time detailing the glass code:

• Custom animations, including bento finger poses.
• Manual vs automatic drinking.
• Named drinks have special flavors and descriptions.
• “Custom” drinks have more generic flavors that depend of their composition.
• Drinks have a set number of “sips” before the glass goes empty.

I also encountered a rather nasty rendering issue while making the final model for the highball glass. I can’t really fix it so I kinda “worked around it” by using less transparent glass. It’s not perfect but it’s not too visible.

So that’s a total of 4 recipes that are more or less “final” (unless I add some particle effects):

• Glass of Nothing.
• Marsblast.
• Blue Fairy.
• Custom Drink (I still need to fix the color generation there)

I got some of the basic functions I need for the “re-rezzing” of drinks (like for the vacuum system but a bit better), so they can be dropped and set on compatible surfaces (coaster… table?). I got “some” of the code to get them serialized into a tray, which, ideally would be drop-able too. So overall, good progress in 3 days.

But honestly, should I just take a break from this project and work on something “more KDC” for a while? If I’m counting this properly, between modeling, texturing and code this has been 5, maybe 6 weeks?

And this isn’t close to finished. Even if I do not release the tray at the same time, there is still all the drinks, models, and RLV functions to make.

Feel free to IM me in-world with your opinion.