ue-editor-launch

To fix soft_ue_cli check-setup failures and 502 errors, launch UnrealEditor.exe to start the project .uproject, validate SoftUEBridge reachability, and apply restart-based recovery or NO_PROXY adjustments until the bridge responds successfully.

Unreal Engine automation workflows fail with SoftUEBridge timeouts when no interactive UnrealEditor instance is running. Reliably locating and starting UnrealEditor.exe restores bridge reachability for soft-ue-cli dependent tasks, preventing false negatives.

The best way to launch UnrealEditor.exe for Windows automation without multiple instances is resolving the executable via environment-variable override or fallback path, then starting the .uproject file as a deterministic script entrypoint.

Yes, you can use an environment variable to override the UnrealEditor.exe path. The skill applies environment-variable override lookup first, then falls back to a known path resolution to reliably start the project for soft-ue-cli workflows.

To restore SoftUEBridge reachability for blueprint and PIE inspection, launch the project .uproject in UnrealEditor, then repeatedly run soft_ue_cli check-setup and status commands to confirm the bridge is healthy before proceeding.

Launching UnrealEditor.exe addresses proxy issues by suggesting NO_PROXY adjustments during bridge health checks. If the bridge still returns 502 or times out, the skill applies restart-based recovery strategies to restore connectivity.