Accuracy of fps when in VR after changing the engine.ini systemsettings
When testing out my maps without adding the defaultengine.ini system settings from Epic the visual effects of the low framerate reported by my counter are representation of low framerate. So a framerate of less than 30 provides a very hideous experience.
However by putting in the systemsettings changes the VR experience is completely stable even at 30fps. Whilst this is great in terms of how effective those settings are. Is it possible that the framerate I am getting is now only reporting an editor value and not reporting an effective value for VR?
So in the case of only getting 70fps reported in VR and this is in game. Where would you now draw the line if it seems completely stable?
asked Mar 15 '17 at 12:18 PM in VR
Follow this question
Once you sign in you will be able to subscribe for any updates here