Buggy debug mode

Fragment of a discussion from Talk:RoboResearch
← Thread:Talk:RoboResearch/Buggy debug mode/reply

Jump to navigation Jump to search

So that's just an argument to the JVM, right? Custom JVM args is near the top of my list for RoboRunner, so I'm working on it now. But there are some things like "-nodisplay" that are arguments to Robocode itself, which wouldn't work because I don't launch Robocode (just use the control API from my own program). So I'd have to add arguments myself if I wanted to let you configure it to actually display battles, for instance.

Nevermind, did some testing. =)

You do not have permission to edit this page, for the following reasons:

The action you have requested is limited to users in the group: Users.
You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

The bug is in [[RoboResearch]], not [[RoboRunner]]. Currently I'm using a custom BattleRunner class which passes the correct argument. It's makes a 2% APS difference in some challenges when using all cores.

I'll try [[RoboRunner]] someday.

Return to Thread:Talk:RoboResearch/Buggy debug mode/reply (3).

Yeah, I know, it just reminded me of the related issue in RoboRunner. It's funny with RoboResearch, I feel like everyone has their own set of hacks in their local instance. =)

Wow, 2% difference in debug mode? That's crazy.

Retrieved from "http://robowiki.net/wiki/Thread:Talk:RoboResearch/Buggy_debug_mode/reply#Buggy_debug_mode_1420"