[Fallout 4 Weapon Switch Delay Fix
Kody Coste
I know it has nothing to do with any mods people that run the game completely stock has the problem. And I know quite a few people have said useing the optimized vanilla textures mod helps a little bit but it still happens.
I have a bug with the quick select stuff. I use a gamepad and when using the d-pad weapon select to change from one thing to another it takes 5 seconds or so to equip the new weapon. In a fire fight when I want to put my rifle away and switch to a shotgun for close range, it's super annoying because there are some enemies that close the gap really fast.
Huh seems like for once there is an issue I don't seem to have. Either I don't have this problem in my game or I just don't notice it. Is it worse in one game than another..? And was the issue fixed in FO4 or does the issue happen in that game too?
As far as I know this bug is only in Fallout 4. It also depends on how far in to the game you have gotten. Pretty much everybody that has this problem says its not there at the start of the game but the longer you play/farther in to the game you get the worse it gets. But also I have read not everybody has this problem. But more people do then don't.
I've encountered problem too, but with over 200 hours it hasn't gotten worse for me. If you're afraid of your weapons not coming out fast enough I suggest switching between them after fast travelling to a location so the game is forced to load them.
Hey everyone i know im not the only one whos experienced this before but there are numerous steam posts talking about this issue. the problem is switching weapons may or may not always work sometimes it can take up to 5-10 seconds to switch weapons and this is annoying during fire fights and when fighting the legendary bullet sponges i have yet to find a mod that fixes this and i was hoping to find some insight on this issues. thanks for reading.
In my first playthrough, soon after release, I ran all sorts of HD texture mods including weapons ones (my rigs not the best, but it is pretty good - specs on my profile page- and installing HD graphics is my typical first move with any beth game... until this one) and the constant, sometimes seemingly endless, hotkey/ weapon switch delay drove me absolutely batty. One of the reasons I quit playing, really. And I noticed that the delay was worse in graphics-intensive areas, like in the middle of a downtown firefight, as opposed to where there's not much going on graphically like when you're out in the wilds setting up a sniper position.
This time around, I've really toned down my HD graphics (with, alas, no weapons HD graphics) and the delay isn't even remotely close to being as bad. (Was it fixed in whole or in part by a Beth patch in the meantime? Impossible for me to say.) But, for sure, the delay is ALWAYS worse if I'm rocking some amazing HD-textured mod-introduced gun as opposed to a vanilla weapon. If I'm just switching between vanilla weapons (again, I'm using vanilla weapons textures), there's virtually no delay. For example, I ditched an amazing gauss rifle retexture (despite hating the look of the vanilla gauss) because it just delayed switching too much. And I gave up on the utterly amazing RU556 assault rifle mod because of the consistent extra couple seconds that it introduced to hot key switching. That said, I am using the SCAR-LK assault rifle mod (original version) as, compared to the various other gun mods I've tried, its delay isn't too bad and is worth the extra badassery the gun brings. The R91 assault rifle was pretty good too. (Note that I really haven't tried a ton of gun mods so can't really give a wide range of exprerience. Note also that I don't have an SSD, although I personally can't see the hard drive coming much into play on this issue.)
Can't believe i just found this out, mashing the number key you've assigned the gun to (instead of just pressing once) will mitigate the issue most of the time. Quite embarrassing as i have just over 1000 hours in the game.
So i've already made a thread on the r/Falloutmods sub, and whilst I got replies, i figured why not get some input from more modders that most likely have closer 'fields of expertise' at this, than I do.
"If you don't know what i'm talking about, it's the issue when you switch weapons and it takes longer than usual to load them in. On my 1gb HD 7750 (mind you, game itself runs fine) it's pretty bad, having to wait 3-10s randomly - thankfully it's relatively uncommon for me.
It's purely an I/O latency issue (probably coupled with some performance deficiency in the engine code that we can't do s*** about). Everyone who archives his mods that would install loose files into ba2 archives has seen noticeable decreases in the frequency of the issue appearing, most see it disappearing completely.
If you were to try to build a workaround, I could imagine a script that periodically, every few seconds, spawns one of all of your carried but not equipped weapons behind the player and immediately deletes the reference again. This should keep all the gun asset data in fast memory. It does cause additional load on the engine though and possibly makes it worse in a different way.
I used to think it was slower to have an archive, my reasoning being that it would take longer to load in a ba2 file and extract it, but that's not how it work evidently. It would seem if your esp has an archive it will drastically shorten the lookup latency, like it tables the contents of it individually, and especially if it's a small archive.
This is precisely the case. People have been making performance experiments using ba2 files and they're essentially always faster than loose files, apparently because the application handles all I/O by itself rather than going through the entire OS I/O stack. BA2s are faster even if not compressed.
When I set GTA V to run in fullscreen, and if I switch between the game and the desktop, the screen goes black for around 2 seconds, then it recovers. BUT GTA V doesn't freeze if I press W while the screen is black, as I notice that the car in the game starts moving.
If GTA V was in windowed mode and if I switch between the desktop and the game, the screen would not go to a black screen. If press Alt + Enter (to make it fullscreen), it would go to a black screen. I don't know what is the problem.
This is very normal. Running in windowed mode and full screen mode are two very different environments. When in windowed mode, the application runs like any other windows program. When running in full screen, you pc "dedicates" the machine as if that is all thats running. Obviously stuff is still running in the background on the OS, however the way the drivers and such act is different. Upon switching from a windows application back to your screen, all of that has to re-initalize and those few seconds of black screen is the result.
The graphics thread on the other hand has a lot of work to do. It has to set up the entire graphics pipeline from scratch. Textures have to be loaded, shader programs have to be compiled and started on the GPU, and the various shader stages have to be pipelined together. This bring up will take some time, the largest time is probably loading in the textures.
On a single threaded program all of this setup would have to be done before the program accepts any keypresses and would delay your time to get moving, but in a multi threaded program these two things can happen at the same time. Obviously if one thread is ready before the other though you will get this "odd" sort of behaviour.
The differences between full screen and windowed modes is that in fullscreen mode the application assumes it has full control when in focus and when not in focus you do not want it to "hog" resources. Windowed modes are generally for when you want to switch between the game and Windows quickly and not unload the graphics data. Windowed modes are usually slightly slower than full screen, but have no delay when alt-tab is used to escape the program.
This fixed it for me. This leads me to believe that fullscreen mode may have problems dealing with overlays. So if for example you don't have a NVIDIA GPU (which would mean you don't have GeForce Experience) look for any other overlay, that you are currently using. Disabling them could be the answer to your prayers.
This happens as the game you are playing is disabling the graphics thread in order to save resources while you are not playing the game. This takes a second or two and after this is completed your GPU starts rendering the desktop or other windowed app (and not before).
You can avoid this by setting your game to "Windowed" or "Borderless Windowed". You can usually find this option somewhere in the game settings, and Borderless Windowed looks the same as fullscreen but acts as a window, so if you alt-tab out of it, it will switch instantly, at the cost of performance for whatever other app you're using.
Wow, I did what I could for readability and flow. The various bugs really need to be worked into the applicable articles. Some of these are either very useful, or horribly reproducible. Out of everything on the site, the bugs really need a lot of work. Maybe this should be retitled as the not yet categorized bug list, and ship everything that can be categorized off to the applicable articles. Pinkynperky04 02:41, October 28, 2009 (UTC)
This is if you decide to kill crowley for tenpenny, I thought my game glitched when i went to tenpenny for the reward, cuz after collecting it kept saying to go get my reward from tenpenny, of course at this point i had all 3 keys to give to crowley as well, and after checking the forums and seeing that was a glitch i just continued, after going to collect the power armor at ft constantine, the achievement became unlocked and the quest closed, just so else suffers the same grief of thinking their game is broken.
795a8134c1