CTRL+ALT+Left Click not working
Recently I made a clean install of everything, but when I installed the
most recent Daz Studio 4.16 via DIM a weird thing happened;
Using the old ctrl+alt+left click shortcut in the viewport doesn't work; it wont let me orbit or anything. Nothing happens.
Every other combination with ctrl+Left click does work,
for example ctrl+shift+left click and ctrl clicking items in the scene and in viewport all function correctly.
It's just ctrl+alt+left click that doesn't want to work, so I don't think it's a mouse or keyboard problem.
Any ideas on how to fix this?
I'm on an updated Windows 11 if that helps.
Edit: I managed to move the ctrl+alt+mouse shortcuts to shift+mouse instead, which feels better honestly.
Still, it's strange that I can't use CTRL ALT LEFT CLICK in Daz 3D. I couldn't rebind to it either.
Comments
There is a script that wil generate a list of shortcuts - download using the link above the code, then drag it into the Daz Studio Viewport to execute.
Thank you for the reply. I hate to sound ignorant, but I don't know where "above the code" is referring to this script download?
My problem might be part of a bigger problem though since I've noticed my Daz Studio layout resets everytime I re-open Daz,
even if I close it properly. I've used Daz3D for a decade and I've never seen this behavior.
The log simply states that the program couldn't open the dsx files for actions, toolbars, menus, layout etc.
and it doesn't find the files when I try to load them manually through Workspace > Select Layout.
And then even more bizarrely (?) if I drag my freshly-made layout file into Daz Studio 4.16, the program reverts to default City Limits Lite (which I don't use),
or it simply crashes. I've reinstalled with DIM on various drives, tried the Public Beta version as well, and its always the same result.
I've checked the properties on the executables to make sure it's not running with elevated privileges/admin.
So yeah, I've been reading for hours on how to fix any of this without much luck,
but I'm not beaten yet. I wonder if it has something to do with the computer having a fresh Windows 11 install.. I've no clue.
Windows can be weird with permissions sometimes.
Anyway, thanks for any help. I'm guessing I might have to submit a ticket, though I don't know where to start with explaining all these errors.
Otherwise, Daz Studio itself works fine. I can open my old scenes and render and animate to my heart's content;
I just have to fix the layout and set the shortcuts every time I open the program.
I've attached a small log sample of the errors concerning .dsx files.
.. and breathe.
Well, it does help if I include the link to the script - sorry. http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/actions/action_accelerators/start
It does, however, sound as if something is interfering with the saving of the presets - what security and other system tools are you running?
Oh, so I wasn't completely dumbounded by the script thing then. Thanks for clarifying.
As for what I'm running for security, it's Malwarebytes and the Malwarebytes Firewall Control. I did just now remove the Malwarebytes antivirus and rebooted, but I'm getting the same results still. I'm adding a bigger chunk of log to attachments where you can see me opening Daz, trying to mod some stuff, and then closing Daz. Then when I re-open, it has just reverted to the default UI, and the layouts I made can't be found under Workspace > Select Layout either.The user layouts do exist in "...AppData\Roaming\DAZ 3D\Studio4 Public Build" but Daz can't open them according to the log. Now when I drag and drop the layout .dsa files into Daz, the UI blinks then ignores it.
I've included the log from me opening and closing Daz Studio 4.16 twice, once before reboot with AV protection running, and once with standard Windows Defender running. I see some other errors in the log but they're beyond my comprehension.
OK, this is the Public Build with the new safe-write to stop the layout files from being corrupted (at least as readily) and it does look as if something (Malwarebytes or folder permissions) is blocking access.
I have Malwarebytes too and just tested, the Public Build remembered a layout change so I don't think it is MWB, at least not on its own.
Yeah I've been jumping back and forth between public build and the normal 4.16 to see if there's a difference. The last 2 years I've preferred the public build due to some render settings I like to tinker with. That said, I disabled Windows Defender and tamper protection, and I still have the same problems.
Maybe I can force ownership of some drive via scripts and direct DIM to install there? Or will the layout settings always store on the C drive? I'll see what I can come up with and keep trying stuff cuz I do believe this is a problem on my end; and as you say, likely something with folder permissions which Windows sometimes stumbles with. My Daz content drive is G: and since I can save and open scenes fine, maybe that's a hint to move stuff there.
The layout files will always go to the AppData folder on C:, I'm afraid.
Darn.. Well, if I remember right, you could make a symbolic link to make Windows 10 think AppData as on C: but it was actually on the drive of your choosing. The same trick should work in win 11. Not sure that'll help though. I'll update here if I figure anything out.
Update: I decided to uninstall everything including DIM, and reinstalled everything making sure to have "default install paths" set in DIM. My problems still remain in the newest 4.16 public build. HOWEVER ~ the stable Daz 4.16 works perfectly fine! That is to say, it remembers my layout and shortcuts, but I still can't use CTRL+ALT+Left Click for pivoting the viewport or rebinding, but that I can live with. Maybe it's just this version of the public build that's disagreeing with my PC? Hopefully a new one comes along soon that addresses this weird problem.
That does sound like an access or permissions issue. Perhaps there are corrupt copies of the interface files that cannot be updated or removed - go to
%AppData%/daz 3d/studio4 public Build/
and try removing the actions, customactions, layout, menus, and toolbars .dsx files, then restart Daz Studio Public Build and see if it will now be able to save the layout.
So here's a thing. The actions, menus and toolbars folders are empty. Also the layout files themselves show as .DSA and not .DSX, I don't know it that matters. Anyway, I've attached a zip file showing a step by step process of doing what you suggested, with a log. In short though, it didn't work. Public Build still just reverts to the default state and the log shows it can't load or save the files.
The session layout, the one that is saved on exit, is in the Studio4 Public Build folder not User Layouts. It was some of the .dsx files in that location, if any, that I was asking you to remove.
Apologies, I misunderstood. I once again (hopefully) did as you suggested. I deleted the files, though as you can see in the attached screenshot, only layout.dse was there. When I relaunched, it re-created those files but Public Studio still won't save or remember the layout I create.
Layout.dse was not oen of the ones I suggested deleting, just the .dsx files. Clearly they are not being created at all for soem reason, yet the log file is. Check to see if malwarebytes is logging the blocking of those files.
WELL, after a lot of struggles and (trying to) follow your advice without results, I decided to wipe Daz and related things off the harddrive. I used DIM and IObit Uninstaller to clean everything 100%. Then I noticed Daz 4.20 was out, so I reinstalled both the normal and public beta build. Same problem still, and this is with no antivirus running at all. The public build still won't not let me save/load layouts or shortcuts or anything UI related. Otherwise it works fine.
The standard 4.20 build works perfectly (besides the ctrl+alt+left click not working). I've double-checked security settings on the folders and programs; they're allowed to execute, read and write on all PC accounts and the ownership settings are correct as well ~
So basically I'm about to give up on this for now and blame PC Anti-Render Gremlins or something. I mean, the normal Daz 4.20 works, so I'm basically fine even if I love tampering with new technologies in the public builds. I'll be happy with the one program working and I hope those gremlins keep away from it.
Unless you have any other ideas (and I appreciate all your help), I'll stop worrying about it for now. And if I fix it in the future, I'll update this post just in case someone stumbles over it with the same problems.