Leaderboard

I have no solution as of yet, but i do know that the camera slowly shifts up or down (mostly down) and it seems related to the aiming animations, cause they hold camera position info for the guns. What i also know is that when Bethesda's gamebryo engine goes above 60 fps, you are going to get nasty bugs in the game, every single Bethesda Gamebryo game does it. So making sure the FPS never reaches 60 fps would ensure it won't happen, someone said 54 fps limiter, but 56 is also good, cause every limiter has a slight variance in framerate, so if you'd set it to 58, it would occasionally touch 60 fps, and then it can happen again. It looks to me like the animations are not completely played out and blend into the next iteration too early, but i also know that when it starts you only have to aim and move your mouse up and down and you see it drop down pixel by pixel with every move you make, and it only stops when you limit your fps again below 60, i tested it with ENB limiter, cause you can enable disable that while playing. Also, if you play for a while without limiter, after a while in first person you get smaller and smaller, but if you then go into 3rd person you see that the player's scale is ok, it's just that the first person camera has dropped. It isn't related to stutter remover, cause if you limit your fps with other software then stutter remover, it works fine too. It is most likely a Gamebryo fault, so you'd have to device a workaround for that, as in, control the position of the camera, someone like the guy from enhanced camera could probably make that happen in a fose plugin, or you might be able to edit the animations and remove the camera positioning from the animation or something like that.

Not yet - the mod seemed to be used to make the first person shoot-from-hip model follow the pointer tightly rather than being anything to do with RH_Ironsights. I will set the fps clamp back to 60 tomorrow and try this though. I am still trying to track down my hitching issue. It is not graphics related as I found when I set up a new profile in MO. I got perfectly smooth turning and movement with ALL model and texture mods enabled but all gameplay, location and so on mods disabled. I am wondering since it occurs indoors and out when swinging the camera if it is a script going mental under certain circumstances and the main thread being too busy to cater for it. No idea how to track it down since it is not dependably reproducible.

Been testing stuff for a few days, FNV and FO3's Stutter remover suffer from the same problem, when (in the older version) bFix64Hertz = 1 or (in the latest version) GetTickCount = 1, the camera starts to drop IF your FPS is the same as your monitor's refreshrate, if they differ, the camera stays aligned at all times. If you disable the gettickcount, the camera will never go out of alignment but you get microstutter. The solution i have found acceptable for myself is to set gettickcount to 1 and set my monitor refreshrate to 50Hz, and my Fps cap (in stutter remover ini file, NOT in ENB or AMD settings !!) to 60Fps, then it's almost smooth, and you have a tiny bit of screen tearing (not really tearing but it looks like it a bit) fixed 1 cm on the bottom of your screen (more like a tiny line when you move around). I posted my findings on stutter remover site, cause Ironsights have nothing to do with it, Vanilla Ironsights animations (the ones that just adjust FOV, not really ironsights but the animfiles are named with a is suffix) are also bugged as in, the camera shifts there too, so it has nothing to do with RH's Ironsights mod, it's purely a stutter remover problem.