Difference between revisions of "Thread:Talk:Gilgalad/Minibot?/reply (10)"

From Robowiki
Jump to navigation Jump to search
m (Reply to Minibot?)
 
m (fotmatting)
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
Yes, I run 2 clients. More pacifically 2 machines, both of which run roborumble and meleerumble, one of this additionally runs meleeTop30. As far as I can see, they have identical relevant software configuration.
+
Yes, I run 2 clients. More specifically 2 machines, both of which run roborumble and meleerumble, one of this additionally runs meleeTop30. As far as I can see, they have identical relevant software configuration.
  
I will try to isolate a problem. I left running only one computer with meleerumble and roborumble. Let's see if the currently running is a guilty one.
+
I do not get it: microrumble and nanorumble seems to be fine with either of the clients, but minirumble is populated with megabots. Any idea what is going on?
 +
 
 +
As fat as I see after some tests, it is not a particular client issue. At start up, either of the clients cleans the mess, i.e. removes bogus entries. But then as it runs, it reintroduces them.
 +
 
 +
Also, both clients complain:
 +
Could not load properties file: ./roborumble/files/codesize1v1.txt
 +
 
 +
I will report it to Fnl again.

Latest revision as of 18:48, 6 September 2014

Yes, I run 2 clients. More specifically 2 machines, both of which run roborumble and meleerumble, one of this additionally runs meleeTop30. As far as I can see, they have identical relevant software configuration.

I do not get it: microrumble and nanorumble seems to be fine with either of the clients, but minirumble is populated with megabots. Any idea what is going on?

As fat as I see after some tests, it is not a particular client issue. At start up, either of the clients cleans the mess, i.e. removes bogus entries. But then as it runs, it reintroduces them.

Also, both clients complain:

Could not load properties file: ./roborumble/files/codesize1v1.txt

I will report it to Fnl again.