448 réponses à ce sujet

[Zilvermoon]

Luke Barrett wrote...

Hey, everyone. Just wanted to chime in and say that I'll be taking charge of relaying all these issue on to design/programming in order to get this patch rolling. Now, admittedly I have much more experience with DA2 mechanics than DAO so I apologize in advance if I ask anything really dumb

Signature saved me a ton of hours reading through the forums, THANKS !!

[Brent I]

Will this fix it so i can start the damn games

[Gorath Alpha]

Get serious. No one should have to answer a totally out of context insult like that one without treating it and the author like a troll.

Modifié par Gorath Alpha, 20 juin 2011 - 07:24 .

[Rob Bartel]

Brent, can you provide some more information about what you're experiencing?

Thanks,
Rob

[Sammimo]

Hi, just want to say thanks to Bioware for diverting some resources to work on this. I Loved this game from the day it came out, I have bought all the DLC and only ever had the dlc unauthorised bug once due to daupdater service not starting. I play on windows 7x64 now so I get the random crashes sometimes - just remember to save often! DA2 just didn't sound like my sort of RPG and I'm still happy with DA:O anyway on my 5th play through.

So there, THANKYOU BIOWARE I hope they allow you enough time to sort out more issues.

Looking forward to the new patch

[Macropodmum]

Not sure if it has been mentioned previously and I apologise if it has... but some way of aquiring items that were bugged and not dropped i.e. Lorekeepers Robes would be great for those of us who really like matched sets. I have searched through the Wiki post on console codes but it seems there is no option to add these types of items which is a shame, I do remember one of the NWN games having the "give_item" option to retrieve bugged items.

[sami jo]

As has been stated a few times now, the current patch work is focused solely on DLC authorization issues. A number of bug fixes are listed on the first page of the Community Fixit project thread, and missing items can also be obtained using console scripts (directions on the wiki)

[Macropodmum]

Thanks I will check there then, the wiki had no information I could see on using console to obtain specific items however.

[RaenImrahl]

I've been away for a while, but a brief update for the community:

Testing continues on beta patch 1.05. It appears to fix some of the outstanding DLC issues. However, it also seems to exacerbate some load time and slowdown issues. Luke and Rob have reported in to the Beta Test Group that the programmers are busy comparing the new code with older patches to see what might be causing this. It's a time-consuming process.

We expect to have at least one more version of the beta patch to test before it's made official.

Best,

RI

[Requiesta De Silencia]

RaenImrahl wrote...

I've been away for a while, but a brief update for the community:

Testing continues on beta patch 1.05. It appears to fix some of the outstanding DLC issues. However, it also seems to exacerbate some load time and slowdown issues. Luke and Rob have reported in to the Beta Test Group that the programmers are busy comparing the new code with older patches to see what might be causing this. It's a time-consuming process.

We expect to have at least one more version of the beta patch to test before it's made official.

Best,

RI

are they slow down over playtime issues like the current memory leak, or just consistent slow load times?

[RaenImrahl]

Requiesta De Silencia wrote...

are they slow down over playtime issues like the current memory leak, or just consistent slow load times?

An excellent question, and one right now that's hard to answer.  I'm neither a programmer nor am I privy to the day-to-day conversations going on within the development team.

Based solely on my own experiences-- I've never been truly convinced that the "memory leak" issue is a genuine memory leak, where memory addresses aren't being properly cleared while the game is playing. I've suspected, and the developers have implied, that some of those "memory leak"-type issues might actually be a side effect of the malfunctioning DLC authorization function.

With the current patch 1.05 beta, after about an hour and a half of play, I experienced a significant delay in load times, exiting the game, and even transitioning between combat/exploration and some cut scenes. I did not see a significant slowdown in combat-- but I started a new game and haven't been playing with some of the higher-level powers.  No crashes, and no instability-- but the slowdowns grew in frequency and duration as I played.

This problem has been reported by many beta testers... so we're making progress.  The devs now know what to look for, and as I said before, the labor-intensive process has been underway to examine the patch code line-by-line.  I am hopeful, when they discover a cause, that the solution might actually improve the overall performance of the game, including for those who have encountered this "memory leakish" thing.

Again, just my observations... I don't want to speak too much out of school... but I have confidence that they remain committed to issuing a successful, functional 1.05 patch.  

RI

p.s.  If anyone else wants to join the beta test group (sadly Steam users are ineligible, because of how Steam patches the game)... send me a personal message and we can get you hooked up.

[Requiesta De Silencia]

RaenImrahl wrote...

Requiesta De Silencia wrote...

are they slow down over playtime issues like the current memory leak, or just consistent slow load times?

An excellent question, and one right now that's hard to answer.  I'm neither a programmer nor am I privy to the day-to-day conversations going on within the development team.

Based solely on my own experiences-- I've never been truly convinced that the "memory leak" issue is a genuine memory leak, where memory addresses aren't being properly cleared while the game is playing. I've suspected, and the developers have implied, that some of those "memory leak"-type issues might actually be a side effect of the malfunctioning DLC authorization function.

With the current patch 1.05 beta, after about an hour and a half of play, I experienced a significant delay in load times, exiting the game, and even transitioning between combat/exploration and some cut scenes. I did not see a significant slowdown in combat-- but I started a new game and haven't been playing with some of the higher-level powers.  No crashes, and no instability-- but the slowdowns grew in frequency and duration as I played.

This problem has been reported by many beta testers... so we're making progress.  The devs now know what to look for, and as I said before, the labor-intensive process has been underway to examine the patch code line-by-line.  I am hopeful, when they discover a cause, that the solution might actually improve the overall performance of the game, including for those who have encountered this "memory leakish" thing.

Again, just my observations... I don't want to speak too much out of school... but I have confidence that they remain committed to issuing a successful, functional 1.05 patch.  

RI

p.s.  If anyone else wants to join the beta test group (sadly Steam users are ineligible, because of how Steam patches the game)... send me a personal message and we can get you hooked up.

darn I was about to send you a personal message until you said Steam and ineligible

well if it helps any, I have just let the game run at the title screen for about an hour and I noticed its memory usage rising from about 55k kb to 250k kb. CleanMem also seems to be fixing the issue for a time, but the load times will still get longer if I play for several hours. Maybe it's a mix of DLC authorization issues and memory leaks in some areas?

[RaenImrahl]

Requiesta De Silencia wrote...

darn I was about to send you a personal message until you said Steam and ineligible

well if it helps any, I have just let the game run at the title screen for about an hour and I noticed its memory usage rising from about 55k kb to 250k kb. CleanMem also seems to be fixing the issue for a time, but the load times will still get longer if I play for several hours. Maybe it's a mix of DLC authorization issues and memory leaks in some areas?

Could be, although with the title screen, I'd suspect it's the former (DLC) and not the latter.  Conventional wisdom, at least, would point to a memory leak being "fed" by the loading of successive environments and objects during actual gameplay.  Are you using a 32-bit or 64-bit operating system?

Also, everyone should keep in mind that some of Origins' coding is clunky and will never be corrected...  DA2 uses essentially the same engine, but the developers have said that some of the changes inplimented for that game just can't be reverse-engineered into Origins. 

Modifié par RaenImrahl, 26 juin 2011 - 02:13 .

[Flamingphoenixdragoon]

Hello, just wanted to pop in and give a quick message of support.

I just so happened to pick up and finally finish my first play-through of of DA:O this past week, and I started Awakening today as well. (I had bought the expansion back during a very good sale on Steam.)

However, after reading up a little bit on Awakening, I find the very consistent and significant bugs involving conversation flags and lost items/quests to be very game breaking, and I do not wish to progress forward knowing this.

I am very happy, however, to see that Bioware hasn't abandoned its customers and is attempting to make the game playable for as many people as possible. I know your latest patch will primarily deal with crashing issues, it appears, but I sincerely appreciate any efforts your programmers and technical staff take to fix outstanding issues involving important conversation flags (such as with Morrigan and the Dark Ritual), and all of the issues with Awakening!

Good luck!

[ShinsFortress]

Flamingphoenixdragoon wrote...

I know your latest patch will primarily deal with crashing issues, it appears, but I sincerely appreciate any efforts your programmers and technical staff take to fix outstanding issues involving important conversation flags (such as with Morrigan and the Dark Ritual), and all of the issues with Awakening!

Good luck!

Main priority for the coming patch is DLC (login/authentication) issues.

[Jei]

RaenImrahl wrote...
(sadly Steam users are ineligible, because of how Steam patches the game)

Does this mean that the official, finished patch won't work for Steam users? Or just the current beta patch?

(I also wonder if this is why none of the authorization fixing methods work for me.)

[SGMRock]

Jack Stark, Steam doesn't support almost all beta tests so its normal for this to happen. Steam users will get the full patch I'm sure though normally a day after its out to everyone else.

"Also, everyone should keep in mind that some of Origins' coding is clunky and will never be corrected... DA2 uses essentially the same engine, but the developers have said that some of the changes inplimented for that game just can't be reverse-engineered into Origins."

Thats too bad because even though DA II is a lot prettier with DX11 graphics settings and high res texture pack, I still think DA:O is the better game. I just started playing DA:O again after playing 50 hours or so of DAII and man I love DA:O so much more. Only thing I miss in DA:O over DA II is that your character actually talks when you say stuff. I never really missed it before but now after playing DA II it seems like dead air on the radio everytime you pick a conversation option.

[RaenImrahl]

Jack Stark wrote...

RaenImrahl wrote...
(sadly Steam users are ineligible, because of how Steam patches the game)

Does this mean that the official, finished patch won't work for Steam users? Or just the current beta patch?

(I also wonder if this is why none of the authorization fixing methods work for me.)

The official patch WILL be available via Steam.  The beta isn't because of how Steam delivers updates to PC users.

[Requiesta De Silencia]

RaenImrahl wrote...
Could be, although with the title screen, I'd suspect it's the former (DLC) and not the latter.  Conventional wisdom, at least, would point to a memory leak being "fed" by the loading of successive environments and objects during actual gameplay.  Are you using a 32-bit or 64-bit operating system?

Also, everyone should keep in mind that some of Origins' coding is clunky and will never be corrected...  DA2 uses essentially the same engine, but the developers have said that some of the changes inplimented for that game just can't be reverse-engineered into Origins. 

32 bit operating system, and I tested the load times from the party camp to Orzammar (travelling between the two, which means no travel time or blood splotches on the map) today. Original load time was about 10 seconds either way. After an hour of waiting in Orzammar it was up to about 20 seconds. After another hour this time waitin in the party camp it was about 25 seconds between the two.

(I have to put the abouts in, because stopwatches aren't perfect...and I have a habit of putting about next to data after spending a year with an OCD statistics professor .-.)

...and not being a computer programmer or even vaguely knowing how DAO was coded, I have no clue what the heck this data means just figured if I'm going to test something I should probably test everything.

[Macropodmum]

I would have to agree that the load times get longer the longer the game is running. In the early stages load times are barely noticable but after having the game running for more than 8 hours the loading times get quite lengthy (into the several minutes) or to an endless loop which don't load at all. I assumed this was just because the game was loading more and more data without clearing any throughout the game. Restart the game and the loading times are minimal again.


Specs:
AMD Athlon™ 64 X2  4600+
4GB Ram
NVIDIA GeForce GT 220 (1GB )
SB Audigy 4
DirectX 9.0c

Modifié par Macropodmum, 27 juin 2011 - 12:49 .

[Rob Bartel]

The load-time increases being reported in the beta are apparently lengthier (over a minute) and appearing more quickly (within the first hour of play) than those in 1.04. Memory footprint remains essentially unchanged during that period which rules out a traditional memory leak as the likely culprit. We're continuing to investigate but don't have a lot of progress to report at this point.

Hope that clarifies,
Rob

[jareklajkosz]

Rob,

I think the extreme loading times have something to do with the number of area transitions that have been initiated in the game. An easy way to see this is by repeatedly going back and forth between two locations in the game (it's more obvious if you go between two areas that have a large amount of assets, say.. between Denerim and Redcliffe). The loading times get consistently longer and longer the more transitions are made between the areas.

Just testing it a bit right now, it seems like it has more to do with how many unique areas you've visited. I went between Soldier's Peak and Cadash Thaig a couple of times, then went between party camp and Cadash a few times, didn't notice too much difference, went to Honnleath, went between the cellar and the town about 20 times, started going back between the party camp and Cadash again, and I started noticing that the Cadash loading times were increasing a little bit. Hope this helps!

[Tpiom]

Most interesting, jareklajkosz... Join the beta team right away!

I should also check out if it's true for me too.

Modifié par Tpiom, 02 juillet 2011 - 11:42 .