Algodoo

Mr. Cubert Farnsworth could not possibly know if the ship's engines moved the ship or if they moved the Universe around the ship if their velocity was constant. If the engines were to speed up or slow down, then he would know for certain if the engines were moving the ship, or if they were moving the Universe because inertia would resolve his dilemma.

Albert Einstein thought about this kind of stuff a lot!

You made an interesting observation as described in your scene which I will certainly experiment with to see if it might be useful in any of my own scenes. This new way of using an object as a moving origin point might open up a whole new way of designing Algodoo scenes. Good job!

Nice work. Thanks for sharing.

Xray - They also make light to travel faster, and they could travel at 99% of speed of light, so that mean it is actually faster that "our" light
Bessy´s engine have efficiency of 200%, so maybe it was moving universe with acceleration of normal ship, even if thrust is OVER 9000...
Ok, that´s enough

S_noonan - I accidentally found this script in console while I was looking for something like "execute" in Java, i want to find closest object with property, for ex. materialName:"object" and command will return everything, like pos vel etc. of that object, even if there are more object with that name
Do you understand me?

just use entityByGeomID() or entityByID()

As of the scene, that's a nice find. I guess it'd be better (performance-wise) to update the position every x seconds, since this has huge overhead when there are lots of objects on the scene and frequencies around 120-240 hz

I want to have multiple objects with same property (blue color for ex.)
Then i want to "scan" for blue objects and pick one, then get it´s properties, like pos etc.

JakubKubo -- I use entityByGeomID() in one of my older scenes in order to get ALL variables in some other object in the scene, but it had some very peculiar behavior. Here is how I did it:

First I created a local variable in the object that is to receive the variables. I created the variable like this: _temp = {}
Then in postStep of that same object I added the script: _temp = entityByGeomID(72) where, 72 was the geomID of the object that I wanted to get all variables from. As soon as I started Algodoo, I saw all the other object's variables in the local variable "_temp". But when I clicked on the contents box for _temp, all variables were listed until I clicked on it again, then all the variables disappeared, AND the script in postStep also disappeared! WEIRD! So, I'm not sure if this will work for what you are trying to do. Also keep in mind that all the geom ID's will be different each time Algodoo reloads before starting. So, the number that you use for entityByGeomID will only work for a specific geometry until Algodoo gets reloaded.

Woah jakub, I still remember the time when I explained some thyme stuff to you, but right now YOU taught ME something new. I never knew scene.moveWorld exists. While I don't see much use of it for me, it is fascinating nontheless.
About your question with "selecting" objects dpeending on properties, I must disappoint you. Algodoo has no means of efficiently accesing the entirety of objects in the scene, unless you want to store references to all objects in some ludicrous list, which I can only assume melts down both algodoo's RAM and processing speed. The most you can do is use lasers to periodically scan the area around your cube and compare everything that is hit with your condition. EntityByGeomId can the be used to make the laser do something to the cube in case of success.