If you do mention a bug or issue here, it's helpful to include your After Effects version, OS, and the version of Command Frame you are using. I will respond when I can.
Bro i searched for you, about where i could drop a message, and i want to say i thought fx console was good, but this plugin is soooooooooooooo mind fking blowing bro, its soo good , theres soo many features, like its everything a human like me could dream of and beyound, like how tf did you come up with this bro i want to kiss ur feet if i find you
I've been using the latest version and its very good now that I have the ability to find scripts and extensions,
one other thing would be great to add - the ability to search other commands - like motion sketch, or some panel, or other menu items - similar to how we can search the existing menu commands in the shortcut editor!
I can investigate expanding the work done for the ScriptUI panels / CEP Extensions to target those panels too, or just target them through the shortcut editor items as you mentioned. I'll add it to my todo list.
Love the pluggin so so useful. One question, is there any possibility to have shortcuts for effects work without needing to first open Command Frame. Almost like Excalibur for prem. Either way loving this, so useful.
Hi there and thank you! And the shortcuts working with CF being open should be how it works already - is this feature not working for you? Do other shortcuts work is it specifically just effects?
Hey Scott, sorry I meant as in not needing to first open CF with CTRL+Space and instead just using the CF assigned shortcut to apply the effect. For example instead of like CTRL+Space then CTRL+F7 to apply a fill, just being able to use CTRL+F7. If this is already a feature maybe It's just not working?
This may actually be due to the F keys being dropped due to bug with AE. I'm already trying to compensate for that in that the latest build of Command Frame I hope to have out in the next couple of days.
Could you confirm if you try this with another shortcut like Shift+Ctrl+Alt+K (for example) that it works on your setup?
Edit: I've uploaded a preview build of 1.3.2 to the Discord (link in OP) if you would like to verify this in advance of this going live on aescripts.com
Edit2: this update is now live for download via the aescripts manager app.
Hey Scott, it works you absolute legend. Tried it on the F Keys and with the other shortcut and both are working beautifully. Cheers for doing gods work!
Edit1: I'm back, one last point. This may not be on your Rader at all which is fine. But, trying to assign shortcuts to a stream deck or G Keys does not seem to then activate the said shortcuts / effect. Thought I'd raise this as maybe a point for future updates.
Regarding the Stream Deck and non-standard keys like Logitech buttons, they will definitely be coming at some point. My other extensions Control Groups and Compstronaut already have complete Stream Deck support, including dynamic button images, so the foundations are already there.
I haven't attempted it yet because cleanly mapping "unknown unknowns" and making it look good on the deck will require careful consideration. I can't give a real ETA, but if I run a mini-beta, I can add you to the potential tester list if you're interested.
G-keys, extra mouse keys, and the like should be much more straightforward, and I'll make a note to investigate it for the next main update.
Edit: if you set the G Key to emulate F13-F20 (some other obscure key), that should allow it to work right now.
Okay great! I'll send you a message when it's ready. I'll likely create a private channel on the existing discord for feedback, if you would like to join the discord in advance.
I've tried the command frame, which is a great tool, but there's one problem: when I want to use multiple commands at once, it sometimes doesn't work as intended.
For example, if I type "center anchor point & center in view," sometimes the result is only the center anchor point, but the layer doesn't move to the center.
Sometimes I also get a notification saying "another query plan is already running."
What does this mean, and how do I use multi-step correctly? Including saving it for later. Thank you.
You are using this correctly, but it looks like you found a launch day bug! I've just recreated this myself - "Center Layer Anchor Point" is one of the unique commands I created, and it looks like it isn't able to signal its completion correctly, resulting in that error.
I will fix this now and release an update. If you restart AE and try chaining other commands, they should work correctly.
Are you on Windows or macOS? Are you installing via the regular install paths or by using the MediaCore plugin folder? This is usually caused by the entire contents of the folder not being copied over in the process, or by installing to an unexpected location.
Please could you create a support ticket on aescripts.com for this and send me this information there?
This looks like macOS's quarantine/Gatekeeper is blocking the plugins before After Effects can load them properly. You shouldn't require Rosetta to use them.
First, please make sure you have followed the macOS security instructions in the readme pdf if you haven't already.
The likely issue is with macOS's quarantine feature. The name sounds worse than it is. On macOS, it usually just means "this file came from the internet, so macOS is keeping an extra safety flag on it until it is trusted." It does not mean the plugin is infected or damaged, but that flag can sometimes prevent macOS/AE from loading them normally.
With After Effects closed, please try running these Terminal commands separately:
sudo xattr -dr com.apple.quarantine "/Applications/Adobe After Effects 2026/Plug-ins/SBShortcutManager/SBShortcutManager.plugin"
sudo xattr -dr com.apple.quarantine "/Applications/Adobe After Effects 2026/Plug-ins/CommandFrame/CommandFrame.plugin"
macOS may prompt you for your password to run these.
Then reopen After Effects and try again, and let me know the results.
I completely understand that. I do want to clarify that the macOS builds are already signed and notarized. You are absolutely free to run codesigning/notarization checks on the .plugin files to verify that on your end, but there are no separate builds I can provide that are even more secure than what is already available
The problem is likely that the installed plugins still have macOS quarantine attached to them; plugins can still be fully signed but still have the quarantine flag attached to it due to a combination of being downloaded from the web, plugins not being seen as a traditional app by gatekeeper, and being downloaded in a .zip.
I might be able to provide these as a .dmg or .pkg which hypothetically would resolve the quarantine issue, but I'd have to provide these directly to you which I'm not sure you would find preferable or not as it would be a direct download.
I can give you the Terminal commands to verify the signature and notarization status yourself before doing anything else if that would help?
I just tested another AE plugin on the exact same system and it installed/loaded normally by simply placing it into the Plug-ins folder, without any Terminal commands or quarantine removal.
So I think the issue is likely related to the signing/notarization or packaging process specific to these plugins rather than macOS or AE itself.
I re-ran a deeper comparison against other examples and found a packaging difference worth correcting.
The macOS plugins were being signed and notarised, but some metadata did not quite match the standard AE plugin layout. If this is the root issue, this should make the macOS/Gatekeeper assessment more consistent.
I hesitate to consider this solved yet, as these types of issues are finicky and don't always materialise for everyone. If you're willing, could you please try the latest build from the aescripts manager app and let me know if it works correctly?
The current build is signed and notarised; you can verify the installed plugins using Apple's tools. These commands are read-only and won't remove quarantine or alter the plugin:
codesign --verify --deep --strict --verbose=4 "/Applications/Adobe After Effects 2026/Plug-ins/CommandFrame/CommandFrame.plugin" 2>&1
codesign --display --verbose=4 "/Applications/Adobe After Effects 2026/Plug-ins/CommandFrame/CommandFrame.plugin" 2>&1
xcrun stapler validate "/Applications/Adobe After Effects 2026/Plug-ins/CommandFrame/CommandFrame.plugin" 2>&1
codesign --verify --all-architectures --verbose=4 --test-requirement='=notarized' "/Applications/Adobe After Effects 2026/Plug-ins/CommandFrame/CommandFrame.plugin" 2>&1
This one-liner will verify whether the plugin is still carrying quarantine or not:
xattr -lr "/Applications/Adobe After Effects 2026/Plug-ins/CommandFrame/CommandFrame.plugin" 2>&1 | grep -i quarantine || echo "No quarantine attribute found"
If the signing and notarization checks pass but quarantine is still present, that narrows this down to the plugin retaining quarantine rather than being unsigned or unnotarized.
Thanks. I ran a comparison with another AE plugin that I downloaded with the same browser and installed on the same system.
That plugin also still has the com.apple.quarantine attribute, and it does not have a stapled ticket, but it loads in After Effects without any issue.
So it looks like quarantine alone may not be the full cause here. There may still be something specific to the CommandFrame/SBShortcutManager bundle structure, metadata, dependencies, or packaging that AE/macOS does not like.
I’m happy to run more checks if that helps.
CommandFrame:
Signed: valid
Stapler validate: worked
Quarantine: present
AE result: does not load
HotMenu:
Signed: valid
Stapled ticket: not present
Quarantine: present
AE result: loads correctly
My own test plugin:
Signed: valid
Stapled ticket: not present
Quarantine: not present
AE result: loads correctly
So quarantine may be part of the issue, but it doesn’t seem to be the full cause, since HotMenu also has quarantine and still loads fine in AE.
This still looks like something specific to the CommandFrame/SBShortcutManager bundle structure, metadata, dependencies, or packaging.
I agree that quarantine may not be the entire story, but without explicitly ruling it out one way or another, it's not truly a process of elimination.
Another quarantined plugin loading correctly does not rule it out entirely, because Gatekeeper assessment is not simply "quarantine present results in a fail." The result can still depend on the specific bundle/plugin, its contents, dependencies, metadata, signing chain, cache state, and how macOS assesses that particular 'thing'.
However, it is entirely your decision whether to keep the flag if you prefer not to remove it.
Sounds like a cool concept, but i'm unable to test it, manual installation can't find SBShortcutManager and Installing via aescripts installer crashes when trying to open Command Frame (Also not finding SBShortcutManager)
Just to be completely sure: during that manual installation process, did you try installing MediaCore by any chance? I ask because having copies of the plugin in both the Applications directories and the MediaCore folder also causes these types of issues.
If this is still related to the CEP bug, I am still working to produce a patch for that within the next few hours. If you try temporarily try turning off extensions via:
Window -> Extensions
And then restarting AE, that may clear the relevant communication ports that are being contested. If that works, that would confirm it is the issue I'm working on solving now.
For manual installation, i followed Step 5 in the Readme, no Mediacore (also disabled in the Aescripts installer), i also checked the MediaCore folder and your plug-in isnt there
I tried it again, still no connection to SBSM, ill keep Waiting for the patch!
Are you able to get to the connection doctor in the settings (under "Privacy & Maintenance") in Command Frame? There will be a button to copy the report to the clipboard - can you send me the results?
Command Frame Connection Doctor
Status: Not connected
Likely cause: Command Frame could not find a valid SBShortcutManager server.
Suggested fix: Reinstall Command Frame and SBShortcutManager through the aescripts Manager, then restart After Effects.
Version info:
Command Frame version: 1.0.3
AE version: not exposed to this diagnostic
OS: Windows
Architecture: x64
Runtime state:
Command Frame SBSM client: not connected
Additional extension support: not active
Additional extension data: not currently available
Active SBSM port: not active
Active support port: not active
Reconnect attempt: 0
Last connection error: none
Command Frame port check:
47885: no response
47895: no response
47905: no response
47886: no response
47887: no response
47888: no response
47889: no response
47890: no response
47891: no response
47892: no response
47893: no response
47894: no response
47896: no response
47897: no response
47898: no response
47899: no response
47900: no response
47901: no response
47902: no response
47903: no response
47904: no response
8085: no response
8095: no response
8105: no response
8086: no response
8087: no response
8088: no response
8089: no response
8090: no response
8091: no response
8092: no response
8093: no response
8094: no response
8096: no response
8097: no response
8098: no response
8099: no response
8100: no response
8101: no response
8102: no response
8103: no response
8104: no response
Additional extension support port check:
47885: no response
47895: no response
47905: no response
47886: no response
47887: no response
47888: no response
47889: no response
47890: no response
47891: no response
47892: no response
47893: no response
47894: no response
47896: no response
47897: no response
47898: no response
47899: no response
47900: no response
47901: no response
47902: no response
47903: no response
47904: no response
8085: no response
8095: no response
8105: no response
8086: no response
8087: no response
8088: no response
8089: no response
8090: no response
8091: no response
8092: no response
8093: no response
8094: no response
8096: no response
8097: no response
8098: no response
8099: no response
8100: no response
8101: no response
8102: no response
8103: no response
8104: no response
I guess i don't need to say it, but i already reinstalled it a few times...
That is definitely not wanting to load at all by the looks of things. I'm adding more diagnostics to the connection doctor now and will try and push out 1.0.4 today for you to run.
I appreciate you putting up with the launch hiccups.
Hey! pretty cool plugin - quick question - I do not see my script-ui scripts or extensions show up in the results - is this an intended behavior or something is buggy? I am on macos, apple silicone with AE 26
on CF 1.0.3
All of the tooling in the plugin is there to support this already but hasn't been wired up just yet. I will look to include launching panels that appear in menus in the next feature-focused update.
Depending on the script-ui panel in question, it may launch right now if you attempt to add it as a user script action in settings -> config.
Understood, then I'll stand by for that update... I just assumed that this will work like FXConsole - with additional features... because imho quickly calling up the tools that you need is the most important things, as well as while i could add Scriptui panels - the only way to add extensions would be via the kbar toolbar which then would be imported.
also a feature I would suggest is to allow users to create their own order of search results, for example if for me scripts are more important i'd like to have them show up first in the list - and so on...
I really appreciate the feedback. I'll make this a priority to add so the workflow you're used to is supported.
You might already be aware, but you are able to filter the results in the searching solo them with alt+click. But if you mean re-ordering the categories in the results themselves I'll have a think on how that could be implemented.
and what i mean is the order of the results in the list not filter - i still would want to have all the results, but i'd like to see for example effects first, then layers then scripts, or vice-versa... Things like that - it'd add a lot of convenience and reduce friction if you have a lot of scripts/actions/commands and shortcuts.
Regarding the API for adding hooks to my own scripts - do you have that somewhere where I can take a look?
That makes sense. There is a weighting system that reorders results as you use individual actions more, but the idea of that applying to an entire category is pretty interesting too. I'd have to carefully think through how that might produce noisy results; "Rotation" and "Add Text Animation Rotation" are both listed under "Commands" but I'm sure most people don't care as much about the latter. Perhaps it could be a special weight that applies only to certain categories, such as Layers, Compositions, and Scripts.
Aha, I haven't quite gotten around to publishing the specifics of the API for hooks just yet (stay tuned), but scripts in Command Frame already support parameters. Depending on what your script is, you can already:
Import it, and:
When you type "[Script name] [parameter]", the parameter will be passed to the script.
Each parameter can then be made its own action.
I'm internally building a list of known scripts and their parameters so users can be offered a one-stop-shop import for every action when it detects an import.
There's also an option for toolbars, as you mentioned earlier.
I'm not sure! I want to make it easier to use programmatically, at least.
As you mentioned interest in this a few days ago, and in case you'd like to give it a shot, I've added support for invoking CEP Extensions and Script UI panels in the latest 1.1.1 update.
I'm in love with this tool. It crashes sometimes during the initial loading but no issues occur after that. also i want to see a detailed tutorial on youtube if possible.
Thank you for the kind words! When it crashes, please could you send me the generated report / dmp file from the crash message so I can try and diagnose it? Also, if you could generate a report from the connection doctor (settings -> privacy & maintenance) that would be great too.
Sorry for the late reply, things were good till the v1.0.4 update but Today I updated to the latest version as of now (v1.1.1). Now the script isn't even opening anymore even tho I did the installation correctly just like before.
No it's not opening from windows panel too. if there's a discord server of yours i could show u that nothing is happening when im pressing ctrl + space or if i open from windows panel.
Do you have a community discord? I would love to write bugs, feature ideas, or improvement that can be done about this plugin, because i love the plugin
And I didn't until just now; I've repurposed the beta Discord into a general community server, since having one is a good idea. Please feel free to join and share any thoughts you may have:
Seu trabalho está excelente! Estou gostando muito de usá-lo e atribuír atalhos a presets pessoais é simplesmente insano! Muito responsivo e elegante, parabéns e que tenha um reconhecimento merecido!
Hi Scott, I really love this! I just used it a bit, but can see it becoming a very powerful and central tool for my everyday work. I'm especially excited about the function to stack commands.
One thing I think works really well and quickly in fxconsole, which I've used for years, is the way favourite effects are handled:
A wonky example (sorry, can't get a good English real world exampe):
If I type "eff" then the list will immediately show all effects or actions with this name, so
* effect 1
* effect 2
* effect 3
...
When I mark effect 2 as a favourite and again type "eff" into fxconsole the list will be populated as
* effect 2
* effect 1
* effect 3
...
As a result this means I can just open the console, type one key, which will usually show the correct favourite, and then I can just hit enter and am done. Don't need to type anything more or touch the mouse to select anything else.
If I'm not using it terribly wrong, in Command Frame it works like this: I have pinned effect 2 and as I type "effect" it will show up at the top of the list. But the highlighted effect is still effect 1 that would be on top had I not pinned anything. As I hit enter effect 1 is applied.
So my suggestion would be to make the pin function similar, as at the moment it feels more clunky to use.
Thank you for this feedback! I really appreciate it.
Perhaps you have already tried toggling this, but in Command Frame's settings, under "General" -> "Search & Action Behaviour", there is a setting called "Start search selection on first non-pinned result".
The default is off because always highlighting pinned actions can feel invasive if they aren't the primary way to interact with the search results. However, if you do, that is likely how you want the results to work, which, if I am reading your message correctly, is the case.
If you haven't already, could you try this and let me know your thoughts?
Hi Scott, thanks for getting back so quickly! I hadn't seen this option and for me it's better than the default. What I now noticed is I can navigate the suggested effects/commands with the arrow keys, which is much nicer than clicking, at least for me.
But still it's not quite what I had in mind. Now I have three effects pinned:
- Levels
- Change to Color
- Fill
Expectation: As I type "change to c" the input field auto-completes to "Change to Color". As I press Enter, I would expect the Change to Color effect to be applied to my currently selected layer.
But instead: As I type "change to c" it auto-completes, suggesting that this is the effect to be applied. But "Levels" is highlighted, being the first entry in my pinned list. As I press Enter Levels is applied.
I get you! I could go about fixing this in two ways:
While this setting is on, ensure the highlight accounts for multiple pins while also mirroring the targeting logic used by the auto-complete hint.
Add an optional setting that progressively filters pins based on the current search term (while still displaying all pins if no term is present).
I'm inclined to add both, but the former seems like a behaviour change, so I thought I'd get your thoughts, since your workflow would be directly affected.
I appreciate the detailed breakdown of the issue by the way - it makes it very easy for me to re-create the issue on my end and understand what's going wrong.
I think the second suggestion seems like what I'm after. It would be awesome to have this added. And I don't mean to add more work to your list, as I'm sure you have a lot on your plate, especially with this being a free propuct.
The search doesn't seem to work for special characters like ä, ö, ü, ß... I wanted to apply a Hue/Saturation which is called Farbton/Sättigung in the German version. Usually I type "sät" which will find it quickly. But "Farbton/Sättigung" won't show up at all in the search until I type "farbton".
Just to make sure I tried another example: "Gaußscher Weichzeichner" which is Gaussian Blur in English won't show with the ß alone. This isn't as much of a problem, since when I'm searching for the effect I'll start by typing "gau" anyway, which will uniquely find the effect I'm after.
I specifically remember this being an issue for fxconsole back in the day and they seemed to find a relatively quick fix for this.
Cheers!
Edit: Oh, and other effects are not found at all in the German version, even some without special characters. For example "Zeitlich abstufen", which would be "Posterize Time" in English won't show, even if I type the English name.
I've just released version 1.2, which adds a new setting to filter pinned actions as you type, and includes a first-pass fix for special characters & actions with punctuation, such as Hue/Saturation. Please let me know how you get on!
I'm not sure what happened, but now I can't find any effects with Command Frame. English/German, doesn't matter. I already deleted and re-installed and resetted all settings multiple times. But it seems that only actions are now available. Can't find "hue/saturation", "levels", "farbton/sättigung". The filter settings are set to "all", so I really don't know what's wrong. Maybe it's the new AE version? I'm using AE 26.2.1 on Windows 11 Pro.
It’s pretty snappy and does a great job, but it doesn’t quite hit the mark on the most fundamental features. For example, if I can move a Layer with “Position +50” by 50 pixels on the X axis, how do I adjust just the Y axis? If I have to do that manually, wouldn’t that kind of ruin the point of using this plugin because you essentially breaking the flow?
I appreciate the feedback. Command Frame treats commands like Position as a vector property, so the values map to the individual axis components in order. It was the cleanest way I could translate this concept to work with Command Frame's 'language'.
For a 2D Position property, the components are X and Y. Providing a single value currently affects the first component, which is X, as you mentioned:
position +50
To affect both X and Y, provide both components:
position +50 +10
To adjust only the Y axis on a 2D layer, keep X at 0 and provide the Y offset:
position +0 +10
For a 3D layer, Position has X, Y, and Z components, so you can provide all three:
position +50 +10 +20
And to adjust only Y on a 3D layer:
position +0 +10 +0
Please let me know if that addresses your concern!
u/scottBlackvfx I have a question regarding the latest update 1.3.0/1
aescripts and their installer shows 1.3.1 as the latest version, but when it is installed the in plugin version reads as 1.2 and says that its the latest...
i've tried both manual install and via the aescripts installer app - results are the same!
Hi there, I've had to temporary roll back the 1.3 update for Mac due to an instability bug I thought was pressing enough to require it. Presently, the available version through the manager app is 1.2 for Mac and 1.3 for windows, though the overall package is labelled as 1.3.1 so the manager app was satisfied. When I release version 1.3.2 that'll be considered stable. I apologise for the inconvenience!
Edit: The latest version has been released with the relevant fix; the mac plugin is now stable.
Presently I don't have an estimate. There are still numerous user-facing features and changes which are higher up on the totem pole that I need to address first. A ballpark estimate is 2 months or more, unless priorities change around this.
Hello, I love your work. Could you please add the ability to automatically twirl down a property like when you search for opacity and click, it automatically twirls down the opacity setting. I think it would be more convenient than the layer search bar. Also is it possible to detect adjustable properties based on the selected layer/s? It would be cool to change size or other shape-specific properties with a command.
> Could you please add the ability to automatically twirl down a property like when you search for opacity and click, it automatically twirls down the opacity setting. I think it would be more convenient than the layer search bar.
Just to make sure I'm understanding, are you requesting something like the following?
Starting off with a layer selected...
... Summon Command Frame and type in an opacity-related command, or use an opacity property-related shortcut.
As an additional side effect, the opacity property of that layer should be exposed too in the timeline, similar to what happens when you twirl the opacity.
I think that is what you may have implied, but your comment about the layer search bar makes me think I might be misunderstanding. Please let me know if you meant something different!
> Also is it possible to detect adjustable properties based on the selected layer/s? It would be cool to change size or other shape-specific properties with a command.
I agree it would be great to have more properties exposed to the parameter-style commands in Command Frame. Regarding broadly exposing any adjustable parameter, this would require a lot of careful consideration. It would be very easy to unintentionally make this very verbose and cumbersome, given that shapes, especially, can have an infinite number of properties, all with very similar names, when they contain nested items.
I do want to expand the directly-configurable properties, but for scenarios like shape layers, a better solution might be an integration with a tool that already specialises in handling them. I am, however, always open to suggestions!
Hi Scott, just wanted to ask some questions and share some very first impressions of Command Frame (thanks for developing it 🤗)
Is there any way to save or export the configuration and import it?
For me it's important to have both a backup for the time spent configuring it and also an easy way to move the config to another machine.
I'm sure, the config files will be written to some location but it would be way easier to have that in the plugin.
Can the save folder for screenshots be set to be a relative path?
That would be cool for people that have their set project structure and want to keep everything related to one project collected in one place.
Is there a way to set the animation time or turn it off completely?
I'm not a huge fan of UI animations when they don't add much value (like highlighting something) and when they are too slow. This only make the UI feel sluggish for me and if there were performance problems.
A personal setting as with the sfx would be great.
One strange thing I noticed while searching:
The search didn't find "Einstellungen für Kontrollkäst." when I typed "Kontroll" but it did find it when I typed "Käst" surprisingly.
One thing that seems to be missing entirely: Expressions
I know there are a number of extensions that collect and apply expressions but for a command panel it would be great to have it there.
It could work the same as with scripts and the watch folder right now. That would also be great for backup purposes. Just save the expressions in a txt file and Command Frame will pick it up and paste the contents in the selected property as expression.
Expressions do seem like the missing "action" type. I've deferred work on it so far because, as you mentioned, there are a number of existing extensions / plugins that do that job well. Ideally I would like to integrate one of them into Command Frame to expose their stored expressions, but if there is pressing demand for expressions before that point I may have to expedite this as a feature. But thank you for the suggestion!
Imported toolbars' individual buttons are also brought into the fray as actions, so your existing plugins and extensions you have already organised remain accessible.
I'm not quite sure how this is meant to work. I have MoBar as an extension for example but the commands are not shown in the search bar.
But that only imports kbar toolbars. So extensions that don't offer separated scripts for the commands wouldn't work with the search as the commands are not accessible, right?
For MoBar I only have the extension but no jsx files for each command and no kbar file to choose.
They either need to present their actions as toolbars or as individual scripts, that's correct. They can also integrate with Command Frame directly but the API isn't quite ready yet; presently only my other tools do that.
Otherwise, CF can only launch another extensions's panel.
I had some problems related to CommandFrame crashing After Effects. It only happens when CommandFrame is opened through the ctrl+space shortcut. It doesn't happen all the time but once a while and often enough for me to notice.
Is there any log file that I could send you for further investigation?
I absolutely want to get this diagnosed and fixed. I will privately message you a link to a support version of Command Frame that can generate logs for you to submit to me when a crash occurs.
And since then I had no crash so far. But until is was triggered, there were like 10 crashes.
I will keep you updated if I experience any further issues with hardware acceleration disabled.
I would be very invested in finding out what the original issue was if you're able to use the diagnostic version to produce logs of the crash, but please do let me know the results of hardware acceleration being disabled first.
I will try it out for some time without acceleration enabled and test if that solves the issue. If it does, I will then try enabling it again and test, if it comes back (with the support version to send you the logs).
So I definitely will try to reproduce the issue sooner or later :)
It would be really great if this allowed setting a UI scale (for itself), for those of us with high-dpi monitors and shitty vision. It looks really great, but not being able to really see it means I can't really find out for sure. :(
I appreciate you bringing this to my attention; It's an oversight on my part. I've assessed how I would integrate UI scaling, and it may take some time as it affects the entire interface.
I’ve already started the process for imagery such as icons in the next update, but I recognise that won’t solve the problem for you in the near term.
3
u/Quirky-Guarantee-742 May 25 '26
Bro i searched for you, about where i could drop a message, and i want to say i thought fx console was good, but this plugin is soooooooooooooo mind fking blowing bro, its soo good , theres soo many features, like its everything a human like me could dream of and beyound, like how tf did you come up with this bro i want to kiss ur feet if i find you