Lab report — expectations and outline

Wed, 14 Oct 2026 00:00:00 +0000

Your report should make clear what you did, how you did it and what you understood. Keep it short, visual and easy to review: favour screenshots and brief explanations. I already know the lab instructions; present your own work without copying or explaining the assignment again.

1. Header and Git repository

Submit your report as a PDF. At the very beginning, clearly include:

The first and last names of everyone who worked on the lab.
Your programme, year and group.
The course, lab number and title, and submission date.
A link to the project’s Git repository whenever requested. Providing this link is good practice even when it is not explicitly required.

The instructor must be able to access the repository, download the project and test its features. Include any brief instructions needed to run it, for example in a README.

Optional, but helpful: organise commits or tags by question, step or feature to make your progress easier to follow and support technical assessment.

2. Progress through the lab

Follow the main steps of the lab. For each step, present:

What you implemented, with one or more readable, captioned screenshots showing your progress.
How you proceeded and what you understood, in a few short sentences or bullet points; mention implementation choices when they help explain your work.
Any difficulties or blockers: what went wrong, what you tried and how you resolved it. Clearly identify any issues that remain unresolved.

Document intermediate steps as well as the final result. Your images should show how the application developed and which features you implemented along the way. Add a short caption explaining what each screenshot shows or demonstrates.

3. Conclusion: final state and personal reflection

End with a brief assessment:

What the final application actually contains: completed and tested features, partial or missing elements, and known limitations.
Optionally, a personal reflection: what you learned, the main difficulties, possible improvements or ideas for further work.

Should you include code?

There is no need to copy your code into the report. A very short snippet of pseudocode or code may help explain a particular function or choice when it makes the explanation simpler.

The report is used to assess your approach and understanding. Technical assessment of the code and application testing use the Git repository.

Reusable outline

Header — names, group, course, lab, date and Git link.
Lab steps — for each step: work completed, captioned screenshots, approach and choices, and any difficulties and solutions.
Conclusion — the application’s exact final state, limitations and optional personal reflection.

Before submitting, check the PDF, author details, screenshot readability, coverage of intermediate steps and access to the Git repository if you provide one.

Unity setup — Brest campus PCs

Mon, 02 Feb 2026 00:00:00 +0000

Unity Hub and Unity 6.3 LTS

Launch Unity Hub from the school computer’s applications menu (on Linux: Applications > Development > Unity Hub, depending on the workstation). Sign in to your Unity account, creating one if needed, and follow the workstation’s license instructions.

In Installs, use the already installed Unity 6.3 LTS. Its version starts with 6000.3; keep the installed patch for the lab.

If the installation is not listed, use Locate and select the Editor/Unity executable belonging to the workstation’s 6.3 installation. The exact path depends on the school’s setup: ask the instructor if necessary. The old /opt/img/Unity-2021.3.9f1/Editor/Unity path no longer matches the course version.

Create a Universal 3D (URP) project. In Window > Package Management > Package Manager, prepare Input System, Unity UI and the FPS controller dependencies during the session. Under Edit > Project Settings > Player > Other Settings > Configuration, select Active Input Handling = Input System Package (New) if it is not already selected, then accept the requested restart.

Export requires the workstation platform’s build module. If missing, inform the instructor; Unity Hub > Installs > installation menu > Add modules can add it when workstation permissions allow.

Visual Studio Code (C# editor)

Current integration uses the Unity extension published by Microsoft in VS Code. It installs the required C# dependencies, including C# Dev Kit. In Unity’s Package Manager, use Visual Studio Editor, at the stable version offered for the editor and at least 2.0.20. The older Visual Studio Code Editor package is no longer maintained. Microsoft instructions.

To open scripts in VS Code:

In Unity, open Edit > Preferences > External Tools (on macOS, preferences are in the Unity menu).
Under External Script Editor, choose Visual Studio Code or use Browse…. On Linux workstations where installed there, the executable is /usr/bin/code.
Use Regenerate project files if needed, then open a script from Unity to load the complete project in VS Code.

Troubleshooting auto-completion

Check that Microsoft’s Unity, C# and C# Dev Kit extensions are enabled and Visual Studio Editor is installed.
Open the complete Unity project, rather than a standalone C# file. Regenerate project files and reload the VS Code window.
Inspect extension messages and resolve compilation errors in Unity’s Console.
If a .NET runtime or SDK is requested, follow the extension’s instructions and have the workstation installation checked.

The old OmniSharp Use Global Mono = always instructions concern a previous generation of integration and should not be applied by default to this setup.

Choosing the project folder

Store the project on the local disk, such as the workstation’s local workspace or /tmp on Linux if intended for the session. The local SSD avoids network storage delays during import and compilation.

End-of-session backup

Temporary storage may be deleted on restart. Save and copy your project to your personal storage before leaving the workstation. Keep Assets (including .meta files), Packages and ProjectSettings. Unity can regenerate the Library and Temp caches.

Practical Guides | Étienne Peillard