This could be saved in the config (the window dimensions are already part of that, but are currently only changed by the user).

This would combo nicely with #12.

When running the drawing example I noticed that regular (non-agent) annotations are not dimmed when the server disconnects while it seems everything else is. Regular annotations should be dimmed too.

Before server diconnect:

After server disconnect ("helloworld" and "2.0" not dimmed):

This is counter-intuitive, it seems like they should also work when the PlayerControls window is focused. Then the hotkeys could also be put into the button tooltips.

Interestingly enough, it uses the correct icon after moving RoboViz to a second monitor (in which case init() is called again).

The ball already has a shortcut. This would speed up the process of selecting a specific player (which currently involves: toggling player numbers, searching for the agent and selecting it by clicking on it).

Something like:

Ctrl + F1-F11 keys for the left team
Ctrl + Shift + F1-F11 keys for the right team

could work.

Could have a hotkey to open the config window.

RoboViz is using 10% of my CPU when it is idle (not connected to a server). I wonder why. I would expect that it is trying to connect once a second or so, but does not do other things in the meantime.
Ubuntu 12.04

Currently, all dialogs are opened at (0, 0). This is especially annoying with multi-monitor setups, when RoboViz is on one monitor and dialogs open on another.

Shift + F12 could open a dialog that allows you to specify the desired resolution of the screenshot.

Alternatively, the screenshot dimensions could be specified in the config and default to the window size. This would remove the delay that inputting the desired resolution creates, but it removes the option of changing the resolution at runtime.

The FOV is largely based on personal preference.
This could be done via the config file, shortcuts (mouse wheel, up / down keys) or both.

There's nothing about the buttons that indicates that they're clickable - typically there's at least some sort of visual feedback for hovering over and clicking a button.

RoboViz would have to cache the time values of the last 5 or so seconds along with the real time and calculate at what percentage of real time the server is currently running.

This could be displayed as a factor in a textfield next to the game status. The visibility of that text could be toggled via a shortcut (M perhaps).

According to @pmacalpine, RoboViz doesn't work on Macs because of the Java 7 requirement. It wouldn't be too difficult to continue supporting Java 6, the only downsides should be less nice syntax (diamond operators, switch on String, Multi-catch..).

Travis CI can also be set up to use JDK 6.

Reported by @klausdorer. Apparently, this happens on Linux (at least Ubuntu) with a multi monitor setup. Couldn't reproduce this on Win7.

Like x1.5 / x0.5 etc. Currently there are sysouts containing the player fps after a change, which is probably a workaround for something like this.

This could be a JSpinner, removing the need for the "Faster" and "Slower" buttons.

The goal overlays from the entire game will pile up and display if the slider is dragged to the end. Could be fixed by displaying the overlays a set amount of frames instead of measuring the real time.

Shift + drag left mouse might work as a shortcut.

Drawing a vector in 3D could be tricky, would work if it's only on the x/y-plane and z is handled differently or ignored.

This would be very useful to test certain situations like goalie behaviors / goal keeping.

On my desktop computer with a AMD graphics card:

On my laptop with a NVidia card:

Currently doesn't work:

bash bin/linux-amd64/roviz.sh 
Starting RoboViz in live mode
Error: Could not find or load main class rv.Viewer

In some situations, loading a logfile can take a while - during that time, RoboViz is frozen with a white screen and almost looks like it's crashed.

See http://sourceforge.net/p/rcroboviz/feature-requests/1/.

Strangely enough, this is only an issue on linux and works fine on windows.

See this todo.

A tree seems like a more natural / useful representation since the drawing ids are dot-separated and can be grouped similar to packages.

Even if RoboViz is located on a secondary monitor (windows at least).

There might be a workaround to make it look nice even without AA.

See http://sourceforge.net/p/rcroboviz/feature-requests/6/.

Could be done via a flag in the config.

The framerate is extremely choppy since logfiles typically only record every 3rd cycle. This especially affects fast movements like those of the ball when it's kicked.

It's probably possible to do some interpolation between cycles to make the playback a little smoother.

Now that there are five different robot types it would be nice if when just looking at a robot on the screen there was some type of indicator as to what type (0-4) the robot is. This is especially true for types 0 and 2 which have the exact same body dimensions.

In this particular instance, it happened in logmode when moving RoboViz to a second screen on linux. This also seems to be happen on some windows machines right after RoboViz is initially started though.

Would be nicer to provide a more helpful error message like "Unable to receive draw commands - another RoboViz instance is already listening on the same port".

Could be done by drawing the balls path as an arrow while the corresponding modifier keys are held. This would be especially useful for the 45 degree angle option to see whether the ball will end up in the goal.

Quick mockup of what this could look like:

Specifying the log file directly with --logFile is convenient, but currently there's no way to start RoboViz in logmode without specifying a valid log file right away, even though there exists a UI for selecting files with a file open dialog (which some users might prefer).

These two features only being available in live mode might not be a necessary limitation - they would certainly be useful in logmode as well.

• replace the filter text by *
• press the regex button
• run RVTester (seems like there need to be drawings)

Caused by: java.util.regex.PatternSyntaxException: Dangling meta character '*' near index 0
*
^
    at java.util.regex.Pattern.error(Pattern.java:1955)
    at java.util.regex.Pattern.sequence(Pattern.java:2123)
    at java.util.regex.Pattern.expr(Pattern.java:1996)
    at java.util.regex.Pattern.compile(Pattern.java:1696)
    at java.util.regex.Pattern.<init>(Pattern.java:1351)
    at java.util.regex.Pattern.compile(Pattern.java:1028)
    at java.util.regex.Pattern.matches(Pattern.java:1133)
    at java.lang.String.matches(String.java:2108)
    at rv.ui.DrawingListPanel.setListChanged(DrawingListPanel.java:194)
    at rv.comm.drawing.Drawings.fireShapeChangeListener(Drawings.java:96)
    at rv.comm.drawing.Drawings.update(Drawings.java:204)
    at rv.Viewer.update(Viewer.java:379)
    at js.jogl.prog.GLProgram.display(GLProgram.java:72)
    at jogamp.opengl.GLDrawableHelper.display(GLDrawableHelper.java:191)
    at javax.media.opengl.awt.GLCanvas$DisplayAction.run(GLCanvas.java:873)
    at jogamp.opengl.GLDrawableHelper.invokeGL(GLDrawableHelper.java:363)
    at javax.media.opengl.awt.GLCanvas$DisplayOnEventDispatchThreadAction.run(GLCanvas.java:890)
    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:301)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:744)
    at java.awt.EventQueue.access$400(EventQueue.java:97)
    at java.awt.EventQueue$3.run(EventQueue.java:697)
    at java.awt.EventQueue$3.run(EventQueue.java:691)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:75)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:714)
    at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
    at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

Invalid regexes shouldn't be able to crash RoboViz. Ideally, the regex button is greyed out if the regex in the textfield is invalid, and have a tooltip that indicates this.

Currently, camera movement feels extremely slow when zoomed out / far away from the field, and almost too fast when very close. This would help with that.

Goes back to normal after leaving fullscreen mode. Only tested with one of my windows machines so far.

This should be possible for at least the draw commands to make sure the byte buffers are parsed correctly.

B is already used for a "drop ball", and Ctrl + B ("control ball") seems more intuitive and easier to remember than 0.

Player 4 + 5: incorrect rendering
Player 6: correct rendering
Player 9: no shadow

@klausdorer suggested this might only happen since newer simspark versions where the field is bigger, which suggests something about the light frustum coordinates / size could be wrong.

The relevant code is in EffectManager and ShadowMapRenderer.