I tried reading the Rate from MouseAxisInputFunction with an AddOnScreenDebugMessage().
Initially it displays the Rate accurately even when Im not holding the mouse button down.
Which does suggest I can apply it in the Tick().
It continues to displays the Rate accurately while I am holding the mouse button down.
However, after I release the mouse button it displays 0.0 regardless of what my mouse is doing, until I once again hold the mouse button down.
The AddOnScreenDebugMessage() is the first line of code within the MouseAxisInputFunction and is NOT subject to any kind of an if/then filter.
So it should be displaying the actual axis value, which means it would be 0.0 regardless of where I apply it.
(unless you are talking about a different method of reading the axis value?)
I no longer think the problem is with the camera control code.
I suspect there is some kind of viewport focus shenanigans going on in my UI I have to fix, but have no Idea what could be the culprit.
Thats why I asked what opening the console does, as I thought maybe if I knew it could narrow down the search.