-
Notifications
You must be signed in to change notification settings - Fork 124
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
2.0 Camera #242
Comments
Had that problem on older versions, but reseting to default and setting free camera move again on "B" solved it for me. |
Just resetting it back to normal then setting free camera move back to b? |
same problem for me, didnt find the solution |
Yep. I have just recently getting this issue like a few days ago. I’m still on version 1.2.1. Sometimes camera is to the left or slightly down. |
Sometimes this is caused by an in game bug where the freecam just doesn't work. That is fixed by resetting to default keybindings and changing it back to 'b'. however that bug only happens between closing and opening the game, not during a playsession. ALWAYS before you start the bot, check that the freecam is working. If its working, and the bot still fails to reset the camera reliably, then its possibly something to do with the bot. |
Same issue for me. I've tried resetting the default keys and then changing it back to B. It didn't fix the problem. |
Yes, i can confirm that the problem persists, i make sure 3 times that the camera is working and still getting the camera on the left side. |
i just cant find the way its not bugging. Every 30 minutes camera goes on :( |
same problem |
Sorry, end of the support. Statement: |
2.0 is working perfectly the only problem is that when is catching a rare fish and shows the animation most of the time won't reset back, sometimes is working sometimes isn't . but i ll say every 30 minutes the bot will stop working as it will not fish anymore as the camera will be facing left side.
Is it possible to edit the amount of they the b button is pressed? or something?
The text was updated successfully, but these errors were encountered: