Logged in but virtually nothing I can do.

Reproduction Rate: 100%
Blocker? Definitely
Details: Logged in without problems but that was about as much as I could do. Camera viewport was higher than normal (just below ceiling level) and non-reticule mode was active. I could move the pointer and managed to double-vlick a door to open it, but that was the full extent of what I was able to do/ My avatar didn't appear. I couldn't switch to reticule mode usiing tab key. Movement keys did nothing.
Performance was poor, at 8-9 fps, but that's about normal in Ardoris for me. I could use the pointer to access the upper-right icons which allowed me to bring up settings and quit.
Steps to Reproduce: Log in (with Linux client?) in populated area.
User Specs:
OS: Linux 4.4 LinuxMint 18 64bit
CPU: AMD FX(tm)-9590 Eight-Core Processor (8) System RAM: 16000
GPU: AMD Radeon (TM) RX 480 Graphics GPU RAM: 7733
SotA.EarlyAccess.Linux.64.403.Date.10.18.16
Area: Ardoris
Loc: (168.4, 59.5, -103.8)

 

Follow up:
After making this report I restarted the client and started on the Novia map. All went as expected and I was then able to enter Ardoris normally.

 

Having the exact same issue - logged into house and can't move at all. Will try to log back in on the main map instead of resuming in my house.

Edit: Yes - logging into the World Map allows me to actually move once logged in

 

Glad I saw this thread. had the exact same problem. So, I logged out, then logged back into the overworld map and can now move again. But this needs to be looked at. Something isn't quite right here.

 

Thank you all for reporting. Have any of you been able to reproduce this issue since it was first observed? Or since changing scenes after the initial load into the client, did it correct itself permanently? Are there any common threads between your experiences, between having all been in houses/lots at the time it was observed? Any additional information would assist us immensely. We're having difficulty reproducing this internally.

 

I haven't been able to login in since. Not for lack of trying. I'm filling out a bug report now.

 

Bug has been submitted for review and resolution.
Bug reference id: 35677

 

OK, manage to manually start the client from a shell. On entering Ardoris, parking my Avatar at my home and logging out. When restarting, I had the same experience as before, so it is repeatable.

 

With your permission, I'd like to access your character directly, if still stuck at the house.

 

Same here: after recalling from Ravensmoor to my house in Spite I cant move at all. Can klick UI-things with mouse pointer, thats all will Exit and start anew on overworlds map now
10/19/2016 6:34 PM
Title: immobile like Bug reference id: 35677
Reproduction Rate: happened once - will try to reproduct
Blocker? Avatar immobile
Details: Same here: after recalling from Ravensmoor to my house in Spite I cant move at all. Can klick UI-things with mouse pointer, thats all will Exit and start anew on overworlds map now
Steps to Reproduce: recall from Ravensmoor to my lot
User Specs:
OS: Windows 10 (10.0.0) 64bit
CPU: Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz (4) System RAM: 16350
GPU: NVIDIA GeForce GTX 1070 GPU RAM: 8145
SotA.EarlyAccess.Win.64.403.Date.10.18.16
Area: Novia_R5_City_Spite
Loc: (203.3, 35.9, -152.7)

 

10/19/2016 8:04 PM
Title: another one... immobile like Bug reference id: 35677
Reproduction Rate: every time
Blocker? Avatar immobile
Details: same happens when returnig from my Basement to the lot I own. Avatar cant move. Mouse pointer can still be used
Steps to Reproduce: Zone from Basement to lot above
User Specs:
OS: Windows 10 (10.0.0) 64bit
CPU: Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz (4) System RAM: 16350
GPU: NVIDIA GeForce GTX 1070 GPU RAM: 8145
SotA.EarlyAccess.Win.64.403.Date.10.18.16
Area: Novia_R5_City_Spite
Loc: (195.6, 35.9, -151.1)

 

I'd also like to add that while the mouse pointer could be used, mouse-look did not work.

 

@Lord Barugon @Mirellani Brave @Archer @Alexander @amaasing

We are still investigating this issue. While not a crash, something that might help us is if you all can help observe whether any errors occur when entering a scene with the player controller broken. Suggested test case:
1. Start on World Map to free your camera and make it workable again
2. Use the chat command /debug to bring up the debug console bar on the top edge of the screen
3. Do what you need to do to get the bug to occur (load into the house where you know movement is locked)
4. Once successfully entering a locked movement state, use your cursor to click on the rightmost red button on the debug bar (looks like a little switch). This will expand it. You can filter specifically for Errors by unchecking the "Debug, Info, Warning" options above the console screen. You can also go backwards and forwards in the logs using the arrows in the bottom right.

Try and see if there are any unique red error messages that are produced when you get caught in this state, and copy them here.

Another alternative is, once the bug occurs, log out immediately... navigate to your local game directory, go into the data folder, and copy your "output.log" file and send it to rromero@portalarium.com for review. That log will contain a lot of the same console information you would see using debug, and we might be able to see exceptions or errors occurring at the time your controls get locked up.

Thank you all for reporting on this issue. I'd like to get it fixed asap.

 

Sure. I haven't logged in since.

BTW, I'm unable to find the output.log file. I looked in /usr/local/games/shroud-of-the-avatar-qa and ~/.config/Portalarium

 

For linux, I would try to rely on the /debug method described. At least until I can determine the directory your folder gets put into.

 

This issue seems to be fixed in QA 404. I've only logged in once, but it worked fine.
Getting to use the /debug method was impossible with the issue I had. No keyboard control.
BTW I always enable /debug in QA ;-)

 

Once I exited to the menu and started on the world map, the controls started working. I can log off and on or quit any number of times and they still work. It problem was present just for that initial login.

 

Holy crap batman! I didn't even know that existed. I will certainly put it to good use.

 

Please do! If something seems functionally broken, having the /debug up works wonders.

You can even bring it up beforehand and it will persist for as long as the client is open. You could log in to Offline mode, hit /debug, log out, then log into your broken character and see what the debug console produces.

 

@Lord Barugon @Archer @Mirellani Brave Has this issue recurred since latest patch?