Code center > Confirmed & Outstanding bugs
Weird teleporter problem.
Testlund:
Alright, follow these steps:
1. Delete all files that DB creates the first time it is run to make sure you start out clean and to replicate this procedure properly.
2. Put my global.set file, robot files and sim files in the proper directories.
3. Start one instance of Darwinbots, press pause and load the sim named A.sim.
4. Start another instance of Darwinbots, press pause and load the sim named B.sim.
5. Put these two instances next to each other, for example like the picture shows and press play on both instances.
6. You need of course set your own paths for your teleporters. One folder for bots to go from sim A to B and another folder for bots to go from sim B to A like the picture shows.
7. Just run these sims and see what happens. Bots may or may not teleport correctly. The result may differ from each time you start the sims! You may have to close and open the instances again before you load and start the sims to get a different result.
Sometimes I get an error message that says "File already open and that the bot is not a valid bot." This is also a new phenomenon. I had my antimalware software turned off when I tested this so there shouldn't be anything outside of Darwinbots that could access the files. If I just close those dialogs the sims continue to run.
So I've been repeating the process several times but now it has decided to work fine everytime!
Testlund:
Now I've been trying the above mentioned steps on my laptop with Win XP. After several failures I finally got the teleporting to work. Only difference was that I got the dialog boxes popping up several times that the files were already in use. After clicking away those the teleporting started to work without any more issues. I had antimalware software turned off there too. I think DB sometimes has problems with file access when using teleporters.
Botsareus:
ok, thank you for more info, I'll test this further when I have time, but I am putting this on reasonably lower priority at the moment as you demonstrated a work around.
I am assuming it (works) under any settings and any robots...
Testlund:
Yes, you can can put it on lower priority. This is definitely a bug though. I just tested version Darwin2.46Beta.exe and it works perfect. I'm trying a workaround. Maybe if I load and save the sims in this version first and then load them in version Darwin2.46.02BetaD.exe I might be able to get it to work. :P
Botsareus:
Really? It is that resent? Ok I'll play with it tomorrow, what could have changed between Beta and version D that will cause this? :blink:
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version