If you encounter a bug, please fill out the bug report form. Provide a detailed description on how to reproduce the bug. Attach log files located here: "Cyberpunk 2077\bin\x64\plugins\cyber_engine_tweaks\mods\ImmersiveFirstPerson\ImmersiveFirstPerson.log" "Cyberpunk 2077\bin\x64\plugins\cyber_engine_tweaks\scripting.log" If logs are too long, publish them on pastebin.
Keep in mind, every time the game is updated, it takes a couple hours for CET to update as well.
The new mod version requires to modify one of the game's internal configuration files. If there are no other mods that modify it, then it should be perfectly fine. This does not reset or modify your game settings and keybindings, those are somewhere else. This modification lowers the minimum allowed mouse sensitivity from 1 to 0. This is necessary for the FreeLook to work correctly, otherwise the character will slowly move with the camera. If you don't use FreeLook, feel free to not replace the options.json file. I'll be looking into ways to work around the issue, but for now the file will be replaced.
You can also update the file manually, if you don't want to replace it. To do this open r6/config/settings/platform/pc/options.json file, find "FPP_MouseX" option and look for "min_value": 1.0 line, change 1.0 to 0.0. Do the same for "FPP_MouseY" and you're done. Here's an example
Immersive First Person only changes the first person camera. Invisible body, wrong body models, missing on-foot radio, and any other issues not related to camera — ARE NOT RELATED TO THIS MOD. Please, stop reporting it.
if your torso turns invisible, try changing some appearances at the mirror. CONFIRM THEM. Then look down and see if it worked. It should've. I had a body mod, and after the update and getting a different body mod, this is what worked for me. The problem is not this mod itself. Hope this helps :)
Can we get a version without the free look function?
The core is done wayyy too early in 2021 when people didn't know much about modding, and the coding is really problematic. I don't even know lua and there's easy tells everywhere, such as duplicate tracking of mouseY, checking x = nil when the statement modifies y, etc... Also there's a s#*! ton of accesses to mod specific files and fpp (which is I think why getting on cars or using TPP mods are so problematic) that might not be always available, but zero try catching for errors before using them as function params.
There are literally hundreds of reports of crashes and bugs. And when I try to run the lua scripts thru copilot theres dozens of red flag all across the board. This free look BS needs to separated out or fixed. Deprecate its functionality even, not much people need the dynamic free look pan speed code, or the free look snap back transition for example.
I know you prob meant this sarcastically, but I actually do have a question: In the helpers.lua the isClimbing function returns the enum for the .Carry game state. Is that intentional, like does the blackboard not have a climbing game state or is this better?
I noticed people in comments having issues when climbing a ledge holding a weapon which messes up the mod, I was wondering if that was the issue. I had no idea where the blackboardDefs are or what the states names are, so I changed it to return .Climbing with a try catch for now.
If you are trying to get someones help, maybe don't start off by assuming their intent to be negative. There is zero chance he feels motivated to help you after that opening. Just be nice, it'll go a lot further, and he might actually want to help you, because you came at him in a positive way vs a negative way.
What we say matters, especially when we seek altruism.
Now imagine how much worse my comment would have come off if I started it with. "I know you are probably going to ignore this."
...but you'd be grumpy too if u spend 2 hours in this files' codes, and figuring out you might be crashing because he checked x twice and y 0 times).
Now seriously tho I'm prob only tilted because this brings back the pain of doing CS hw in college. And later fixing mine and others' CS hw in college. So yeah this was "unprofessional" of me to bring personal emotions into a free mod comment, and sorry for that.
> This free look BS needs to separated out or fixed. Deprecate its functionality even, not much people need the dynamic free look pan speed code, or the free look snap back transition for example.
You have sources for how many people use the free look "BS"? Impressive, care to share them?
> ...but you'd be grumpy too if u spend 2 hours in this files' codes, and figuring out you might be crashing because he checked x twice and y 0 times).
Yes, but I wouldn't write what you wrote. I would be grumpy inside but not be stupidly arrogant on Nexus because I know that installing mods comes with the risk of instabilities.
"Deprecate its functionality even, not much people need the dynamic free look pan speed code, or the free look snap back transition for example." You have no idea what I'm talking about do you, go get urself a rick text editor and look at the damn code. There's a ton of QoL code that is appreciated, but weights the mod down when it is not stable. E.g. the smooth/dynamic curve transitions which are known to cause problems. Also if you've look at the code you would realize that the mod has too much effort invested in either the freelook or the camera control alone be well able to run in 2 separate option files.
"I would be grumpy inside..." Yes yes, now don't go get yourself a depression, you can deal with ur little instabilities, well I fixed the damn problem. (Actually this is just the point of the argument, I haven't had any problems with the mod since but I have no idea if I fixed it or is the previous crashes just not this mod related... I guess I'm not even sure how to confirm, as everytime I compile the crash dump Visual Studio just point to some random nonexistent virtual ram address that I do not own the skills to pin point back to when it existed?)
Is it possible to create a delay between moving the gun and moving the screen when I move the mouse(Input lag / camera inertia)
Someone had created this Reshade preset for Stalker 2, but I cant get it to work with Cyberpunk. This mod made firefights even more immersive and intense.
I would love to see it implemented in Cyberpunk.
It seems like you have the skills to accomplish this.
This mod works when my FOV is at or lower than 80 and doesn't work above it. I'd like to play it at a higher FOV but it doesn't work past a certain value. Is there any way to change this?
курсор начал постоянно сам по себе двигаться вверх . При этом движение по горизонтали работает хорошо. А вот по вертикали блокируется и само движется вверх . перезагрузка помогает мин на 5. наигранно 70 часов этот баг впервые
Hello to all users! Problem: When looking down I see the model and textures of the vanilla body. JB - TPP MOD WIP returns a custom body, but the game crashes from any sneeze. Question: What did you do in such cases? List of mods, maybe there is something extra here? https://pastebin.com/m3vyxcSu List of Archive sequences: https://pastebin.com/QyeDrn6s
Heho, I really enjoy the mod! I am using it together with first person camera and while its working fine with no crashes there is some sort of "shift" or "snap" when I look down. Do you know of any fix to prevent this? I cant get a similiar setting with the FPC mod unfortunatly without setting the camera so far back that every other weapons feels like zooming in.
1265 comments
If you encounter a bug, please fill out the bug report form.
Provide a detailed description on how to reproduce the bug.
Attach log files located here:
"Cyberpunk 2077\bin\x64\plugins\cyber_engine_tweaks\mods\ImmersiveFirstPerson\ImmersiveFirstPerson.log"
"Cyberpunk 2077\bin\x64\plugins\cyber_engine_tweaks\scripting.log"
If logs are too long, publish them on pastebin.
Keep in mind, every time the game is updated, it takes a couple hours for CET to update as well.
The new mod version requires to modify one of the game's internal configuration files. If there are no other mods that modify it, then it should be perfectly fine. This does not reset or modify your game settings and keybindings, those are somewhere else.
This modification lowers the minimum allowed mouse sensitivity from 1 to 0. This is necessary for the FreeLook to work correctly, otherwise the character will slowly move with the camera. If you don't use FreeLook, feel free to not replace the options.json file.
I'll be looking into ways to work around the issue, but for now the file will be replaced.
You can also update the file manually, if you don't want to replace it. To do this open r6/config/settings/platform/pc/options.json file, find "FPP_MouseX" option and look for "min_value": 1.0 line, change 1.0 to 0.0. Do the same for "FPP_MouseY" and you're done.
Here's an example
The core is done wayyy too early in 2021 when people didn't know much about modding, and the coding is really problematic. I don't even know lua and there's easy tells everywhere, such as duplicate tracking of mouseY, checking x = nil when the statement modifies y, etc... Also there's a s#*! ton of accesses to mod specific files and fpp (which is I think why getting on cars or using TPP mods are so problematic) that might not be always available, but zero try catching for errors before using them as function params.
There are literally hundreds of reports of crashes and bugs. And when I try to run the lua scripts thru copilot theres dozens of red flag all across the board. This free look BS needs to separated out or fixed. Deprecate its functionality even, not much people need the dynamic free look pan speed code, or the free look snap back transition for example.
https://github.com/cp2077/ImmersiveFirstPerson
In the helpers.lua the isClimbing function returns the enum for the .Carry game state.
Is that intentional, like does the blackboard not have a climbing game state or is this better?
I noticed people in comments having issues when climbing a ledge holding a weapon which messes up the mod, I was wondering if that was the issue. I had no idea where the blackboardDefs are or what the states names are, so I changed it to return .Climbing with a try catch for now.
What we say matters, especially when we seek altruism.
Now imagine how much worse my comment would have come off if I started it with. "I know you are probably going to ignore this."
Food for thought.
...but you'd be grumpy too if u spend 2 hours in this files' codes, and figuring out you might be crashing because he checked x twice and y 0 times).
Now seriously tho I'm prob only tilted because this brings back the pain of doing CS hw in college. And later fixing mine and others' CS hw in college. So yeah this was "unprofessional" of me to bring personal emotions into a free mod comment, and sorry for that.
You have sources for how many people use the free look "BS"? Impressive, care to share them?
> ...but you'd be grumpy too if u spend 2 hours in this files' codes, and figuring out you might be crashing because he checked x twice and y 0 times).
Yes, but I wouldn't write what you wrote. I would be grumpy inside but not be stupidly arrogant on Nexus because I know that installing mods comes with the risk of instabilities.
You have no idea what I'm talking about do you, go get urself a rick text editor and look at the damn code. There's a ton of QoL code that is appreciated, but weights the mod down when it is not stable. E.g. the smooth/dynamic curve transitions which are known to cause problems. Also if you've look at the code you would realize that the mod has too much effort invested in either the freelook or the camera control alone be well able to run in 2 separate option files.
"I would be grumpy inside..."
Yes yes, now don't go get yourself a depression, you can deal with ur little instabilities, well I fixed the damn problem.
(Actually this is just the point of the argument, I haven't had any problems with the mod since but I have no idea if I fixed it or is the previous crashes just not this mod related... I guess I'm not even sure how to confirm, as everytime I compile the crash dump Visual Studio just point to some random nonexistent virtual ram address that I do not own the skills to pin point back to when it existed?)
Someone had created this Reshade preset for Stalker 2, but I cant get it to work with Cyberpunk.
This mod made firefights even more immersive and intense.
I would love to see it implemented in Cyberpunk.
It seems like you have the skills to accomplish this.
(Fake) Free-Aim at S.T.A.L.K.E.R. 2: Heart of Chornobyl Nexus - Mods and community
You need change your BODY GENDER in save editor
Female -> Male -- and save changes, then swich back Male - Female
Problem:
When looking down I see the model and textures of the vanilla body.
JB - TPP MOD WIP returns a custom body, but the game crashes from any sneeze.
Question: What did you do in such cases?
List of mods, maybe there is something extra here?
https://pastebin.com/m3vyxcSu
List of Archive sequences:
https://pastebin.com/QyeDrn6s
I am using it together with first person camera and while its working fine with no crashes there is some
sort of "shift" or "snap" when I look down. Do you know of any fix to prevent this? I cant get a similiar setting with the FPC mod
unfortunatly without setting the camera so far back that every other weapons feels like zooming in.