Unable to start SlipstreamViewer.exe - Entry Point Not Found #644
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#644
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Environment
Slipstream Beta 1.3.0.1
Microsoft Windows 11 64-bit (Build 22621.4317)
Description
Whenever I try to start the SlipstreamViewer.exe of the Beta 1.3.0.1 on my Windows 11 PC, I get the error message in the image attached. It reads:
If it helps to narrow down the issue: in my PC, the D: drive is a hard drive, while the C: drive is the SSD where the operating system is installed.
Reproduction steps
It just happens when I try to open the SlipstreamViewer.exe from the Beta 1.3.0.1 version.
Adding to this, it might be of note that I used the .zip installation, rather than the .exe setup installer.
Thanks for the report. We've found the cause: the 1.3.0 Beta 1 Windows build shipped an old
openjp2.dll(OpenJPEG 2.4.0) next to an exe that needs 2.5.x. Your drives aren't the problem. The fix is tracked in #647, and a fixed Windows build will follow.Fixed in 1.3.0 Beta 2, now available from the downloads page and the update feed. The Windows zip and installer ship OpenJPEG 2.5.4, so the viewer starts again. If you unpacked the zip over an older install, use a fresh folder or let the installer replace it. Please let us know if it still fails.
Testing on Beta 1.3.0.2, the .exe initiates properly on Windows. Closing the issue.
Fixed in 1.3.0 Beta 2, and confirmed working by users who had the error. Thanks for reporting!