stride3d / stride3d/stride

Improve installation process

Open
#856 3 comments 1 reaction 1 assignee View on GitHub

@xen2 is already working on this.

Since Oct 5, 2020.

area-GameStudio area-Launcher enhancement priority-high work-estimate-M
Dominant language
C#
Stars
7.8k
Forks
1.2k
Avg merge
2d 17h
Merged PRs (30d)
49

Description

Is your feature request related to a problem? Please describe.
New users may become discouraged when dealing with issues early on. Having an opportunity I decided to install Stride onto a clean system (without Visual Studio and SDKs) to see what is the new user's experience.

Here is the full video, from zero to running a game in ~20 minutes: https://www.youtube.com/watch?v=SX5gLobqf6M

  • If the launcher needs updating, we should suppress the dialogs asking to install Stride/plugin
  • Progress bar needs to show some progress - from 2:40 to 7:20 (4:40min) the user doesn't get any indication if Stride is installing correctly or maybe it hang
  • Finally when Stride got installed it defaulted to .NET Core 3.1, which I haven't installed
    There should be a check done to discover which SDKs/build tools the user has in their system and grey out unavailable framework.
  • Having started Stride in .NET Core 3.1 mode there was no feedback for nearly 2 minutes (11:52 - 13:47) when finally a dialog window popped up saying I don't have a compatible version of MSBuild.
    In general, the "Start Stride" button should remain greyed out until Stride has loaded correctly, or a clear error message should always be displayed (sometimes Stride may just silently never open).
  • VC++ Redistributable 2013 is required in both versions x86 and x64 and wasn't installed with Stride - I had to manually download and install those (Interestingly enough the GameStudio launched with just x86 version).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.