4 réponses à ce sujet

[Nathan Frederick]

BETA PATCH 1.01 available now!:
http://social.biowar...0/index/6482838

This should fix this issue.   If you have applied this patch, and still have this problem, please let us know.

We have identified a problem where the game cannot save. This presents itself as three symptoms:
--You get a perpetual "saving" spinner on the right.
--Your save + load options are greyed out in the "escape menu"
--You will hang on the next transition after a save is attempted (which for most people is at the end of the blightlands, because the initial autosave is still trying to save).   If you have autosave disabled, and manually attempt to make a save, this will occur on your next transition.

This is currently occurring because the game is only utilizing one CPU - either because your machine only has one (single core machines) or your machine is only attempting to use one (multicore machines).  The game saves asynchonously (ie, on a seperate core) to allow you to keep playing while it saves, which it cannot do with only one core.

We have not seen this issue on multicore machines internally, but several forum users here have started to diagnose the problem, and I will paraphrase them here:

If you have a multicore machine, you see how many cores the game is utilizing by bringing up task manager, clicking on "Processes" then right click on "DragonAge.exe", then choose "select affinity".  If you see a single un-greyed checkbox, windows only recognizes one of your cores, regardless of what you have in your box.  Some users have reported that this was a BIOS configuration problem.  I don't have any specific details on how to address this, as it can vary wildly by machine.

If you see multiple available boxes, windows is only allocating one towards running the game - you may be able to manually select additional cores to make the game use them, alternatively, there are a couple third party applications which can instruct applications to use certain cores on launch. 

qalan wrote...

I have a triple-core processor and had the
'no save' problem initially too. Then I used an outside program (CPU
Control) and found that my machine was only using a single processor to
play the game. Once I used CPU Control to 'force' the game to use
multiple processors, the saving problem went away for me... I realize
this doesn't help the folks with single core processors, but it might be
an alternative for some dual+ core gamers to waiting around for a
patch/fix...

Catpriest wrote...

Hi,

I've experienced the same
issue and tried some of the workarounds offered on other sites including
updating my device drivers, disabling music, setting directx to version
9 and running the DragonAge2.exe directly in stead of using the
launcher. None of this worked. Disabling autosave is pointless too since
the save spinning will still be permanent after your first manual save.

I
have Windows 7 and a Quad Core CPU and yet I experienced these issues.
So I checked my task manager > performance and saw that I only had
one CPU there. So something weird was going on. I then opened my start
> run > msconfig and went to boot > advanced options and
deselected the checkbox for 'number of processors'. Then I rebooted. Now
I have 4 CPU's in my task manager. Just tested the game and now it
works fine, even with autosave on, music enabled and Directx 11.

(NOTE:
if you do see more than one CPU under task manager > performance yet
still experience this issue, then start DA2 > press the windows
button on your keyboard OR ctrl-esc OR alt-tab to see the taskbar, then
right-click it and go to taskmanager > processes.  Right-click
DragonAge2.exe and choose "Set affinity". Then make sure 'All
processors' is selected.)

I hope this can be of some use to those of you who have a multicore CPU yet still experience this issue.

Cheers,
Oliver

(EDIT: added the 'set affinity' bit)

Edit:  Added information provided by Catpriest

Modifié par Nathan Frederick, 11 mars 2011 - 10:56 .

[Nathan Frederick]

duke3292 wrote...

conan69 wrote...

 I'm another victim of this, but whic test this game? Mickey mouse? This is not a minor error! 

Well when they test games, they use high end multi core computers. Most people use mid range gaming PCs (including me). They should test out the game on minimum specs though.

Actually, we test from out MIN SPEC through to relatively recent... with the majority of our hardware being roughly the Reccommended.   My personal machine is a Core2 Duo @2.66ghz.  I have a single geforce 8800 GTS, one 24" monitor (which I got recently, when my old 17 broke), and 17" as my secondary screen.   There's a great misconception that we have stockpiles of the shiniest, newest, awesomest machines around.   We don't.   Machines cost money, and much like most users, we replace them when they become badly outdated, or they break. 

And the Min Spec is a dual-core.   There is no equivalent single-core to a dual core.   They can have similar process speeds/memory/etc... but they never have multiple cores.   Most games these days will use multiple cores - any game that is launched on the consoles simultaneously/before the PC HAS to use multiple cores, or they wont function on the consoles - and most games these days are multi-platform. 

Most users have multi-core machines, and are unaffected by this issue.

That said, we don't want people with single core machines to be unable to play the game except in ironman mode, so we're going to fix it.

We're working on it.  We know what the problem is, and we're fixing it.  

Sending anything out to the public involves several steps which are out
of our control.  If  we say we will have a patch on Day X, kick it into
the pipe on schedule, and there's a problem downstream from us... we get
the flak for it. 

You're never going to get any ETA out of us other than "we're working on it", because if it's off by even a little bit, everyone freaks out even more.   We've been through that dance in the past.  You are either angry because we're not telling you much... or you're really angry because "we lied about putting something out on X date".  We can't win.

Would you guys be happier if someone stopped into every thread every day saying "Still working on it"?  It doesn't really accomplish anything.

[Nathan Frederick]

MaddyDad wrote...

Nathan talks about not being able to win when it comes to giving some sort of guidance as to when a patch/workaround will be available. We're not seeking a definitive time, Nathan - just some sort of guidance. The E in ETA stands for "estimated". That's what we want, an estimate. Today-ish? Tomorrow? Next week? Next month? Just a rough idea would be nice.

ETA:  Now.

http://social.biowar...0/index/6482838

[Nathan Frederick]

Faykaholic wrote...

well, I have the steam version? Is it updating automaticly or what?

The beta patch will not work with Steam, sorry.  

Steam will receive the final patch once it is confirmed to be working (beta patches are not allowed on Steam).

[Rob Bartel]

Sorry - the patch will not be final and Steam-ready in time for the weekend. In the patch thread, however, there are some suggestions as to how your Steam entitlement also grants you access to the game via EADM. Sorry, I don't know the full details myself.