Bugs with 1.03 patch...
#326
Guest_iHNS_*
Posté 15 mars 2010 - 09:06
Guest_iHNS_*
#327
Posté 15 mars 2010 - 09:12
#328
Posté 15 mars 2010 - 09:22
#329
Posté 15 mars 2010 - 09:27
#330
Posté 15 mars 2010 - 09:42
#331
Guest_iHNS_*
Posté 15 mars 2010 - 09:46
Guest_iHNS_*
Also, from facebook:
Ed Cooper games company: oh yeah so we got this awesome idea for a game i think we should work on, yeah we think it would really be succesfull.
EA : oh hai guys, watcha doin? ohh new game idea ? yeah so like we can publish it and **** yeah... yeah? come on..
games company : errr .. yeah???????
(at time of game release)
EA : so yeah ...
So simply written yet so simply describing the whole thing LMAO
#332
Posté 15 mars 2010 - 09:53
#333
Guest_iHNS_*
Posté 15 mars 2010 - 10:00
Guest_iHNS_*
#334
Posté 15 mars 2010 - 10:01
mikelegacy wrote...
Any ideas when a new stable patch will be ready? Awakening comes out tomorrow
Nobody has a clue.
Since even I have send out a hopeful PM, while not being a person to normaly do that, I am quite sure that the community coords, devs and customer support have had a fair number of requests for any sign of life whatsoever.
Though there has been no official post and noone has gotten any answer so far
(though to be fair, I only send my PM a couple of hours ago)
#335
Posté 15 mars 2010 - 10:46
#336
Posté 15 mars 2010 - 10:55
Trefalen wrote...
The thing that concerns me is, how did a patch cause so many problems?
My guess?
The developers are discovering that adding additional content is breaking lots of original content and making the base game unstable. The executives are crammed up their asses telling them to produce new stuff and get it out the door ASAP while the customer base suffers because there's not enough QA people on the team.
#337
Posté 15 mars 2010 - 10:57
xoxmxox wrote...
I posted a problem yesterday/early morning today that after I patched I never really saw all the crash you guys talk about but one thing did went wrong on my game I tried to make a new character (clean no mods or dlc not even the official ones) but when I'm in the character creation screen I can't see my character so I have no idea what he/she look like at all not even the voices work so my question is is there anyone having the same problems or is it just me because this all happened after I used the new patch. I just want to know if the patch did this as well or something I did is what causing this "malfunction" to happen.
I created a new character as well in 1.03. However I did not experience any problems whatsoever. The lag and loading time were the same as in 1.02 and my game did not crash at all. I only turned off my official dlcs and left my mods on. The mods worked fine. As for pick pocketing, I'm not a good tester for that. Pick pocketing has been broken for me since 1.02.
#338
Posté 15 mars 2010 - 10:58
considering going back to 1.2 - even if it means I can't play the
expansion. Not only does my game have way more frequent crashes (and I'm not using Win 7) - the
pathing is terrible. Party members seem to get stuck on, around, and
behind things and won't move until I take control and move them or get
far enough away they jump ahead. Very annoying in combat. Nothing like
engaging the enemy and having my tank 30 feet behind me admiring the
rock under his foot. Although enemies are having the same issues -
getting stuck behind columns, behind doors, on blades of grass. Sorry -
spoilers here - but I couldn't complete Return to Ostagar in my current
game because the Necromancer got stuck on something after running up a
ramp towards the Tower of Ishal. He showed up in the cutscenes in the
tower and on the battlefield - but never spawned down there. Killed the
ogre and went back up to find him still in that spot on the ramp outside
the tower. I was able to kill him there but couldn't get the end
cutscene for Cailin. Never had the pathing issues until 1.3. Noticed a
lot more lag in the new patch too.
#339
Posté 15 mars 2010 - 11:07
CultKiller wrote...
xoxmxox wrote...
I posted a problem yesterday/early morning today that after I patched I never really saw all the crash you guys talk about but one thing did went wrong on my game I tried to make a new character (clean no mods or dlc not even the official ones) but when I'm in the character creation screen I can't see my character so I have no idea what he/she look like at all not even the voices work so my question is is there anyone having the same problems or is it just me because this all happened after I used the new patch. I just want to know if the patch did this as well or something I did is what causing this "malfunction" to happen.
I created a new character as well in 1.03. However I did not experience any problems whatsoever. The lag and loading time were the same as in 1.02 and my game did not crash at all. I only turned off my official dlcs and left my mods on. The mods worked fine. As for pick pocketing, I'm not a good tester for that. Pick pocketing has been broken for me since 1.02.
ok i found the reason why it was happening sorry for bothering you peeps here =D but yah I see the things you guys are talking about my game crashed twice already I will try to play again later.
Modifié par xoxmxox, 16 mars 2010 - 01:01 .
#340
Posté 15 mars 2010 - 11:09
Just because the devs are not responding does not mean they do not see all of the problems you guys are having with patch 1.03.
Chris Priestly just posted a bunch of times on the Awakening forum about 30 minutes ago. I'm 100% confident that he is not ignoring the two topics about patch 1.03 with 16 and 14 pages worth of replies in both topics.
Again, have patience I'm sure he is aware that this is an issue. Give them time to fix this problem then once they have a fix for it he will post a message to update us.
Modifié par Age of Dragons, 15 mars 2010 - 11:13 .
#341
Posté 15 mars 2010 - 11:17
Age of Dragons wrote...
To those of you complaining about no devs posting on this topic..........you need to have patience jeez.
Just because the devs are not responding does not mean they do not see all of the problems you guys are having with patch 1.03.
Chris Priestly just posted a bunch of times on the Awakening forum about 30 minutes ago. I'm 100% confident that he is not ignoring the two topics about patch 1.03 with 16 and 14 pages of replies in both topics.
Again, have patience I'm sure he is aware that this is an issue. Give them time to fix this problem then once they have a fix for it he will post a message to update us.
The problem is that people have plans on buying Awakening, may have it pre-ordered. The patch is required to play the expansion so this is the last chance to chancel a pre-order of a product that may very likely not be useable.
Chris Priestley has been on the forum 3 hours ago as well. Again, like now, locking a couple of threads.
This thread has been going for a week now. A week during which he has been active on the forum. He may very likely be well aware of the threads (I am counting on him being aware of it), but a week has been plenty of time to drop a simple one liner "we are aware of the problem and are feverishly working on fixing it".
Obviously, the answer is: don't buy a product that seems to be broken.
But it is sad when a company has it's customers begging it to give them a reason to still buy the product, and the company doesn't do it.
That said, this thread is about bugs, not about hypothetical discussions to what extent Bioware is working on remedying this mess. For that reason I apologize for getting drawn off-topic
#342
Posté 15 mars 2010 - 11:24
#343
Posté 15 mars 2010 - 11:26
melkathi wrote...
Age of Dragons wrote...
To those of you complaining about no devs posting on this topic..........you need to have patience jeez.
Just because the devs are not responding does not mean they do not see all of the problems you guys are having with patch 1.03.
Chris Priestly just posted a bunch of times on the Awakening forum about 30 minutes ago. I'm 100% confident that he is not ignoring the two topics about patch 1.03 with 16 and 14 pages of replies in both topics.
Again, have patience I'm sure he is aware that this is an issue. Give them time to fix this problem then once they have a fix for it he will post a message to update us.
The problem is that people have plans on buying Awakening, may have it pre-ordered. The patch is required to play the expansion so this is the last chance to chancel a pre-order of a product that may very likely not be useable.
Chris Priestley has been on the forum 3 hours ago as well. Again, like now, locking a couple of threads.
This thread has been going for a week now. A week during which he has been active on the forum. He may very likely be well aware of the threads (I am counting on him being aware of it), but a week has been plenty of time to drop a simple one liner "we are aware of the problem and are feverishly working on fixing it".
Obviously, the answer is: don't buy a product that seems to be broken.
But it is sad when a company has it's customers begging it to give them a reason to still buy the product, and the company doesn't do it.
That said, this thread is about bugs, not about hypothetical discussions to what extent Bioware is working on remedying this mess. For that reason I apologize for getting drawn off-topic
You make valid points. I agree with you.
#344
Posté 15 mars 2010 - 11:38
-and yes, I uninstalled, reinstalled and applied the patches. Fresh install, fresh game.
#345
Posté 15 mars 2010 - 11:40
DexterRich wrote...
Still can't name Dog on human noble (though there is a fix through the toolset), AND no items when I get successful picking pockets, AND I can't interact with Dog... all I get is (Happy Bark!) AND you have to go to character sheet and back to inventory for weapon damage updates...
-and yes, I uninstalled, reinstalled and applied the patches. Fresh install, fresh game.
Which patch?
#346
Posté 16 mars 2010 - 12:54
#347
Posté 16 mars 2010 - 02:09
Note: I didn't have any crashes prior to 1.03 however. But fewer crashes is at least an improvement.
Modifié par mathyes30, 16 mars 2010 - 02:10 .
#348
Posté 16 mars 2010 - 03:14
#349
Posté 16 mars 2010 - 04:20
Until I got to the final battle.
I killed the archdemon, got the cut scene after killing it, and then the game goes to the coronation ceremony. Now, there's a loading screen to get to an area where to talk to your companions, say good-bye, and leave and get the credits. I can't get there, though. The game always crashes during that loading scene. I can't get to the post-coronation ceremony. I've tried three times, and it's always the same. Is this related to the patch? I'm guessing it is, because I've gotten to this part a number of times before with no problem.
I have a post-coronation auto-save. Will it make a difference if I missed out on the post-coronation ceremony, or will it not matter, since the save is from right after the archdemon died? I'm guessing it won't make a difference when I import the character into Awakening, but I did want to talk to my companions at the post-coronation ceremony.
#350
Posté 16 mars 2010 - 07:15
On a side note: I had no issues with RtO tonight.
Played a different character as well and ran into an oddity. I don't know if it's patch related, but in 4 previous runs through this area before the patch I never saw this happen, so I suspect it has to do with the patch. Anyway, (I'll try to keep the spoilers to a minimum) I was outside the room where you can learn the Arcane Warrior specialization and got through the battle there. When I went to move I was suddenly teleported to the area where you get the Juggernaut plate. I had not solved the riddle to get into that area yet. I played out the battle there, just to see what would happen, and it seemed to work without a hitch. After the battle I could collect the plate. Reloaded the quick save to get back to before the battle outside the Arcane Warrior room and continued from there. No issues after that (well, pick pocketing is still broken, but...) When I went back later and did the Juggernaut Plate area, it worked as it was supposed to.
Also, I'm starting to notice a very minor amount of stuttering in some areas. It doesn't happen often and it's minor enough that it doesn't really bother me, but it's definitely there. I figure this is likely patch related as well, since so many others are reporting the same thing to various degrees.




Ce sujet est fermé
Retour en haut




