calani
Dreaming of Sushi ~
This bug is an elusive one.Well I updated my driver's got a fresh version of starmade and put the --verbose in. The new launcher still dosn' t activate
It's completely silent: there's nothing to indicate a crash even happened, apart from the log ending at event App ready. It's also extremely rare: you are the fifth reported case. I've yet to determine any cause, either, despite having been affected at one point. Furthermore, the three reported fixes have nothing in common (apart from being on Windows), and the hardware and environments seemingly have nothing in common, either.
In the spirit of learning more about this adversary, could you provide me with a dxdiag and a copy of the launcher's console output? (To get the console output, run the new launcher from the command line, again with --verbose). My leading hypothesis is that the cause is environmental, meaning something on your system is causing the crash.
Furthermore, if you're running Windows, could you peruse the windows event log? There's a small chance it will show something useful near the time of the launcher crash. If there's anything, it would likely show up under Windows Logs\Application, though it may be under Windows Logs\System instead. Unfortunately, I cannot tell you what you are looking for.
After that, you can try these fixes:
1) (Steam; any OS) Delete all files within SteamApps\common\StarMade, with the exception of the StarMade game folder residing therein. Afterwards, extract the files from the standalone new launcher install, which you can download from here. This resolved the issue for me, though frustratingly I was never able to reproduce it again afterward.
2) (Windows, AMD) Uninstall all AMD drivers (all, not just graphics drivers; some are hard to find) and update to the newest versions from their website. For one affected user, apparently an outdated driver (one that wouldn't autoupdate to the newest) was causing a conflict somewhere that resulted in this same issue.
3) (Windows) Reinstall windows. Totally overkill solution that's quite strangely not guaranteed to work.
Again: please provide me a dxdiag, the console output, and any possibly relevant info from the windows event log. With luck I'll find something that will help me squish this bug for good!