deranged
Cipher
...and expert mode goes off... Now let's see if it is good for what it is.
IE games didn't adjust AoE sizes based on attributes. Which can change during an encounter!IE games were like that. You work it out. Flames can be a bitch at the start, but it would be way too easy with AOE markers - which is why I suspect people thought it was so OP, because it became a no-brainer when you knew exactly where it would go. Things like chill fog with a basic radius range, you get an intuition for it.
IE games didn't adjust AoE sizes based on attributes. Which can change during an encounter!
It's still less than ideal because I want to use the extra range to actually hit the enemies.IE games didn't adjust AoE sizes based on attributes. Which can change during an encounter!
Isn't the extra-range party friendly?
had that, too. seems to be tied to the flesh constructs, make sure you kill'em all before talking to azo again.Well the whole Sanitarium area is bugged to hell (on latest patch) and my progress has been halted... until patch. The whole area went aggro on me on first floor. Well done Obsidian. They sure had a lot of time to expend writing all those backer soul descriptions, but I guess a few 'minor' things slipped through the cracks.
Baldur's Gate would keep the areas cached in RAM (if you had enough) so while the initial load was slow, returning to areas would be pretty speedy. No such luck here, which is a pity because I wouldn't care if PoE used all 6GB of my RAM if it meant faster load times. No doubt Unity is to blame.Actually stopped playing for now because the long loading times make Defiance Bay unplayable for me. Which is weird. In BG 1/2 I remember having to wait 2 minutes or so for an area to load, but now even 30 seconds feels way, way too slow.
Easy there, chief. Whatever you do, don't post that on SA or they might actually do it.Baldur's Gate would keep the areas cached in RAM (if you had enough) so while the initial load was slow, returning to areas would be pretty speedy. No such luck here, which is a pity because I wouldn't care if PoE used all 6GB of my RAM if it meant faster load times. No doubt Unity is to blame.Actually stopped playing for now because the long loading times make Defiance Bay unplayable for me. Which is weird. In BG 1/2 I remember having to wait 2 minutes or so for an area to load, but now even 30 seconds feels way, way too slow.
Easy there, chief. Whatever you do, don't post that on SA or they might actually do it.I wouldn't care if PoE used all 6GB of my RAM if it meant faster load times. No doubt Unity is to blame.
No such luck here, which is a pity because I wouldn't care if PoE used all 6GB of my RAM if it meant faster load times.
No such luck here, which is a pity because I wouldn't care if PoE used all 6GB of my RAM if it meant faster load times.
NEVER encourage incompetent developers to eat up all the RAM they want.
No such luck here, which is a pity because I wouldn't care if PoE used all 6GB of my RAM if it meant faster load times.
NEVER encourage incompetent developers to eat up all the RAM they want.
What else is it there for? Consuming available resources to make something more responsive is perfectly reasonable. Many optimisations exchange memory use for speed. This isn't demoscene wanking.