2015 keyboard shortcuts stop working

[Anonymous]

Hey gang,

A few of my guys are experiencing this problem since switching over to Max 2015.

They'll be working away and all of a sudden the keyboard shortcut commands for EVERYTHING will become disabled. When I say everything I mean everything. T for Top, F9 for Render, C for Camera etc. etc. You get the idea.

It's not the Keyboard Override toggle and it's impossible to work out what it is that might kick it off.

A Max restart fixes things.

Have any of youz experienced this or do you have any ideas that might help us?

Many thanks for any help!

[Anonymous]

I often work with two, three 3ds max scenes in same time, and this is a problem. I hope that it will be removed.

A general look at how to do this in the program Cinema 4D, where you can open multiple scenes in a single program, copy between materials and objects, and it is very convenient. Maybe do it in a 3ds max?

[Alfred.DeFlaminis]

Hello @Anonymous,

It's not really a problem unless you open or close multiple Max windows within a few seconds of each other, so it shouldn't be hard to avoid.  Also free scripts such as Copitor have existed for a long time that copy between Max instances and it's worth checking out.  Give it a shot!

Best Regards,

[Anonymous]

in Cinema 4d copy option is there by default, and it is convenient.
Why not build it in max? Why should I download the scripts?
The problem exists with the keyboard. We live with this for many years.
But it is not convenient. Avtodestk turn a blind eye. Trifle and can not fix.

[Alfred.DeFlaminis]

Hello @Anonymous,

I can see you feel strongly about this, I would suggest putting this up on the Feature Request board and the community can vote on the issue.  I don't disagree with you that it would be cool.

3ds Max and Maya were built to be extended via scripts however, and it's one of their strong points.  If you avoid all 3rd party scripts you are limiting yourself.  Some of those 3rd party scripts are very creative and those authors deserve some love and recognition for their hard work in my humble opinion.

I don't want to get too off topic here, but I am totally willing to discuss this more in a new thread.  

Best Regards,

[Anonymous]

After 3 days of trying some of the shortcuts not working, on 2017 and on 2016 in another computer.

What I checked where Edit-ctrl-alt, alt-x and more.

[Anonymous]

[SOLVED IN MAYA]
I'v found this video on Youtube usefull. This way will solve all issue.

https://youtu.be/k2oKSU2ww8s

[Anonymous]

Thanks but not relevant

[Alfred.DeFlaminis]

The main thing that trips people up is that there are hotkeys for "Edit Poly" and "Editable Poly".  Often people set them for one but not the other, expecting them to work interchangably which they do not.  

The other main thing that can trip people up is the Hotkey Override.  

For anyone having issues ( @Anonymous) which hotkey are you setting, and where?  Can you please post a screenshot of where it's being set as well as the modifier stack on the object where the hotkeys aren't working?  Thank you for doing that!

EDIT:  Left out the word "other" leading to two main things.  

Best Regards,

[Anonymous]

Thanks for the answer.

Attached is a print screen

I've started max->built a box->swift loop

Then I tried to do a swift loop with Ctrl-Alt (and any other combination).

Shift gives what you see in the ps "shift".

Any other combination the second temporary loop disappears- and that's it. Nothing new created as far as I can see.

I have not created any shortcut myself, assuming that those were already assigned.

(I'm rather new to max, but have past experience with other software)

Thanks again

Shahar

[Alfred.DeFlaminis]

Hello @Anonymous,

Thanks for the information.  I think it may be just a bit of confusion about how the tool operates, please correct me if I'm off in my post here.  The second screen shot looks like a "Flow Connect" to my eyes...  which is exactly how the Shift + Loop operates for the most part.  

When you use Control + Alt it does not create new loops, rather it moves currently selected loops.  If you have a loop selected and then Control + Alt click on one of the edges it's intersecting and drag the mouse, it should straighten and move that loop to where you are dragging.  So, it wouldn't create a new loop.  From your post it sounds a bit like that is what you were expecting.  

It's possible I'm misunderstanding you.  The only modes that create new loops however are just clicking normally and using Shift + Click.  Control, Alt, +/- Shift are just modifiers of that base function on already created loops or to delete loops.  

Best Regards,

[Anonymous]

Hi Alfred

The misunderstanding is all mine... A bit new to the max, as I wrote.

Thanks for your help.

Shahar

[Alfred.DeFlaminis]

Hello @Anonymous,

No problem at all!  I'm happy to help you in any way.  Those tools are so much different than the others that it's totally expected for there to be a learning curve, no worries.  I hope that helps!

Best Regards,

[Anonymous]

Hey Guys I think I solve this .. you just have to type anything in the search by Name and press enter .. then you will return to viewport the shortcuts will work again ..

[Anonymous]

Wondering if there was ever a solution for this? I am still on 2015 and have this happen all the time. I have to restart or reload the .kbdx file for my interface to get the shortcuts back. Thanks!

[Alfred.DeFlaminis]

Hello @Anonymous and welcome to the community,

As of now I can't even log it properly because I can't find steps to repro.  If you know how to make this happen consistently please let me know.  I've spent hours trying to repro with no success.  Did you check out post 21 and 22 of this thread?  Is that what is happening to you?  What if you turn off Select Children in the scene explorer?  

Best Regards,

[Anonymous]

Thanks for the reply! Noted. I will try to figure out what cues it. Right now I have not seen a significant correlation. It has happened without using the "select children" action. I dont use shortcuts for 100% of the moves so its hard to see exactly when they were removed. I will to try to pay attention to the steps preceding it. Thanks again. Ill write back with any developments. 

[Alfred.DeFlaminis]

I really appreciate that @Anonymous.  I've put in too much time to simply walk away from it but I simply cannot get it to happen on my end.  If you do find anything at all that seems related, please let me know.

Best Regards,

[Anonymous]

 Yo, don't know if anyone's still kicking around here but I figured I could add my two cents to the pot. Had this happen to me as well using max 2017 latest service pack. However I cant get mine back, restart max, restart the machine, delete ENU folder reload .kbdx (or whatever the filetype for the keyboard shortcuts are), nothing gets the shortcuts back.Only thing I haven't yet tried is to reinstall max which I'd really like to avoid seeing as there are quite a few plugins to then also have to reinstall and setup.

The only thing that does still work is holding down ALT and dragging to rotate the viewport, everything else is dead. The only other noticeable thing that I am seeing is that when I do press ALT  is that every dropdown in the top toolbar (Edit, Tools, Group, View, Create, Modifier, Animation, etc etc) gets a small line under it as well as when I press some keys sometimes it opens one of the dropdowns.

So I cant say for sure but the last thing I did before all of this happened was that I installed the PowerCoreTools script v1.2. A script that lets you limit the amount of CPU power being used at render time through pre and post render scripts. A previous version of which is featured on apps.autodesk.com here:https://apps.autodesk.com/3DSMAX/en/Detail/Index?id=6551778389700789765&appLang=en&os=Win32_64

The version I downloaded/installed: http://www.frogsinspace.at/?p=2998

I installed the script, worked a little bit no problem that night, had something rendering overnight and I think that when I came back to the workstation the morning after it was no longer working properly after opening a new scene. 

[Piotr.Forkasiewicz]

Thank You so much for solving super annoying problem!