12
a month later

Release 0.99.122 - Nov 25, 2022, the problem remains although in release notes says it is fixed:
" Profiles runs with Rosetta under Apple Silicon #3398 @CyberArchon "

  • Vlad replied to this.

    Polygon5 Looks like CPU type identification error while generating launcher script.

    Can you please zip the profile launcher "Orion - Test.app" (located under ~/Applications/Orion/Orion Profiles/<Unique-ID>/Orion - Test.app) and send to us, so that we can check the generated script.

    Also please send output of command sysctl -n machdep.cpu.brand_string

    If possible can you also send terminal output of attached command line tool please

    cputype.zip
    13kB

        Polygon5 What if you try to run your Orion Profile directly, like executing "Orion - Test" app directly. Let us know if it still uses Rosetta? or the issue is limited to initial launch of any profile at creation time?

            Polygon5 I think I got the issue. Looks like macOS forces execution of such scripts wrapped with app bundle as an intel build. Rosetta is needed to initiate execution of launch script. But the main Orion app is already running using current architecture (means Apple Silicon in your case) 🙂

            Which you can also confirm using "Activity Monitor" after launching Orion profile.

                dino Rosetta installation pops-up even on direct execution.

                    dino
                    I Think you did !
                    Yes, the main Orion is running as "Apple" and since I don't have rosetta installed couldn't be run otherwise, right?
                    So, is there a workaround ? 🙂

                    • dino replied to this.

                        Polygon5 For now you can use terminal (as a workaround, to open any profile) to do that as a workaround. Like executing direct path to script in terminal will do the job.

                        ~/Applications/Orion/Orion Profiles/<Unique-ID>/Orion - Test.app/Contents/MacOS/Orion (Replace with your path)

                        Or

                        you can make target profile as "Default" using "Profiles" Library (or as "Manage Profiles..."), and then make your target profile as Default (means with what profile you want to run your main Orion App) by context menu, and relaunch main app, you will be running your target profile now.

                        We will look into this dependency and will try to find alternative to it soon for sure 🙂

                          No one is typing