[Thyme][1.5.61]Thyme Command/Variables List

[Matten]

stop being lazy

It's not lazy, it's handy. Otherwise you have to put in the description of the scene: "To input an object first put it on the ground and then change it's collideSet to CE, then...". And I don't think that would come a popular scene, only because of this.

I almost never use lasers with 127 as a collision group.

It's just an example, not a real story.

[Rideg]

What I meant is that you could set the laser default collision group to a custow one. In my case that would be 64.

[Chronos]

stop being lazy

It's not lazy, it's handy.

You know what else is handy? An elephant button.

[Matten]

elephant button?

[Chronos]

Yes, so whenever I need to make an elephant, I can just click that button instead of building it myself. Sure, it might be useless, but it's helpful to me.

[xplane80]

Now that is an amazing idea Chronos. The best I've ever read!

[Matten]

But I think the default function would be more usefull as an elephant button.

[Chronos]

Nope. It will be helpful to me, so I want it in.

[Rideg]

yeah but a default function would be helpful to multiple users.

[Chronos]

It would be helpful to a few. The others aren't lazy. Besides, you would have to go to the options menu when you're done and change it back anyway, or keep changing it back to A when you don't need it. It's not very practical.

[Rideg]

yes it is. If you don't want to use every collision group as a default you can change it to any collision group.

[Chronos]

You don't use every collision group as default. You use A.

[Rideg]

on lasers???

[Chronos]

Ok, I didn't hear you say lasers. Just disable them. It's not that hard. Besides, when I use lasers, I have them on every group more often than not.

[Rideg]

Didn't hear but read sorry just had to.

Well back to point I just think it would give the user a little more management over the program so you could customize it after how you would use Algodoo.

[tatt61880]

Since v1.7.5,
There are new function Scene.moveWorld.
This function is similar to Scene.moveToOrigo.

For example,

Code: Select all

Scene.moveWorld([1, 0])

will move the whole current scene rightward just 1m.

[Rideg]

w00t? like move all object to the right?

[Mystery]

Yes also No, it could just be moving the point of origin [0.0, 0.0] We will never know.

[Chronos]

Actually, you can know. Just move the world to the left about 50 units, then go to the world origin. If the scene is still in the origin, it moves the origin. Otherwise, it moves the objects.

[Mystery]

Well if it doesn't move the camera (Like you are suggesting) then it's neither.
AFAIK The way thyme works, the only way this would work is by moving all the objects.

[tatt61880]

Sorry but new another command.

New function "Bench_Steps" was added at v1.8.
This function will be used for benching purpose.

For example, in my PC, with the scene Algodoo/scenes/official/Cause and effect.phz,
> Bench_Steps(1000)
1000 steps took 2.5950012 seconds.


---
Next variable is also useful.
GUI.sliderLabelPrecisionOffset = 0, default = 0. Higher values gives more significant digits in the slider labels
(NOTE: This variable exists since v1.7.6)

[Paradigm 29]

Have all the new variables been edited into the original post?
Rather, can someone (tatt) edit the original post to include all of the new variables and commands?

[tatt61880]

Have all the new variables been edited into the original post?
Rather, can someone (tatt) edit the original post to include all of the new variables and commands?

I've made a variable table for you!
The table has all variables/commands which is in v1.8.0. (except for geom variables.)
Algodoo wiki: Thyme

I don't have a plan to make a geom variables list, sorry.

[Paradigm 29]

Thanks. I'll be sure to look on the wiki from now on.

[electronicboy]

okay, what on earth does SPH.SetClassicSPH do?