Plazmid

That sounds like a great idea! I'm sure Obsidian would appreciate it. There are a lot of issues right now, too many for Forum to properly manage effectively. Any suggestions as to which one (bug tracker) to use? Not to mention that it needs to live somewhere.

Hello MouseHopper24, Any luck? That is a shame that you are having such a hard time. It sounds really frustrating. When you get the patch installed, try running the game as administrator. There is something fishy about the problem you are having, as the game is not crashing, you are stuck running the game for the first time. I hope one of the Obsidian Devs, or someone on this board who is familiar with PoE's registry or configuration files might make a suggestion. This might be a registry issue or initial configuration issue. There are references in the forum to the PoE registry entries. You might try, if you are feeling brave, deleting the PoE registry tree and then running the game again. I'm hoping that the Game will rebuild a missing registry tree if it can't find it. If not, I would save the tree before you delete it. That way you can put it back if you need to. Good luck and I hope you get your game working!

Just confirmed from the blog that this was a hot-fix for the unable to unlock/open doors and chests. Please, upload one of your saves so the devs can look at it. I personally use drop box.

From other posts, I had the impression Obsidian was working on several hot fixes. I too got a 500MB+ update last night/this morning. Perhaps this is the set of hot-fixes. Given how quickly this update came out, I can't imagine they had very much time at all to test the fixes thuroughly. Since we don't work for Obsidian, we don't know the whole story either. Keep your saves in a safe place and give Obsidian some time to fix it. I'm sure they will fix it. The devs have been very active. You may want to start looking into making arangements to upload your save that isn't working so Obsidian can take a look and see what went wrong. And, I don't think this was a Steam Issue. Unless you had auto-update off and it pushed the update anyway. I have updates enabled, so no big surprise.

I've gone through and checked maps (like the Vale) where my map was really dark before and it has been fixed (for me at least) in patch 1.03! Yay!

The dark map issue was resolved in patch 1.03. I just verified it in the Vale, where my map was really dark in the initial release (1.02)! Yay!

Perhaps a conditional set, that applies only to monks. Perhaps the game's mechanics don't make this so easy.

Hello BMac, Thanks for responding. It looked like a display issue. It is humorous. Man, it took me a really long time to complete some of these quests And, in some cases, I went back in time. Now that's some dedication! Cheers!

Hello Obsidian. I can confirm that patch v1.03 did not resolve this issue in the journal. I will attempt to upload my savegame (if you still need it) when I'm able to (at work currently).

Is this with v1.02 or with 1.03?

Yes indeed! Steam has started a very large download for PoE. I'm guessing a patch! Yay!!!!!

Some people don't want the patch, in that way they can troll all the day. Professional Trollers. No more rhyming, I mean it!

No, it was a hit. Notice the text "(Hit)". The damage was 0.0 because your target is already dead. Sometimes when a hit happens very soon after a target has been defeated it gets into the combat log, because the game hasn't had time to fully appreciate the dead status of the target. In those cases you will see a hit for 0.0 damage in the combat log. Ah, ok. Minor bug in the combat log due to order of events. Log posted an entry after the combat was actually resolved. Perhaps an enhancement would be to indicate "Target Dead", or, not log that event at all.

I'm confused. The diaglog says "Hit" Accuracy was way lower than defnse, true. Yet the roll was a 90, with a final being 65, a hit. What am I missing? Is there an instant "miss" if your Acc - Def is a negative number?

Rabbit season, duck season. To each his own. I do think Gog could use a different patch management system. I use both Gog and Steam, and others. Having to re-download all of the content (most of time) is a pain.

The article is 16 hours old. That "tomorrow" is "today." *Mind blown* "Tomorrow is today?" Said in the little green men voice from Toy Story....."Oooooo"

No, she is just *REALLY* smart

You sound like me. There are many types who play these types of games. I've seen some jokingly request that the Game be set to the hardest mode by default. That certainly isn't me. I'm the guy who plays in 'normal' and plays causually. The guy who plays perhaps 2 hours a day, if that, because that's all I have time for between work and other obligations that are more important to me. To me, this game is 'entertainment'. I play for enjoyment. Oh yes, there is something really, really wrong with us

I think all animals should have hats! And your mouse should be one of those thumb-ball mice.

Hello Silencio, There are several memory issues with 32bit systems, especially since Windows 32bit is restricted to 3GB of addressable memory. Check out the work-around FAQ. There is a reference there as to how to increase the amount of memory available to the game. To Quote from the FAQ For 32-Bit Machines There are reports of reporting crashing when transitioning on 32-bit machines. We are aware of the issue and attempting to fix it. This issue did come up on Wasteland 2, which is another Unity project, and a workaround was discovered by their fans: here You can change your system settings on your computer to increase RAM used by a single application. However, there are inherent risks involved when changing settings involving your operating system and any attempts to change your system settings will be at your own risk. Obsidian is not liable for any issues that might occur with those settings. Good luck to you! I hope you can work around this issue on your system.

Wow, Hopefully this is addressed in the 1.03 patch. If not, 1.04. Hopefully someone will start a new thread to track issues in 1.03 so all these issues don't bleed together.

Well, Some of this is the result of Kickstarter mechanics..... You make a pledge on Kickstarter (Most pledges include a digital copy of the game). And wait. Unfortunately, unlike other methods of purchasing a game, now you have a few years to build your anticipation and expectations.....and, you have the rights to a copy of the game. So, the game is coming down the pipe and release day happens. And, instead of pining at the store, you have the game, pre-downloaded via Steam or GOG. Kinda hard not to play when the game is in your hands, and you have 2+ years of anticipation built up. Imagine if you are the unlucky one who is exposed to some unpleasant bugs. This is the unfortunate other side of the blade of Kickstarter. Makes waiting for a patch all the more difficult, for different reasons. Not to mention the other oddities of a Steam and Gog ecosystem. Now most developers can't just post a hot-fix, the game is under the control of Steam and Gog. Now, not only must you get the patch built, you must also work through Steam and Gog (as a developer) to integrate and post a patch. Not as easy as it looks. And, is much more friendly to the combine as many fixes into a patch practise. This way you don't waste your time constantly posting to Steam (and, I bet Steam charges for the posting....they are a business too.) Wow, who woulda thunk how this type of technology and process would fundamentally change things like this...? Brave new world.

Hello Arulan, here are some workarounds. It looks like a Unity issue. Here is the post that addresses this issue: http://forums.obsidi...llscreen-steam/ Here is the post on Steam that shows one way of fixing this issue: http://steamcommunit...s/?id=414835388

Oh my lord! You just had to, didn't you?

And to think I was complaining about too much graphic Violins in the industry. I'll take that over Sax. Maybe a French Horn. Or a Tuba. Yes, a Tuba.