Perlin

Long builds and Keep going

Builds that keep running when you close the tab, and picking up one that stopped.

Perlin's builds run on VYBE.ART's servers, not in your tab. Once you've sent a prompt you can close the tab, switch to another piece, put the laptop to sleep or lock your phone, and the build carries on. The finished piece is waiting when you come back.

A big piece, such as a game with several systems, can take a while. This page covers what happens while you're away, how to start something else or stop a build, and what Keep going does when a build stops short.

Leaving a build running

Send your prompt
Perlin starts the build. You don't need to wait on the stage.
Go and do something else
Close the tab, lock the phone, or press New piece to start another idea. Opening another piece from My pieces leaves the build running too.
See it in My pieces
In My pieces (L), a piece that is still building shows a dot and "Building…". When one finishes while you're on another piece, the studio tells you, for example "“Night Market” is ready".
Come back to it
Open the piece again. If Perlin is still working, the studio picks the build up where it is and you watch the rest live; if it has finished, the result is already in the piece.

New piece and Stop

New piece, in the top bar and in My pieces, starts an empty piece and lets any build that is running carry on. Its piece picks up the result.
Stop is the square button that takes the place of the send button while Perlin works. It stops the build on the server and throws away what it made, even if it had finished a moment before. The reply reads "Stopped." and the version on the stage stays as it was.

A stopped build is charged for the work it did up to that point. Once the finished piece is rendering on the stage, there is nothing left to stop. If you stop while Perlin is making 3D models, the models are still finished, kept in your assets and charged (Sound FX, Textures and 3D).

How a long build works

For a large piece, Perlin writes a short plan first, so the step under its reply reads "Planning the build" before "Writing the code". A very long build runs in stages, handing its work on from one to the next. At each hand-over a step reads "Carrying on", with a note such as "From the work saved so far". You don't need to do anything.

You may also see "Retrying", for example with the note "Busy right now; Perlin switched to a backup to keep going". That too carries on by itself.

Keep going

Sometimes a build stops short: it is too big to finish in one go, or something fails partway. If Perlin saved its work so far, the reply says so, for example "This one was too big to finish in one go. Perlin kept its work so far and can keep going from there.", and offers Keep going.

Press Keep going
It's on the last reply, under the note. Perlin starts again in the same reply, from the code, plan, sounds and textures the build had saved, rather than from the beginning. The step reads "Carrying on", "From where the last attempt stopped".
Let it finish
The rest of the build runs like any other, and the finished piece arrives as a new version.

Keep going runs at the effort level and switches set when you press it. It's a new request, charged for what it takes; the build that stopped short isn't charged, apart from any 3D models it made, which are in your assets.

Other buttons may sit beside it:

Try again sends the same request again from the start.
Open draft in editor opens the code Perlin had written so far in the code editor, to look at or finish by hand.

Keep going isn't offered for fixes or look-overs, or for a build that failed before it had saved anything; those offer Try again only.

Still stuck, or something here out of date? Tell us