Fix 64bit Executable and Parameters #9
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Sorry for my late response, I've seem your PR then I forgot about it. I'll look into it when I get back from work (about 9 hours from now) |
|
Okay, I just ran Astyle, as I had forgotten that, and commited that change as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update 1.70 exchanged the 32bit for a 64bit executable, thus it is now called arma3.x86_64 instead of arma3.i386
For some reason, startup parameters seem to be case sensitive now.
There is also a bug that crashes the game if you alt-tab out of ArmA immediately after starting it with -noSplash. Added a Warning Tooltip.