topic Re: Keyboard doesn't work for any commands in explore mode in Modeling

Keyboard doesn't work for any commands in explore mode

Anonymous — Tue, 22 Sep 2015 18:46:26 GMT

My keyboard becomes inactive when I enter explore mode. I can move a bit with my mouse. However, I can't move forward with the arrows or back or adjust speed or anything. I feel like the mouse has been given full control.

Re: Keyboard doesn't work for any commands in explore mode

Laszlo Nagy — Wed, 23 Sep 2015 17:23:17 GMT

When you enter Explore mode, the 3D Explore Information Dialog comes up. Does it show all the keyboard shortcuts you can use? (See attached image).
If not, maybe there ar eno keyboard shortcuts assigned at all so you need to assign them or switch to the Standard Shortcuts scheme in the Work Environment Dialog.

Re: Keyboard doesn't work for any commands in explore mode

Anonymous — Thu, 24 Sep 2015 12:55:08 GMT

The standard dialogue does come up, but none of the usual commands work.
I checked my shortcuts in the work environment and there aren't any assigned even in the default Standard Shortcuts 19. Would you be able to take screen shots of what yours say?

Re: Keyboard doesn't work for any commands in explore mode

Laszlo Nagy — Thu, 24 Sep 2015 13:25:28 GMT

My Work Environment looks the same as yours. Looks like these are non-customizable shortcuts, because it should say: Lateral Move Left /Lateral Move Right, but there are no such commands available, only Lateral Move (which I am not exactly sure what it does).
But this still does not give an explanation to why these shortcuts don't work for you at all.

You may try cleaning your ARCHICAD preferences, see if that handles it:

http://helpcenter.graphisoft.com/troubleshooting/setup/repair-archicad/#Cleaning_preferences_on_a_MAC

(Or, could they be interfering with some Mac system shortcuts or shortcuts in another application?)

Re: Keyboard doesn't work for any commands in explore mode

Anonymous — Wed, 30 Sep 2015 14:06:36 GMT

I've tried the cleanup and the explore mode still doesn't work. I can't think of anything else as to what could be interfering with these commands.

Re: Keyboard doesn't work for any commands in explore mode

Stress Co_ — Fri, 02 Oct 2015 08:03:24 GMT

This has happened to me a few times now.
I also lose the ability to toggle "Quick Selection" on/off with the space bar.

Restarting my Mac seems to solve the problem... till the next time.

Not a very complex project, but I only have 8 GB of Ram,.... so maybe?

Re: Keyboard doesn't work for any commands in explore mode

Anonymous — Mon, 09 May 2016 15:43:34 GMT

Did you ever resolve this issue? I am having the same problem with my Macbook... but NO problems on my iMac or even my PC!!! i can "look around" but my feet are "Frozen in place" when in explore mode. arrow keys dont work, nor do WASD keys. and these keys all work fine in Plan Mode, etc.
i am working with large files (IFC Revit imports), but again the files open and operate fine on PC and IMac, just not laptop (Macbook)!!? help?

Re: Keyboard doesn't work for any commands in explore mode

Stress Co_ — Mon, 09 May 2016 16:01:13 GMT

I haven't had any problems since bumping my memory to 24 GB.

Re: Keyboard doesn't work for any commands in explore mode

Anonymous — Mon, 04 Jul 2016 12:00:00 GMT

So ArchiCAD 20 has arrived and I still am having the same issue with Explore mode not working. Another keybord shortcut that stopped working is the magic wand (spacebar). I was able to override the shortcut but it was strange it just stopped working one day.

Re: Keyboard doesn't work for any commands in explore mode

Jeff Kogut — Tue, 05 Jul 2016 14:21:58 GMT

Have you tried going back to default keyboard settings? Do they work? Then rebuild your custom keys?

Re: Keyboard doesn't work for any commands in explore mode

Anonymous — Tue, 05 Jul 2016 14:25:04 GMT

I was given a new work environment to replace mine and everything started working again. However, as soon as I started to add my own shortcuts again explore and magic wand stopped working.

Re: Keyboard doesn't work for any commands in explore mode

Jeff Kogut — Tue, 05 Jul 2016 14:30:51 GMT

Sounds like there is a conflict then. Rebuild one key at a time and test? Maybe an assigned key not showing up as used is conflicting?

Re: Keyboard doesn't work for any commands in explore mode

Anonymous — Tue, 05 Jul 2016 14:59:31 GMT

i have been dealing with the same issue on my macbook Archi 19 (explore mode not working - can use the mouse to "look around" but cannot move in any direction). i have tried loading different work environments, including the standard. i have tried opening a solo .pln file vs a teamworks project and always the same issue. i have high RAM, hard drive, and memory - better than my home iMac or work PC - both of which work just fine with archi 19 explore mode. was going to try downloading archi 20 this week on macbook - fingers crossed for a fix.

Re: Keyboard doesn't work for any commands in explore mode

Eduardo Rolon — Tue, 05 Jul 2016 15:32:25 GMT

Stuff to try:

It might not be ACs fault it can be another program that is taking over the keys. Either change Keyboard layouts (to US) to verify or check under System Prefs -> Keyboards ->Shortcuts and/or Text
Additionally you can try rebooting in Safe Mode and open AC to see if the shortcuts work, if they do then that could mean that another program is at fault.

Re: Keyboard doesn't work for any commands in explore mode

Anonymous — Wed, 10 May 2017 19:10:40 GMT

craziest thing... i was still having an issue with this (on my souped-up MacBook Pro) for the past year. even downloaded Archi20, but had same issue - on solo projects and teamworks alike. THEN, 2 things happened: i upgraded to current ioS AND finally ran a Time Machine backup (2 separate backups actually, just in case). My plan was to wipe the machine to factory settings and then reload and re-install to see if problem fixed. but decided to check one last time before that drastic step... and it works!!! i can finally use my laptop again in 3D explore mode!!! not sure if it was iOS-related or backup/ memory related... but who cares?! it works!