-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Viewmodel FoV is broken #25
Comments
So did I fixed it? |
At FOV at 85, the view model distance does work, however I'm getting interesting issue involving the glow, so far only seen on the PDA and SMG. The glow from their displays creates a 'box' of light that just ends. The only fix I've found right now is turning the view distance back to the lowest setting. The farther away the models are, the more visible the issue is. I just thought I'd bring this up just to insure you're aware of it, if there's no fix then that's fine, I don't mind having my guns against my cheek, but I do like the view models being farther away. |
I'm aware of this bug and sadly haven't found any solution yet. |
I figured that was the case, and it's ok, shame a fix hasn't been found yet, I do like the feature. |
This issue also breaks the Flashlight causing unusual cut off. |
The issue is now fixed with the commit d9626ad. So this issue will close now. |
Describe the bug
The Viewmodel FoV option, either in the options menu or console command, doesn't work accordingly.
To Reproduce
Either go to Advanced Options and switch the Viewmodel FoV or use console command "pm_vmfov".
Expected behavior
It should change the position of your weapon, either further ahead of you or closer.
Instead, only the "light" on select weapons (Machinegun, Chaingun, Plasma) is moved around, not the model itself.
Additional context
I would make this another issue but I think it can go here just fine...
It seems that pressing on the Viewmodel FoV bar in Advanced Options crashes my game, no idea why. I can easily use arrow keys to switch it around though.
The text was updated successfully, but these errors were encountered: