-
May 16 2012 08:26 AM #41
Re: Sapience - Add this to known issues
Please add follow problems to the germen/french version of the known issues:
- outdated translations of skills, traits and legendary attributes from ministrels and champions (are still Pre-Isengard)
- false names from Relictmaster and Forgemaster in Dunland and The Great River
- invisible daily taskcounter in the questlog
- french map of Eriador in the german client
http://forums.lotro.com/showthread.p...an-Translation
-
May 16 2012 08:29 AM #42
-
May 16 2012 06:43 PM #43
Re: Sapience - Add this to known issues
More bugs for you. Here's what the Greater Scroll of Delving looks like when you have it in your inventory bag;

Icon is normal when these scrolls are in vault or shared storage, and they're also showing up correctly in tooltips when linked to chats. Icon only gets screwed up when it's in the bags.
Strange. Really strange.
Edit: That specific type of scroll seems to be the only one bugged. Stat legacy scrolls, "Legacy Tier Upgrade" scrolls found from a lootbox, both types of empowerment scrolls etc, are working correctly.Last edited by Elaida; May 16 2012 at 06:46 PM.
Leader of Freelancer, Eldar
Kinship founded at 22th September 2007. We're always looking for good fellows to join our little nuthouse. Click here!
-
May 16 2012 10:26 PM #44
Re: Sapience - Add this to known issues
So 90% of the cards being used
You have 2 max lvl chars that look around a lot and do deeds http://www.youtube.com/watch?v=CpIxPbN9azQ
Playing on 'ULTRA' is no big thing if that's all you do.I told the people harping on about 'lore breaking' they were tedious and boring, so they voted away my one point of rep.
-
May 16 2012 10:37 PM #45
-
May 17 2012 02:02 AM #46
Re: Sapience - Add this to known issues

Achilles: At night I see their faces. All the men I've killed. They're standing there on the far bank of the river Styx. They're waiting for me. They say, 'Welcome, brother'.
-
May 17 2012 05:46 AM #47
Re: Sapience - Add this to known issues
Okay. Slow down a bit and let me get this straight.
There are two totally different hardware manufactures. Whos products are really different. Not only in the way the hardware is physically build it self. But also in the ways the software like the drivers and internal protcols are working, designed and created.
Your programm produces the same error on both of those hardware products.
And you are telling this is caused by two individual issues those both Hardware products have started to produce at the same time. And somehow it was the time U.7 was released?
I call that 'balls'. And would like to hear what Nvidia and AMD has to say to that theory of failing hardware.
The most common factor of those hardware products is directX. But I dont see you claiming Microsoft to be the root of the problems?
Okay, If you prefer. Lets call it an Hardware.Issue. An issue your programm has with the hardware.
But as well I could say its an engine.issue when my car runs out of fuel and I call BP or Shell to fix it.
If you cant play the game on ULTRA you are out of luck ^^ lower settings are no longer supported.
-
May 17 2012 06:09 AM #48
Re: Sapience - Add this to known issues
Hey again, guys and gals. I found another annoyance I haven't spotted before... Look at this screenshot, and the area covered by the "Opponent Vitals" UI element. Basically, it's way too large and the area covers the quickslots bars at the bottom of my screen as well.

The problem: Opponent Vitals element seems to get some kind of "always on top" setting on it occasionally. Sometimes when I have a target selected, it blocks me from clicking the first five quickslots on the first quickslot bar; the default, unmovable bar that is. Second and third bar in the screenshot are undocked, and the skills in those two are clickable.
6th skill in the first bar is only half-covered by the Opponent Vitals element. When the issue hits me, left half of that icon is not clickable (it doesn't show the skill tooltip for example), right half of it works. I haven't spotted this issue before, but as we're talking about bugs, I think this does classify as one.
I can't see any reason for that element to be so large anyway, as less than half of the reserved area is ever being used. Could the area used by this UI element be reduced in size - not just to avoid this kind of issues, but also to allow for more accurate customization of UIs? In that screenshot, vitals are already pretty much as low as you can put them. I'd prefer having them even further down on the screen.
As can be seen in the screenshot, I am indeed using Custom UI. However, I also tested it with the default UI and the problem appeared with that as well; Opponent Vitals are sometimes blocking the access to docked quickslot bars... In fact, with the default UI, all three quickslot bars became blocked instead of just the first one.
The issue may be related to alt-tabbing between a full-screen game client and desktop / other softwares. I don't see why alt-tab should break it really, but it seems to be nearly foolproof method for "getting this bug to work", if such expression can be used. :P
Edit: Ok, the post below this says it's been there at least from 2010. I've never spotted it, though I rarely click the icons on the FIRST quickslot bar. Paying a little more attention showed to me that it's in fact blocking bars 1-2 with the Custom UI, bars 1-3 with the Default UI.
First bar is always blocked after alt-tabbing or selecting a new target in both UIs. Second bar is blocked in both UIs, until any skill (or an empty skill slot) on that bar is clicked. Third bar has not been blocked, not even one single time, with the Custom UI, but when using the Default UI, it works similarly with bar 2; skills behind the vitals are unclickable until you click one that's available or use one on that bar through key mappings.
Annoying. If the element area had it's pointless bottom half removed, there would be no issues with the current positioning of that element. What surprises me though, is that player's own vitals do not block anything, ever. Not in my game client at least. That feels strange, as the elements itself seem like they were simply copies of each other, just with the portrait mirrored.Last edited by Elaida; May 17 2012 at 07:52 AM. Reason: Added a bit more information to the bottom...
Leader of Freelancer, Eldar
Kinship founded at 22th September 2007. We're always looking for good fellows to join our little nuthouse. Click here!
-
May 17 2012 07:04 AM #49
-
May 17 2012 07:54 AM #50
Re: Sapience - Add this to known issues
As someone pointed out - 'only' Nvidia and ATI =)
On low and medium overall graphics settings, the wardrobe light goes away as you turn the character around.
(And bouncing weapon on my back is making me seasick!)
-
May 17 2012 08:16 AM #51
Re: Sapience - Add this to known issues
Please add these...
You in a box cosmetic no longer shows your dyed color. The box wont even show on your character screen unless it's the original version.
Burglar in stealth can barely see your character.
Sounds some sounds are way too low while others are way too high. Have tried adjusting settings numerous times to no avail.
-
May 17 2012 05:42 PM #52
Re: Sapience - Add this to known issues
So, good news on the jet black character issue everyone. We were able to repro it on a couple of machines on our side and found the little error that was causing it to misbehave on some machines. You'll see the fix in a future update, but it will be Known Issued for now once we get the known issue translated. Thank you all for the reports and the information!
Seraphina Brennan -- Turbine Community Specialist
"When in doubt, reach for the stars. That way you'll never come up short."
Don't forget about our Facebook page! and Twitter page! =^_^= Questions on our policies? Read the community guidelines!
I try to answer all of my PMs, but I get a lot! Sometimes I may not get back to you, but I have read your mail!
-
May 17 2012 06:31 PM #53
Re: Sapience - Add this to known issues
Abso-bloomin'lutely great news! Previewing cosmetics and dyes are pesky at best currently, and I know not everyone gets the same issues. So I'm very glad to hear it was findable. Don't throw out any of those machines over there, no matter how obsolete they get... some of our rig specific bugs may be riding on them. *grinz*
♥Wargs Rule!♥ *But only because we have no playable feline races.*
˙˙˙sƃuıɥʇ ǝʇıɹnoʌɐɟ ʎɯ ɟo ʍǝɟ ɐ ǝɹɐ ǝsǝɥʇ*sƃuıs* ¡ʎɯ ɥo ♥sǝıƃɹɐʍ puɐ 'sǝssǝɹʇsıɯ-ǝɹol 'sǝsɟlǝ♥
Founder & Altoholic: playing wargies and loremistresses since 2006 SoA beta. *Jingle Jangle!*

-
May 17 2012 07:11 PM #54
Re: Sapience - Add this to known issues
Celestrata, thanks for the information, it's appreciated as ever.
But, what about the wobbly weapons and sound problems experienced and /bugged by many players on these forums - are these not even considered known issues yet? Without wishing to sound hyperbolic these issues negatively affect the game immersion so much for me that I have currently stopped playing LoTRO.
-
May 17 2012 11:02 PM #55
-
May 17 2012 11:08 PM #56
Re: Sapience - Add this to known issues
To be honest, at first the weapon bouncing looking weird. Then it sort of grew on me and I thought they looked more realistic. How often do we actually "run" around for any long period of time? Not much really.
-
May 18 2012 12:12 AM #57
Re: Sapience - Add this to known issues
I don't get it.
Do you have your character constantly set on walk?
Or is it that you swift travel everywhere?
My lower leveled toons run all over the place.
And even my capped guard in combat has her main weapon and shield bouncing all over the place. In draig my shield will hover above my arm as Draig does his thing that makes you bounce. Any glow from LI's make it even worse. To me, it looks like a TV representation of what its like to be high.
-
May 18 2012 12:23 AM #58
Re: Sapience - Add this to known issues
I'd like you to add one more thing to the known issues of U7.
Currently, the L65 Helegrod Warden 6/6 Armor bonus is not working. It is supposed to remove the BPE penalty from Recklessness stance but it is not doing so. Other wardens on the forums have also confirmed this, and testers can easily reproduce the bug by strapping the armour and noticing that both on the tooltip of recklessness and on the character panel, the recklessness BPE penalty remains the same.
I have already submitted a bug report on this, and I've asked other wardens to do so. But I thought it can't hurt to have it put on the U7 known issue list as well.
By the way, please mind that I have confirmed this ONLY on the L65 version of the armor. I don't own the L50 one so I dunno if that one is also bugged, but I wouldn't be surprised if it is as the underlying code should be the same. When The Powers That Be go thorugh this bug, it would be advisable to also check the L50 version.
One last thing, this 6/6 bonus was created previous to the Warden revamp, so the removal of the Recklessness BPE penalty no longer has the same meaning and usefulness as it had pre-revamp. The Powers That Be should seriously consider revising this bonus. I suggest that since the 3/3 bonus improve warden's taunt threat by 15% ( I dunno if this is working btw, I have no way to test it) then maybe the 6/6 bonus should improve tanking threat in some way. Maybe lifetap gambit duration? Fist-shield aggro transfer gambit buff? I dunno, up to you guys.Last edited by EtherSunrider; May 18 2012 at 01:31 AM.

-
May 18 2012 12:31 AM #59
Re: Sapience - Add this to known issues
Settings on High (as was suggested).

Uploaded with ImageShack.us
Does not look realistic.
Took a bit to get a good screen shot of it, but in any case, /bug it every time?
Seriously, this happens every time I go into combat.
-
May 18 2012 02:53 AM #60
Re: Sapience - Add this to known issues
It's a bug in player character animations, plain and simple - the weapons are out of sync with the avatar and the LI weapon glow is out of sync with both. I'd make a good wager the LM bug is also related to this problem. Thank you for the evidence Anwiga.
The sound engine is also suffering from issues of not properly syncing with the environment or even obeying or retaining player's volume level preferences.
For me, considering this was deemed release quality code, these issues are unforgivably shoddy.
-
May 18 2012 03:36 AM #61
Re: Sapience - Add this to known issues
No. You don't bug it every time. You make one report per specific bug and select the correct frequency from the dropdown menu shown in the /bug form. Have you even taken a look at that form, if you aren't aware of how to fill it in?
If you see more than one different bug, that you think to be unrelated to each other, you should make one report for each of these bugs. Combining different bugs into one reports is not a good way to do it, as it can make things much more difficult for developers depending on what kind of tools they're using for bug tracking. I've seen a few tools, and with most of them, having just one bug listed per report is the only proper way to go.
In your case, as the bug happens every time you go into combat, you select "Every time" as frequency. Then you fill in some instructions on how to make it happen. For example, "Go into combat with Class X (of Race Y if the bug only appears with specific race), with weapon types A (and B, if it's a dual-wielding class) in use".
Basically, this kind of very simplified instructions are always welcome. It may feel obvious to you, but if the reader of your bug report has never seen the described problem himself, he may have no idea what you're talking about - until he reproduces it with your step-by-step instructions.
It also makes the whole process quicker, as developers have clear instructions of reproducing bugs; it saves time, when they won't need to figure out how to make all these bad happen, or with what race, class and weapon type.
In my opinion, bug report can never have too many details or reproducing instructions.Leader of Freelancer, Eldar
Kinship founded at 22th September 2007. We're always looking for good fellows to join our little nuthouse. Click here!
-
May 18 2012 04:14 AM #62
Re: Sapience - Add this to known issues
The black character (also with darkness stuff) happens to me on my PC ant Notebook as well. But more important thing after U7 bothers me. I can't hear any UI sounds loke players joining/leaving fellow or raid, NPCs talking and so on... Haven't changed the Auio settings a bit...

-
May 18 2012 08:49 AM #63
Re: Sapience - Add this to known issues
Second Marshal Luc Brandenbuck ~Battlemaster~
Stalker's Enemy*Reaver's Enemy*Blackarrow's Enemy*Warleader-Foe*Weaver's Enemy*Defiler-Foe
Champion:'The only thing our opponents can do that we care about is die.'-Graalx2
-
May 18 2012 08:58 AM #64
-
May 18 2012 10:30 AM #65
Re: Sapience - Add this to known issues
(full quote posted, as requested)
The reason that the Vitals UI element is so large is because buffs/debuffs are part of it. The UI container has to be large enough to accommodate a HUGE number of buff/debuff icons. I have seen even this amount of space filled.
I think it would be a good idea to separate the buff/debuff area from the Vitals UI, and allow us to customize how buffs/debuffs are displayed a little more (vertical vs horizontal vs a big block like it is now). I know that there are LUA plugins that do this, but I'm not a big fan of most LUA plugin (most have to be updated too frequently to be worth it). This would also reduce the size of the Vitals UI to something more reasonable.
While you burn at the stake, I dance with the flames. I take what you love and leave you in tears. I am relentless, unpredictable, and waiting for your last breath.
-
May 18 2012 11:20 AM #66
Re: Sapience - Add this to known issues
As the main issue in this thread has been looked into and is now a known issue, I want to close our discussion out here. I don't want this thread becoming a jumble of issues, as I'd rather track each issue in a separate thread. However, to that end...
JoeSO and others that mentioned the sound issues: There's already actually a thread running on the sound issues. Please discuss them in that thread in order to help us with our investigation. (http://forums.lotro.com/showthread.p...und-issues-WAI)
Lainalagos and Anwiga: This is the first report I've heard of the weapons performing this way. You both have said you have /bugged this, which is great, but I'd like to open a new thread on that subject so we can keep that in a new discussion.Seraphina Brennan -- Turbine Community Specialist
"When in doubt, reach for the stars. That way you'll never come up short."
Don't forget about our Facebook page! and Twitter page! =^_^= Questions on our policies? Read the community guidelines!
I try to answer all of my PMs, but I get a lot! Sometimes I may not get back to you, but I have read your mail!
-
- Community Guidelines
- New Posts
- Dev Tracker
- Forum List
- Discussion Forums
- Classes
-
Worlds
- Arkenstone
- Brandywine
- Crickhollow
- Dwarrowdelf
- Eldar
- Elendilmir
- Evernight
- Firefoot
- Gilrain
- Gladden
- Imladris
- Landroval [EN-RE]
- Laurelin [EN-RP]
- Meneldor
- Nimrodel
- Riddermark
- Silverlode
- Snowbourn
- Vilya
- Windfola
- Withywindle
- Anduin [DE]
- Belegaer [DE-RP]
- Gwaihir [DE]
- Maiar [DE]
- Morthond [DE]
- Vanyar [DE]
- Estel [FR-RP]
- Sirannon [FR]
- Bullroarer (Public Test Server)
- Community
- Gameplay
- PvMP







I believe the issue is because it had 2 lights, once in each side. And now they'r removed so there's only 1 left, and the character blocks light to the other side.




