Jump to content
Jade Shadows: Share Bug Reports and Feedback Here! ×
Jade Shadows: Known Issues ×

[Foundry] Unable To Craft Specters


Bibliothekar
 Share

Recommended Posts

If I want to craft Specters and choose to keep my saved loadout (instead of the current one), my foundry tells me that there is an 'Unknown Error' after I confirm that I want to craft them.

If I choose to use my current loadout, my foundry becomes entirely unreactive after I confirm that yes, I want to craft them. I can't even start other jobs.

Link to comment
Share on other sites

Im having this problem too. ive done a few tests with different Warframes and weapons....all result in the same outcome. the specter fails to be made and the foundry cant do anything else till i re-log in. and even then it will only do non specter related tasks normally.

 

normally i rarely use specters but ive been dieing to update my old specter layout with my new weapons and warframes.

Link to comment
Share on other sites

Yeah same problem. Unknown error. Support ticket and EE file logged.

 

Anyone been able to get around it?

 

Have tried rebuilding loadout... no joy...tried different frames... no joy...tried using stuff you get at the start of the game....ex/paris/skana/kunai....no joy.

 

I dont use them much but still...a lil bit frustrated

 

 

Link to comment
Share on other sites

Ok it worked for me it may for you.....try this

 

1.REMOVE syndicate sigils and moustache...it may be just the sigils...but didn't have enough resources to craft more specters to narrow it down atm.

 

2.Overwrite old layout with new. 

 

3.Now you can craft specters with no "unknown error".

 

4. Say ty if it worked for you as well ;-)

Link to comment
Share on other sites

In the thread to 15.1.3 someone mentions that they have been fixed. I'm downloading the fix right now, gonna try my saved loadout first then your suggestion.

 

/e: Preserved loadout works, overwriting the current loadout (with Sigil equipped, because - squirrel!) works too. So thanks for posting your solution, but it looks like it's not needed any more. Maybe with a later update, should the problem re-appear. :)

Edited by Bibliothekar
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...