I think it might have been a weird install problem, but the FOSE global, and the chicken and egg quests and scripts were overwriting necessary fallout.esm info. Anyone else have that problem? I just cleaned it up in TESEdit.
Hey I know this is a little off-topic, but this seems like the most appropriate (and most active) place to post. Is there any way to change the view of the pipboy camera (like while using the pipboy) so that it can appear closer to the player? It's randomly further away (not b/c of this mod or anything), and I was just looking for a fix. Thanks. Good work on this mod by the way.
EDIT: btw, this could help out errors created when using mods like the Pipboy Readius, which also sometimes messes with pipboy camera...
EDIT2: So I did some poking around in the fallout.ini file, since its the only thing I'd know how to mess around with, and figured out how to bring the camera closer to the pipboy, or Readius, or whatever you're using. Just go into the Fallout3.ini file and under:
[Display]
find the line:
fPipboy1stPersonFOV={insert number}
It was set to, by default, 47 for me. Though the code directly under it said the default is 55. I guess for the real pipboy, b/c using 55 will further distance the pipboy away. I keep it set to 37 (I'm using the Pipboy Readius mod now). I don't know if the value should change if the resolution is different though... but yeah, just modify that line, and you have an easier to read pipboy.
Just to be clear the final result looks like (in my case at least):
fPipboy1stPersonFOV=37
PS: if the up/down axis could be altered, and the pipboy thereby centered a bit better, than you could probably zoom in even closer, since the pipboy is slightly closer to the bottom and not really centered perfectly...
I could do that. As a matter of fact, I just wrapped up a template for an object script which allows for remapping of hotkeys. I could add a bit of code to the camera object so, say '<' is left, '>' is right and '?' is centered, but all three could be mapped to whatever.
Thanks for the interest and suggestion. I'll flesh out the hotkey stuff soonish.
Edit: Check this new, experimental version out? If all goes well, I'll update the main download. Your camera shifting hotkeys are in and then some.
Are you sure it's Automated FOV.esp and have you downloaded the most recent iteration? I just double checked by entering Tranquility Lane and the OA pod (other instances where RemoveAllItems is used on the Player) and got through without issue. I don't have a save anywhere near that point in the game or I'd check MQ09, but the scripting is just like MQ04/DLC02OA1, so I highly doubt the menu item would crash in one instance but not the others.
Chances are, something else is causing the crash.
Evidently, the timing of RemoveAllItems during the abduction is different or ...something as I was able to reproduce said crash after all. New version (1.3) won't crash. Sorry for having doubted my plugin was the culprit.
New version up which will fix that issue (was over the forced removal of the menu item and it trying to replace itself). Also, scoped weapons while aiming might have appeared odd when using non-standard FOV settings. The new version offers an optional fix which will set the FOV to 75 when a scoped weapon is equipped and drawn, then back to your chosen FOV when unequipped or holstered.
shiholude: The overridden records are unreferenced. Use of them will not break anything, so there's nothing to fix in that regard. Use "Build Reference Info" on Fallout3.ESM with FO3Edit and see for yourself...
Persistent CTD in Anchorage, The Pitt and Tranquility Lane all caused by removing camera controller from inventory, quick fix is to flag item as "Quest item / Persistent reference".
Give Feedback
19 comments
Is there any way to change the view of the pipboy camera (like while using the pipboy) so that it can appear closer to the player?
It's randomly further away (not b/c of this mod or anything), and I was just looking for a fix. Thanks.
Good work on this mod by the way.
EDIT: btw, this could help out errors created when using mods like the Pipboy Readius, which also sometimes messes with pipboy camera...
EDIT2: So I did some poking around in the fallout.ini file, since its the only thing I'd know how to mess around with, and figured out how to bring the camera closer to the pipboy, or Readius, or whatever you're using.
Just go into the Fallout3.ini file and under:
[Display]
find the line:
fPipboy1stPersonFOV={insert number}
It was set to, by default, 47 for me. Though the code directly under it said the default is 55. I guess for the real pipboy, b/c using 55 will further distance the pipboy away.
I keep it set to 37 (I'm using the Pipboy Readius mod now). I don't know if the value should change if the resolution is different though...
but yeah, just modify that line, and you have an easier to read pipboy.
Just to be clear the final result looks like (in my case at least):
fPipboy1stPersonFOV=37
PS: if the up/down axis could be altered, and the pipboy thereby centered a bit better, than you could probably zoom in even closer, since the pipboy is slightly closer to the bottom and not really centered perfectly...
Thanks for the interest and suggestion. I'll flesh out the hotkey stuff soonish.
Edit: Check this new, experimental version out? If all goes well, I'll update the main download. Your camera shifting hotkeys are in and then some.
Are you sure it's Automated FOV.esp and have you downloaded the most recent iteration? I just double checked by entering Tranquility Lane and the OA pod (other instances where RemoveAllItems is used on the Player) and got through without issue. I don't have a save anywhere near that point in the game or I'd check MQ09, but the scripting is just like MQ04/DLC02OA1, so I highly doubt the menu item would crash in one instance but not the others.
Chances are, something else is causing the crash.
Evidently, the timing of RemoveAllItems during the abduction is different or ...something as I was able to reproduce said crash after all. New version (1.3) won't crash. Sorry for having doubted my plugin was the culprit.
shiholude: The overridden records are unreferenced. Use of them will not break anything, so there's nothing to fix in that regard. Use "Build Reference Info" on Fallout3.ESM with FO3Edit and see for yourself...
Vault on Infiltration