docs/unreal/getting-started/setup.md L68 (v2.3 and v2.2) tells Windows users to right-click their .uproject and select Generate Visual Studio project files. Drew left a TODO on this line asking for a fallback note for users who don't see that context-menu option (it depends on a shell extension that the UE installer may not have registered, or that another install clobbered).
The macOS step at L77 already shows the standalone-script approach (GenerateProjectFiles.sh). The standard Windows equivalent is GenerateProjectFiles.bat under <UE_INSTALL>/Engine/Build/BatchFiles/Win64/, but the exact path and any Beamable-specific considerations should come from someone who has dealt with this in the SDK team (Rauiz, Felipe, or Vitor would likely know off the top of their head).
Scope: add a second sub-step (or a "If you don't see this option" admonition) under L68 with the recommended command and the path on a default UE install.
Originally flagged in docs/unreal/getting-started/setup.md L68 on unreal/v2.3 and unreal/v2.2.
docs/unreal/getting-started/setup.mdL68 (v2.3 and v2.2) tells Windows users to right-click their.uprojectand select Generate Visual Studio project files. Drew left a TODO on this line asking for a fallback note for users who don't see that context-menu option (it depends on a shell extension that the UE installer may not have registered, or that another install clobbered).The macOS step at L77 already shows the standalone-script approach (
GenerateProjectFiles.sh). The standard Windows equivalent isGenerateProjectFiles.batunder<UE_INSTALL>/Engine/Build/BatchFiles/Win64/, but the exact path and any Beamable-specific considerations should come from someone who has dealt with this in the SDK team (Rauiz, Felipe, or Vitor would likely know off the top of their head).Scope: add a second sub-step (or a "If you don't see this option" admonition) under L68 with the recommended command and the path on a default UE install.
Originally flagged in
docs/unreal/getting-started/setup.mdL68 onunreal/v2.3andunreal/v2.2.