Could we please have a dev respond

[Gedachtnis]

For those that want to use 2 quickbar sets in order to have their General Skills in different quickslots for 2 different spec builds there is, to my knowledge only one workaround that will accomplish this, at least until Turbine fixes this bug.

The key to getting the memory to hold is clearing your character of all specs and specializations prior to switching Quickbar Sets and loading a new Spec Build.

The term Hotbars as used below means a set of quickbars, the ones you can swap (Shield/Sword/Horse)

From my Guide;

However if I like to have different setups of General Skills according to my spec a couple of issue arise.

If I try to do it on all on one Hotbar I have to manually move my General Skills each time I switch specs and that usually means some if not all Trait Skills are going to auto populate all over the place.

To get around this;

Manually place General Skills on both Hotbars 1 and 2.

1) Arrange General Skills on Hotbar 1 about where you'll want them for Spec 1. It doesn't need to be perfect yet..

2) Arrange General Skills on Hotbar 2 about where you'll want them for Spec 2.

3) Go back to Hotbar 1 and load Spec 1. Now you can move your General Skills and Trait Skills around to where you'll want them.

4) Staying on Hotbar 1, load Spec 2. I'd move the new Trait Skills into a Cluster somewhere they'll be easy to locate.

Please note that as of Beta 6 at this point things stop working as expected! There appears to be some kind of bug where the memory function gets messed up. At least I hope it's a bug because the workaround as I detail below requires the purchase of another Spec Tab. Store purchase to implement expected basic functionality is unacceptable. I will update this as functionality is either confirmed, changed, or fixed.


EDIT: UPDATE
Sapience has posted that the memory is indeed not WAI and a fix is on the way, although likely not until after Patch 12.1

5) Purchase a 3rd Spec Tab on your Trait Tree Panel. Do not choose a Specialization or put any Points into this Tab, you want it blank.

6) Click this Tab, Tab 3 so that you "despec" or get back to a point where you have no Specialization chosen and no Trait Skills on your Hotbars.

7) Switch to Hotbar 2 and load Spec 2.

8) Arrange General Skills and Trait Skills as you want them for Spec 2.

9) Load Tab 3 to despec.

10) Switch to Hotbar 1

11) Load Spec 1

All of your Trait Skills should auto populate correctly for that Spec and all your General Skills will be in place for that Spec.

As long as you load Tab 3 and despec yourself before switching Specs or Hotbars everything will auto populate correctly for you. If you forget to despec your first change will work fine, but when you change again that Spec layout will be lost.

If you are running 2 Hybrid Specs and want your General Skills in different Quickslots the issues get really bad. Since Trait Skills always attempt to auto populate the Quickslot they last occupied there is no way I've found to have shared Trait Skills auto populate different Quickslots depending on Spec.

Pretty much you will always have to repopulate manually any shared Trait Skills between two Specs. The best you can do is try placing your general skills in a fashion that requires the least amount of manual population. This is another area that need attention badly.

[QuttideBachi]

Perhaps the Lotro Devs could just go spend a couple days with the Devs at Trion's Rift team and learn how to implement trees and hotbar saves when switching specs. I mean think how many different builds you use in that game and it works perfectly.

[Brandon_Blackbird]

Incidentally, I'm seeing massive memory leaks from the game when doing nothing but standing around swapping & reconfiguring traits around.

After a half-hour of doing this, my Lotro installation was taking up to 2.2gb ram.

Win7 x64 btw.

Memory leak? How can you be sure?

Why wouldn't you want the game to use as much RAM as it can?

Because if it uses too much RAM, it will affect your system and any other processes that are going on.

However, the memory leak has been going on for some time, and is not due to Helm's Deep (just do a search for memory leak). In my case, I've been merrily zipping along without issue until about a month ago, when the memory leak suddenly raised its ugly head. And this is what it does -

While running ONE instance of LOTRO, after about 4 hours (and this will continue to climb until all memory is used and my computer grinds to a halt) -

After shutting LOTRO down (note the cliff-like decline of memory usage)

[Hakorin]

I've been enjoying the new trait system, having less skills (so far) didn't translate into narrowed-down gameplay I feared. I only tried berserker, but it's been exciting and the combo of what the traits give us, have us deciding on the fly which skills to use to max dps, depending on the combat situation and where our buffs (stacks) are at. Much better than the brain-dead wild attack - remorseless spam that the previous system and set bonuses led us into.
One frustration has been the issue with the quickslots though, I have general skills in fixed slots now, but that's band-aid as we're forced to have some of the general skills in a place where we'd rather have other skills for that spec...
Other frustration, and something I can't see the reason for, is the need to completely scrap our spec and start all over again (not to mention having to pay near 1g just to do that) when we want to change some traits? Why can't it be like with our warsteeds, where we can just cancel a few points here and there and re-assign them elsewhere, to adjust to the content at hand?
There's so many different scenario's and I love perfecting specs to maximize what I'll do, I'd quickly respec a couple of things here and there 10 times in an evening easily, as it is now that won't happen, and that makes me sad, because all these new options with traits have me revitalized ingame after 6 years, but there's that nasty have-to-respec-completely-from-scratch-and-pay-loads-so-I-won't-get-to-play-with-all-this-fun-new-stuff-as-much-as-I'd-like-to. [Bloodrage-sprint-trip-cry-roar]

[WinWolf]

Please make this change turbine, i cannot play this game at the moment because i have OCD while organising my setup.

[frosa3]

I've had no issues. A trick that I learned seems to work: after you move your skills as you want them, rename that trait. That seems to lock things in place, and as far as I could tell, it works for all classes. It helps that I keep all the general skills in the same place, of course.

[Atheling]

I've had no issues. A trick that I learned seems to work: after you move your skills as you want them, rename that trait. That seems to lock things in place, and as far as I could tell, it works for all classes. It helps that I keep all the general skills in the same place, of course.

The last sentence is why your trick works For those who need their general skills in different places for different places, this is where it starts to go a bit wonky.

Glad that there's now acknowledgement that there is an intention to have a functional way to save set-ups. I think that will save a fair few people a lot of frustration with this new system.

[Chefson]

We're aware of the issue (and it is an issue, this is not working as intended) and looking at ways to resolve it. We don't have an ETA at this time, but it's probably not something that can be addressed in time for 12.1.

So... one of the most publicised and proudly put forth features of this entire Expac is not working... BUT it got released anyway, with no fix in the forseeable future. Nice move.

[enginekid88]

We're aware of the issue but it's probably not something that can be addressed in time for 12.1.

Can you please do everything possible to get the management to include this fix in the 12.1 update.

I think it is a huge bug and not something to be put on the back-burner. It truly means that I will not re-spec any of my classes until it is fixed.

That mean's I will not be healing on any class, as an example.

This really, reallly sucks.

And please do not think it is only a slight inconvenience and I am taking this too far, no, it is a HUGE inconvenience. And it is astounding that this was allowed to go live.

[WinWolf]

Can you please do everything possible to get the management to include this fix in the 12.1 update.

I think it is a huge bug and not something to be put on the back-burner. It truly means that I will not re-spec any of my classes until it is fixed.

That mean's I will not be healing on any class, as an example.

This really, reallly sucks.

And please do not think it is only a slight inconvenience and I am taking this too far, no, it is a HUGE inconvenience. And it is astounding that this was allowed to go live.

Totally agree with you, this needs to be fixed ASAP.

[Jaberman]

I posted this in another thread, before noticing that this one seems to be the main thread to discuss the issue.

I believe the solution is extremely simple...no need to drag this on past 12.1.

Simply prevent the removal of skills from quickslot bars, when changing trait trees.

If you have skills specific to a trait tree (e.g. RK healing: Writ of Health), then the tooltip for the inactive skill could say something like "Available in Healing Spec only".

This is exactly what used to happen with That Which Does Not Kill Us, a Legendary RK skill (except there was no tooltip explanation). If the legendary trait was unslotted, the skill remained on the bar, but was simply greyed out.

If Turbine wants a more complex system where toolbars will automatically switch based on the trait setup, great...but this is a good, easy, short-term fix that will save us many nightmares.

[Jeremi]

Memory leak? How can you be sure?

Why wouldn't you want the game to use as much RAM as it can?

Because not all of us have endless RAM ^^

This game does have some serious memory leak issues. That's one of the reasons it is now unplayable on a 32 bit OS. It helps to restart it every hour or so if you have limited RAM, else the game will simply crash.

[reiygna]

Memory leak? How can you be sure?

Why wouldn't you want the game to use as much RAM as it can?

Because it doesnt give it back when its done using it, hence it will run out and you will crash. Been like that since ror, still does it in dunland. Perhaps you have a lot of mem and it doesnt bother you, however a lot of us are tired of crashing and this installment is so full of leaks now, its almost unplayable.

Also this should be in its own post.

Thanks Sapience.

[Rumfigger]

I've had no issues. A trick that I learned seems to work: after you move your skills as you want them, rename that trait. That seems to lock things in place, and as far as I could tell, it works for all classes. It helps that I keep all the general skills in the same place, of course.

I tried that. Skill buttons still move around when I change builds.

[Gedachtnis]

If you're changing Quickbar Sets for builds it won't work. The only way to make that work, until they fix it, is to have an extra Spec Tab and keep it clear so you can Untrait before changing bars and builds.

[warthogonfire]

Until it is working as intended, a good compensation for the trouble would be to make respecs free.
(Which would have the nice side effect of helping me figure out how to set up my Captain without going bankrupt. )

Oh please, we need more money sinks in this game, not less

[Tobias_R]

Hi,

And please, whatever you do, don't repeat my misstake: Changing spec forgetting to dismount my warsteed first. When both trait-related and standard-skills also had to compete with my warsteed-skill-setup thing started to get ugly for real...

'Messy' is the word you are looking for...

Regards
/T

[Rainothon]

We're aware of the issue (and it is an issue, this is not working as intended) and looking at ways to resolve it. We don't have an ETA at this time, but it's probably not something that can be addressed in time for 12.1.

Please consider gifting all players a free third trait tab, if this doesn't make it in 12.1.

After all, this is something that was brought up repeatedly during Beta, and it is something that was used as a selling point for the class changes.

Still, I'd rather have it a priority to fix in 12.1, I'd rather have the issue resolved soon than a free tab.

[Neumi]

Hi,

And please, whatever you do, don't repeat my misstake: Changing spec forgetting to dismount my warsteed first. When both trait-related and standard-skills also had to compete with my warsteed-skill-setup thing started to get ugly for real...

'Messy' is the word you are looking for...

Regards
/T

That's a important safety hint, thank you. I can immagine what happened.

Anyway, I didn't have other issues with the quickbar so far.

[theFragmagnet]

Because it doesnt give it back when its done using it, hence it will run out and you will crash. Been like that since ror, still does it in dunland. Perhaps you have a lot of mem and it doesnt bother you, however a lot of us are tired of crashing and this installment is so full of leaks now, its almost unplayable.

Also this should be in its own post.

Thanks Sapience.

I agree that the memory usage has increased since the release of RoR. I have an older x64 system w/8 GB RAM. I saw better performance with the increased memory usage. And I see even more memory usage with HD. And without fail, every time I close LOTRO I see a sharp drop in allocated memory. Completely normal. Expected even.
I run my system for weeks at a time with no reboot necessary. So from my perspective there is no glaring memory leak.

Memory management in a modern OS is complicated and save for an egregious programming error few true direct memory leaks are going to be uncovered by looking at the task manager.

*Edit - abuse of grammar*

[cdq1958]

I agree that the memory usage has increased since the release of RoR. I have an older x64 system w/8 GB RAM. I saw better performance with the increased memory usage. And I see even more memory usage with HD. And without fail, every time I close LOTRO I see a sharp drop in allocated memory. Completely normal. Expected even.
I run my system for weeks at a time with no reboot necessary. So from my perspective there is no glaring memory leak.

Memory management in a modern OS is complicated and save for an egregious programming error few true direct memory leaks are going to be uncovered by looking at the task manager.

*Edit - abuse of grammar*

Seconded. I have utilities that I use to instrument running processes. Bar one rendering related true memory leak in RoR's beta, I have not seen this game have a true, classic memory leak issue. I have seen complications with how Windows does memory management and how this game does heap allocation. I have seen heap fragmentation issues, from the game client itself and from how the client interacts with drivers.

[Sapience]

I'm going to try to explain this as best I can. After looking into this a bit, the 'issue' you're seeing isn't a memory leak. it's actually the game reserving memory and holding it for an extended period, by design. We hold a lot of information in memory for recall when you open and close various menus to speed loading of those screens. Quests, Skirmish data, and trait trees. The trees seem to be the new addition that is taking up more memory than previously. They're also holding it for longer, again by design. The team is looking into addressing the demand, but the problem isn't what we had originally suspected (a memory leak). It's actually holding on to the memory intentionally and for a lengthy period of time. It does eventually release it, but opening other menus/windows, seems to extend it.

[Kerin_Eldar]

I'm going to try to explain this as best I can.

Cool, fine, we now know it's not a leak .. but that was entirely unconnected with what this thread was asking, it was a typical irrelevant OT by someone hijacking a thread for their own pet theory about something totally irrelevant to the thread up to that point.

Can you please get an answer to what this thread is asking about?

[Sapience]

Cool, fine, we now know it's not a leak .. but that was entirely unconnected with what this thread was asking, it was a typical irrelevant OT by someone hijacking a thread for their own pet theory about something totally irrelevant to the thread up to that point.

Can you please get an answer to what this thread is asking about?

Sure, I realize not everyone may have the thread from the top, so I'll repost my reply here. It's post #5 if you scroll up.

We're aware of the issue (and it is an issue, this is not working as intended) and looking at ways to resolve it. We don't have an ETA at this time, but it's probably not something that can be addressed in time for 12.1.

[Yula_the_Mighty]

Cool, fine, we now know it's not a leak .. but that was entirely unconnected with what this thread was asking, it was a typical irrelevant OT by someone hijacking a thread for their own pet theory about something totally irrelevant to the thread up to that point.

Can you please get an answer to what this thread is asking about?

Your answer is in post 4 from Sapience. A fix is coming but the fix may not be in 12.1. It misses 12.1 then we are looking at a 2014 fix we are almost out of time in 2013.