Weird teleporter problem.

[Testlund]

I was just going to upload a zip here where I caught this error in Safe Mode. Whenever I try to restart DB after that I keep getting "Invalid procedure call or argument". I'll try this drop first and see if it solves anything.

[Testlund]

I'm afraid this drop didn't work. It gave me this:

[Testlund]

Here is the zip file. I decided to zip the whole DB folder. I know that's not what you want but I'm thinking the folder structure is important to see how this problem relates to the teleporters. Just double-click the DB exe file in the "Instance A" folder and you should get an "Invalid procedure call or argument".

The picture shows the error when it occured in Instance A.

[Botsareus]

I will have to revert them changes then. But not today. I am going to go watch the super ball.

[Botsareus]

Ahm, Testlund Ignore most of your PMs on this topic. ' File already open' is a very ambiguous error message. Here is what it actually means:

Code: [Select]

Open "C:\Users\Owner\Desktop\ok.snp" For Output As #1
Open "C:\Users\Owner\Desktop\yo.txt" For Output As #1 'This is the only way apparently to cause "file already open"
Close #1
Close #1
This basically means I am using the same file number for more then one file (as I thought) What I do not know is why my current mod was a complete fail or even if it has to do with the seeding system I started development on.

It is a good thing that you gave me the whole damn DB folder, it gives me things to work with.

[Botsareus]

Ok,

1.) The new tag component I added brakes reverse compatibility, I totally forgot to check for a continue code, lol.
2.) I had to move the saving loading label termination code so it encapsulates the whole routine.

[Botsareus]

Here it is, apparently the test first philosophy has not helped my sloppiness much, If you see any more problems I'll set up a long term and try to catch it. I have your DB directory I can base my experiment off that.

[Testlund]

OK, I will put this to the test. I'll let you know later. 

[Testlund]

20 minutes later... 

You should be able to reproduce this by just loading "A.sim" and "B.sim" and wait until a bot enters a red teleporter.

[Botsareus]

That is a different error then you had before, I am on the right track. 
Spent the day cleaning up the league engine, more Friday.

[Botsareus]

Once I figured out that you can only use file numbers in the range of 1 trough 511 (how quaint) I got the save organism code to work.
Now I only need to figure out why load organism still does not work.

[Botsareus]

Testlund, I have faith in this drop 
Don't mind that the option tabs open up weird, I will reset them later.

[Testlund]

This looks like it might be the real deal; the fix that will take DB to it's alpha state, after 10 years of development. The bots goes through the teleporters as they should.

I'll run this sim through the weekend. Then I'll start a new sim and see how that works. So far this teleporter problem has been very random, so it might take a few tests to be sure.

[Testlund]

The problem is still there. Have you tried to run these sims with all the mutation features enabled? The ones you got from me had these features disabled. I still think this has something to do with the likelyhood of this bug to manifest itself.

[Testlund]

So if I understand this right there were two things that caused problems with the teleporters. The one that I think you fixed with version Darwin2.46.02BetaH that involved file names/access.

The other seem to involve what's being written into the bot files. It looks now like it's the "Epigenetic Reset" and "Normalize default mutation rates..." on the Mutations tab in "Global Settings" that makes the teleporters unable to teleport. The bots just goes in and disappears.