Anyone else experiencing these bugs/problems with the Foundry?

cnynridr2

When I go to test the map from any point my character always has his key binds all reset or just missing. Then if I publish and decide to run it in game if I exit the foundry then select character then enter the world alot of the HUD components disappear. IE the encounter bars at the bottom, the quest tracker, Pray timer etc. I have checked the B button and gone into the HUD hide/unhide and they are just not there. The only way to correct this is to exit the program completely then re-launch it.

Secondly, this one is very annoying. When I choose to test play an objective from a certain story point it always puts me in the zone in spot but doesn't complete the previous objectives before it so I can move on to the point I want to check. I end up having to always play from the beginning of the dungeon. Very annoying. You think it would clear all info before the point I want to log in after in the story or at least give you the items you need to progress to start at that story point.

drakedge2

#1 - if you have a gaming device plugged in like a joystick, or controller, try unplugging it.

#2 - That sounds like an odd bug, what I do is right click on the map and do "play from here" load the map, go back to the foundry and then click on the story objective i wish to test, and then click play from here. That works for me, and it might for you.

cipher9nemo

For your first issues, perhaps the client isn't given enough privs to edit the keybinding config files? Are you running as Administrator? Or is your file in the Administrator group? (for Pro or Ultimate versions of Windows). Also you can change compatibility to have your client run as the Administrator.

For your second issue, yes, that's a know problem. Playing from specific points in a quest is buggy and annoying. As a workaround, just temporarily move the objectives you want to test to the top of your storyline, and either change your starting point or add a teleporter to get to your starting point. To make it easier on my testing, I don't set the "visible" property of objects for specific objectives until I'm done testing and tweaking everything else within a set of objectives.