Severely limited perk tree options(Creation Kit)

[TerraMcCloud]

for some reason in the perk tree dialog I can't do anything but add perks and move perks around, all other options are greyed out and can't be used.

 

I can't even link up perks. I've tried running the CK as admin but it literally did nothing(I honestly think steam just eats the run as admin attempt).

 

I want to link up a smithing perk to another smithing perk, but since I am restricted to only adding and moving perks(As all other options are greyed out and can't be clicked) I am at a loss, if anyone knows why I can't fully edit perk trees please reply and let me know why.

[Shadeybladey]

You have your esp active?

[TerraMcCloud]

You have your esp active?

 

Yes I have it active

[Shadeybladey]

Hmm.

 

It's a long time since I messed with perk trees and I'd have to update Steam and the CK to have a look at my mods, which is not possible atm due to internet issues.

 

But, as I recall, it's not as simple as dagging/dropping and drawing lines in the perk tree diagram for the Skill. You have to edit which perks are pre-requisites for others, what the conditions are etc.

 

Sorry for the delay in replying and sorry I can't be of more help atm. Hopefully, someone else can chip in or you can find out what you need from the Wiki or from searching the forum.

 

 

:sad:

 

PS Also, check which version of Skyrim and the CK you have and make sure everything is updated, just in case. I heard there was some issue with certain CK updates and there may be some issues with Skyrim SE vs Legendary and so on.

[TerraMcCloud]

Yeah I had all that set up, I just couldn't draw a line to it.

 

Regardless I found away around it, using TES5EDIT and the perk tree plugin for it I was able to add the link I wanted.

[VanKrill]

So, in editing the perk trees, the editor which shows the boxes, is only used to create the Star Field graphics, it does not actually set the linkages for the requirements for each perk.

 

So, if you're adding a Leatherworking series of perks, to the Smithing menu, would have Leatherwork 1, which is needed before Leatherwork 2, etc.

 

Well, you can create the graphic in the box editor, drawing the lines between each box node.

 

But that does not create the actual skill requirement dependencies, that has to be done by editing the Perk itself, and the bottom box which sets the requirements, such as Smithing level, or the "Has Perk" in LW2 to need LW1 to gain the skill.

 

The easiest way to understand it, is look at the existing perks for the Smithing skill, and how the requirements are set in the Perk editor.

 

The box and line editor only changes the graphics, but does not create the logical linkages and dependencies.

 

There are some great tutorials available via google search to learn all about making new perks.

 

https://www.youtube.com/watch?v=ECryUnMljEU

Edited May 3, 2017 by VanKrill

[Shadeybladey]

Yes, VanKrill has it right.

[Lollerpotomus]

I know you guys are trying to be helpful but you are answering a different and more basic question then welch is asking. This is happening to me too currently. We understand how to modify perk dependencies in the perk window using hasperk comparisons and that that is not the function of the perk tree modification window under the actor value section. That isnt the problem we have. In the perk tree modification window we cannot use any function besides add perk and move. all the other options in the rightclick menu are greyed out and we cannot draw connecting lines, when we try nothing happens and the perks remain unlinked.

[Deleted3082751User]

i believe this issue is caused by a dll file, and i believe that file is the enbseries file

 

so move the d3d9.dll file to desktop (before opening the creation kit), and then see if that resolves the issue

 

i had this issue a long time ago, and i remember it was caused by a dll file, which i am pretty sure is the enbseries dll.

 

or if you have reshade, move the dxgi.dll file to desktop

Edited September 18, 2017 by Guest

[Novem99]

i believe this issue is caused by a dll file, and i believe that file is the enbseries file

 

 

twistedfatal is right. Had the same problem. Follow his solution.