Browse Search Popular Register Upload Rules User list Login:
Search:
When the scne starts, the box still has collision 1(A) and this makes it able to collide with the little box which also has collision group A. Simply set the collision group of the box at the beginning to B and it should work
Also move the lasers a bit inside the frame. else, the laser get's blocked before the box even hits the beam. Best you set the frames collision group To 4(C), and the lasers script to e.geom.collideset = 1 to = 5 and e.geom.collideseet = 2 to = 6. Then you pretend that the box falls out of the frame
Do you feel da magixs? This is an really really good script you used here. Well done
I finally found out how to trigger the creation of an undo point. The asve fields of all parts of this game work now!
The 3D scenes are getting better and better and better! Each one of you needs to continue the 3D technique and create something a little bigger from it!
Stop spamming cmoments on others scenes. This scene works perfectly fine, and the only place where glitches could occur is the F and R as it's components aren't fixed to anything except some boundary boxes. And if you use the drawing/moving tool during the scene, it can only fail.
Nice idea. Could I use this for one of my minigame scenes? It would be perfect for platform spawning
wow, nice power. Good there are still people who don't just make marble races xD.

Btw: Thanks to you i finally know how to make for-functions again:D
Are you allowed to duplicate these, use hinges,scripts,cutting them,etc. Just To specify
Dear Emanuel,
I always disliked that users who are into marble races upload like 50 marble races or similar per day and this way flush all the quality scenes out of the news section. I would like to hear if it's possible to add a Tagging system to the Algobox, and sorting scenes using these Tags, similar to entrys on other forums. This way, people can directly use an advanced search option to look for the tags they like, and see all scenes containing these tags. People could easily find marble races, or mechanical scenes, game, or anything else. It would greatly improve the organisation and help people seeing the scenes they like, and keeping the other scenes for these that like other types of scenes, without flushing away what one could like.
Looks like someone forgot to tweak emove the body attribute of the stickmans while beeing furious :3
I know you do this for your fun with marble races, but please try to avoid static scenes, as algodoo scenes are supposed to let something happen.
If you mean changing the layer of an existing object, try e.other.layer = XYZ
if you mean changing the layer when placing the object(which i dont guess as you are adept in my opinion ^^) rightclick the background and click the layer tab. Then add the amount of layers you need. Select the layer your objects should be in and place your objects.

I write all of the info as I want to make the answer understandable for everyone:)
*We should take the marble races, and push them somewhere else...* -patrick star
I stay to my idea of adding a tagging system, along with name search. This way we can simply add a -Marble_Race tag and we would not see any marble races, while the fans of them could do Marble_Race and they only see marble races. This could be combined with a tag for the autor name, and you can quickly find any scene. Multiple tags and name search is enough to quickly locate any scene. One could set some standart tags then in his profile or something, so he doesnt need to write one and the same tag over and over. The old search system is quite random in my opinion, and this search would help blacking out whatever one doesnt like
One way, which is pretty massive in dooing, is by making the triggerer take all relevant data of the shape whose layer should change, and then delete that and instantly add an replacement shape with the changed layer(you can in fact write layer := something). Other than this, i dont know, as the layer attribute is the last attribute left as an readonly attribute(a similar problem was with the pos. attribute when it was readonly a long time ago)
It should be managed that 1st some tags get set automatically as recommendation, read from the description or the title. then the other relevant tags maybe need to be set(like, at least 2 set tags necessary to submit), so that every submitted scene can be found via tags at least once.
Those who haven't noticed yet, part 4 has been published:D
Anything for contest entries;)
The reason is because algodoo is made of 40% younger audience(i guess) and 60% adult/teenager. of the yougner ones maybe 10% are inactive while of the adults maybe 30% as they have less time. This results in a majority of young people who mostly seem to like marble races, which of course causes you to get lots of view. I have about 1 page of scenes(you can look if you want) with varying views over the time, ranging from 100 to an absolute maximum of about 850, which is hard to reach nowadays as my scenes are on the new page for 2 hours before they are on page 2 where only half the people look. you can either try atracting all the people a bit, or you try attracting a few people with something very interresting. otherwise you have low downloads :L
Another note: try using the forum. I have made an announcement a few scenes ago about using message scenes. In the forum your messages are always visible and easily accessible
Yeah, but having the game is already a lot of work by him. If there only was a way to make the small guys make big stuff :I
use google or the algodoo forum if its related to google:/
He is busy, and only looks on algodoo every couple of time i think...
I have the permanent urge do make jokes about the marble flood in my scenes, but that would draw negative attention to me. The problem is that I cant even find ideas from userscenes anymore because all you get is marbles. maarrbleess. I am slowly but steadily getting mad about this :I
Use the forum for such questions. The algobox is mainly for displaying your created scenes
The problem is: we dont have it with 1 user spamming 10 scenes per hour, but 10 users spamming 1 scene each. If we make a time limit it should apply to all users, which would mean someone makes his marble race, and in return the nice boys cant publish their scene because the limit has been reached. So an limit for all users is not fitting. I have to admit: it may not be against the rules, but the rules can be changed in case of emergency. And this is going to turn into an emergency if the prior 16 years old users leave and 11 years olds come. Marble races need to be banned in some way from algobox, because algodoo isnt made for dooing stuff that one could do in RL, but for trying the genius physics powers. This in return reminds me of phun, which has limited abilitys, but all the stuff you need for an marble race. So one could take phun, modify it, and turn it into the new marble race simulator 1.9001 . This of coruse is splitting the game, which you probably dont favor. The other possibility is a subforum on algobox, where only marble races should be posted. Any marble race outside this forum is getting deleted, resulting in efficient packing of all marble races.
Use the forum for messages, its way more effective
I dont mean this offensive, but please try not to make static scenes like marble race results. You own over 700 marble scenes, which is a bit enough in my opinion. The algobox wasnt made for result scenes okay:/
Didnt you already say that in a scene?
previous | 1 2 3 4 5 … 31 | next