In my first-person game the player spends a lot of time selecting various objects via a mouse click, then seeing a GUILayout list of buttons and then clicking one with the mouse pointer.
When there is no menu showing I use a crosshair texture in the centre of the screen to show what you are pointing at while moving around the game world. Selectable objects change colour when they are under the crosshair, showing the player that they can click them to get the context menu.
When the context menu appears I lock the mouselook, make the mouse pointer visible and wait for the player to click a button. When they click a button, the menu disappears, the mouselook becomes active again and the mouse pointer is hidden.
But this constant hiding and unhiding of the mouse pointer is a bit irritating. Is it viable to have a different method of clicking the buttons, for example by allowing the use to mouselook the crosshair texture over the button and then get them to click it. The menu would have to dart around the screen in response to the mouselook until the player got the button they wanted under the crosshair.
Would this be motion-sickness inducing and rubbish? If yes, what else can I consider. If not, does anyone have a script to show how I need to move the buttons around?
Thanks