Jump to content
  • 0

Amalgamated bug report


Pop

Question

I'm about 40 minutes into a very leisurely paced run through the beta. Amuaua (or however you spell that) monk, good times. It will interest you to know that I've run into bugs. Here are a few of them:

 

 - At present, the fight at the Dyrford bridge between the party and the hooded dudes + their pet boars (shouldn't there be just one?) is an utter debacle, which I'm sure is some confluence of niggling combat bugs and unfamiliarity with the game systems, but more than that it looks like the combination of occlusion in the grassy area (?) and the color of the grass blending with the color of player indicators makes it very hard to track the whos and whats and whys of combat. The high resolution just makes things difficult to see. Beautiful, but incomprehensible. The indicators need to be good and thick and unmistakable when combat is happening.

 

 - It appears that priest spells that are described as only affecting enemies are affecting my party as well.

 

 - The priest spell "Despondent Blows" is ostensibly usable outside of combat but when activated, the spell won't cast and the targeting reticule apparently persists until the game is reloaded. No other mouse-dependent functions work while the reticule is up, though you can still switch characters with the hotkeys (note that the reticule persists when changing characters).

 

 - This has probably already been reported, but there is a problem with characters who get knocked out in combat being unresponsive after recovery. I played through the bridge fight three times - the first time I had cast a vampiric-type AoE spell in combat and had snagged one of my party members in the blast. After combat that character was locked in an unbreakable hit reaction loop at 0 stamina (while the rest of the party recharged in moments). Second time, two party members were knocked out but didn't get up once the enemies had been killed. Third time, a CNPC was knocked out, got back up after the fight, but couldn't be controlled. I reloaded from this point and was able to resume control of him.

 

 

 - Zoom bug: I've only encountered this at the starting area, near where the fight takes place (SEE ATTACHMENTS). Using zoom features in any other area, indoor and outdoor, seems to yield no problems, but it doesn't work here -  instead of zooming, it seems like one or two layers of the visuals are affected. While the size of objects and characters on the screen stays the same, fog of war radius constricts with "zoom out", and it appears it messes with water effects as well, creating an empty "ghost" of the waterwheel animation (see image #2).

 

- Beyond that, "The Dyrwood pt. 1" contains a brief shift from past tense to present tense that doesn't make a lot of sense (ex. "he did" vs. "he does"). It shifts back to past tense by the end of the text.

 

I'm out of upload space on this post so I'm writing another one real quick.

post-17393-0-92284100-1408416444_thumb.jpg

post-17393-0-29991800-1408416460_thumb.jpg

Link to comment
Share on other sites

3 answers to this question

Recommended Posts

  • 0
- There are font issues as well, though I don't know if they're related to the scaling function in the options menu. As you can see, there are margin issues with the header and the body of the text crowds the stylized first letter (I forget what they call that).

 

I'll drop by this thread should I inevitably encounter more bugs!

post-17393-0-18694800-1408417074_thumb.jpg

  • Like 1
Link to comment
Share on other sites

  • 0

Another bug - started up another game as a druid (much more intuitive class) and I'm running into the "replicating" modal ability issue that a lot of people seem to be having. But more importantly, after loading the game at one point I started receiving a new talent that looks bugged. Observe the attachment. Not only are there missing strings, the text that is there doesn't make much of any sense. The talent is essentially a fireball (?) with a very wide AoE that imparts a status effect, listed in the log as *missing string*. "Enemy X affected by *Missing String* for 54 seconds", etc.

post-17393-0-33188400-1408432017_thumb.jpg

Edited by Pop
  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...