Allowing Player Motion about fpsci

[bboudaoud-nv]

@jspjutNV has indicated this will not be hard to enable (look at use of setMoveRate() in line 123 of App.cpp though avoiding issues w/ targets in walls is another story. We should also vet whether or not m_userSettingsMode is being used correctly here (allows you to move even when playMode = True up until you close the tab menu for the first time.

[bboudaoud-nv]

A recent commit updates the GUI for playMode=False to allow player motion based on a checkbox. The speed of player motion is not yet controllable. This should also resolve the bug in issue #19.

[jspjutNV]

Let's make player motion controllable as @bboudaoud-nv suggests by having an experiment config parameter that controls the motion speed. We could also expose that value in the devMode GUI (playMode=False).

[bboudaoud-nv]

I've added a moveRate parameter to the experiment config file as of a recent commit.

This now allows designers to set the player move rate in m/s. There are now multiple issues related to when moveRate != 0. For example the player can now spawn, then move past targets, effectively "losing" them in the scene. In addition, since no collision detection with the scene is enabled, the player can easily move through walls/spawn targets behind them. We should consider what sort of minimal subset of features we will need to implement to get this movement mechanic working well/true to the typical FPS experience. Maybe we should create a new issue to track this development.

[bboudaoud-nv]

Should we add a GUI field to playMode = false to allow the user to dynamically control the move rate while in-game?

[bboudaoud-nv]

A recent commit adds support for changing the player motion speed in developer mode (playMode = false). I'm going to leave this issue open since its original "problem statement" includes things like target motion not being dynamic to the (newly) added player motion.

[bboudaoud-nv]

Let's close this issue for now and create a new issue for target motion not being responsive to player motion, as this is another issue altogether