Keyboard shortcuts stopped working

Strange issue popped up on my desktop copy of Daz Studio.  All of my keyboard shortcuts stopped working.
The issue happened at some point before updating to the most recent version, and and has continued.

Did I accidently change a setting that disabled them?  (I was messing around with getting the tool bar at the top setup how I want it)
All of the keyboard controlls still work fine on my notebook copy of Studio.

Comments

  • denmisundenmisun Posts: 29

    note: the public beta and stable version use different setting/preference files. So if by 'updating' you mean you went from stable to beta, then that would explain it.  

  • JamesJABJamesJAB Posts: 1,760

    Not running the beta version

  • You can reload the shortcuts (dfaults or a saved set) from the Customise dialogue - use the load button at the bottom, then tell it what type of elements to load.

  • RhiannonRhiannon Posts: 36
    edited July 2017

    You can reload the shortcuts (dfaults or a saved set) from the Customise dialogue - use the load button at the bottom, then tell it what type of elements to load.

    Where is this "customize dialogue" you mention?  Can't seem to find it, I'm having the same issue with keyboard shortcuts not working.  

     

    Post edited by Rhiannon on
  • barbultbarbult Posts: 23,133
    edited July 2017

    On the Windows menu, select Workspace. The last item on the menu that pops out is Customize. The shortcut is F3 (once you have your shortcuts working again).

    Although, I don't know what button Richard is referring to, to reload shortcuts.

    Post edited by barbult on
  • Click the Import... button and then select Actions and then the layout you want - probably Default - Advanced.

  • RhiannonRhiannon Posts: 36

    Thanks for the info.  Actually what seems to have worked is Windows -- Workspace -- Customize, then click the "Defaults ..." button in the lower left hand corner.  Excellent!  

  • Yes, defaults would do the same thing but - as i recall, I didn't dare try it - across the board.

  • I know this is an old thread. But thanks, Richard. I ran into the same problem. Your solution solved the problem. 

  • yinliang9yinliang9 Posts: 40
    edited July 2018

    Sorry if this counts as a necropost, but I wanted to note that I just ran into the same problem as two others on this thread have, and Richard's method fixed it for me as well. I didn't even have to lock in the changes. I just hit Defaults, confirmed it, then cancel when everything changed. All my tab settings returned how I had them, only now my inputs work again.

    It happened after an automatic reboot after a Windows update, in case that helps any potential troubleshooting down the road. (That could just be a coincidence, of course.)

    Post edited by yinliang9 on
  • This bug is still actual, you need time to time set to defaults, otherwise shortcuts are not working.

  • 4.14 pro, just reporting in that this bug still exists

  • 4.15 pro. Just now, after updating Windows, the keyboard stopped working. Found a solution in this thread. As mentioned above, the "default" button helped.

  • alxalx Posts: 53

    worked for me, too. thanks a million- turns out I use keyboard shortcuts almost exclusively and don't even remember how to use Daz without them...

  • evilcho_evilcho_ Posts: 79

    Richard Haseltine said:

    Click the Import... button and then select Actions and then the layout you want - probably Default - Advanced.

    This worked for me, but care to tell me why this happened in the first place? I've been using Daz Studio since 2017 nearly every day and I've never, ever encountered this bug and one night it randomly happened. 

  • evilcho_ said:

    Richard Haseltine said:

    Click the Import... button and then select Actions and then the layout you want - probably Default - Advanced.

    This worked for me, but care to tell me why this happened in the first place? I've been using Daz Studio since 2017 nearly every day and I've never, ever encountered this bug and one night it randomly happened. 

    Perhaps DS crashed on exit, or was force-quit, while writing the file. Perhaps a system tool of some kind (e.g. security software) caused an issue. perhaps there was simply a disc error. It isn't possible to know, probably even if you have the log files from when or immediately after it happened.

  • evilcho_evilcho_ Posts: 79

    Richard Haseltine said:

    evilcho_ said:

    Richard Haseltine said:

    Click the Import... button and then select Actions and then the layout you want - probably Default - Advanced.

    This worked for me, but care to tell me why this happened in the first place? I've been using Daz Studio since 2017 nearly every day and I've never, ever encountered this bug and one night it randomly happened. 

    Perhaps DS crashed on exit, or was force-quit, while writing the file. Perhaps a system tool of some kind (e.g. security software) caused an issue. perhaps there was simply a disc error. It isn't possible to know, probably even if you have the log files from when or immediately after it happened.

    I see. I do force quit it very often, so that is probably why. Interesting that it never happened before though. 

  • evilcho_ said:

    Richard Haseltine said:

    evilcho_ said:

    Richard Haseltine said:

    Click the Import... button and then select Actions and then the layout you want - probably Default - Advanced.

    This worked for me, but care to tell me why this happened in the first place? I've been using Daz Studio since 2017 nearly every day and I've never, ever encountered this bug and one night it randomly happened. 

    Perhaps DS crashed on exit, or was force-quit, while writing the file. Perhaps a system tool of some kind (e.g. security software) caused an issue. perhaps there was simply a disc error. It isn't possible to know, probably even if you have the log files from when or immediately after it happened.

    I see. I do force quit it very often, so that is probably why. Interesting that it never happened before though. 

    It would depend on exactly what was happening - hit just the wrong moment and this can happen, or the database can become corrupt. It's much safer not to force quit.

Sign In or Register to comment.