[sara OMAR]

Despite some serious issues reported during the beta (that were not addressed in the incremental update), it seems that 1.6.89.0.6 has gone live as the beta forum is now closed. Release notes are available http://www.gamesas.com/topic/1308295-steam-updates/page__view__findpost__p__20943412.

Again I am forced to ask, "what is the point of these public betas if no action is taken on the bugs reported?"

[Devils Cheek]

Steam just updated my game right now.

[Markie Mark]

It is indeed now live on Steam, and Gstaff has also updated that information in the official Updates thread.

The final version now available from Steam is exactly the one that has been available as beta.

There does not seem to be a corresponding version of the Creation Kit up, at least immediately.

[Susan]

Live on Steam despite all the new bugs within 1.6 - weird.

[Scared humanity]

Maybe they were really anxious to have the beta forum closed.

[Cassie Boyle]

Live on Steam despite all the new bugs within 1.6 - weird.

I haven't been following the beta, what are the new bugs?

[sally coker]

I haven't been following the beta, what are the new bugs?

Unless anything's changed since the last beta, off the top of my head:

- certain fires now have a thin, black 'hitbox' style outline around them. http://i.imgur.com/I9P2x.jpg
- if you alt-tab out of the game, then alt-tab in, you will have a Windows pointer flailing around on your screen in addition to the in-game cursor. To avoid this, only alt-tab out of the game while on the tab/quick menu. This can happen in windowed or fullscreen mode.
- in mounted combat, the crosshair cursor sometimes disappears.
- if you're using older AMD drivers and Skyrim's in-game AA, fires will cause rampant, seizure-like yellow flickering. I don't know how old the drivers have to be for this to present. I'm using 12.4 and couldn't replicate it. The solution is easy, though: upgrade your drivers already! Or, if you can't for whatever reason, disable Skyrim's in-game AA and force AA through the Catalyst Control Center.

And most importantly: there's a script error now in one of the Companions' questline scripts (the maintenance one, IIRC) that has the potential to break that entire questline. Until someone comes in and confirms that's been fixed, I would highly, highly recommend that you not use 1.6 with a savegame in which you're either trying to do the Companions' questline or intended to do it at some point.

Edit: Although, I haven't downloaded any Skyrim updates today. So it's likely that what went out to the public as a general release was the last beta update we got...Companion script bug and all. If this is true, Bethesda, I am extremely disappoint.

Son of the edit: Also not a "bug" per se, but if you're using a mod that adds or changes animations, it will bork mounted combat completely. Uninstall them completely or wait for updates.

Likewise, any mod that makes alterations to vanilla dialogue, including the USKP, is going to cause issues with silent or missing dialogue. Again, either uninstall these mods or wait for an update.

Son of the son of the edit: Added an image for the fire outline glitch and another visual glitch relating to fire.

[Aaron Clark]

And most importantly: there's a script error now in one of the Companions' questline scripts (the maintenance one, IIRC) that has the potential to break that entire questline. Until someone comes in and confirms that's been fixed, I would highly, highly recommend that you not use 1.6 with a savegame in which you're either trying to do the Companions' questline or intended to do it at some point.

Edit: Although, I haven't downloaded any Skyrim updates today. So it's likely that what went out to the public as a general release was the last beta update we got...Companion script bug and all. If this is true, Bethesda, I am extremely disappoint.

Ugh, that is one of the last remaining things for my main character to do. I was hoping to do that questline whilst I await Dawnguard.

Hrmpf.

[GEo LIme]

Oh, don't you dare forget, that opening and closing the items/magic menu while riding causes your horse to change its heading.
Also, I think, crossfire users have a flickering issue with lights.

Come to think of it, this may be a very clever move by Bethesda. Now they won't have to wade through miles of mod-issue ridden bug reports interleaved with a good amount of whining, but can neatly read all good bits from here.

So, just to spite that, I won't tell them, that when riding horses left ("A") or right ("B"), they agree to only turn in one direction when moving the mouse. Oops.

[A Dardzz]

Unless anything's changed since the last beta, off the top of my head:

- certain fires now have a thin, black 'hitbox' style outline around them.
- if you alt-tab out of the game, then alt-tab in, you will have a Windows pointer flailing around on your screen in addition to the in-game cursor. To avoid this, only alt-tab out of the game while on the tab/quick menu. This can happen in windowed or fullscreen mode.
- in mounted combat, the crosshair cursor sometimes disappears.

And most importantly: there's a script error now in one of the Companions' questline scripts (the maintenance one, IIRC) that has the potential to break that entire questline. Until someone comes in and confirms that's been fixed, I would highly, highly recommend that you not use 1.6 with a savegame in which you're either trying to do the Companions' questline or intended to do it at some point.

Edit: Although, I haven't downloaded any Skyrim updates today. So it's likely that what went out to the public as a general release was the last beta update we got...Companion script bug and all. If this is true, Bethesda, I am extremely disappoint.

Ah, okay, that last one sounds nasty, looks like yet another thing for the Unofficial patch makers to fix . The others, well, I never alt-tab, I have a laptop to use for other stuff while I'm playing, and I can handle the hitbox.

[Jennifer May]

... most importantly: there's a script error now in one of the Companions' questline scripts (the maintenance one, IIRC) that has the potential to break that entire questline. Until someone comes in and confirms that's been fixed, I would highly, highly recommend that you not use 1.6 with a savegame in which you're either trying to do the Companions' questline or intended to do it at some point.

This particular issue was reported directly to Gstaff by Arthmoor and a savegame was requested and supplied. Can someone who has allowed Steam to update Skyrim report the current version number of TESV.exe? It would be nice to confirm that information before discussing this too much.

[Bitter End]

This particular issue was reported directly to Gstaff by Arthmoor and a savegame was requested and supplied. Can someone who has allowed Steam to update Skyrim report the current version number of TESV.exe? It would be nice to confirm that information before discussing this too much.

Apparently you missed my post #3 in this very thread. Clarification: "exactly" means complete bitwise match of all files involved.

Ah, okay, that last one sounds nasty, looks like yet another thing for the Unofficial patch makers to fix .

Oh, and there is this very minor issue, that until they release an updated version of the Creation Kit, mod developers are unable to access the new Update.esm to see what has changed and how their mods should be adapted to it.

And the USKP as it stands today is not compatible with the new game, but causes lots of missing dialogue, and may require an extensive amount of work to update. So, if you are relying on the USKP, it might be a good idea to go and learn some golf in the mean team.

[Amber Hubbard]

Ah, okay, that last one sounds nasty, looks like yet another thing for the Unofficial patch makers to fix . The others, well, I never alt-tab, I have a laptop to use for other stuff while I'm playing, and I can handle the hitbox.

Yeah...most of the glitches are (relatively) minor, although personally I find the Windows mouse pointer bug damned annoying. Which is probably why the patch got the green light...except for the script bug with the Companions' questline. Minor detail there, really.

This particular issue was reported directly to Gstaff by Arthmoor and a savegame was requested and supplied. Can someone who has allowed Steam to update Skyrim report the current version number of TESV.exe? It would be nice to confirm that information before discussing this too much.

Well, my TESV.exe is still 1.6.89.0...Steam hasn't downloaded anything, and I just launched the game and it didn't try downloading any more updates. Which suggests that the version I have from the last beta is current with the version on Steam's servers. Someone who wasn't in the beta is welcome to double-check this for me though.