Skip to main content
G
groovdafied17847557
Participating Frequently
December 1, 2021
Question

AE ExtendScript coding in MS Visual Code vs Adobe's legacy IDE?

  • December 1, 2021
  • 1 reply
  • 250 views

So I'm just starting out with ExtendScript to hopefully build tools for myself and team. I'm on Big Sur OS X, but noticed that Adobe ExtendScript cannot run, due to it being 32bit, so I learned the VisualCode route and am up and running 100%, along with Types-For-Adobe.

 

The issue I'm really experiencing as I'm dabbing with the code is that when running across bugs, there are times where AE will just simply crash before I see the syntax errors and I'll have to wait to pull up AE again to find out what I did wrong.

 

There are also times where AE will crash to a point the code is no longer responsive, or where I'll need to either log in/out of my OS account and start up the IDE and AE, or even do a full on reboot where I'll finally see the syntax errors and just hope things will work as I learn.


Should I just bootcamp my mac, run Windows and install the legacy ExtendScript by adobe and code in there? Would the experience be any better, or will I still face the same crash/login-out/reboot behavior? Are there any other IDE platforms that offers a better coding experience?

 

I'm on the latest AE and VisualCode, and plugins.

 

Thank you!

This topic has been closed for replies.

1 reply

Mylenium
Mylenium
Legend
December 2, 2021

ESTK never had this kind of deep binary access to the programs and wouldn't actually load anything, hence a lot less crashes or basically none (until you actually run the script from within the app). Would going back to it solve your actual issue? Doubtful, since according to reports from users on other forums it doesn't fully work with newer releases and functions don't even show up. At best that would make it then a dumb text editor with JS syntax highlighting. Feel free to try, but it might be better to just reign in your VS stuff and turn off live debugging, code completion and otehr such stuff that is prone to causing crashes. A lot of functions and panels in Adobe apps are still modal and you'll always hit a snag at some point where the only reliable way to asses the state of your script is to actually run it from within a standalone AE.

 

Mylenium

    G
    groovdafied17847557Author
    Participating Frequently
    December 3, 2021

    Thank you so much for your response. I'll make due with what I got 🙂

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices