Your courtyard prototype needs one more pass before a teammate can test it. The ramp needs repositioning, a few props need adding, and the lighting should make the route easier to read. You have the Unreal Engine project and your Googlebook. You need access to Unreal Editor to make those changes, test the character’s movement, and prepare a playable build.

Vagon Cloud Computer gives you a Windows workspace you can control through your Googlebook’s browser. The workstation runs the editor and handles the project’s processing, while you use your laptop’s screen, keyboard, and mouse to work.

Unreal Engine also supports Linux development, but Googlebook’s Linux environment needs separate consideration, particularly around graphics support. This guide follows a cloud workflow for opening an existing project and completing the next development steps.

You will learn how to prepare the editor, transfer the complete project, adjust the level, and test it in Play in Editor. Then you will package a Windows build, check it on the workstation, and share it with your teammate.

Source: Epic Games

Can Googlebook Run Unreal Editor?

You can use Unreal Editor from a Googlebook by accessing a supported desktop computer remotely. With a Windows cloud workstation, the editor runs on that computer while your Googlebook displays the session and sends your keyboard and mouse input.

Direct installation requires a closer look at the operating system and graphics environment. Epic documents Unreal development on Windows, macOS, and Linux. Googlebook OS does not provide the same environment as any of those desktop platforms.

What about Linux?

The Googlebook Terminal provides a Debian virtual machine and a way to launch graphical Linux applications. However, Unreal Editor also needs graphics capabilities that meet Epic’s Linux requirements.

Google currently lists GPU acceleration for its Linux VM as future work. Terminal availability alone therefore does not establish a suitable Unreal Editor environment, especially for demanding real-time scenes.

Playing a game and developing one require different tools

A game built with Unreal Engine may run on Android, Windows, or another supported target platform. That does not mean the Unreal Editor itself runs on every device capable of playing the game. Development requires the editor, project assets, and the tools needed for the chosen output platform.

For our courtyard prototype, we will use a Windows cloud workspace. It provides a place to open the project, adjust the level, test movement, and package a Windows build from your Googlebook.

Get Unreal Editor Ready on Vagon

Prepare the cloud workspace around the project you want to open. The main choices are the workstation’s resources and the Unreal Engine version. Once those are ready, you can work in the desktop editor from your Googlebook.

1. Create your computer and select Unreal Image

Create your Vagon Cloud Computer, choose a nearby location, and select a GPU-equipped performance option.

Epic’s recommended Windows specifications include 32 GB of RAM and 8 GB or more of graphics memory. Use these as starting references; larger environments and demanding rendering features can need additional capacity.

During application selection, choose Unreal Image, the option listed in Vagon’s Game Design application catalog. This prepares an Unreal development environment as part of the computer setup.

Allocate storage for the engine, project assets, cache, and packaged builds. Keeping multiple engine versions can require additional space, so account for the project’s version before choosing your storage.

2. Connect from your Googlebook

Start the computer and connect through your dashboard. The Windows desktop opens in your browser, giving you access to the prepared applications and working files.

Use full-screen view for more room around the Level Viewport, Content Browser, Outliner, and Details panel. A mouse is useful for navigating the scene and positioning actors.

Your Googlebook controls the session while the workstation processes the editor’s graphics and development tasks. You can now open the engine or prepare the version required by your project.

3. Check the engine version and launch the editor

For an existing project, identify the Unreal Engine version used by its author. Check the versions available in the cloud environment and launch the matching release.

If you need another version, use the Unreal Engine > Library section of the Epic Games Launcher inside Windows to install it. Sign in with your Epic account when required.

Matching the project’s engine version helps avoid an unnecessary conversion. If you intentionally upgrade, follow Epic’s project conversion guidance and open a copy.

For a new prototype, launch the editor and choose the Third Person template with Blueprint as the project type. This gives you a character and movement setup to build around.

Using C++? Check the compiler and Windows SDK requirements for your selected engine release. Existing code projects and some plugins need those tools.

With the editor ready, the next step is to bring in the complete courtyard project.

Move the Complete Project With Vagon Files

An Unreal project is a folder containing its settings, assets, and supporting files. The .uproject file identifies the project, but it does not contain the level, materials, textures, or gameplay logic by itself.

For our courtyard prototype, transfer the complete project folder so the ramp, props, character, and lighting assets remain available when you open it.

Prepare the project folder

Save the project and close the editor before preparing the transfer. If another person supplied it, confirm the engine version and any required plugins.

Epic’s project directory structure explains the main folders:

For a straightforward first transfer, package the complete folder rather than removing unfamiliar directories. If the project uses external files or plugins installed at engine level, include their setup information as well.

A ZIP archive can keep the folder structure together during upload. For a team project already managed in source control, obtaining a complete working copy inside the workstation is another option.

Upload through Vagon Files

Open Vagon Files from your dashboard and upload the project package from your Googlebook. You can upload while the cloud computer is stopped, allowing the transfer to finish before your editing session.

Inside the Windows desktop, access the uploaded package and extract it into a working folder. Open the .uproject using the engine version prepared in the previous section.

If Unreal reports a missing plugin or module, address the named dependency before continuing. Code plugins may need a compatible Windows build or compilation tools.

Allow the project to prepare its assets

The first opening can involve shader compilation and other asset preparation. Unreal stores reusable results in its Derived Data Cache, which can reduce repeated preparation work.

Allow those tasks to complete before judging viewport performance. Then open the courtyard map and check that the character, materials, and props appear correctly.

The Migrate tool serves a different purpose: copying selected assets and their dependencies between Unreal projects. It is useful when combining content, but transferring an existing project requires its settings and supporting files too.

Once the level opens correctly, save your working copy. You are ready to reposition the ramp and make the first scene changes.

Make Your First Level Changes

Open the courtyard map and inspect the route the character will follow. We will reposition the ramp, add a few props, and adjust the lighting so the path is easy to recognize. Save a working copy of the level before making changes.

The main editor panels support different parts of the job:

Reposition the ramp

Select the ramp in the Outliner or viewport. Use the transform gizmo to move it into place, then inspect its Location, Rotation, and Scale values in the Details panel.

Grid snapping helps you align it with nearby geometry. Check the connection at both ends: a small gap or raised edge may interrupt the character’s movement even when the ramp looks correctly positioned from above.

If the ramp is a Static Mesh Actor, inspect its collision settings and the mesh’s collision geometry. A visible surface needs suitable collision to support the character. We will verify that behavior in Play in Editor.

Source: Epic Games

Add props and adjust their appearance

Find the required assets in the Content Browser and drag them into the level. Position them around the route while keeping the intended passage clear.

Check their scale against the character and surrounding architecture. For repeated props, duplicate a placed actor and adjust its transform.

If you change a shared material, other objects using it can change too. Create a separate material instance when the prop needs its own supported parameter values, such as color or roughness.

Source: Epic Games

Make the route easier to read

Select the relevant light actors and adjust their placement and intensity. Review the ramp from the player’s likely approach, checking that its edges remain distinguishable from the ground.

Use the same viewpoint to compare changes. Brightening the entire scene may improve visibility, but a targeted lighting adjustment can provide clearer guidance.

Save the level and any modified assets. Your first revision is ready; next, choose performance settings that support comfortable editing and testing.

Source: Epic Games

Choose Performance for the Viewport, Shaders, and Builds

Unreal Editor uses computing resources differently as you work. Moving through the courtyard relies heavily on graphics performance, while preparing shaders or compiling code places more demand on the CPU. Loading assets, running the editor, and testing the project also require sufficient memory.

Choose your workstation around the activities the project needs:

Epic’s recommended specifications include 32 GB of RAM, 8 GB or more of VRAM, and a DirectX 12-compatible graphics card. These provide a starting reference. A compact prototype and a detailed environment with high-resolution textures have different demands.

Keep editing quality appropriate to the task

You do not need the highest viewport quality for every placement decision. Unreal’s scalability settings let you adjust rendering quality while working.

For the courtyard, use a quality level that makes navigation comfortable while preserving enough detail to assess the route. Reducing resolution scale can also lower the rendering workload.

Return to the intended quality settings when reviewing lighting and presentation. Changes to shadows, reflections, or global illumination can affect how the scene looks, so review those features before approving the result.

Source: Epic Games

Account for Lumen and Nanite

Features such as Lumen and Nanite have specific hardware and project requirements. Confirm those requirements for the engine version you are using rather than assuming every GPU configuration supports every rendering path.

A suitable GPU helps you work with demanding visuals, while sufficient VRAM provides room for their graphics data. Additional system RAM supports larger editor workloads but does not simply become equivalent GPU memory.

Give compilation and cache room to work

The first project opening may spend time compiling shaders and generating derived data. Those tasks can temporarily compete with editing for resources.

Unreal’s Derived Data Cache retains reusable results. Keep adequate storage available and allow initial preparation to finish. Repeatedly clearing the cache can create more work on subsequent openings.

Vagon’s performance options let you change the available resources as the project grows. You can select more capacity for a heavier environment or build workload while retaining your applications and files.

For a useful comparison, test the same level, viewpoint, and quality settings after asset preparation finishes. That helps you choose resources around the work you actually perform.

Test Movement and Interactions in Play in Editor

With the ramp and props positioned, use Play in Editor to check how the courtyard behaves during gameplay. A scene can look correct in the viewport while collision, character spawning, or camera behavior needs adjustment.

Save your changes, then choose a play mode from the toolbar:

For our prototype, Selected Viewport provides a convenient first check. Start the session, click inside the game view to capture input, and move the character along the intended route.

Source: Epic Games

Check the following:

• Starting position: The character appears at the intended spawn point.

• Ramp traversal: The character can approach, climb, and leave the ramp.

• Prop collision: Objects block or allow movement as intended.

• Camera behavior: The player can see the route without unexpected obstruction.

• Interactions: Any existing triggers or Blueprint actions still work.

Walk through the route from both directions. A ramp’s angle, collision shape, or connection to the ground may prevent traversal even when its visible geometry appears suitable.

Press Shift + F1 to release the mouse back to the editor when needed. Stop the play session before making your next level adjustment. Changes made during play are generally temporary unless explicitly preserved.

If Unreal reports Blueprint errors, inspect the relevant messages and correct them before repeating the test. Save the edited assets afterward.

PIE helps you iterate quickly. Once the route works here, the next check is running a packaged Windows build outside the editor.

Package a Windows Build and Check It Before Sharing

Once the courtyard works in Play in Editor, create a build your teammate can test outside Unreal Editor. Packaging prepares the project’s code and assets for a target platform, producing an application with the files it needs to run.

We will create a Windows test build and run it on the cloud workstation before sharing it.

1. Set the starting map

Open Edit > Project Settings > Maps & Modes and set Game Default Map to the courtyard level.

This determines which map the packaged application opens. Having the courtyard visible in the editor does not automatically make it the application’s starting level.

Save the map and any modified assets.

Source: Epic Games

2. Choose the packaging settings

In Project Settings > Packaging, select Development as the build configuration for this test. Development builds are useful while checking behavior and investigating problems.

Review the List of maps to include in a packaged build, particularly if your project restricts which maps are packaged. Include the courtyard and any other maps the test needs.

For a C++ project or one using code plugins, confirm that the compiler, Windows SDK, and plugin dependencies match the selected engine release. Blueprint projects can also gain compilation requirements through their plugins.

Source: Epic Games

3. Package the project

Open the toolbar’s Platforms menu, select Windows, and choose Package Project. Select an output folder separate from the working project.

Allow the packaging process to finish. If it fails, open the Output Log and inspect the relevant error messages. A generic “Unknown Error” at the end often provides less useful information than the earlier message identifying a missing dependency or failed operation.

Source: Epic Games

4. Run the packaged application

Open the output folder inside Windows and launch the project’s executable. Confirm that:

• The courtyard loads as the starting map.

• The character spawns and accepts input.

• The ramp and props behave as expected.

• Materials, lighting, and required interactions are present.

This checks the actual packaged application rather than relying solely on the editor session.

5. Share the complete build folder

Archive the packaged output folder together, including its executable and supporting files. Sending only the .exe can leave the recipient without required project data.

Place the archive in Vagon Files, then download it to your Googlebook or use your preferred sharing workflow.

The build targets Windows. Your Googlebook can store and transfer the archive, while running the Windows executable requires a suitable Windows environment. Keep the editable project saved separately so you can continue development after your teammate’s feedback.

Source: Epic Games

Quick Fixes for Common Interruptions

When something interrupts the session, check the part of the workflow involved. A project dependency, rendering bottleneck, and connection delay require different responses.

For a project-opening error, keep the message available while checking the named plugin or module. Avoid upgrading the project simply to see whether the warning disappears; use the intended engine version first.

For performance checks, let initial shader preparation finish before comparing configurations. Keep the same viewpoint and quality settings so the comparison is useful.

Save after meaningful changes and keep the cloud computer running until packaging completes. After testing and transferring the build, stop the workstation from your dashboard. You can return to the saved project when the next revision is ready.

Final Thoughts

Your Googlebook can be the device you use to develop an Unreal project, from level edits to a tested Windows build. A cloud workstation provides the desktop environment and computing resources, while you control the editor through your browser.

Create your Vagon Cloud Computer, choose Unreal Image during setup, and bring in your complete project. Match the engine version, make your changes, test them in Play in Editor, and check the packaged application before sharing it.

FAQs

Can I install Unreal Editor directly on Googlebook?

Epic does not document a native Unreal Editor installation for Googlebook OS. You can access the Windows editor through a cloud workstation. Unreal also supports Linux development, but using it inside Googlebook’s Linux VM requires separate checks for compatibility and graphics support.

Can Googlebook’s Linux Terminal run Unreal Engine?

Terminal provides a Debian virtual machine capable of launching graphical Linux applications. Unreal Editor also requires suitable graphics drivers and Vulkan support. Google currently lists GPU acceleration for the VM as future work, so Terminal availability alone does not establish a suitable Unreal development environment.

What is Vagon’s Unreal Image option?

Unreal Image is listed in Vagon’s Game Design application catalog for preparing a cloud development workspace. Select it during computer setup, then check the installed engine version. If your project requires another release, prepare that version inside Windows before opening the project.

Can I use Blueprints and C++?

Yes. You can edit Blueprints in Unreal Editor and use Windows development tools for C++ projects. C++ compilation requires a compatible compiler and Windows SDK for your engine release. Some code plugins also require those tools, even when the rest of the project uses Blueprints.

Can I use Lumen and Nanite?

You can use these features when the workstation’s hardware, drivers, engine version, and project settings meet Epic’s requirements. Support differs by rendering feature and configuration. Check the intended rendering path, then test the actual scene before choosing the quality settings for editing or delivery.

How much RAM and VRAM should I choose?

Epic’s recommended Windows specifications include 32 GB of RAM and 8 GB or more of VRAM. Treat those as starting references. Detailed environments, large textures, multiple development applications, and demanding graphics features can need additional capacity. Evaluate performance after initial shader preparation has finished.

Can I run the exported Windows game directly on Googlebook?

A Windows executable needs a suitable Windows environment. Your Googlebook can download, store, and share the packaged build, but that does not make it a native Googlebook application. Test the build on the cloud workstation and send the complete output folder to Windows users.

Do I need to pay for Unreal Engine?

Unreal Engine offers free use for eligible users and projects, with royalties or seat licensing applying in other circumstances. Check Epic’s current licensing options for your intended use. Cloud computer usage is a separate cost, as are any paid assets, plugins, or services you choose.