{"id":14239,"date":"2024-10-21T14:01:51","date_gmt":"2024-10-21T18:01:51","guid":{"rendered":"https:\/\/www.sceneri.com\/?post_type=sceneri-pro-docs&p=14239"},"modified":"2024-11-01T19:48:48","modified_gmt":"2024-11-01T23:48:48","slug":"beta-github","status":"publish","type":"sceneri-pro-docs","link":"https:\/\/www.sceneri.com\/sceneri-pro-docs\/introduction\/beta-github\/","title":{"rendered":"Beta & Github"},"content":{"rendered":"
<\/i><\/span>Note: If you are going to be working with the engine code, see the Technical Documentation<\/a>.<\/span><\/div><\/div>

Downloading Release Builds<\/h3>\n

Windows<\/h4>\n
You can find the latest release build of the engine on GitHub<\/a>.<\/span><\/div>\n
<\/div>\n
Simply download the WindowsEditorRelease.7z<\/em> package, extract it and run bin\/Windows\/ReleaseDevelopment\/Editor.exe<\/em>to start the precompiled engine. This version of the engine is not connected to any version control.<\/div>\n
<\/div>\n
We recommend working with an engine synced from Git, see below.<\/div>\n

Apple (macOS & iOS)<\/h4>\n

Running via TestFlight<\/h5>\n
Start the TestFlight app signed in with your @ngi.ne Apple ID. Then install the available Mac or iOS builds of ngine.<\/div>\n<\/div>
<\/a><\/span><\/div>

Syncing the engine repository from Git<\/h3>\n
    \n
  1. Download a git client such as Github Desktop<\/a>, and <\/span>Download and Install Git<\/a> (command line tools)<\/span><\/li>\n
  2. Download and Install Git LFS<\/a><\/li>\n
  3. Sync the https:\/\/github.com\/nginetechnologies\/ngine<\/a> repository<\/span><\/li>\n
  4. Obtain the ngine binaries (platform-specific)\n
      \n
    1. Windows: Run SyncLatest.bat<\/em><\/li>\n
    2. MacOS: Run SyncLatest.sh<\/a><\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

      Updating the Engine<\/h4>\n
        \n
      1. Download the latest engine Git data via your Git client<\/li>\n
      2. Obtain the ngine binaries (platform-specific)\n
          \n
        1. Windows: Run SyncLatest.bat<\/em><\/li>\n
        2. MacOS: Run SyncLatest.sh<\/a><\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

          Syncing samples and templates from Git<\/h3>\n

          Steps to sync the Samples repository<\/h4>\n
            \n
          1. Sync the nginetechnologies\/ngine-samples-internal (github.com)<\/a> repository using your Git GUI<\/li>\n
          2. Rename the directory from ngine-samples-internal to ngine-samples<\/li>\n
          3. Open a git terminal in the new directory<\/li>\n
          4. Run the command git remote rename origin internal<\/code><\/li>\n
          5. Run the command git remote add public https:\/\/github.com\/nginetechnologies\/ngine-samples.git<\/code><\/li>\n<\/ol>\n

            Steps to sync the Templates repository<\/h4>\n
              \n
            1. Sync the nginetechnologies\/ngine-templates-internal (github.com)<\/a> repository using your Git GUI<\/li>\n
            2. Rename the directory from ngine-templates-internal to ngine-templates<\/li>\n
            3. Open a git terminal in the new directory<\/li>\n
            4. Run the command git remote rename origin internal<\/code><\/li>\n
            5. Run the command git remote add public https:\/\/github.com\/nginetechnologies\/ngine-templates.git<\/code><\/li>\n<\/ol>\n
              Then, when developing push changes to branches to the internal<\/strong> remote. For example, if using git terminal:<\/div>\n<\/div>