Jump to content
  • Sign Up

Plazmid

Members
  • Content Count

    73
  • Joined

  • Last visited

Everything posted by Plazmid

  1. Yep, most patch notes do not include every last thing. Usually just the highlights. Or, some dev would be stuck writing a small novella every time a patch was released.
  2. Wow! A combination of cloud syncing, a faulty save file, and multiple systems using the same Steam account. That's cool that the problem was investigated and resolved. Nice!
  3. Hmm, if you encountered it KracsNZ, then it happened. Its just rare. I would keep this open for a bit longer, at least until 1.04 (official) or 1.05.
  4. Please post your saves via dropbox or similar so the devs can look at it. I would include a save that is broken and the save that is working.
  5. Here is an interesting observation. I don't have the beta option for my version. The only beta option listed on the beta tab is "none" I have the "Royal Edition" installed. Core OS is Windows 7 x64 Pro How can I start using and testing with the beta builds?
  6. I really think this is a very effective approach. Rather than releasing patch after patch blindly, a beta patch program with major fixes (to a point, else it will never get released) and a spattering of minor fixes for those willing to try. At least when they formally release 1.04, it will hopefully be pretty solid (but with known issues). Then, 1.05 will go to beta and we can beat on that one.
  7. Wow, Great problem description. I wish others were as thorough as you have been.
  8. From the sound of that, this doesn't look like a configuration issue anymore. This sounds like an issue with the core save/load codebase. In yours and others cases, its following a different path than some of us. The question now becomes, why? Sounds like the devs need to take a very careful look at the code that touches saves and figure out what is going on. Can Obsidian push a dev version that has debug enabled and can dump info on the whole save/load process?
  9. Well, no wonder Obsidian is having so much trouble. There doesn't seem to be a unified version of the game. And if the systems Obsidian QA is using don't match up to the rest of us..... It would seem that the first step is to figure out why the disparity! This save game issue is very pervasive, from the amount of forum and board traffic I'm seeing. I'm also running Windows 7, and haven't hit this issue. So, why is my system different? Someone needs to figure out why these systems are different. Are there subtle setup differences in the original installs? Did installing the Beta (Original) change things? I'm betting (from experience) that some build made configuration entries that are no longer used and the released game installer didn't not perform effective cleanup. It's time to start some good forensics Obsidian. Hey nPHYN1T3, does your registry settings reference the offending locallow directory? This is a mess.
  10. This seems to be more in line with the issues experienced. I would give this a try.
  11. The devs left a little note on the patch notes for 1.04 apologizing for their seeming lack of responsiveness. They are really busy. I can believe it.
  12. I would prefer not to disclose such information. I hope you will not be offended. Nope, not offended at all. Just curious. Cheers
  13. I saw that Obsidian is pushing patch 1.04 now. See if that addresses your issue (and everyone else who is having this issue) [Crossing Fingers]
  14. My money is on changed save validation code since this area was probably tweaked to retroactively fix save games from initial release. Is there a way to dump debug that will shed some light on the issue? There have been hints that some Linux users are also hitting this issue, which points back to internal save validation code. Maybe its too sensitive and exhausting retries. Only way to know for sure is to get the validater to dump debug and then re-scan the saves directory. See if someone can whip up a way to instrument this area of code and push it as a hot fix so you can debug this.
  15. Programmed ? Of course! Released ? Never, except exactly one. For just a couple of reasons: Spend a lot of time to make perfect architecture Defensive coding Competent QA team Good architecture leave no places for most stupid "bugs", defensive coding style & techniques forced across team by team lead(s) with apropriate monitoring (code review, etc.) leave no places for pesky "bugs". In most cases defensive coding allows to detect these "bugs" at first run after they are was introduced (in simplest cases via the appropriate assertions and invariants checks across the code). I personaly not even count these as a bugs because it mostly never even reach the QA team and detected by programmer himself during write-run-check cycles. For me bugs are the errors which are detected by QA team (or, the worst case - by user) and which are really not obvious errors in code. It hard to believe but my team never released any "game-braking" bugs. Actually we never released any major bugs, thanks to 3 points I have mentioned above (well, it is also because quality of the products was a priority for our company) I have only one relatevely serious bug released in my practice. It was threads synchronization bug. It reveal itself once in a 2-3 month (for a QA machine run in 24/7 mode, just to say), so it was really tough beast. It was never fixed because whole subsystem were refactored and rewritten (not due to the bug but for other purposes). So, PoE situation is not normal under any circumstances. It is not normal to have first-day patch, it is not normal to have tons of obvious bugs detected by users in fisrt 3 days after product release. I would say it is unacceptable, especially for bugs in game mechanic, which are essential for such game types. Does we complain about the annoing but harmless UI bugs ? No! We complain about broken abilities which could be detected by QA team before release, we complain about broken combat math which could be perfectly self-tested by set of good unit-tests or via other techniques. So we complain agains the things which never should occur for released product. I hope you get my point now. Hey Alex, What was the name of the game your company released, if you can tell us? At least describe it Like the core system (Epic's Unreal engine, Gamebryo, etc.) and the target platform (PC, Xbox, etc.) What was the size of the dev and QA team, and what was your ballpark budget?
  16. There appears to be something afoot that was introduced with 1.3 Is everyone having this issue running Windows and using Steam? http://forums.obsidian.net/topic/75825-30-hours-all-gone-saved-games-missing/
  17. So, what OS are those of you having save issues on? Is there anything remarkable about your user profile? I.E., not an Admin, but a user? Perhaps multiple drives, with the OS mapped to a drive other than C. Yes, I'm grasping at straws. Perhaps some dev introduced an absolute path issue in some of the code that was merged. I know some applications have relative path issues with Windows 7. And, there can be odd permission issues, especially with the %user%/%appdata% permissions. So far, it looks like everyone having the issue is running Windows.... Hmmmm.
  18. The interesting part of this issue, and I've seen this issue posted quite a bit, is that the default action seems to be to verify the steam files. Here is my take on this issue: There is definitely something wrong with the save/load mechanism. From a practical point of view: 1) These issues started with the patches with Steam. (At least it seems that way) 2) The saves that have been uploaded are not having issues on Obsidian's systems, implying that the save files are not corrupted. At least some of them are not. 3) There seems to be evidence that it is a client/host issue. So, what are the requirements, from an application level, to recognize a save file? Next, we need a tool (or method) to verify the pieces required. ie Registry, Application, config files, app path, etc. The only way this issue is going to get fixed is to identify what is going wrong. Obsidian, can you create a tool that will verify savegame integrity and can validate the other requirements needed to verify a savegame as valid? Perhaps there are some arguments we can give the executable that might help you isolate the problem. Re-installing the application over and over again is a recipe for frustration.
  19. Oh, BG, BG2, and IWD were all buggy when they first came out. Some Bethesda comments also brought a chuckle, since I remember vividly how bad some of their first games were. Does anyone remember Skynet or Daggerfall when they first came out? I also remember that everyone of these games got better over time. And I enjoyed them all, flaws and all. But, I do not believe Obsidian did this on purpose to PoE. I don't think any of these companies released buggy software on purpose. I can't think of why a company would do that when they depend on selling games. And, if you look at the art work and dialog, and the creativity that went into it, the devs and design team poured some serious effort into this game. It really is unfortunate. I can say that I'm a little disappointed that here is yet another game that is still a little rough. But it is more of an "Ah man, I wonder how many patches this one will take?" But, it will get fixed, I'm pretty sure of that. It definitely could have benefited from a lot more testing. Any piece of software can. I'm just going to wait and sip my coffee. And play some PoE. Knowing full well that I might hit an issue here and there. Nothing in this world is perfect, although we would all like things to be.
  20. Fantastic! (Yes, pun intended) I'm glad the laptop cooler worked in your case. Many laptops aren't really designed for intensive games. As pointed out in other posts, effective cooling tends to be an issue and many manufacturers take a gamble that most users will not push the hardware that hard in reality. But, some really do. Unity, as a whole, tends to really push hardware since it is graphics intensive. You have the CPUs working hard, and the GPU(s) also working very hard. That generates a lot of heat, which you can feel from a laptop streaming out the vents and the fan running at full tilt. Not too far a stretch that many feel their system is running too hot since it probably feels hot from what was described. And the fans are most likely running loud. In comparison to how the laptop feels and sounds when you are not gaming. Makes sense to me.
  21. Hello Maquabra, The GOG patch to Build 530 (1.3.0530) posted today. You can update your game to the hot-fix release. Not perfect, but better. Barring a slow internet connection.
  22. I'm pretty sure it includes the other hot fixes. As Romeo pointed out, the build is now 530. The previous hot fix was in build 526.
  23. Well, I noticed tonight we are now on build 530. Anyone know what changed?
  24. Don't want to come out as rude but I can't see how it has anything to do with this thread . Game is tones of fun - still they had a horrible bugged release that's all. I have to agree with what appears to be the baseline premise of BugsVendor. This game seems to have been released prematurely. At least that is the retrospective view now. Yonjuro also made an excellent point in that we, as the end-users and enjoyers of this game, can't be 100% sure of what Obsidian knew, and did not know, about how the game would fare in our hands. We really can't be sure can we, that Obsidian released the game knowing parts were broken? There are some indications, yes, but I wouldn't bet my mortgage on it. And, what about Obsidian's vested interest in the success of this game? Their business success depends on the success of this game. And from what I've seen, they have truly poured blood, sweat, and tears into this. It doesn't make any sense to me that if Obsidian intended to hoodwink us, why did they put any effort at all into this? Wouldn't it have been easier (and less expensive for them) to have kept the game unfinished for as long as possible so they could run off with the money? All the evidence I've seen so far seems to point in the direction of good faith from Obsidian. I truly believe that they thought this game was release-worthy, and were not anticipating the volume and types of problems that we are seeing now. And, for those who are willing to try to understand, this game is not a toaster. It has been designed to run on multiple platforms (Linux, Mac, WIndows) using Unity. There were bound to be problems that you just can't anticipate. Not to mention probably lines of code into the 100s of thousands, if not more. This game is really complex. But, they have been willing to listen and patch their game. They are trying, and I can see it. Those of you having problems have every cause to be frustrated and disappointed. However, rather than gather pitchforks and torches, wouldn't it be more effective to support Obsidian in the hopes that they can fix the problems? Dead companies can't fix anything. Sacred 2 anyone?
×
×
  • Create New...