Jump to content

DOWNLOAD MODS

Are you looking for something shiny for your load order? We have many exclusive mods and resources you won't find anywhere else. Start your search now...

LEARN MODDING

Ready to try your hand at making your own mod creations? Visit the Enclave, the original ES/FO modding school, and learn the tricks of the trade from veteran modders...

JOIN THE ALLIANCE

Membership is free and registering unlocks image galleries, project hosting, live chat, unlimited downloads, & more...

Arthmoor

Ambassadors
  • Posts

    1,175
  • Joined

  • Last visited

  • Days Won

    25

Posts posted by Arthmoor

  1. Indeed. If you haven't yet updated to 1.2, DON'T. Unless you LIKE there being no elemental resistances and/or your dragons never being within melee range.

    I realize that with Steam this may not be possible since it's "don't update me" option rarely works as advertised, even in "offline" mode. I'm still a happy 1.1 non-infected user and plan to stay that way until Bethesda goes and hires a real QA team.

  2. Yep, early alpha quality but at least the BAIN tab works and you can manage saves and screenshot with it. That's all we need it to do at the moment. Bashed Patch support will come soon I'm sure, but there's little point right now with no mods out.

    That stuff with the string data makes me wonder if we're going to get stuck having to maintain weird things like that with our own mods as well.

  3. I haven't quite figured out why people are using the LAA patch. I have no such thing in place and the game has had all of one CTD in 110 hours of play. At Ultra settings with some ini stuff slightly over the default limits.

    I don't doubt that the DRM update really did introduce crashing. It wouldn't be the first game to suffer something like that. Pools of Radiance on PC was a disaster of CTDs and in-game lag until Ubisoft relented and patched the DRM out. The game suddenly sprang to life and was smooth as butter. You'd think after repeating the same mistake over and over again that the industry would finally get it. Students of history they are not.

    People also insist Bethesda had to push this update, but every indication I see says Valve did it because Bethesda's people act like they haven't pushed anything. Including direct responses from their email and phone support people who insist the second patch is still being worked on. Nobody seems to know about the DRM update. If they're all lying then Bethesda has somehow mastered the art of effective conspiracy and cover up. Something that's highly unlikely to happen.

  4. Best be sure it's the XBox version too, because the PS3 version appears to have gotten shafted hardcore again. They're raging out of control on the official forum over it. Far more than PC gamers are raging over getting the finger with the DRM update.

  5. Well it cost me a bonus during the DB quest but other than that it only seems to be causing people to be up and about at ridiculous times of the day. Which is the weird thing. The TIME (ie 5pm, 8am, etc) is correct. Sunrise and sunset still happen at the correct moments. It's just the day name that flips, but that's one of the global variables so messing with it in weird ways can break stuff.

  6. Well I told 3 buddies who make most "steam haters" look like angels about the bypass and they bought the game. I of course warned them not to log into Steam or it would break their game. That's 3 sales Bethesda got because of the bypass. Mistake or otherwise, those guys would not have bought the game if Steam needed to be launched even in "offline" mode (which is a joke).

    Several people who specifically set Steam to offline mode still had this patch forced down their throats and hadn't thought to backup their unmodified EXE file. There really is no good reason we should be beholden to a company that has zero stake in any of this. Much less put up with them violating their product terms and conditions. In some countries this patch is straight up illegal because it installed new software without obtaining consent first.

  7. Actually a lot of folks had their game updates turned off already. This patch was forced outside the normal system just because you logged in to Steam. Good thing I never do and have no intention of doing so unless a patch comes along that has a good reason to put up with it. I'm not exactly pleased with the fact that doing so will expose me to massive CTDs like everyone seems to get from it.

  8. Well I've managed to dig up about the only viable explanation - that because there was a bypass, Valve threw a fit over some ridiculousness in their contract terms. IMO, that's a sign Valve is already too powerful when they're able to bully a response like this and issue the update on their own. All signs seem to point to Bethesda itself not knowing this was coming. Nick Breckon and Pete Hines are both talking about how the 1.2 patch hasn't been issued yet. There's only one small sticky post about it on their forum and it doesn't mention who the source was. The poor community managers are always the last to know when stuff like this happens.

    Zenimax might have known, but if you think Bethesda is secretive, Zenimax is like trying to uncover the Illuminati. Of course, for those not in the know, they're all the same company anyway. The web is rather thick. Too many corporate shell games going on.

  9. This sort of underhanded crap is precisely why I don't like Steam. Fortunately my distrust of Valve and Bethesda runs deep enough that I don't touch anything to do with Steam. This bypass thing was like a dream come true, and I'll continue to enjoy the game without it. Their patch that's coming next week likely won't fix anything anyway. Their track record indicates the opposite - they'll break way more than they fix.

    There's no good reason they couldn't have just left it alone. All they're doing is creating rage on the forums and driving lots of people to piracy instead.

  10. Yeah, mine is uber-screwed right now too and all I did was turn vsync off in CCC. It's been off since the card was installed. I don't like how it jacks frame rates, but this Skyrim thing has come completely out of nowhere. Someone seriously needs to get fired for this one.

  11. Keep in mind. Without hacking the ini file, you can't turn vsync off. There's no option for it. It's incredibly amusing that they can't seem to get this stupid Gamebryo stuff to work and won't wake up to the fact that they need an ACTUAL new engine instead of a frankensteined modification of a broken system. There's a reason nobody else in the industry still uses it.

    Er, ok. So it's also come to light that doing this via your graphics driver will ALSO cause the bug to manifest. Gah. I sure hope my game hasn't been screwed over by that because that IS one thing I have the driver override as a hard setting.

  12. They're using FNVEdit, which isn't something I'd recommend doing since it DOES NOT have all of the proper record definitions for Skyrim. This sort of thing happened initially with FO3 too and ended up biting a lot of folks in the ass once the GECK came out. I guess nobody has the slightest bit of patience as far as cobbling mods together.

    Texture and sound replacers are about all that's safe to do right now.

  13. That would probably work so long as all you planned to do was play the game. Modding tools would still be looking for it in the old location unless you adjust the registry, which would probably then piss off Steam when patch time comes.

  14. That is welcome news. Does this mean we can uninstal Steam entirely once the game is installed?

    That I don't know, because I haven't tried it. It depends on whether or not Steam removes game files when it's uninstalled.

    The other problem with that is that Steam will be the only way to receive future patches. It remains to be seen whether or not any DLCs come out on disc.

  15. It's true, launching the game's own EXE directly bypasses Steam. Just like launching FO3's EXE bypassed SecuRom. It isn't known at this point though if this was intentional or not, but either way, it was a welcome surprise.

  16. For future reference (I ran into this too) the sound fix is the answer. It'll also work set to 48000, which is what I picked. The default had been sitting at 192000 for ages without a problem. I recall having run into this with Gothic 4 and having an equally tough time figuring out what was wrong. Someone on the Bethesda forum mentioned this and it worked.

×
×
  • Create New...