The fact that you can make a mod out if the original audio and it works means this shouldn't be an issue.
Bethesda is on the job!
[t]https://www.timeshighereducation.com/Pictures/web/y/c/w/scientist-06-16011_450.jpg[/t][t]http://www.bls.gov/ooh/images/1997.jpg[/t]
[QUOTE=J!NX;51280120]Bethesda is on the job!
[t]https://www.timeshighereducation.com/Pictures/web/y/c/w/scientist-06-16011_450.jpg[/t][t]http://www.bls.gov/ooh/images/1997.jpg[/t][/QUOTE]
Given how unstable Bethesda's games are, this image is more accurate than not.
[QUOTE=Linkuya;51280179]Given how unstable Bethesda's games are, this image is more accurate than not.[/QUOTE]
the dude in the gray hair isn't even holding a calculator, it's actually just a flask for his whiskey but he's so wasted[URL="http://65.media.tumblr.com/80a9fdee4ab1d31441870e477f6c8f5c/tumblr_inline_ns0u5nnJe61s3cj0w_500.jpg"] he's just pretending it isn't so he doesn't get caught[/URL]
really shows you what bethesda is like tbh
Followed with a 5 GB patch existing out of the original uncompressed audio files :v:
better to just re-work the entire thing
is bethesda just really poorly structured or something? how do their games always release in some kind of broken state? this game already came out in 2011 and they still found a way to fuck it up
[QUOTE=TheHydra;51280477]is bethesda just really poorly structured or something? how do their games always release in some kind of broken state? this game already came out in 2011 and they still found a way to fuck it up[/QUOTE]
all they had to do was make it better across the board and they added an ENB and broke the sound and resold it
pretty fucking embarrassing tbh
[QUOTE=J!NX;51281576]all they had to do was make it better across the board and they added an ENB and broke the sound and resold it
pretty fucking embarrassing tbh[/QUOTE]
It's worse than that. ENB was a framework that allowed for custom shaders, engine-level bugfixes, and more. The new engine is running on DX11 with a few new post effects-- which isn't bad, but it's nothing compared to ENB. As I understand, the shaders are pre-compiled, preventing easy modification and some of the unique techniques we saw used in ENBs. No more Matso DOF or MXAO, SSSS, SSR, etc.
[QUOTE=TFA;51281637]It's worse than that. ENB was a framework that allowed for custom shaders, engine-level bugfixes, and more. The new engine is running on DX11 with a few new post effects-- which isn't bad, but it's nothing compared to ENB. As I understand, the shaders are pre-compiled, preventing easy modification and some of the unique techniques we saw used in ENBs. No more Matso DOF or MXAO, SSSS, SSR, etc.[/QUOTE]
Dunno about the others, but you can totally inject Matso DOF and MXAO with ReShade, I'm doing it right now
reshade's subsurface is ass until someone rewrites it.
They could have changed the game around a bit (as an option) and gotten some of that classic-tes fan money
I'm honestly more concerned about the fact that installing Skyrim Special Edition on a system that still has Skyrim Regular Edition on it and running it at least once seems to forcibly lock out the keyboard for regular Skyrim. While it shouldn't have any bearing on the files in regular Skyrim's installation directory, running the game at least once does seem to cause an issue with a certain file in regular Skyrim's directory that causes the keyboard to be forcibly locked out, only allowing a player to enable Steam's in-game overlay or hit Alt+F4 to exit the game. I can understand wanting to address the sound problem in Skyrim SE, but they should also be focusing on figuring out why Skyrim SE is managing to break a rather important file in regular Skyrim's directory when it shouldn't have any bearing on it whatsoever and essentially brick the game.
[QUOTE=Katra804;51282069]I'm honestly more concerned about the fact that installing Skyrim Special Edition on a system that still has Skyrim Regular Edition on it and running it at least once seems to forcibly lock out the keyboard for regular Skyrim. While it shouldn't have any bearing on the files in regular Skyrim's installation directory, running the game at least once does seem to cause an issue with a certain file in regular Skyrim's directory that causes the keyboard to be forcibly locked out, only allowing a player to enable Steam's in-game overlay or hit Alt+F4 to exit the game. I can understand wanting to address the sound problem in Skyrim SE, but they should also be focusing on figuring out why Skyrim SE is managing to break a rather important file in regular Skyrim's directory when it shouldn't have any bearing on it whatsoever and essentially brick the game.[/QUOTE]
That's because the controller setting is checkmarked. You'll need to mod ini settings or use a controller to disable it.
this happens in their other games as well, the game detects a controller and enables gamepad mode, locking keyboard and mouse out. Some devs actually program this in.
games NATURALLY should be able to just, run a gamepad and KB/M at the same time, but whenever you see them separated hard that's most likely programmed in
[editline]30th October 2016[/editline]
yes, this is full blown retard mode on their part.
This fucking game also suffers from the same screen resolution issues as Fallout 4. If you aren't using a 16:9 or 16:10 monitor then the game will refuse to run in fullscreen unless you edit an ini file and make it read only. At least for me anyway.
[QUOTE=J!NX;51280120]Bethesda is on the job!
[t]https://www.timeshighereducation.com/Pictures/web/y/c/w/scientist-06-16011_450.jpg[/t][t]http://www.bls.gov/ooh/images/1997.jpg[/t][/QUOTE]
Are you sure those aren't Gearbox employees?
Because their Duke Nukem 3D "remaster" suffers from the exact same problem, only 100x worse, and it's been 3 weeks since release and they still haven't managed to patch it.
There's only about 350 sounds in that game too so you'd think it'd be a matter of a few hours.
What's up with re-releases and fucked audio quality this month anyways?
[QUOTE=J!NX;51281576]all they had to do was make it better across the board and they added an ENB and broke the sound and resold it
pretty fucking embarrassing tbh[/QUOTE]
Honestly when they fix the sound issues and modding catches up this will have been worth it.
[media]https://www.youtube.com/watch?v=T6EjcESYIXk[/media]
Even if they just released the x64 version for free like they did with absolutely no changes visually it would be worth it. The stability for modded and unmodded game afforded by the x64 executable is a big deal for me for the $0 I spent on it. Some people are already in the ~100 mod range for this game and are reporting much better frame rate and stability compared to the original edition.
[QUOTE=J!NX;51282109]That's because the controller setting is checkmarked. You'll need to mod ini settings or use a controller to disable it.
this happens in their other games as well, the game detects a controller and enables gamepad mode, locking keyboard and mouse out. Some devs actually program this in.
games NATURALLY should be able to just, run a gamepad and KB/M at the same time, but whenever you see them separated hard that's most likely programmed in
[editline]30th October 2016[/editline]
yes, this is full blown retard mode on their part.[/QUOTE]
Actually no, it's not because of the gamepad mode being enabled; that's literally one of the first things Bethesda suggests checking to ensure that it didn't re-enable itself, and the people who have reported this bug checked to see if bEnableGamepad= was somehow reset to 1, and nearly all of them were not (and even those who were claimed that the keyboard lockout was still persisting after disabling the gamepad again). Plus, if the gamepad were enabled, the mouse automatically disappears by default, so trying to use the mouse in the menus or even during the game while the gamepad is enabled would render it useless since it wouldn't do anything or even appear. What happens with this bug specifically is that, even though you're set to use the mouse and keyboard, only the mouse seems to work; you can either move the mouse around and select different things on the main menu if you haven't loaded a save, or you can load a save and turn your character, swing your weapon, block with the shield, shoot your bow, or cast spells (depending on whatever you had equipped at the time), but you literally can't do anything with the keyboard to actually move around. It makes it so that you can't even open the console or pause the game if you load up a save. Your only functionality with the keyboard because of this bug is hitting Alt+F4 or hitting whatever button(s) you use to open the Steam in-game overlay.
The problem actually stems from the ControlMap_Custom.txt file in regular Skyrim's install directory somehow being corrupted or replaced/changed after Skyrim SE is launched at least once (I say at least once because some players, myself included, had it happen after launching it two or more times instead of just once). For whatever reason, Skyrim SE is messing with that file in regular Skyrim's directory; I would normally have suggested deleting that file entirely and just re-binding the keys for anyone else having that issue, but even that doesn't seem to work. Currently, the only known fix at this time until Bethesda actually addresses it is to replace that file with an older version of the file (which a friend of mine fortunately posted [URL="http://steamcommunity.com/app/72850/discussions/0/305509857568868342/"]here[/URL] in the Steam community forums for Skyrim). Why Skyrim SE is doing this is currently unknown to even Bethesda, but they are trying to look into what is causing Skyrim SE to have this kind of effect on regular Skyrim.
[QUOTE=Doom64hunter;51282597]Are you sure those aren't Gearbox employees?
Because their Duke Nukem 3D "remaster" suffers from the exact same problem, only 100x worse, and it's been 3 weeks since release and they still haven't managed to patch it.
There's only about 350 sounds in that game too so you'd think it'd be a matter of a few hours.
What's up with re-releases and fucked audio quality this month anyways?[/QUOTE]
no, this is gearbox
[t]http://3.bp.blogspot.com/-76JDVzNAqwQ/VPXvtpgabZI/AAAAAAAAAro/LWgsklPjaTo/s1600/kids_in_science_lab_trans.png[/t][t]http://infinitymartialarts.com.au/wp-content/uploads/kid-scientist.jpg[/t]
Every time I tried playing Skyrim SE, the refresh rate for Vsync would match my monitor, which means the game runs at 144 FPS.
The game can't handle 144 FPS and constantly cancels my attacks, makes water flicker rapidly (audibly and visually), and breaks many NPCs.
When I do get the game to run at 60 FPS, the game doesn't last more than 40 minutes before it crashes.
It amazes me that the game came out LESS stable than the original.
[QUOTE=Cold Finger;51283814]Every time I tried playing Skyrim SE, the refresh rate for Vsync would match my monitor, which means the game runs at 144 FPS.
The game can't handle 144 FPS and constantly cancels my attacks, makes water flicker rapidly (audibly and visually), and breaks many NPCs.
When I do get the game to run at 60 FPS, the game doesn't last more than 40 minutes before it crashes.
It amazes me that the game came out LESS stable than the original.[/QUOTE]
Fallout 4 had the exact same problem
Sorry, you need to Log In to post a reply to this thread.
