Hello. I just thought I'd share a few thoughts on the current, (Beta opt-in), state of Fallout 4 since I've been playing with FO4 for awhile now, and spent some time looking at the Beta, and a few other things.
1. Modless - There are some things in Fallout 4 for which people have developed mods, but which should not need mods developed for. Some of these mods may seriously deprecate performance due to the add-on nature of them; mostly due to BSA2 texture handling, additional handling, etc..
Foremost of these for me, are things like water reflections/Fake reflections. I have recently made the swap to a much more realistic solution, and yet, I feel I really shouldn't have to. When I approach a Fake reflection in game from a puddle or something, I see a glare-rich, icy surface from all glancing angles. Usually with Blue sky and clouds reflecting in it from directly overhead if I am standing on it. Even underground. There are actually 2 mods which combined fix this.
Cubemaps. I dropped a bunch of these files into a backup folder and found fixing the glare issue boiled down to just a few cubemaps. You don't even need the additional work-arounds, which I also dispensed with; though it doesn't produce quite as nice of reflections without. The replacement maps aren't even big. Unfortunately it has other issues which produce some odd visual effects like Grey Mr. Handy. I'm sure that could be dealt with, but regardless, have to wonder why this isn't just patched.
I'm not sure why the Sky reflects in underground puddles, aside from that it is reflecting worldspace in the engine, and possibly someone forgot to block it. I assume the mod which fixes this flags the puddles to prevent this, or something. I haven't delved into the why or how really; just made observations on the result. I use Post Processing too, which can make the effect better or worse depending on the settings.
Next, I think I'd have to look at simplified Post Processing used to improve the visual quality/fidelity of the game without adding any extra features or effects. I use Post Processing just to improve the base quality, over Ultra settings, with all the various effects enabled. Without it, I have a washed out, blurry/undefined view; where with it, I can see what I'm looking at. I think it's great that the game has a visual style; I just find it hard to appreciate when that style suddenly makes it impossible to identify what I am looking at, and requires me to add post processing to make it easier to identify.
By doing this I am actually decreasing performance. Recently, with the new Beta, it seems performance is seriously deprecated as a result. I'm getting 16 ms frame renders without, and 33 ms frame renders with, when the post processing effects-together-take less than 1 ms. This tells me the frames are rendering twice. Once for the base game render, and again for the post processing. At least, I assume. I've never looked at it until I saw the FPS drop after the Beta opt-in. Over 10 FPS, and sometime 25 FPs drop.
By comparison, before the Beta Opt-in, I was getting an average of 57 FPS with the post processing enabled in all areas I checked. I have add-on textures, so this could be increasing each frame render time to such an extent that the combined render time causes a significant difference. I'm not sure, but I have seen my FPS drop to as low as 14 today, in a fog, and this is consistent in the vault, which I think still uses all Vanilla textures. I actually took a guess when I checked the files and assumed maybe it was the Cuda driver I had never seen before, but I haven't thoroughly tested, (i.e: not yet opted out to do a performance check). Quite possibly this means the post processing drivers will need an update.
Regardless, unless you want something 'special', this shouldn't be needed.
Aside from that, there are some special cases:
- Power Armor HUD colors: The Pip Boy and base HUD/Interface both have the option to color shift; why was this not included? It is orange-yellow, and in my opinion absolutely horrid to have in your face while in PA. I actually spend much less time in PA because of it, and recently downloaded a replacement. I've not even looked at it yet, but assume it will be an improvement. I see no need to change the actual dash, which is btw influenced by opacity shifts iirc.
- Options: NVFlex I enabled this today just to check it out. It works, and it has next to no performance loss on my system. It's actually kind of cool, even if it's a bit odd that a cooler which drops paint/enamel pieces, or a bottle which drops shattered glass doesn't have damage after/during. You can see the radius on water as you move away from the location of disturbance. Not as a loss of particle effects, but as a blue ring which follows you around.
Why can't I enable it in options? I have to edit a file to use it, when I am aware that file will likely be written over at some point. Same with particles max. I have added these to Custom, but not tested to see if it works there. I know some things don't, and generally assume these won't.
Other options. I just think the list should be longer, and Custom should be used more/where the changes are written to and pulled from. It would make sense. I don't use the 3rd party solution. Among these, I think should be disabling Bloom, enabling HDR, and disabling DoF entirely. Just to be friendly to those who like to use post processing, because-lets be honest-they conflict.
- HBAO/SSAO: Currently these need to be tweaked in the files to make more effective. I'm not sure this results in more realistic effects. What I have noticed is that I can barely tell when either is in use. They are extremely limited in actual effect from what I have observed turning them on and off and switching between them, and I am not a fan of excessive use of various effects, including these. Still, they are an improvement, if only barely noticeable. My experience suggests they need tuning to make them more realistic, and obvious, but it may also stem from another problem.
- Tuning performance. Something odd I noticed about FO 4 is that moving between performance settings makes next to no difference, even when you are suffering performance issues. I've noticed it with other games too. Maybe it's just my system, but I can move between the highest performance options with no change in frame rate quite often, or at most 1 FPS difference.
More specifically, and aside from such observances, wouldn't it be nice if tuning performance actually increased the output of various effects? I think so. For example, does it take more or less performance to render 5000 particles, or 500 particles? More generally, (although NVFlex doesn't seem to care at that particular number). These aren't tuned by moving through the base quality settings from what I've observed, and yet I think they probably should be. Save people messing with all those numbers in files they shouldn't even need to access 90% of the time.
I actually seemed to have gained 2-3 FPS just by dropping particles from 750 to 500. Makes no difference without Post Processing, (59-60), but with the current issues it takes it from 24-33 to 29-37 with that and some other things, even with NVFlex enabled.
2. The Game:
- Minutemen side quests and radiant quests. I can literally pass Preston 5 times in 2 minutes and get 3 quests from him. This is not quite infuriating. Just dropping this to 1-at-a-time would be amazing. And that includes when there is a main quest active, such as Tenpines, because it is basically the same thing. I don't need to have to deal with 3 radiant quests, Tenpines, and Olivia Station all at the same time. I don't think anyone does. It actually gives me a false sense of urgency for all of them, when it should be some sense of prioritization. Impending doom of multiple settlers, with immediacy, in 5 different locations in opposite directions kind of messes with that however.
- LOD popping. I experienced this so little I thought it was someone elses problem when I discovered it. Turns out if you stand on the pointy rock, or to the East of it, on or above the platform at the top of the stairs, above the Quarry pit, the trailer yard and mire just become a square of water LOD, and everything else vanishes. This is a bug obviously. It is not present from any other location I am aware of.
- Movement in Scope. Okay, I understand this, but it's an issue. Create a deadzone for this please, because when you hold down L3 on the Gamepad, you walk off cliffs, building, etc.. without even knowing it, while shooting hundreds of rounds at things like Death Claws. Seriously, that thing is insanely tough on Normal, and it runs away unless you are on the ground. I spend an average of 1 hour killing it in Concord, because getting on the Ground with it always results in death if you are in the open. It just rips the PA to shreds and you with it. Kind of tedious.
I should only move when I've pushed the L3 down and rocked it more than 50% from center. If L3 isn't down, it should be normal. This can be a little erratic at times too, but that's I assume the scripts in the background, current load on the CPU.
- Detection and Following. Sure, NPCs getting after you and then becoming distracted makes it really easy to just knock them all down with a bit of planning and almost no risk... They actually take a shot from a 308, wander around for a ~20 seconds looking for the attacker, then go back to strolling amiably. This is not normal behavior. Even if they can't find me they should go to cover, and so should anyone else in their vicinity that has been alerted. At the very least.
On the other hand, I've had NPCs chase me quite a distance when I've been spotted. Leaving all help and support behind even. This is basically fine except, lets face it, running off cliffs, ledges, buildings, church steeples and the like, and falling to their death is a bit excessive. They will jump off the Corvega plant just to get a shot at you if they don't have the angle on it. Maybe not a great idea. It was amusing dodging the falling Raiders and watching them go splat though.
The AI is kind of dumb, in a nutshell. The only mod I've found that tries to deal with this also ends up causing convo's to be broken because of increased detection distance, and I assume also results in near enemies hostile to each other killing one another long before you even know they're there. Maybe that should happen anyway, or would normally, but it's not really intended.
3. Other:
The textures. I'm not sure if this was rush-rush, or what, but I've noticed some things.
- The UV Maps are being tricked in in some cases. This basically means the textures for those UVs have been over-sprayed to account for them not being quite on with the UV stitching on the mesh. Not sure why, but I recall that weird bar-spectrum texture on edges of a number of textures.
Does this also mean the Normals are out? I'm sure it's not every case, but there is another problem with this: Texture replacement and Texture load/optimization. If I were to create a new texture from existing, I would literally need to grab a normal, black out between the normal to create a mask, move that to the diff, and then see what I had to work with. Great, but now I also have to consider black areas being on the model because the UV Map is off. I may be wrong but the supposedly untouched, up-res'd textures I've seen were almost solid. That is, they were sprayed from one side to the other with brushed on scratches, colors, etc..
Very artistic I guess, but think of the unused detail going into the texture files. How much wasted space when it could just be black? The Chinese Sword is a great example. One in which I can't even identify where the UV Unwrap begins and ends, or even what it is actually supposed to be. I have no idea, and I at that point understood suddenly why so many people have just made matte black textures for things. Everything. Looks awful btw.
Anyway, just some thoughts, critique, etc.. I'll add more if I think of it.