P: Record action bug when setting keyframes on an object property

[Yin5C38]

Issue: record action bug when setting keyframes on an object property

Photoshop version: All Photoshop CC versions from 2015 to 2019 (does NOT happen in the CS6 version)

OS and version: Windows 10 21H1

Steps to reproduce the behavior (most options are not mandatory, posted just for reference):

- open Photoshop without creating or opening any file

- start recording your actions

- File / New / random resolution transparent Document

- Timeline: Create Video Timeline

- 3D / New Mesh From Layer / Mesh Preset / Sphere

- select 3D Panel: Scene: Sphere, then its Properties: Coordinates in the appropriate panel, then Timeline: <Current Layer>: 3D Meshes: Sphere, and click the stopwatch to Enable Keyframe Animation [stopwatch turns yellow]

- go to a random time in the Timeline and set, say, the Y axis angle to 90 degrees

- stop recording

- play your recorded actions

Expected result: the recorded actions should play without issues / errors (like in Photoshop CS6)

Actual result: an error reading <The Command "Enable" [Sphere] Is Not Currently Available> is thrown

Test file: I could have uploaded a saved action file, but the steps to reproduce the behavior are too simple

Notes:

- I have no idea if this has been fixed already in subsequent Photoshop CC versions, but although I acknowledge the complexity of your products and the huge task of mantaining and developing them, having such a bug persist across so many versions is kind of embarassing for a top product of a top company

- this bug refers to the Photoshop inability to (re)play a recorded action where the property (i.e. 3D Meshes: Sphere) of an object (i.e. <Current Layer>) becomes "selected", or "enabled", if you like

- the steps to reproduce the behavior were written without Photoshop installed (for obvious reasons, since such jobs are impossible to do), so perfect accuracy is not guaranteed

[Yin5C38]

For the record, the bug is present in the 2021 version of Photoshop (and probably in the last version as well, although I saw you fixed an unrelated action bug for the latter recently). I'm curious how long it will take to acknowledge and fix the bug, just for fun, because other (free) sofware developers would have already come up with a fix by now - I know at least two such examples.

Anyway, using the old CS6 version seems the most feasible choice for users. The only problem that version has is not being able to see the entire RAM amount on new systems, but that is fixable through a simple registry addition. Certainly much more reasonable than the buggy CC versions.

[Kukurykus]

Could you share that 'simple registry addidtion'? Thank You!

[Yin5C38]

Sure, the registry addition (along with its possible - but unlikely, in some scenarios - drawbacks, mentioned above) is explained quite well here. It's basically about overriding in the appropriate HKCU\Software branch of the registry the 'detected' amount of RAM by (older versions of) Photoshop with the value corresponding to your system. This will turn that value into a static, instead of a dynamic one, but then nobody changes the amount of RAM in his system (which would require an updated value) every 5 minutes anyway. You can safely set the percent of RAM actually being used by Photoshop in Edit / Preferences just like before, only now the total RAM that the percent is based on would be the value you set in the registry instead of the previously incorrect 'detected' value.

[Kukurykus]

I remember many users experienced this bug (before a fix), that did not affected me. I'll look into it closer...

[Yin5C38]

Which bug are you referring to? The action bug or the RAM bug?

[Kukurykus]

Not yours unfortunately yet, but let's see response. The RAM of course.

[Yin5C38]

Ah, ok. Mine is probably going to be left unnoticed since apparently Adobe decided to remove the 3D stuff from the Photoshop products (even though the bug is perfectly able to cause similar effects even after the removal, in other areas requiring 'enabling' a subproperty of a property, so to speak). The RAM one is strange, since you'd expect a 64bit program to correctly detect the memory amount, as it doesn't suffer from the limits of a 32bit one. Feel free to look into the latter, of course.

[J453]

Sorry. 3D features in Photoshop are no longer being developed. https://community.adobe.com/t5/photoshop-ecosystem-discussions/photoshop-3d-features-are-being-remov... 

[Yin5C38]

Oh yes ... after 2 months of not bothering to answer this bug report, finally Adobe found the time in their "busy" schedule to come up with the perfect excuse to not fix it (and mark their own answer as the correct one): the features related to the bug were removed from the product.

This is just brilliant, LOL! Fortunately I don't depend on this lousy customer service and didn't lose anything because of it bar the money already spent, but this should be a lesson for people looking to buy (sorry, rent) such products. Also, on a more serious note, despite the fact that the 3D features are going to be removed from Photoshop (something I was aware of), it seems corporate minds have a problem understanding that this is actually a bug related to Actions and not necessarily 3D (i.e. it happens whenever a subproperty of a property is "enabled") - it's just incidentally that I discovered it while working with the (now, obsolete) 3D features.

Anyway, it's your product, your money, your customers, feel free to let bugs unresolved - and thanks for answering ... eventually. It's not like I'll cry at night because you're not true professionals...