Will camera stutter with the mouse ever get fixed?

[Not Lee Harvey Oswald]

This has been a documented issue for a while now: https://steamcommunity.com/app/1745510/discussions/0/3271310792394930986/?tscn=1668797062

I'm running at 165hz and the game isn't dropping any frames, but the camera still has this weird stutter to it when look around with my mouse. But there's no stutter when I use a controller.

[Stephen7853]

Originally posted by Traveller:

Originally posted by Lothar:

Thank you JellyPuff I will read the posts on this when I have time and see if any of these fixes help.

I am sorry to hear the problem is even worse at 60HZ, I feel like that should work even if higher refresh rates have problems.

I think FPS or frametime either, plays a role, or covers the issue a bit.

I just now force disabled V sync in my NVIDIA drivers, and capped the game FPS at 500. My monitor is max 144HZ so I am still at that refresh rate. To my surprise the stutters are gone. I think I can still see the weapon model stutter a little bit, but the look and feel is vastly improved. That may explain why G L U E does not see this issue at 240 FPS.

Edit: Nevermind the stutter is still there. I just tried it again and it is back.

Try this, but you should use lower values accroding to your desired framerate:

"If you're using a 60hz monitor and you know how to use BepInEx and UnityExplorer (or some other inspector plugin), you only need to change one variable to fix the jutter:

UnityEngine.Time.fixedDeltaTime = 0.0167"

Works for me.

Does this also fix enemy turn speed slowing down at high framerates? Or just the camera?

Also, I have a 240hz monitor and can confirm the stutter issue's still there when you move with the mouse

[Traveller]

Originally posted by Stephen7853:

Originally posted by Traveller:

Try this, but you should use lower values accroding to your desired framerate:

"If you're using a 60hz monitor and you know how to use BepInEx and UnityExplorer (or some other inspector plugin), you only need to change one variable to fix the jutter:

UnityEngine.Time.fixedDeltaTime = 0.0167"

Works for me.

Does this also fix enemy turn speed slowing down at high framerates? Or just the camera?

Also, I have a 240hz monitor and can confirm the stutter issue's still there when you move with the mouse

0.0167 value is for 60 fps. So if you need smoothness on 240, divide by 4 = 0.004175.

"Does this also fix enemy turn speed slowing down at high framerates?" - I have no idea, since I play at 60 fps.

[Sang-de-brume]

Please guys can someone explain me how to enter those variables ? I managed to install BepInEx and UnityExplorer into the game but I dont know how to find UnityEngine.Time.fixedDeltaTime. I really want to play this game. Thx

[JellyPuff]

Originally posted by Traveller:

UnityEngine.Time.fixedDeltaTime = 0.0167"

Works for me.

Then there really must be 2 kinds of camera jittering issues going on with Lunacid, because this did not fix it for me (60FPS/60Hz). Would've been surprising, if it did though, since locking to 50FPS was never working for me either.

What did work before 1.0 made it incompatible, was a modded "Assembly-CSharp.dll" from the other jitter-thread made by a fellow user. Dunno what it changed exactly, though. Supposedly some physics-related thing(s) to update 120 times a second.

[Lothar]

I tired the DeltaTime fix as well and it didn't seem to make a difference for me.

Originally posted by Sang-de-brume:

Please guys can someone explain me how to enter those variables ? I managed to install BepInEx and UnityExplorer into the game but I dont know how to find UnityEngine.Time.fixedDeltaTime. I really want to play this game. Thx

Here is where I set the value:
https://imgur.com/3FQO4kk

You go to Class and then search for UnityEngine.Time. Select it and then in the "Inspector" window search for FixedDeltaTime. The default float value should be 0.02. But you can edit it from here.

Again I am not sure if this is the correct way to do this. I am kinda fumbling through this as well.

Let me know if it helps you though.

[Sang-de-brume]

Thanks for your kind help ! Sadly it didn't improve anything... I'm really surprised that people can play like that.

[Lothar]

I know what you mean. If I play for a while I don't notice it as much. But if I go play another game with more fluid and precise mouse control, and then come back I totally feel it right away.

It sucks because the rest of the game works great. This is the only issue. Unfortunately it is hard to enjoy the game because of it.

[DAOWAce]

So I have a solution that is a persistent fix and doesn't require editing every runtime, or bepinex.

Grab UABEA: https://github.com/nesrak1/UABEA/releases

Open the globalgamemanagers file. Default path is steamapps\common\Lunacid\LUNACID_Data

You should immediately see in the list an unnamed asset with the type "TimeManager".

Select it.

Click "Edit Data" on the right sidebar.

Change the Fixed Timestep number to something divisible by your monitor's refresh rate. Calculation is 1/#, so for 60Hz it's 1/60 = 0.0166. Play around with this to see if slightly higher/lower values exhibit less stuttering. I found 0.016 better than 0.0167 people are saying, on a 120Hz monitor, and better than 0.0083 which should be 120FPS.

Click "OK"

File - Save.

The fix is now permanent, and will only change if an update replaces whatever file this is stored in.


As usual, the effects this has on the game are unknown.

Juddering may vary based on your game's framerate and change constantly. Have to use a strict FPS capping tool like SpecialK or RivaTuner to eliminate variance in synchronization.

[Emperor's Fist]

Originally posted by DAOWAce:

So I have a solution that is a persistent fix and doesn't require editing every runtime, or bepinex.

Grab UABEA: https://github.com/nesrak1/UABEA/releases

Open the globalgamemanagers file. Default path is steamapps\common\Lunacid\LUNACID_Data

You should immediately see in the list an unnamed asset with the type "TimeManager".

Select it.

Click "Edit Data" on the right sidebar.

Change the Fixed Timestep number to something divisible by your monitor's refresh rate, or whatever framerate you're running the game as. Calculation is 1/#, so for 60Hz it's 1/60 = 0.0166. Play around with this to see if slightly higher/lower values exhibit less stuttering. I found 0.016 better than 0.0167 people are saying, on a 120Hz monitor, and better than 0.0083 which should be 120FPS.

Click "OK"

File - Save.

The fix is now permanent, and will only change if an update replaces whatever file this is stored in.


As usual, the effects this has on the game are unknown.

Juddering may vary based on your game's framerate and change constantly. Have to use a strict FPS capping tool like SpecialK or RivaTuner to eliminate variance in synchronization.

This seems to have done it for me!

[Cavou]

Originally posted by DAOWAce:

So I have a solution that is a persistent fix and doesn't require editing every runtime, or bepinex.

Grab UABEA: https://github.com/nesrak1/UABEA/releases

Open the globalgamemanagers file. Default path is steamapps\common\Lunacid\LUNACID_Data

You should immediately see in the list an unnamed asset with the type "TimeManager".

Select it.

Click "Edit Data" on the right sidebar.

Change the Fixed Timestep number to something divisible by your monitor's refresh rate, or whatever framerate you're running the game as. Calculation is 1/#, so for 60Hz it's 1/60 = 0.0166. Play around with this to see if slightly higher/lower values exhibit less stuttering. I found 0.016 better than 0.0167 people are saying, on a 120Hz monitor, and better than 0.0083 which should be 120FPS.

Click "OK"

File - Save.

The fix is now permanent, and will only change if an update replaces whatever file this is stored in.


As usual, the effects this has on the game are unknown.

Juddering may vary based on your game's framerate and change constantly. Have to use a strict FPS capping tool like SpecialK or RivaTuner to eliminate variance in synchronization.

I can also confirm that this works excellently! It's not a 100% flawless fix, even with the setting at 0.016 at a solid 120 fps capped through Special K, but it's so much of a massive improvement over vanilla. Thank you, DAOWAce!

[NoVa]

Could not get this to work, tried all values listed and others not listed. Refunding. I shouldn't have to modify game files to get a game to work as intended with mouse. Also looking at threads this problem has been around for a very long time. I 100% Support the dev adding pronouns and all the nonsense attention it has gotten for it does not phase me, and I had friends suggest this to me when they didn't know it was already on my wishlist as I love Kings Field (I did not even know it was the root of the souls games, and didn't enjoy a souls game until Elden Ring.)

Unfortunate the steps we have to go through to get things to work properly. And no official statement that I could find about it, and I am not about to delve through a discord to find one.

Leaving this as a negative review on the game. Thanks for trying friends.

[Cavou]

Originally posted by NoVa:

Could not get this to work, tried all values listed and others not listed. Refunding. I shouldn't have to modify game files to get a game to work as intended with mouse. Also looking at threads this problem has been around for a very long time. I 100% Support the dev adding pronouns and all the nonsense attention it has gotten for it does not phase me, and I had friends suggest this to me when they didn't know it was already on my wishlist as I love Kings Field (I did not even know it was the root of the souls games, and didn't enjoy a souls game until Elden Ring.)

Unfortunate the steps we have to go through to get things to work properly. And no official statement that I could find about it, and I am not about to delve through a discord to find one.

Leaving this as a negative review on the game. Thanks for trying friends.

Yeah I've been trying to get Kira's attention to fix the mouse movement since the beginning of Early Access. They fixed the camera movement, but not the viewmodel movement unfortunately. I hope they fix the viewmodel before they stop patching Lunacid.

[Stephen7853]

Originally posted by Cavou:

Originally posted by NoVa:

Could not get this to work, tried all values listed and others not listed. Refunding. I shouldn't have to modify game files to get a game to work as intended with mouse. Also looking at threads this problem has been around for a very long time. I 100% Support the dev adding pronouns and all the nonsense attention it has gotten for it does not phase me, and I had friends suggest this to me when they didn't know it was already on my wishlist as I love Kings Field (I did not even know it was the root of the souls games, and didn't enjoy a souls game until Elden Ring.)

Unfortunate the steps we have to go through to get things to work properly. And no official statement that I could find about it, and I am not about to delve through a discord to find one.

Leaving this as a negative review on the game. Thanks for trying friends.

Yeah I've been trying to get Kira's attention to fix the mouse movement since the beginning of Early Access. They fixed the camera movement, but not the viewmodel movement unfortunately. I hope they fix the viewmodel before they stop patching Lunacid.

They actually did fix it lol but it only lasted for one beta update and was broken again the next week

[NoVa]

Originally posted by Stephen7853:

Originally posted by Cavou:

Yeah I've been trying to get Kira's attention to fix the mouse movement since the beginning of Early Access. They fixed the camera movement, but not the viewmodel movement unfortunately. I hope they fix the viewmodel before they stop patching Lunacid.

They actually did fix it lol but it only lasted for one beta update and was broken again the next week

That means it's not fixed. If it gets fixed I will repurchase

[Stephen7853]

Originally posted by NoVa:

Originally posted by Stephen7853:

They actually did fix it lol but it only lasted for one beta update and was broken again the next week

That means it's not fixed. If it gets fixed I will repurchase

I know, just saying it's absolutely something that the dev can do, but hasn't, or isn't aware that it's broken again.
Also worth mentioning, playing above 60 fps has issues of its own regarding difficulty, cause enemy turn speed is way slower, so even if the camera does get fixed, that's another thing to consider