Elm Trees

[Sindala]

Elm trees now have a huge 'aura' surrounding them that stops you from selecting a mob near it unless you have a 'select nearest mob' hot key set up.
Seems worst near Sable shores with the greater ulmus beetles but is also bad on AI with the ruxus.

[AmonGwareth]

Have you noticed if the aura is for large and massive trees or all trees? Cause no changes were made to the entity files for any of that.

[C`gan]

This might be the same thing I'm encountering in the yew forest where I can't select shining essence nodes (or treants or bloodsnouts or oastics) if there's a yew tree of any type on the same side of my character.

[Nia]

Yes, I had the same yesterday and the day before trying to select bright essence residue in the maple west of Harton Valley.

I used to call the flax "greedy" because when you would try to select some nearby sandstone (say at Pratt's Pond) you would have to move around or turn so the flax was no longer in view to select the stone. It was the very same thing that was happing to me over the weekend with the maples & essence.


Nia : Blight : Chronicles of the Twisted Guild

[velveeta]

that's been happening forever, i just ignored it as part of the game functioning.....

[TheRock]

I have to disagree with you Velveeta
I was out near Winter's Vale killing Than'kuk Scouts and it is very annoying when you can't select the scouts until they are very close. I have been out there before the update and never had that problem. I did not notice this happening in the doom though. When you have a clear view of the mob you should be able to select them like it always was. Something changed by accident.

Cheers

[AmonGwareth]

Okay, I think we've narrowed down the cause of this. A while back we switched a lot of in-game objects (mostly resource nodes) to be non-collidable in order to help with some performance issues. There are some differences in the entity files and we're looking into that as the cause. Thanks for your patience.

[Knossos]

I am wondering if that change to non-collide might have been made at the time as the stone direction markers which for my windows 7 x64 went from non-collide to invisible (unless the markers are either near the position of the toon when logging in or near a destination pad when teleporting - in both cases with the loading screen on and then visible with collide)? Or perhaps the stone direction marker phenomena is somehow related?

Knossos

[AmonGwareth]

I am wondering if that change to non-collide might have been made at the time as the stone direction markers which for my windows 7 x64 went from non-collide to invisible (unless the markers are either near the position of the toon when logging in or near a destination pad when teleporting - in both cases with the loading screen on and then visible with collide)? Or perhaps the stone direction marker phenomena is somehow related?

Knossos

No, they are still using the same file and are set as collidable.

[Knossos]

OK Thank you , Amon.

Knossos

[awdz]

Any timing on when this fix will go in? I was standing in an elm tree today, clicked on it to harvest and a tree that I could not even see in my window interfered with my gathering - "You are too far away from the resource node to gather resources from it." I turned a bit and then was able to harvest that tree with no further problem.

I also had difficulting selecting cedar trees when gathering from them earlier today. I've not tested other forests yet while gathering from them but have noticed issues with selecting targets while hunting when nearby trees (yew, thornwood).

[Vaz]

In short, all trees are like this. Glad a cause has been found and a fix might be on the way.