Aller au contenu

Photo

Patch 1.05 PUBLIC BETA - fixes authorization issues


255 réponses à ce sujet

#201
flexxdk

flexxdk
  • Members
  • 1 791 messages

Elegant wrote...

Whacka, as much as these things SHOULD be fixed, it appears that the team only has interest in fixing outstanding things such as the DLC authorization problem in this patch which really prevents people from playing the game period. Other issues such as those that you have listed are what we're trying to resolve using fixes we make or share with others in the Community Fixit thread in this forum.

Again, refer to our thread and see if you can find a fix made by someone (I know we have one for Shale's Rock Barrage). Patch 1.05 will be strictly a DLC fix and nothing more.

ARGH DARNIT.

Thanks for pointing it out I'm in the wrong thread. D:

#202
JayK47

JayK47
  • Members
  • 5 messages
Well, this did so far fix the authentication issue I was having. Weird thing though, I had no authentication issues before. I can't help but think the issues came from the BioWare server and suddenly I need a patch. Let's face it. Requiring a login just to play a game may work fine for a while. It is not a long term solution. Long term is a server shutdown and no way for me to play my DLC. It took entirely too long for me to install the main game and get all the DLC to work. Worst yet it took a beta patch just so I could play the DLC I just purchased. Now my loads takes far too long. Considering the age of the game and the age of my PC, my load times should be negligible. I cannot say that I am motivated to purchase DA2. The DLC won't work. Waste of my money. Thanks.

#203
Captain Sassy Pants

Captain Sassy Pants
  • Members
  • 300 messages
So, the community is left to do all of their dirty work at fixing their broken game, that we all paid for?

That's amazing.

#204
Kevlevin

Kevlevin
  • Members
  • 25 messages
What about the impulse version of the game? Sorry if this has been asked, I just might have overlooked it.

#205
Elegant

Elegant
  • Members
  • 40 messages

Captain Sassy Pants wrote...

So, the community is left to do all of their dirty work at fixing their broken game, that we all paid for?

That's amazing.


The community chose to do this we can simply choose not to.

The only question I see bioware asking about a 2 year old game is: Can we they complete a full playthrough? Yes. Our job is done! But since that answer is no, we have this patch.

The game isn't completely broken, I can bet you've completed the game once already, even if you had some bugs you still completed it so the game isn't entirely broken.

#206
Elementialomnicron

Elementialomnicron
  • Members
  • 45 messages
Kay, i had no clue where to post this so i thought here would be good..

Ever since i got 1.05 beta, loadings times are longer yeah, but im okay with that.

Its the RANDOM CRASHES that really peeve me off.

anyone know how i can prevent these random crashes other than saving a Sodding ton?

#207
Furtled

Furtled
  • Members
  • 426 messages
@Elementialomnicron

There's two options, first you can roll back to 1.04 if you kept a copy of your old daorigins.exe file, alternatively you can have a look through the Solutions round-up thread for a possible fix. I've had CtD issues with the game since I got it and there's a few things in there that can help you minimise the risk depending on your system set-up.

Hope that helps.

Modifié par Furtled, 05 octobre 2011 - 08:35 .


#208
Furtled

Furtled
  • Members
  • 426 messages

Kevlevin wrote...
What about the impulse version of the game? Sorry if this has been asked, I just might have overlooked it.

Honestly got no idea, if it's set-up like Steam could be that they don't allow beta patches so it'll be a case of waiting for the official release - sorry!

#209
Elementialomnicron

Elementialomnicron
  • Members
  • 45 messages

Furtled wrote...

@Elementialomnicron

There's two options, first you can roll back to 1.04 if you kept a copy of your old daorigins.exe file, alternatively you can have a look through the Solutions round-up thread for a possible fix. I've had CtD issues with the game since I got it and there's a few things in there that can help you minimise the risk depending on your system set-up.

Hope that helps.


well, cant go back to 1.04, cause i dont have a copy/dont want to lose my DLC's that i paid good money for.

Ill look at the solutions round-up thread again, but there isnt much in there that helps.

Im afraid that EA/Bioware needs to pull their **** together, and get crackin' on a very minor fix, for a very massive problem.

Im annoyed that i paid 30 dollars for that, and i had to go through a day's worth of angst to at least partially remidy it. Image IPB

#210
Thandal N'Lyman

Thandal N'Lyman
  • Members
  • 2 402 messages
You can get 1.04 direct from the official patch site, since it's the last release (1.05 is beta). 
social.bioware.com/page/da-patches

And you won't "lose" your DLC.  Once the "authorization" entries are recorded, you're g2g.  And except for those cases where a DLC needed something in a later version in order to actually function, it doesn't matter which version of the .exe you're running.  (I've rotated though 6 in the past several weeks as the dev team has been providing different ones to test. Image IPB )

Modifié par Thandal NLyman, 06 octobre 2011 - 03:48 .


#211
Elementialomnicron

Elementialomnicron
  • Members
  • 45 messages
so hey wait, if my authorization issues are gone, can i unintall it from Origin, and get rid of origin service, then re-install on steam and the verification issues are gone?

#212
ShinsFortress

ShinsFortress
  • Members
  • 1 159 messages
No.

#213
Elementialomnicron

Elementialomnicron
  • Members
  • 45 messages

ShinsFortress wrote...

No.



be-cause...?

#214
jess879malagant

jess879malagant
  • Members
  • 70 messages
You Probably purchased Dragon age on Origin. It would make sense that if you stopped using Origin Service and switched to steam that you would not be able to use your copy of dragon age on steam unless you bought the Dragon age steam version.

#215
Elementialomnicron

Elementialomnicron
  • Members
  • 45 messages
Yeah, i bought my copy on steam, so i thought that switching from origin to steam would work.

Modifié par Elementialomnicron, 07 octobre 2011 - 03:36 .


#216
Caldazar Soulraven

Caldazar Soulraven
  • Members
  • 1 messages
The one thing that really needs fixing are these stupidly long load times that get introduced with the 1.05 beta patch....

#217
Elegant

Elegant
  • Members
  • 40 messages

Caldazar Soulraven wrote...

The one thing that really needs fixing are these stupidly long load times that get introduced with the 1.05 beta patch....


*Hopes that this involves fixing the engine*

#218
Billybadaxe

Billybadaxe
  • Members
  • 1 messages
When are the continual crashes to desktop going to be addressed?

#219
ShinsFortress

ShinsFortress
  • Members
  • 1 159 messages
Continual CtD is unlikely to be fixed, since it happens to a minority of users (thus making it more likely a setup issue). The authentication (and for those with 1.05 beta, load time) problems are far more widespread. That's the focus for 1.05.

Given how long 1.05 is in coming, and how little communication we're getting from Bioware on it, my guess is that 1.05 is like 1.69 for NWN. Anything after that is down to the community.

Modifié par ShinsFortress, 09 octobre 2011 - 08:56 .


#220
Gorath Alpha

Gorath Alpha
  • Members
  • 10 605 messages

ShinsFortress wrote...

... my guess is that 1.05 is like 1.96 for NWN. Anything after that is down to the community.

1.96?    Fingers going faster than the controller synapses?  1.69 is the number I remember. 

#221
ShinsFortress

ShinsFortress
  • Members
  • 1 159 messages
Correct. Editted.

#222
Althernai

Althernai
  • Members
  • 143 messages

ShinsFortress wrote...

Continual CtD is unlikely to be fixed, since it happens to a minority of users (thus making it more likely a setup issue). The authentication (and for those with 1.05 beta, load time) problems are far more widespread. That's the focus for 1.05.

It's not a setup issue. I've tried it with distinct machines (one with an AMD GPU and the other with Nvidia) and it happens under exactly the same circumstances. It's related to quad-core CPUs (and maybe Windows 7 x64, though I'm not so sure o that).

That said, the CtD issue can be addressed by messing around with the CPU affinity. If that is set to 2 cores, it more or less goes away (not entirely, but once every 20 hours is far less annoying than once every 45 minutes). The long loading times issue has no user-created solution and thus is significantly more important.

#223
ShinsFortress

ShinsFortress
  • Members
  • 1 159 messages
That's true too. I had temporarily forgotten the number of cores/x64 issues, as myself and my gaming friends all run 32-bit on our gaming machines. So that aspect could in theory be addressed in a patch, but surely that would be a very invasive update (or not?) and thus also very unlikely to happen given what little attention Bioware/EA seem to be applying to non-authentication issues.

The CtD issues you mention, are the more or less since the current beta patch?

Modifié par ShinsFortress, 09 octobre 2011 - 12:03 .


#224
Funkjoker

Funkjoker
  • Members
  • 486 messages

ShinsFortress wrote...

The CtD issues you mention, are the more or less since the current beta patch?


social.bioware.com/forum/Dragon-Age-Origins/Dragon-Age-Origins-PC-Technical-Support/random-crashes-89244-1.html

Look at the date. It's a problem for many users and BioWare didn't acknowledge it (at least not in the forums). It can only be fixed by BioWare. The temporary solution to set the core affinity is suboptimal, as there's a significant frame-rate drop.

Furthermore, we haven't heard anything for weeks now according patch 1.05. And I'm still eager to hear some good news about 1.06. There are still crucial issues to be addressed (technical and import issues).

#225
Furtled

Furtled
  • Members
  • 426 messages
Only thing I can add is that they're still testing the 1.05 patch. I have the CtD issue myself but fiddling with the core affinity and some of the memory fixes in the solutions thread have helped.