326 réponses à ce sujet

[PoiSIN-XIII]

Yet another day passes. I guess to most it only felt like the 1 day but I was at the midnight release and just feels like its been forever.

[Elysium-Fic]

/bump

Some official word on the status of the problem would be nice.

[Oscal]

IT WORKS for me.
My theory is correct: my multiple core CPU was actully running as single core.
(you can check this with task manager)

After updating the BIOS (by Asus updater in my case), the task manger shows that the CPU is actually running multiple cores now.

I am not sure whether it is due to old BIOS or previously mal-setting of the BIOS. I can save and load game now.

Hope this can help some of you. (do write down your bios settings before updating it if you are not familiar with hardware setup).

Happy gaming!!!

[Damoroc]

Oscal wrote...

IT WORKS for me.
My theory is correct: my multiple core CPU was actully running as single core.
(you can check this with task manager)

After updating the BIOS (by Asus updater in my case), the task manger shows that the CPU is actually running multiple cores now.

I am not sure whether it is due to old BIOS or previously mal-setting of the BIOS. I can save and load game now.

Hope this can help some of you. (do write down your bios settings before updating it if you are not familiar with hardware setup).

Happy gaming!!!

Very interesting theory. If this were the root of the problem, would mean single core people are completely shafted for the time being.

[Q4Waveslr]

Oscal wrote...

IT WORKS for me.
My theory is correct: my multiple core CPU was actully running as single core.
(you can check this with task manager)

After updating the BIOS (by Asus updater in my case), the task manger shows that the CPU is actually running multiple cores now.

I am not sure whether it is due to old BIOS or previously mal-setting of the BIOS. I can save and load game now.

Hope this can help some of you. (do write down your bios settings before updating it if you are not familiar with hardware setup).

Happy gaming!!!

Where does it tell you in Task Manager if your duo core is operating a single core?

[duke3292]

Well sounds like us single core users are going to have to wait a month or more just to play

[ineverfailz]

In the DA2 config tool, under system information it says under number of cores: 2. If the config tool can find 2 cores, the game should as well. (I am being lazy when it comes to updating my bios. I have a new motherboard and quad core coming from a vendor tomorrow :-))

Nathan from Bioware was going to take it home last night and see if he could recreate the issue outside of a company computer. Hopefully, he took a release version with all the DRM and such, not an in house copy. I'll wait and see what he has to say.

[SheilaD67]

I hope its soon. I don't normally buy the game immediately at release, but wait a few months for patches and other bugs/glitches to be revealed and fixed. I jumped the gun this time, really wanting the signature edition. Hubby is laughing at me (in the nicest of ways) because I broke my long standing rule with this game.

The game runs smoothly, considering I have a low end computer with low end hardware...it's just when it comes to getting to the load screen for Kirkwall when all gets loopy. And, even though I've disabled the auto save, I don't really want to keep a running, unsaved game going. Because, when a fix is finally created, I'd have to shut the game down anyway, loose everything I earned, and be so frustrated that I won't even look at the game for about another week (really).

So, I'm gonna keep a weather eye on this thread, hope that Nathan and Co. can come up with a solution quicker than a month, and play DA:O and write for now.

[Nathan Frederick]

I dusted off my wife's old single core machine and was able to reproduce the problem last night.

The problem is 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).

Programming is working on the problem now. I don't have an ETA on a fix, but we have been able to recreate it, which means we can work on fixing it now.

[Docam]

Nathan Frederick wrote...

I dusted off my wife's old single core machine and was able to reproduce the problem last night.

The problem is 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).

Programming is working on the problem now. I don't have an ETA on a fix, but we have been able to recreate it, which means we can work on fixing it now.

I feel like a fat kid at a pie eating contest now.

[Q4Waveslr]

Nathan Frederick wrote...

I dusted off my wife's old single core machine and was able to reproduce the problem last night.

The problem is 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).

Programming is working on the problem now. I don't have an ETA on a fix, but we have been able to recreate it, which means we can work on fixing it now.

Have you been able to recreate it on only single core machines in house?

Possibly this implies that those of us with multi core machines experiencing this problem are operating on only one of our cores and can fix this by updating BIOS ect ect

P.S. Thanks for the update and glad you guys are on it!

[Nathan Frederick]

We were able to reproduce it internally by forcing the game to run only on a single core at a code level, which does seem to imply an issue with multi-core issues running on only a single one for some reason.

[duke3292]

Nathan Frederick wrote...

I dusted off my wife's old single core machine and was able to reproduce the problem last night.

The problem is 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).

Programming is working on the problem now. I don't have an ETA on a fix, but we have been able to recreate it, which means we can work on fixing it now.

I have all those sypmtoms. Thanks for letting us know you guys are working on it. Guess this gives me time to do some DA:O playthroughs.

[shiro677]

Nathan Frederick wrote...

I dusted off my wife's old single core machine and was able to reproduce the problem last night.

The problem is 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).

Programming is working on the problem now. I don't have an ETA on a fix, but we have been able to recreate it, which means we can work on fixing it now.

Thanks a lot for the update, I appreciate the work.

[SheilaD67]

Nathan Frederick wrote...

I dusted off my wife's old single core machine and was able to reproduce the problem last night.

The problem is 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).

Programming is working on the problem now. I don't have an ETA on a fix, but we have been able to recreate it, which means we can work on fixing it now.

Exactly what's happening with my game as well.  And, while an ETA would be outstanding, the fact that you guys are working on it makes me do a little seated jig.  *jig*  There, all done.

I'll do a more elaborate dance once a fix has been put into place.

[azreal117]

thanks bioware. now to finish my play through in da:o.

[Dark Nekomancy]

I know that i7 and i5 with turbo boost can actually shut down cores to put more power to a single or only the ones needed. This might be why some multi cores are having this issue. Not sure on how to stop that without going through bios. Just as a heads up as why it could be happening to some multi cores

[Nicademas]

thanks for getting back to us Nat! I hope that it can be fixed on single core machines. I been playing the game fine with no problem (auto save off) So I know my 1 core pc can run the game. It doesn't make sense that 1 core would cause it not to save.

I just met the Qunari guy from the trailer after hours of playing before Windows decided to update itself and reboot. Couldn't save game anyway lol, but it was a blast to play... So I'll be hoping for a fix soon..Thanx

[MemeLeigh]

Nathan Frederick wrote...

I dusted off my wife's old single core machine and was able to reproduce the problem last night.

The problem is 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).

Programming is working on the problem now. I don't have an ETA on a fix, but we have been able to recreate it, which means we can work on fixing it now.

YAY **happy dance**
I will join the group finishing up some origins playthrough.

[teeballin]

Same thing going on with my pc.... ty for working on the issue!!   
I read somewhere that ME2 had a similiar issue with the single core and dual core saving... maybe looking back on that would help for a quicker fix? just a suggestion

[Dasmende]

Thanks Nathan for the update.. I eagerly await the fix. Guess I'll go finish my last character in Origins... till then. Signed... a single core user..

[Sir Mighty Khan]

Thanks for the update, was hoping to get some real time in playing before my work week began, but this just gives me my 3-day weekend from 4-10's for my first true experience (however long that takes) as well as the extra Gig of RAM time to get here.

Game really does run great and look great, even with medium graphics. The mobs on the screen caused no lag and the FPS I'm getting is good, so we know as most of us are reporting this that everyone did a good job there optimizing it even for older machines to play. Load times of the two loads I did get through were much better than in Origins.

Modifié par Sir Mighty Khan, 09 mars 2011 - 06:00 .

[Barbaric35]

Having problem also. After having game loop several times at Kirkwall loading screen I tried the following, just to make sure it was not a permissions problem.
*Disabled Auto-Save
*Ran Game as Administrator
*Played through ProLouge
*Hit escape in Kirkwall
*Chose Save
*Acted like a sucessful save
*Checked in Documents folder of game and did not see save folder just the files created when you first start
*Finished dock portion of game and when I went to go up the stairs got the loading loop even though AutoSave was supposed to be disabled, which makes me think once you do a save the autosave is automatically re-enabled

*I will disable firewall and AV before I try it next when I get home and see if that changes anything.

[DashRunner92]

teeballin wrote...

Same thing going on with my pc.... ty for working on the issue!!   
I read somewhere that ME2 had a similiar issue with the single core and dual core saving... maybe looking back on that would help for a quicker fix? just a suggestion

Though both problems seem to steam from single/dual core issues, with ME2 it was that single-core users couldn't even start the game, not that saving was an issue. I remember that patch taking forever >_< Imagine like how you are all complaining right now, but add an entire month of time..  but there was WAY more people with the single-core problem in ME2 so I suspect that their are plently of single-core users playing DA2 right now. Oh well, it can't be worse than the New Vegas game corruption glitch that broke the game for months until a patch finally came out.

[Oscal]

Q4Waveslr wrote...

Oscal wrote...

IT WORKS for me.
My theory is correct: my multiple core CPU was actully running as single core.
(you can check this with task manager)

After updating the BIOS (by Asus updater in my case), the task manger shows that the CPU is actually running multiple cores now.

I am not sure whether it is due to old BIOS or previously mal-setting of the BIOS. I can save and load game now.

Hope this can help some of you. (do write down your bios settings before updating it if you are not familiar with hardware setup).

Happy gaming!!!

Where does it tell you in Task Manager if your duo core is operating a single core?

Open the task manager, then press Alt V, then press C.
There should be two options to show how to display the core usage record.
If there is only one (grey out) option, then it means only one core is functioning.