Jump to content

Jazou

Members
  • Posts

    87
  • Joined

  • Last visited

Everything posted by Jazou

  1. Source: http://forums.obsidian.net/topic/74701-obsidian-why-isnt-there-any-hotfix-yet/page-3?do=findComment&comment=1625275
  2. Oh, what a pitty. I would pay $173 to see your sweet bootie. But seriously: I didn't want to start a whining thread. I just wanted to get an answer from the developers why they are pressing as many fixes as possible into a single patch instead of releasing some (or one) pre-patches with stuff that is already done. It's sincerely interest, not a troll question.
  3. You have to try not to save and reload in any of the areas where you can recruit a party member. If the area has a building you can go inside and save there, for example. +1 But I also want to add that you should be careful when equipping new item with stats bonuses. Some of them can lead to stat stacking even without saving/loading within said areas. Best advice is to check your characters stats consistently and create new saves instead of overwriting older ones. Always keep the option to load an older one when your current savegame shows some irregularities. The only other option is to wait for the patch.
  4. It's a bug. Check: http://forums.obsidian.net/topic/73449-stat-bonus-modifiers-can-erroneously-be-applied-multiple-times-allowing-stats-to-grow-beyond-intended-values/ Temporary solution can be found here: http://forums.obsidian.net/topic/73449-stat-bonus-modifiers-can-erroneously-be-applied-multiple-times-allowing-stats-to-grow-beyond-intended-values/page-9?do=findComment&comment=1619415
  5. Point taken. In what kind of culture are they living? As ogres are just a fictional creatures I would say it's okay to say they are living as a tribe. PS: Also the ogres of warhammer are also living in a tribe culture.
  6. Okay. Probably you didn't read my posts attentively but it's okay.
  7. This answer is not just for you but for everyone who responded in a similar way: Maybe my statement was a bit cloudy. It's not about rushing to release unverified fixes. It's just about not holding back what is probably already fixed and tested.
  8. Of course BugsVendor is right that in planes and cars occur by far less bugs than in games. But that's because in embedded systems (like planes and cars) everything ist checked massively including complete model checking, which is something no one from us would finance for a computer game. The reason that planes and cars cost more than computer games is not only about the material/physical value - it's about the entire effort in otherwise sections - like the testing. So you really can't compare planes and cars to gaming software. -- Just another edit: But I also can't believe that the ones who are stating that they hadn't any bugs are right. E.g. there are items with +stats bonus which will give you the bonus permanently even after you've already unequipped them and so on... You must be really lucky if you didn't get into at least one bug. (Not saying that everyone experience this that much that it's becoming game breaking)
  9. Yes, it's a bug. Check: http://forums.obsidian.net/topic/73449-stat-bonus-modifiers-can-erroneously-be-applied-multiple-times-allowing-stats-to-grow-beyond-intended-values/ -- Edit: (Cheating)-solution can be found here: http://forums.obsidian.net/topic/73449-stat-bonus-modifiers-can-erroneously-be-applied-multiple-times-allowing-stats-to-grow-beyond-intended-values/page-9?do=findComment&comment=1619415
  10. I have to add: Nevertheless I would appreciate if there would be some official announcement about the known bugs to inform people like you and preventing them from play before the game is patched.
  11. Offended? Dude, I would feel offended when they would have created bugs intentionally, but feeling offended by bugs which can happen to every developer seems kind of stupid. I'm very sure these bugs annoy Obsidian much more than you.
  12. Releasing fixes without testing them will inevitably introduce new bugs. Testing a fix adequately is a very labor-intensive process. Testing multiple fixes at once is, generally speaking, not much more labor intensive than testing a single fix. Because of this, it is more efficient to bundle multiple bug fixes into a single patch than it is to release multiple patches each of which fixes one bug. For example, imagine they have 10 bugs to fix. Then imagine that creating a fix takes 2 days and testing a fix takes 5 days. If they make one patch for all 10 bugs it takes them (10 x 2) + 5 = 25 days to fix those 10 bugs. If they put out 10 separate fixes then it takes them 10 x (2 + 5) = 70 days to fix all 10 bugs. Yes, the first two bug fixes would come sooner (one on day 12 and one on day 24), but the other eight bugs will be around longer and the process of fixing them all will take an extra 45 days. Obviously these specific numbers are totally made up, but they illustrate something that is real. If you're going to fix a specific bug, the first step is to identify those use-cases where the bug occurs. Based on the found use-cases you build proper test-cases which will serve as an indicator for the targeted bug. If the test-cases have any kind of intersection with test-cases from other bugs, than of course they will be tested together, but often there isn't any intersection and than you wouldn't get any benefit by testing them at one go. So, normally that kind of separated bugs (without intersection in test-cases) are tested in separate sessions and mostly right after implementing the probable fix. That's why I was thinking that there could be already some verified fixes on the developers computers which are just hold back because Obsidian don't want to bring an update where people will scream "B-b-but my issue isn't fixed with this update!" I got the feeling that some fixes are hold back to release a super extensive 1.03 patch so almost no one could complain about. I know that releasing pre-patches/hotfixes is a bit of extra effort. But you have always to ask if this effort is worth the benefit that some customers could get from it. PS: I'm a developer by myself and this is how we handle it in our company. But it's just a small one for individual industry software, so I don't want to pit myself against game-developers. It's just why I thought that there indeed could be already a small hotfix for at least one serious bug.
  13. Dear Obsidian, first at all I want to clarify that I respect your hard work and you guys did really create a great game. This thread is not determined to be a troll or whining thread - instead I want to ask a genuine question: Why isn't there any hotfix yet? I did already ask this question inside the stat stacking bug thread but as I think that my posts probably weren't read by devs, I wanted to separate this question in an own thread. Please Obsidian, don't do the mistake to wait for delivering one big update that fixed as many bugs as possible. Instead please deliver a hotfix as soon as possible so that at least some bugs (or even only one) get fixed in short time. We don't demand an all-in-one fix for "everything" - just sharing what is already done would be amazing. Every day there are more players getting into troubles and I'm sure some of the reasons are already eliminiated and are just waiting for other fixes to provide all of them together within the announced patch. I have the feeling that the patch got already a bit delayed because you want to fix as many bugs as possible within this week. But in some situations it's better to satisfy the crowd step by step instead of waiting to make everyone happy at once. Please note: This is not a rhetorical question - I really would appreciate an honest answer. What are the reasons to put many fixes within one update instead of providing small hotfixes to the community when there are that kind of critical/game breaking bugs? Or didn't you fix at least one of them yet? (I wouldn't blame you for that either!) I just would love to hear an official statement - please give us more info about the actual state. Best, A fan of your work
  14. I still don't understand why there isn't a hotfix available when some problems are probably already fixed. We don't demand an all-in-one fix for "everything" - just sharing what is already done would be amazing. Every day there are more players getting into troubles and I'm sure some of the reasons are already eliminiated and are just waiting for other fixes to provide all of them together within the announced patch.
  15. Und noch eine andere winzige, aber doch störende Kleinigkeit im Schwarzen Hund: Datei: 07_cv_gilded_vale_innkeeper.stringtable <Entry> <ID>3</ID> <DefaultText>"Ich hätte gerne eine Zimmer."</DefaultText> <FemaleText /> </Entry> sollte natürlich lauten <Entry> <ID>3</ID> <DefaultText>"Ich hätte gerne ein Zimmer."</DefaultText> <FemaleText /> </Entry>
  16. Ich weiß ja nicht, ob das den Sinn zu weit verfälscht, aber besser finde ich: "Er trägt eine Augenklappe mit der aufgestickten Abbildung eines Augapfels und während sein eines Ohr als verstümmelter Rest dessen nur noch zuckt und krampft, stellt sich das andere munter auf als du dich nährst." -- EDIT - Oder Vorschläge nach Einbeziehung von Gruftlords Post: "Um seinen Kopf trägt er eine Augenklappe mit der aufgestickten Abbildung eines Augapfels und während sein eines Ohr als verstümmelter Rest dessen nur noch zuckt und krampft, stellt sich das andere munter auf als du dich nährst." oder auch "Um seinen Kopf trägt er eine mit einem Augapfel bestickte Augenklappe und während sein eines Ohr als verstümmelter Rest dessen nur noch zuckt und krampft, stellt sich das andere munter auf als du dich nährst." oder eben auch "Eine mit einem Augapfel bestickte Augenklappe ist um seinen Kopf gebunden und während sein eines Ohr als verstümmelter Rest dessen nur noch zuckt und krampft, stellt sich das andere munter auf als du dich nährst." oder "Um seinen Kopf gebunden trägt er eine mit einem Augapfel bestickte Augenklappe und während sein eines Ohr als verstümmelter Rest dessen nur noch zuckt und krampft, stellt sich das andere munter auf als du dich nährst." -- Nochmal ein Nachtrag: Von mir aus könnte man auch den hinteren Teil der Sätze nochmal umstellen: "... und während sein eines Ohr als verstümmelter Rest dessen nur noch zuckt und krampft als du dich nährst, stellt sich das andere munter auf."
  17. What is PC standing for? (I guess it's not Personal Computer ) And if the answer to my first question won't help to know which cipher abilitites are affected - which are?
  18. I have very similar specs to yours and never had any problem with game performance/lags. (i7-4770K 3.5Ghz, 16GB Ram, AMD 7950 3GB, but Windows 8.1) Your hardware should run this game smooth easily. Maybe driver problems or antivir is scanning your harddrive? (slow harddrive?)
  19. For everyone who's same as dumb as me: When it's called you shouldn't save within the areas where you've recruited your companions, it doesn't mean you also shouldn't save in their sub-areas. So if you want to save e.g. within Gilded Vale just enter a sub-area (e.g. Black Hound) and feel free to save without increasing stats. Maybe for everyone else this was already a trivial conclusion, but I thought I couldn't save within the entire areas including sub-areas.
  20. Exactly the same bug happens to me! But only sometimes - so it's not really feature breaking because it doesn't occur all the time.
  21. Oh, thanks for the info Voss. I was reading all that stuff from former lives because I thought it's relevant for the later story.
  22. Ich danke allen Beteiligten an der Übersetzungsverbesserung für ihre Mühe! Keep up the good work
  23. They already announced that update 1.03 will probably be released this week. And maybe they just need a few more hours or days to really make sure that their fix doesn't create different problems? It doesn't benefit anybody if they release a rushed hotfix that even causes more problems than it solves. Pe patient (yeah, I know, it's hard) and let them do their job, QA included. They know the problem and they work on it. There is nothing else they can do at this very moment than trying to deliver the best possible solution. I'm just scared that the scheduled update 1.03 won't come this week because of many bugs that occured/got attention after the original announcement. I don't want the upcoming update get delayed just because not "every" bug is already fixed. In some situations it's better to satisfy the crowd step by step instead of waiting to make everyone happy at once.
  24. The problem is that there occured so many bugs right now that I don't think it will all be fixed within a few days. I think if they've already fixed some of them, it would be better if they would release them now/soon. Every day there are many new players who start their game and will suffer from this bug. This will decrease the fun while playing massively. (or destroy it completely) And this will worsen the general impression of PoE for many customers too. Me - personally - would be upset if I would ruin my savegame/life time while the fix for this problem is probably already on Obsidian's developer computers. I don't think that rolling out hotfixes will increase the general fixing time that much that it isn't worth the benefit for thousands of current players.
×
×
  • Create New...