Possible duplicate of T780?

I had downloaded your starter.exe (thx btw). And updated without apparent problem this time.

In T1327#50788, @lancake wrote:

I'm not sure why you got that blank screen at first (if it's your first time after booting up your pc, it can take a while) but since you were ending processes, I'm guessing you did that in the middle of an update which seems to corrupt the entire installation.

It happens the same way on my windows 8.1 computer, but not reliable enough.

yeah, time to switch to it :P

Really, this should be handled by better versioning -- ex: SemVer

Does this happen on any platform besides Debian 8 (mate)?

Interesting response to not having a connection.
Adding an offline-only mode and have the launcher intelligently fallback to it should resolve this issue.

Added relevant information to reproduce in tester information field.

moving to launcher development, I doubt starmade was ever correctly started in this case, and thus the launcher has to check if it had a valid executable.

Too bad, confirmed that.

'-Djava.net.preferIPv4Stack=true' is already present and passed to the jvm.

Feature request accepted by @calani
sending in queue

-Validated-
-Confirmed-

-Confirmed-

i did tried it last with download 79 ... will try again when there is a newer one

@SmilingDemon: This should be fixed with one of the latest commits; I'm unsure, however, as we have been unable to reproduce the bug on any system or vm. You can test it when the build server is working again ~

The -server option passed to the jvm is strangely not listed in your screenshot, but is present in the code.

-QA Testing-

Behavior may have changed.

-QA Testing-

Starting the Launcher as a fresh install without a Steam client installed crashes when trying to Login.
Skipping the Login part lets you start it just fine.
output from win7 cmd prompt:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.C:\Users\Q>"C:\Users\Q\Desktop\Starmade Launcher.lnk"C:\Users\Q>[2284:0122/231411:INFO:renderer_main.cc(200)] Renderer process starte
d[1408:0122/231458:INFO:renderer_main.cc(200)] Renderer process started
[3144:0122/231458:INFO:renderer_main.cc(200)] Renderer process started
[3632:0122/231514:INFO:CONSOLE(12450)] "ReferenceError: steam is not defined
   at D:\Starmade\starmade-launcher-win32-x64\resources\app.asar\lib\main.js:15
5:51
   at D:\Starmade\starmade-launcher-win32-x64\resources\app.asar\node_modules\a
ngular\angular.js:10249:13
   at processQueue (D:\Starmade\starmade-launcher-win32-x64\resources\app.asar\
node_modules\angular\angular.js:14678:28)
   at D:\Starmade\starmade-launcher-win32-x64\resources\app.asar\node_modules\a
ngular\angular.js:14694:27
   at Scope.$eval (D:\Starmade\starmade-launcher-win32-x64\resources\app.asar\n
ode_modules\angular\angular.js:15922:28)
   at Scope.$digest (D:\Starmade\starmade-launcher-win32-x64\resources\app.asar
\node_modules\angular\angular.js:15733:31)
   at Scope.$apply (D:\Starmade\starmade-launcher-win32-x64\resources\app.asar\
node_modules\angular\angular.js:16030:24)
   at done (D:\Starmade\starmade-launcher-win32-x64\resources\app.asar\node_mod
ules\angular\angular.js:10545:47)
   at completeRequest (D:\Starmade\starmade-launcher-win32-x64\resources\app.as
ar\node_modules\angular\angular.js:10717:7)
   at XMLHttpRequest.requestLoaded (D:\Starmade\starmade-launcher-win32-x64\res
ources\app.asar\node_modules\angular\angular.js:10658:9)", source: D:\Starmade\s
tarmade-launcher-win32-x64\resources\app.asar\node_modules\angular\angular.js (1
2450)

-Confirmed-

-QA Testing-
Not fixed, at least on ubuntu linux 14.04 32bit. Tester information field updated with new log. Does occur on 64bit ubuntu linux 12.04 too, unless the environment path is manually set to the launcher's install folder beforehand. Thus assuming the cause to be a path resolving issue.

What errors get thrown in ubuntu 14.04 x64? Is it trying to launch the game before downloading it? Are there any missing files/dependencies, ex ~/dep/java/jre1.7.0_80/bin/java?
I've so far been unable to reproduce the behavior.

-QA Testing-
Still occurring on ubuntu 12.04 and 14.04, other linux versions are likely also affected.

I cannot reproduce this anymore, even with what I think are the old bad files.

I believe fixing T779 and T739 resolved this issue in v0.0.4; can anyone else verify?

If anyone experiences this when upgrading to the new launcher version, please comment with your OS flavor and architecture, launcher versions (from and to), and any relevant settings files. Thanks!

Assuming this is resolved ~
The missing win32 java dependency will be addressed with the next launcher release. If you are still having issues, please create another ticket!

I cannot duplicate this behavior in x64. Has the new launcher version resolved the issue?

Apart from win32 missing bundled java, is this still an issue?

Changing the selected version in the dropdown no longer triggers an immediate update, instead requiring you to manually click one of the update buttons (either in the build options window or the large orange [UPDATE] button in the lower corner of the launcher)

Increased default max-memory value for x64 from 1gb to 1.5gb
commit: 01e791ccd7e62034e7f4a9208eb4e2bd96320c78