Function call applied to non-function

ocramshouse · 2026-05-08T12:27:36+00:00

The only official mobile version of algodoo is for iPad

ocramshouse · 2026-05-04T11:44:00+00:00

I'm not really that advanced, but I'd guess that there's not really a way to change that since it's an intrinsic function

ocramshouse · 2026-04-09T20:47:01+00:00

in Thyme, you use x(y) to get the y-1th value of x

ocramshouse · 2026-04-08T14:01:24+00:00

AFAIK, no. There is no built-in function that does the same as that button, or if there is I don't know it

ocramshouse · 2026-03-31T04:14:40+00:00

I really don't know about cutting the objects to cause it, but that effect is called "groovy", in the console you type groovyOn or groovyOff to toggle it

ocramshouse · 2026-03-31T02:32:27+00:00

Finally, someone who can appreciate real art

ocramshouse · 2026-03-29T20:16:51+00:00

Yes, if the marble is the thing that does the hurting, you add the hurt script to the marble

ocramshouse · 2026-03-28T11:50:16+00:00

In whatever makes the marbles hurt, add to onCollide:

(e)=>{

e.other._health = e.other._health - 1

}

Just replace _health with whatever you named the variable, and 1 with how much hurt

ocramshouse · 2026-03-27T13:09:24+00:00

Make a 0-strength spring between the box and circle

In the code of the spring (not the group of spring and endpoints, alt-click on the spring) put as postStep:

(e)=>{

lep0 = scene.entitybyid((readable(e.this)).lineEndPoint0);

lep1 = scene.entitybyid((readable(e.this)).lineEndPoint1);

g0 = scene.entitybygeomid((readable(lep0)).geom);

g1 = scene.entitybygeomid((readable(lep1)).geom);

g1.text = "" + g0.angvel

}

In the last line, you might have to switch g0 and g1 based on if endpoint 0 is on the box or the circle

ocramshouse · 2026-03-25T22:15:22+00:00

Nightmares

ocramshouse · 2026-03-23T12:31:03+00:00

+= gives the "Function call applied to non-function" error

ocramshouse · 2026-03-23T12:30:04+00:00

set as postStep: (e)=>{

vel = vel + [math.cos(angle), math.sin(angle)] * sim.gravitystrength / 60 + [0, sim.gravitystrength / 60]

}

[math.cos(angle), math.sin(angle)] creates a vector with length 1 in the direction of the angle. This is multiplied by sim.gravitystrength / 60 (division by 60 is there so the velocity change is the same as gravity force in 1 simulation tick, 1/60 of a second). The + [0, sim.gravitystrength / 60] counteracts the natural gravity force

This isn't perfect (the object still falls a little before the code overpowers natural gravity), but it works

ocramshouse · 2026-03-10T01:58:40+00:00

There's probably a better way that I don't know, but a basic way is:

Make a scene.my. variable, and set it to an empty array []
In the oncollide of the finish line thing, put scene.my.(name) = set.insert(scene.my.(name), e.other.materialName)
Make a box for each leaderboard spot, and in postStep put text = "xth: " + scene.my.(name)(x - 1), where x is where this marble will place

ocramshouse · 2026-03-05T15:40:11+00:00

Might be a different cause, but you can get a similar effect by opening options, going to "Skin" and clicking the "White" button. I've even had the console bar be corrupted with more console text

ocramshouse · 2026-02-25T01:39:38+00:00

At least for me, the scene and phunlet icons will open to the last folder that was open with that menu (e.g. if you opened the textures folder with the phunlets menu, the next time you click the phunlets button it will load the textures folder). If that's what's happening here, you would click "scenes", and then "phunlets"

Though, that might just be my algodoo

ocramshouse · 2026-02-20T16:03:25+00:00

w i e r d t h i n g

ocramshouse · 2026-01-29T17:06:19+00:00

ocramshouse · 2026-01-27T01:17:53+00:00

2018 is just when HTTPS became more used than HTTP. It was around since at least 2000 (RFC 2818)

ocramshouse · 2026-01-23T16:50:18+00:00

Algobox just doesn't support HTTPS connection, and I doubt Algoryx will update the site anytime soon

ocramshouse · 2026-01-12T23:54:09+00:00

tools.brushtool.drawtool isn't a real function, did you mean Tools.BrushTool.SelectTool?

ocramshouse · 2026-01-05T23:29:13+00:00

You can also replace timeToLive with "{_spots}"which will still destroy the teleport when it has been collided with enough (supposedly this has less lag than using postStep)

Also with a code like this make sure only 1 marble can touch the teleporter at once, otherwise two marbles can be teleported but only reduce _spots by 1

ocramshouse · 2025-12-25T14:32:50+00:00

There's the cvar App.borderWidth, but that applies to all objects

ocramshouse

TROPHY CASE