These shouldn't be left as they'll now point towards potentially invalid memory and also cause errors with serializing. Arrays and maps holding them are cleared. Also unlinks and relinks inventory items correctly from the hashmap on traveling.
Adds a multiplayer tab to allow hosting and joining games from within the GZDoom launcher rather than needed to use the command line. This has its own set of defaults independent from the main play page which necessitated rewriting how this information is passed and stored in the backend. A startup info struct is now passed back which has its defaults set from the cvars and then propagates any changes to it back to the defaults after selection is complete, making it much simpler to interface with the engine defaults.
* Cleanup: Alignment, long lines, Replace 0 with SDLK_UNKNOWN
* Gamecontroller api analogue input
* Added some button handling
* Added mapping for other buttons
* Added trigger events
* Added force_joystick flag
* Removed force_joystick flag
Rationale:
1. It was actually broken lol
2. I cannot think of a case where enabling this would be a useful thing for
gzdoom. If the user is using a gamecontroller, it is pointless. If they are
not using a gamecontroller, it will just default to using the joystick api.
If they are not using a gamecontroller, but SDL thinks they are, it is an
SDL bug, and will be reported and fixed
* Modified default mapping
* Added analogue to digital threshold
* Added analogue response curve
* Per axis settings
* Fixed controller reconnect
* Added threshold and curve to IJoystickConfig
Enabled saving of settings
* Added stubs
* Cleanup
Constants are no longer defines.
Constants are mostly shared between backends.
Moved some logic to m_joy
* Implemented xinput stubs
* Implemented dinput stubs
* Implemented ps2 stubs (untested)
* Fixed inclusive check
* Implemented osx stubs (untested)
* Fixed curve implementation
No longer savable, I screwed the curve function up.
I though it needed 2 control points, but it needs 4.
Need to re-do controller settings :(
* Now using CubicBezier struct
* Fixed SetDefaultConfig to match xinput behavior
* Expanded gamepad CCMD
* Rename enum JoyResponseCurve to EJoyCurve
* Initial menu implementation
* Fixed SDL controller setting saving
* SDL gamepads can now actually be disabled
* Fixed initial controller connect of some versions of SDL
* Spelling error
* Enable gamepad by default
* Fixed segfault on some versions of SDL
* Only block keydown
Attempts to balance periods of rough traffic by putting in an artificial delay, smoothing playback but further increasing input delay. This can be disabled with net_ticbalance.
By default allow only settings controllers to save the game. Use actual file names to help prevent possible save file overriding as savexx is unreliable online. Prevent quicksave behavior from working with the rotator. Force a unique netgame subfolder for multiplayer saves to remove the ability to override singleplayer saves. Send over the host's -loadgame argument to make loading easier (will not override the guest's -loadgame in case they need a special file name).
Readds the feature to allow players to ready up during stat screens and intermissions instead of autoskipping based on whoever closed it. Comes with a variety of ways to tweak this behavior such as percentage-based auto starting (with a timer), the ability to unready as needed, and who can control it. Players will still be able to skip through individual screen jobs within the runner while waiting to ready up.
- Use a Light theme to clearly differentiate GZDoom from VKDoom
- Moved the version label to not visually clash with the banner graphics
- Added unique graphics for the banner and the BOOTLOGO
- Changed the loading bar color to match GZDoom's logo
This adds new features (such as themes) alongside fixing numerous bugs. This should be kept up-to-date with upstream more often and changes to it should be PR'd back to its main repo.
Allows manually setting FOV for models instead of scaling from 90 degrees. Positive values are exact FOVs while negative FOVs are scalars from 90. SCALEWEAPONFOV does not work with exact values since it automatically scales based on FOV.
