# Creating your first project

## Creating your first project <a href="#hs_cos_wrapper_kb-article-module-3" id="hs_cos_wrapper_kb-article-module-3"></a>

Once you have installed the Unreal Engine on your computer, you are ready to create your first project. If you need help with installing Unreal Engine, please view the previous section ["Getting and Installing Unreal Engine"](https://knowledge.carbon.show/carbon-for-unreal/installation/getting-and-installing-unreal-engine)

### Launch the Unreal Engine

Using the Library Tab of your Epic Games Launcher, you can launch any of your currently installed versions of the Unreal Engine. To create a new project, start by launching your newly installed version of Unreal with the "Launch" button provided.

### Name and Create a Project from the Launcher

After a short loading period, you will be presented with an Unreal Project Browser/Creator. Here you have access to a series of starter templates, archetypes, or coding packages to get a running start. For a first-time project, select the "**Blank**" template from the "**Games**" category. This will generate an empty project with no unnecessary code added. Project Defaults can remain at a default, however, include Starter Content and Raytracing to enable the best visuals and some simple starter assets to build with.

{% hint style="warning" %}
***CAUTION - For the project location and Path, it is not advised to host the project in any locations that are actively synced by Dropbox, Google Drive, Box, Etc. This can cause issues with file corruption. Use of Source control such as Plastic or Perforce are recommended for groups and those using more than one computer.***
{% endhint %}

&#x20;

<figure><img src="https://support.carbonforunreal.com/hubfs/Knowledge%20Base%20Import/cdn-assets.carbon.showkbcarbon-plugininstallationFirstProject.jpg" alt=""><figcaption></figcaption></figure>

*After setting the defaults, naming and saving the project to your preferred folder location, hit "**Create**".*

### Wait for the Project and Shaders to Compile

After naming and creating the project, Unreal will launch and begin loading the engine for use. This process takes a little time depending on the speed of your computer. Compiling shaders on your first startup takes a while; you will be automatically entered into the project process is complete. (This process will be faster on subsequent project openings)

<figure><img src="https://support.carbonforunreal.com/hubfs/Knowledge%20Base%20Import/cdn-assets.carbon.showkbcarbon-plugininstallationcompiling_Shaders.jpg" alt=""><figcaption></figcaption></figure>

&#x20;

### Entering your First Project

Once compiled, the project will open to a default map. You now have access to an unreal project to personalize, build, or test from. It may show a Plugins window which show which plugins are loaded and which are available to be loaded. It is not necessary to load any additional plugins unless you have specific needs.

<figure><img src="https://support.carbonforunreal.com/hubfs/Knowledge%20Base%20Import/cdn-assets.carbon.showkbcarbon-plugininstallationUnreal_Plugins_Start.jpg" alt=""><figcaption></figcaption></figure>

&#x20;

The project is now ready for Carbon for Unreal Plugin installation

<figure><img src="https://support.carbonforunreal.com/hubfs/Knowledge%20Base%20Import/cdn-assets.carbon.showkbcarbon-plugininstallationUnreal_ready.jpg" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://knowledge.carbon.show/carbon-for-unreal/installation/creating-your-first-project.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.