raea 0.1.7

The Windows release: workspaces that Git for Windows can open (and the ones 0.1.5 and 0.1.6 broke repaired), sign-ins and keys kept, and the app calling your PC a PC.

View as Markdown

raea 0.1.7 is the Windows release. On a Windows PC, 0.1.5 and 0.1.6 made workspaces that Git couldn't open and couldn't keep a sign-in, so the app couldn't finish its first run. 0.1.7 fixes both, repairs the workspaces they broke, and has the app speak to a PC as a PC.

Get the app at raea.io (a Mac with Apple silicon, Windows 10 or 11, or Linux on x86_64).

The engine alone:

Terminal
curl -fsSL https://raea.io/install | sh

On Windows, in PowerShell: irm https://raea.io/install.ps1 | iex.

What changed since 0.1.6

Workspaces work on Windows. raea wrote Windows' long form of a path (\\?\C:\...) into a workspace's Git settings. Git for Windows can't open that, so every Git command in the workspace failed, its projects couldn't be read, and the app couldn't finish its first run (#169). Workspaces and projects are now made and read through plain paths, everywhere raea names a folder: the stage, the bundler, export and live play. A workspace that 0.1.5 or 0.1.6 broke is repaired the next time raea opens it.

Sign-in and keys are kept on Windows. The app kept every secret with the Mac's keychain tool, which Windows doesn't have. Signing in failed on every Windows PC, and a pasted AI key or plugin key was lost. They're now kept on Windows too, and a workspace that can't be made says why instead of leaving the window black.

Your PC is a PC. On Windows the app says "this PC" and Ctrl where a Mac's says "this Mac" and ⌘: in onboarding, setup, the Get Started guide and the app's errors. Words about the Mac's keychain show only on a Mac.

Signing in with another account. raea.io's page for linking a computer says which account it links to, and Use another account signs you out and brings you back to the same code, so you can link the computer to the account you meant.

Known

  • Characters (the Character SDK) didn't make 0.1.7 either; they come in a later release.
  • On a laptop with both AMD and NVIDIA graphics, the Windows app can crash at launch; set WGPU_BACKEND=dx12 (#155).
  • A long 4K raea render can still hang before its first frame (#158).
  • The Windows app is unsigned, as before: Windows asks once whether to run it.
  • A proxy set by an automatic configuration (PAC) file isn't read. If yours uses one, start raea with HTTPS_PROXY set.