Browse Search Popular Register Upload Rules User list Login:
Search:
Configuration Reset Tool

Image:
screenshot of the scene

Author: s_noonan

Group: Default

Filesize: 93.82 kB

Date added: 2021-02-01

Rating: 5.6

Downloads: 596

Views: 71

Comments: 4

Ratings: 2

Times favored: 0

Made with: Algodoo v2.1.0

Tags:

Scene tag

The purpose of this scene is to minimize the effort required to set your personal preferences after resetting Algodoo.

Question: Why would I ever want to reset Algodoo?
Answer: Sometimes the configuration file can get messed up by your scene or other user's scenes. If your scene isn't working the way you intended, it might be easier to reset the configuration than to locate the source of the error only to find out you need to reset Algodoo. If resetting Algodoo fixes your scene, then most likely somebody else's scene messed up the config file. If resetting Algodoo does not fix your scene, then most likely your scene messed up the config file. If your scene is working well on your PC but not on other people's PCs, you might try resetting your configuration file and see if the scene still works on your PC. Creating variables in root scope can mess up the config file. I've done this by mistake a few times. Your code might break something but keep on running. You can check in the console to see if your code is running cleanly.

Also, since I'm on the topic, if other user's aren't seeing some expected images in your scene then make sure each image can be seen in your scene and that the corresponding images are deleted from the textures folder. After a scene is saved, the images should be pulled from the .phz file, not from the textures folder.
Please log in to rate this scene
edit
Similar scenes
Title: Resonating Radial Engine
Rating: 5.5
Filesize: 157.73 kB
Downloads: 602
Comments: 3
Ratings: 6
Date added: 2008/11/05 18:29:00
Made with: Phun
Rating: rated 5.5
download
Title: F450 (xplymouth2) with New V6
Rating: 5.625
Filesize: 127.51 kB
Downloads: 911
Comments: 2
Ratings: 2
Date added: 2012/03/05 12:31:46
Made with: Algodoo v2.0.1
Rating: rated 5.6
download
Title: Hoverstick 1.1
Rating: 5.5
Filesize: 78.54 kB
Downloads: 262
Comments: 3
Ratings: 6
Date added: 2008/07/05 18:04:41
Made with: Phun
Rating: rated 5.5
download
Title: scanner
Rating: 5
Filesize: 103.34 kB
Downloads: 164
Comments: 0
Ratings: 1
Date added: 2020/08/28 11:45:08
Made with: Algodoo v2.1.0
Rating: rated 5
download
Title: a ball shooter
Rating: 5.625
Filesize: 81.35 kB
Downloads: 510
Comments: 3
Ratings: 2
Date added: 2009/07/28 14:30:56
Made with: Phun
Rating: rated 5.6
download
Title: random simple curve gen
Rating: 5.25
Filesize: 119.03 kB
Downloads: 116
Comments: 2
Ratings: 2
Date added: 2020/02/09 01:58:34
Made with: Algodoo v2.1.0
Rating: rated 5.3
download
Nice idea, and a very useful tool. :tup:
Thanks.
I don't know how, but when I play some scenes, and even go do different scene, or to blank one, sometimes I still have code forcing "mode=sim.running" and only way how to get rid of that is reset to default settings (I know some people are using it to secure their sims)
Is there a way how to get rid of it? Where in console is this code running?
Can I report a scene for doing this, without me knowing it? Because it makes me mad when algodoo is doing things on it's own, outside the scene I downloaded
A.k.a it is harmful program for me that I don't know to turn off = virus
Regarding "App.GUI.playMode = sim.running", as far as I know that will only work in an object and can't be done at the root level. If you still have code forcing "mode=sim.running" when you create a new scene, then check the last few scenes you downloaded to see which one caused the problem. If you locate the scene, then you could post the scene's url in the comments here and I can look for the source of the error. Some scenes put the "App.GUI.playMode = sim.running" code in the update event of an object, so there is no way of getting out of playmode for that scene. Loading a new blank scene should not automatically start playmode (assuming you shut it off before starting a new blank scene.

Q: Is there a way how to get rid of it?
A: Yes, use the phunlet in this scene.

Q: Where in console is this code running?
A: I don't have a clue. The console does not retain any code. As far as I know, the only code that runs in the console is temporary code that a user puts there. Code that caused problems for me has always been in a scene. Usually its the result of Algodoo tripping over some code and causing unintended damage or a user creating variables at the root level instead of using "scene.my." variables.

Q: Can I report a scene for doing this, without me knowing it?
A: Maybe, but it usually helps if you identify the scene. Otherwise it's reporting that one of the 158,000+ scenes is causing a problem but you don't know which one it is.

"it makes me mad when Algodoo is doing things on it's own, outside the scene I downloaded"

Some settings persist after the scene is closed, some don't. If a scene creator is going to change a persistent setting, then the scene can read the the users settings when the scene is opened and put them back when the scene is closed. Even this will fail if the user loads a new scene without closing the old scene. Most user's (including me) don't know which variables are persistent and which aren't.

My suggestion would be to find the culprit and tell him in his scene comments that you don't like what he's doing. Most scene creators don't cause problems on purpose.

P.S. An example of a scene breaking the config file can be found at Bacteria under the microscope. Load the scene. Open the console. Start the scene. A few warnings come up. The damage is done. Enter sin(0.75) in the console. Algodoo says it doesn't recognize the function. Close the scene. Reset the config file. Open a blank scene. Open the console. Enter sin(0.75) in the console. Algodoo shows the correct answer. This is an interesting example. I'm sure matto did not do this on purpose.
Last edited at 2021/02/03 09:43:35 by s_noonan