Kevin Turner
Kevin Turner
The game started and has been running for a couple minutes, so it should be showing a "game crashed" message, not the "could not start" message. Launcher 4.5.0 on Ubuntu...
Currently in proof-of-concept stage. https://github.com/flightlessmango/MangoHud ## Implementation Notes MangoHud does provide a wrapper script you can use to launch a process with the HUD enabled. This PR's current implementation skips...
Running unit tests under Java ≥ 16 results in lots of tests not being able to start, some permissions errors about things from one package that aren't open to another....
Someone with a lot of respect for POSIX `sh` overhauled the unixStartScript.txt template for gradle 7.2: https://github.com/gradle/gradle/pull/17666/files#diff-a549a2629a3d96f76e3f043a1526e48fb086e90e9d9d03ae0f7abf6d3e803333 I guess now that we're not trying to apply a diff to upstream's...
From discord earlier: > <keturn> It knows if a game that has been launched from *this launcher process* is still running. But if you restart the launcher, it has no...
The launcher knows where the game is installed and what operating system it's running on. It can add a `-Djava.library.path=` argument to java, set to the natives directory for this...
The current checks that run on pull requests (also known as validation actions, or continuous integration) produce output that looks like a teletype that's trying to save paper by not...
qwc reports > just quit the nightly trying to run the stable, message box with "another game is already running..." > only solveable through restarting the launcher. using launcher 4.1.0...
The "Build and test with gradle" step is the one that's useful to look at when considering branches and pull requests, but right now it has eleventy bajillion lines in...
There's lots of room for improvement when it comes to how the launcher behaves when the game fails to launch! I'm making a list here, but I think incremental improvements...