57d2674f37 Use a modifiable user-preset sample for VS 2022/2019 (#97)
* Use a modifiable user-preset sample for VS 2022/2019

Customizing a repo-tracked preset file doesn't work:

Type in your gamedir for debugging, or toggle verbose mode for the build, or configure Chinese
UB MapEditor: you now have an unstaged `CMakePresets.json` change in your working directory.
very annoying.

Also, Visual Studio 2022's preset support has a bug: if you have a `CMakePresets.json` file,
no matter in which file (user or repo) the preset you have selected is defined, if you click
"Manage Configurations..." it will always open `CMakePresets.json` for editing, setting the
user up for failure and editing the commited-to-repository file.

Having just the `CMakeUserPresets.json` file also sidesteps another poor Visual Studio 2022
decision: hiding in Folder View files that are .gitignore'd (like `CMakeUserPresets.json`).

In the absence of a `CMakePresets.json` file, selecting "Manage Configurations..." will open
the right file for editing.

The workflow is then:

Copy `CMakeUserPresets.json.sample` into `CMakeUserPresets.json` _once_, then customize
that to your heart's content without git bothering you and accidentally adding an
unwanted change to a patch. Or make your own.

* Added auto-copy of profile template.

* declutter things a bit

move function out of root cmakelists.txt file
move user preset template to a presets directory

this is horrible and I hate it

Co-authored-by: CptMoore <39010654+CptMoore@users.noreply.github.com>
2023-01-21 20:26:49 -03:00
2023-01-19 00:13:08 +02:00
2023-01-19 00:13:08 +02:00
2023-01-14 02:08:39 -03:00
2023-01-14 02:08:39 -03:00
2023-01-14 02:08:39 -03:00
2023-01-19 00:13:08 +02:00
2016-01-31 17:54:51 +00:00
2023-01-03 15:51:48 +02:00
2023-01-03 15:51:48 +02:00
2023-01-03 15:51:48 +02:00
2007-06-09 09:01:04 +00:00
2023-01-03 15:51:48 +02:00
2023-01-03 15:51:48 +02:00
2023-01-03 15:51:48 +02:00
2023-01-03 15:51:48 +02:00
2013-04-14 22:58:58 +00:00
2023-01-10 13:50:05 +01:00
2023-01-03 15:51:48 +02:00
2023-01-03 15:51:48 +02:00
2023-01-03 15:51:48 +02:00
2007-10-20 06:56:34 +00:00
2007-10-20 06:56:34 +00:00
2007-10-20 06:56:34 +00:00
2023-01-10 17:52:46 -08:00
2007-10-20 06:56:34 +00:00
2023-01-03 15:51:48 +02:00
2023-01-03 15:51:48 +02:00
2016-03-08 21:06:31 +00:00

JA2 v1.13




JA2 v1.13



Preamble

Jagged Alliance 2 v1.13 is a modification for the Jagged Alliance 2 game.

Original development was done through SVN, this however ended abruptly in 2022, to keep the development going the step to Github has been made.

Feel free to participate in the development!

For more information you can visit the following locations:

In case of any issues, look at Reports or Participation

Downloads

Note

All-in-one releases come for different languages and include JA2 v1.13, the Map Editor and JA2 Unfinished Business.

Visit the releases page to download the latest all-in-one.

Installation

  1. Install the original Jagged Alliance 2

  2. Download the latest all-in-one release and copy its content to JA2 game directory. Overwrite when asked.

  3. Modify ini settings if you like.

  4. Play the game.

    Some additional information on can be found in folder "docs" inside download.

    If you face issues with higher resolutions, alt+tab not working, blackscreen, etc.,
    run the "cnc-ddraw-config.exe" in game-folder and adjust settings to your liking.
    (those issues can occur due to the combination of old game and modern OS/hardware, cnc-ddraw helps to avoid those)

Reports

For more information and reports, visit Bug reports at Bear's Pit Forum or join the Bear's Pit Discord

Participation

Feel free to participate on GitHub. If you want to know how, or simply wanna share your thoughts on a topic join the Bear's Pit Discord

S
Description
No description provided
Readme
57 MiB
Languages
C++ 90.4%
C 9.3%
HTML 0.2%
CMake 0.1%