openmultiplayer / openmultiplayer/launcher
Window becomes invisible/fails to render on launch
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 203
- Forks
- 97
- PR merge metrics
- No merged PRs in 30d
Description
Bug Description
Recently, the OpenMP launcher window disappears immediately after launching. While the application icon remains visible and active on the taskbar, no actual window renders on the desktop.
The issue persists even after a clean reinstallation and occurs either immediately upon opening or when navigating to settings to set the GTA: SA installation path.
Additional Behavior / Workarounds
- Ghost Window: If the invisible window is currently focused, clicking where the window should be does nothing. Clicking outside that area allows the desktop selection "square" to appear, suggesting the window is technically there but failing to render.
- Workaround: Opening another instance of the OpenMP Launcher allows this new instance to work correctly without crashing while the old instance is still active but invisible.
Steps to Reproduce
Note: This issue is intermittent and does not happen 100% of the time.
- Launch the OpenMP launcher.
- Observe if the window disappears from the desktop while remaining on the taskbar.
- (Alternative) Open the launcher, navigate to Settings, and attempt to set the GTA San Andreas installation directory.
Expected Result
The launcher window should remain fully visible, rendered, and interactable on the desktop.
Actual Result
The window becomes completely invisible/transparent, though its process remains active, its taskbar icon is present, and it still intercepts mouse clicks in its hidden boundary.
Environment
Windows 11 Home 64-bit
Open Multiplayer Launcher v1.6.1
Installation
Fresh GTA SA and OpenMP Launcher install
Logs
[00:00:01.146] (304c) INFO Frontend info: Archive checksum valid, processing files
[00:00:02.210] (304c) INFO Frontend info: Validation successful: samp_clients.7z
[00:00:02.211] (304c) INFO Frontend info: Validation successful: samp.dll
[00:00:02.211] (304c) INFO Frontend info: Validation successful: samp.dll
[00:00:02.211] (304c) INFO Frontend info: Validation successful: samp.dll
[00:00:02.211] (304c) INFO Frontend info: Validation successful: samp.dll
[00:00:02.212] (304c) INFO Frontend info: Validation successful: samp.dll
[00:00:02.212] (304c) INFO Frontend info: Validation successful: samp.dll
[00:00:02.212] (304c) INFO Frontend info: Validation successful: samp.dll
[00:00:02.212] (304c) INFO Frontend info: Validation successful: bass.dll
[00:00:02.212] (304c) INFO Frontend info: Validation successful: gtaweap3.ttf
[00:00:02.213] (304c) INFO Frontend info: Validation successful: mouse.png
[00:00:02.213] (304c) INFO Frontend info: Validation successful: blanktex.txd
[00:00:02.213] (304c) INFO Frontend info: Validation successful: CUSTOM.ide
[00:00:02.213] (304c) INFO Frontend info: Validation successful: custom.img
[00:00:02.213] (304c) INFO Frontend info: Validation successful: samaps.txd
[00:00:02.213] (304c) INFO Frontend info: Validation successful: SAMP.ide
[00:00:02.214] (304c) INFO Frontend info: Validation successful: SAMP.img
[00:00:02.214] (304c) INFO Frontend info: Validation successful: SAMP.ipl
[00:00:02.214] (304c) INFO Frontend info: Validation successful: SAMPCOL.img
[00:00:02.214] (304c) INFO Frontend info: Validation successful: samp.saa
[00:00:02.214] (304c) INFO Frontend info: Validation successful: sampaux3.ttf
[00:00:02.214] (304c) INFO Frontend info: Validation successful: sampgui.png
[00:00:02.215] (304c) INFO Frontend info: File validation successful
[00:00:02.329] (304c) INFO Frontend info: No new update available
[00:00:02.329] (304c) INFO Frontend info: OMP plugin is up to date
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. Start by reproducing the intermittent failure on Windows 11 during launch and while opening Settings, then trace the launcher window's startup and rendering path. Done means the window remains visible, rendered, and interactive while the process stays active.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100