Ce sujet est fermé
Servius the bear wrote...
Not been having issues at all
Runs perfectly. But I always patch up if a patch comes out.
No, I'm pretty sure I don't classify them at all. Because doing so requires subjectivity. And when you have hundreds of thousands of active players in both a main game and an expansion, the question of "importance" will take too long to addressCallidus Thorn wrote...
Yrkoon wrote...
I, for one, don't see the need to catagorize bug fixes into "levels of importance". Nor do I think this has to be an "either fix this, or else fix that" thing.
The smaller the bug, the easier it is to fix I would think, which means one patch can contain the core game stability fixes AND a bunch of the lesser 'cosmetic' fixes, which are probably nothing more than simple coding oversights and wouldn't take much dev time to address and squash anyway..
So you then classify a bus that crashes the game to be just as important as one that stops armour appearing? I'm sorry, but that that's just ridiculous.
Again, why does this have to be an "either/or" thing? And how do you define game breaking? I don't recall Victor, or Woo, or anyone else in Bioware saying: "OK folks, the boss says we're only allowed to fix 8 bugs, so which ones will they be?"The greater affect a bug has on the gameplay, the more it needs to be fixed, therefore it's more important. Implying that all bugs are equally important sounds like you're trying to justify a "everything broken in the game must be fixed" viewpoint, which just isn't feasible. Every game has bugs to some degree, if they don't affect gameplay too much, they don't really need to be fixed. They can't fix everything, an "Either this, or that" approach is inevitable, and I'd rather they stopped the game breaking bugs than make sure a set of armour appears.
Modifié par Yrkoon, 14 juin 2010 - 04:37 .
I see.Thandal NLyman wrote...
Yrkoon wrote...
I, for one, don't see the need to catagorize bug fixes into "levels of importance". Nor do I think this has to be an "either fix this, or else fix that" thing.
The smaller the bug, the easier it is to fix I would think, which means one patch can contain the core game stability fixes AND a bunch of the lesser 'cosmetic' fixes, which are probably nothing more than simple coding oversights and wouldn't take much dev time to address and squash anyway..
I will assume that this comment comes from someone who has not had to mange complex, interdependent, multi-person projects in heterogeneous technical environments. If there are infinite resources to devote to the effort, than everything can be "Priority One". Given that this is the real, not the ideal world, and that someone has to decide how to allocate whatever (by definition, limited) resources they have available, then assigning severity/importance ratings is an essential (and early) step. "First things first" is a useful tenet, but someone actually has to determine what's "first".
Modifié par Yrkoon, 14 juin 2010 - 04:26 .
joey_mork84 wrote...
Servius the bear wrote...
Not been having issues at all
Runs perfectly. But I always patch up if a patch comes out.
Same here, but apparently you aren't suppose to say that lol.. Did that in the last update thread and got flamed.
Speaking of which... @Drewbahr: Let's not start that fire, yet again. It didn't go anywhere the last time and surely won't go anywhere this time, either.
Modifié par BrunoB1971, 14 juin 2010 - 04:45 .
several games at once
Modifié par Servius the bear, 14 juin 2010 - 04:47 .
Servius the bear wrote...
joey_mork84 wrote...
Servius the bear wrote...
Not been having issues at all
Runs perfectly. But I always patch up if a patch comes out.
Same here, but apparently you aren't suppose to say that lol.. Did that in the last update thread and got flamed.
Speaking of which... @Drewbahr: Let's not start that fire, yet again. It didn't go anywhere the last time and surely won't go anywhere this time, either.
lol well they can flame me all they want. Its water on a ducks back to me.
Drewbahr wrote...
Oh, and joey_mork84? Not looking to "start things up" but you know the drill - just because you haven't encountered the bugs doesn't mean Bioware's product is perfect and bug-free.
Small bugs can also be caused by bad logic and fixing it may require a complete overhaul of the involved logic. (AKA: Lots of work)Reggler wrote...
Yrkoon wrote...
The smaller the bug, the easier it is to fix I would think
Not necessarily - small bugs can be hard to spot, while some that seem rather complex may actually be very
easy to fix. And sometimes, you spend days looking for the spot in the code something goes wrong at, only to find that the change needed is really minor.
This is why I'm not mad about patching taking long, only that we were kept in the dark about any progress. But since this is no longer the case: Thank you for the updates, Bioware!
Please keep us informed in this way, and in return I promise to not be angry anymore. Noble, ain't I
Drewbahr wrote...
Servius the bear wrote...
joey_mork84 wrote...
Servius the bear wrote...
Not been having issues at all
Runs perfectly. But I always patch up if a patch comes out.
Same here, but apparently you aren't suppose to say that lol.. Did that in the last update thread and got flamed.
Speaking of which... @Drewbahr: Let's not start that fire, yet again. It didn't go anywhere the last time and surely won't go anywhere this time, either.
lol well they can flame me all they want. Its water on a ducks back to me.
It sounds like you play on a PC, in which case your gameplay experience is largely unaffected by the fierce majority of the bugs in the game. Most of the serious bugs (the DEX bug, save corruption bugs, et al) are most prevalent and reproducable on the console versions of the game.
Being on a PC like it sounds, you've already been patched many times over. And if you actually run a rig without any patches at all, and haven't been able to reproduce them, then consider yourself quite fortunate.
Oh, and joey_mork84? Not looking to "start things up" but you know the drill - just because you haven't encountered the bugs doesn't mean Bioware's product is perfect and bug-free.
Oh and you will find I dont back down! Next person come on up 
Modifié par Servius the bear, 14 juin 2010 - 05:18 .
Guest_Antares1987_*
Stanley Woo wrote...
This is just a reminder to keep the platform wars out of the discussion. Let's try to stay on topic, thanks.
Noilly Prat wrote...
There's a weird issue with the Morrigan epilogue mention in Awakening, too. As far as I know, 90% of players who romanced her in Origins probably never saw the reference in the epilogue text boxes in Awakening, whereas certain players who did not might have seen it. There was a pretty big topic about this a while back, and I can't see how it can't be a bug.
Apparently speaking with Morrigan after the ritual at the end of Origins is what does it. It seems that this dialogue sets the Morrigan romance variable to inactive, regardless of what you say, while there is no problem if you simply don't speak with her. I believe David Gaider at one point confirmed that the mention in the Awakening epilogue is supposed to be for all people who romanced her in Origins and got the "ring" text at the end of the game. As it stands, though, this does not occur. I would like to see this fixed as well, if only to ensure that any possible future references to the Morrigan romance in any sequels or expansions will work properly.
Somebody correct me if I'm wrong about any of this, though. I haven't really read anything about it since that one topic a while ago.
Zy-El wrote...
Speaking as one playing on the PC, I'd rather Bioware fix the major, game-breaking bugs that modders cannot. I trust Qwinn and other modders to catch the minor bugs/script errors and with Bioware doing the major bugs
Zy-El wrote...
The Vigilance appearance bug is not something I'd consider major or game-breaking by any stretch. Get real, people, it's just a sword graphic and does not take away from the weapon's performance in battle!
Modifié par switzki, 14 juin 2010 - 05:52 .
Servius the bear wrote...
Mate keep going repeating pritty much the same thing over and over. I have pritty much heard and seen it all before!. Oh and some tips for you mate. Dont think you know everything! Also think first before you speak to
Franpa wrote...
The problem described isn't a memory leak, memory leaks are when a part of a program becomes unstable either due to bad coding or defective hardware and repeatedly allocates RAM to it self over and over until there is no RAM left at which point it either lags badly or crashes.Apex Sammoth wrote...
Feraele wrote...
Apex Sammoth wrote...
Lord Gremlin wrote...
Please, fix PS3 Blight Queller trophy bug already! It's ridiculous: this trophy is glitched and never unlocks. It's not uncommon and such things are usually getting fixed. So please, fix it already.
Also: PS3 version looks better than 360 and people should understand that bugs have nothing to do with raw processing power or something. Nothing at all. It's perfectly possible to create a game that runs perfectly on PSP and almost unplayable on 360 and PS3.
The PC version Looks better then Both I fail to see the point of this argument on a patch thread. What your not understanding about what was said in that post was that the way the games are developed on the PS3 is a bit harder to port over compared to the 360. So it is a bit easier to patch the 360 over the PS3 simply because they are developed on the same format as the PC. Actually there are some major bugs with Dual Cores / Etc and other PC Configs with this game so yes Processing Power sometimes has some issues. If the game is coded wrong not to use certain resources it can cause anything from Memory Leaks to the well known %100 Processor issue with this game.
Hmmm that could be whats causing "some" of the slow motion moving of characters that I see from time to time on my PC. I have an AMD core duo machine. I've seen the 100% processor issue, many times. Always thought it was some sort of memory leak, but as I read in the PC tech forums, (or somewhere) the layman always refers to "memory leaks" when sometimes its not a memory leak but something else. What that might be ..I don't know.
Anyways hope the Bioware team is on top of this. Even still, if I am good about logging out and restarting, or rebooting my machine, I can go and play again. Just annoying crashing in Denerim just before the Final Battle, after killing the first darkspawn general etc. lol Or sometimes when I am about to finish off the Archdemon. A little frustrating. But I always tell myself, hey another chance to do it BETTER. lol
Correct and that is what I call Gamebreaking. This is not a Dex bug or a quest line bug. This is a MAJOR problem. You should not have to restart the game or even change any core affinity. Im sorry but, I don't buy into the Game Works but you have to do "X". Esp when the BOX says I am well above the Sys Req. Keynote here is I don't have to do anything when playing other game including games that have higher System Req.
I do hope there is some sorta fix for this in the Upcomming patch. Any Info on these fixes would be nice Bioware ?
The 100% CPU is NOT a bug and it has been that way since the Windows 95 days. There are ways developers can reduce CPU usage when the CPU isn't required but it comes at the cost of accurate timing/switching between threads. You typically see such energy saving measures in hobby programs like Emulators and mobile applications for laptops etc.. Windows XP, Vista and 7 all feature I believe special "Intel" or "amd" drivers which will split the load of single threaded processes over multiple cores/processors seamlessly which makes it very hard to see if a program truly uses 100% of a CPU core without setting the programs CPU Affinity to a single CPU/Core.
oblivionenss wrote...
Franpa wrote...
The problem described isn't a memory leak, memory leaks are when a part of a program becomes unstable either due to bad coding or defective hardware and repeatedly allocates RAM to it self over and over until there is no RAM left at which point it either lags badly or crashes.Apex Sammoth wrote...
Feraele wrote...
Apex Sammoth wrote...
Lord Gremlin wrote...
Please, fix PS3 Blight Queller trophy bug already! It's ridiculous: this trophy is glitched and never unlocks. It's not uncommon and such things are usually getting fixed. So please, fix it already.
Also: PS3 version looks better than 360 and people should understand that bugs have nothing to do with raw processing power or something. Nothing at all. It's perfectly possible to create a game that runs perfectly on PSP and almost unplayable on 360 and PS3.
The PC version Looks better then Both I fail to see the point of this argument on a patch thread. What your not understanding about what was said in that post was that the way the games are developed on the PS3 is a bit harder to port over compared to the 360. So it is a bit easier to patch the 360 over the PS3 simply because they are developed on the same format as the PC. Actually there are some major bugs with Dual Cores / Etc and other PC Configs with this game so yes Processing Power sometimes has some issues. If the game is coded wrong not to use certain resources it can cause anything from Memory Leaks to the well known %100 Processor issue with this game.
Hmmm that could be whats causing "some" of the slow motion moving of characters that I see from time to time on my PC. I have an AMD core duo machine. I've seen the 100% processor issue, many times. Always thought it was some sort of memory leak, but as I read in the PC tech forums, (or somewhere) the layman always refers to "memory leaks" when sometimes its not a memory leak but something else. What that might be ..I don't know.
Anyways hope the Bioware team is on top of this. Even still, if I am good about logging out and restarting, or rebooting my machine, I can go and play again. Just annoying crashing in Denerim just before the Final Battle, after killing the first darkspawn general etc. lol Or sometimes when I am about to finish off the Archdemon. A little frustrating. But I always tell myself, hey another chance to do it BETTER. lol
Correct and that is what I call Gamebreaking. This is not a Dex bug or a quest line bug. This is a MAJOR problem. You should not have to restart the game or even change any core affinity. Im sorry but, I don't buy into the Game Works but you have to do "X". Esp when the BOX says I am well above the Sys Req. Keynote here is I don't have to do anything when playing other game including games that have higher System Req.
I do hope there is some sorta fix for this in the Upcomming patch. Any Info on these fixes would be nice Bioware ?
The 100% CPU is NOT a bug and it has been that way since the Windows 95 days. There are ways developers can reduce CPU usage when the CPU isn't required but it comes at the cost of accurate timing/switching between threads. You typically see such energy saving measures in hobby programs like Emulators and mobile applications for laptops etc.. Windows XP, Vista and 7 all feature I believe special "Intel" or "amd" drivers which will split the load of single threaded processes over multiple cores/processors seamlessly which makes it very hard to see if a program truly uses 100% of a CPU core without setting the programs CPU Affinity to a single CPU/Core.
Try .net framework 4.0 is said to fix it.
Modifié par Apex Sammoth, 14 juin 2010 - 06:33 .
joey_mork84 wrote...
Would hate to see this thread locked like the last one so.. um.. Keep it civil?
Retour en haut