Etusivu Tutki Apua
Kirjaudu sisään
archive
/
spine-runtimes
peilaus alkaen https://github.com/EsotericSoftware/spine-runtimes.git
2
0
Fork 0
Tiedostot Ongelmat 0 Wiki

spine animation runtime libraries for various languages

#animation #library #gamedev #c #cpp #c++ #csharp #java #lua #flutter #libgdx #ts #xna

Puu: c505061d91
Haarat Tagit
spine-runtimes
ZIP TAR.GZ
Konstantin Tolis c505061d91 [ts][pixi-v7] Fix incorrect pixiObject scale in updatePixiObject 9 kuukautta sitten
.github 227addaee2 [godot] Add web templates with thread support, see #2684 10 kuukautta sitten
examples 417d7c2239 [ts][pixi-v8] Cleanup examples and updated runtime.sh script. 10 kuukautta sitten
formatters 12f11cbbf9 Add spine-android to formatter 1 vuosi sitten
spine-android 220678f336 [android] Next snapshot 10 kuukautta sitten
spine-c e327e9beb5 [c] Port of commit 9d49999: Changed SequenceTimeline to match AttachmentTimeline behavior. 10 kuukautta sitten
spine-cocos2dx 7461b08f36 [cocos2dx] Fix name clash with SkeletonRenderer, closes #2643 11 kuukautta sitten
spine-cpp 5e80111b87 [glfw] Add spine-cpp-lite example. 9 kuukautta sitten
spine-csharp 303cd85308 [csharp] Port of commit 9d49999: Changed SequenceTimeline to match AttachmentTimeline behavior. See #2687. 10 kuukautta sitten
spine-flutter 8d12efd9ef [flutter] Release 4.2.33 9 kuukautta sitten
spine-glfw 5e80111b87 [glfw] Add spine-cpp-lite example. 9 kuukautta sitten
spine-godot b610bd7b7a [godot] Fixes #2670, animation tracks must be set to discrete, so we only get a single name/loop change for each key. 10 kuukautta sitten
spine-haxe 7a028bf6dc [haxe] Port of commit 9d49999: Changed SequenceTimeline to match AttachmentTimeline behavior. 10 kuukautta sitten
spine-ios b2061f1cf9 [ios] Using `UnsafeBufferPointer` to skip data copying and boost performance. (#2686) 9 kuukautta sitten
spine-libgdx 9d49999e2b [libgdx] Changed SequenceTimeline to match AttachmentTimeline behavior. 10 kuukautta sitten
spine-monogame 6553038eb4 [monogame] Port of earlier clipping cleanup commit 485de74: SkeletonClipping.ClipTriangles clean up. 1 vuosi sitten
spine-sdl 9d14027ebb [sdl] Call spSkeleton_update() for physics. 10 kuukautta sitten
spine-sfml 83ac01e76c [c] Port: Scale physics constraint limits with skeleton scale. See #2576 1 vuosi sitten
spine-ts c505061d91 [ts][pixi-v7] Fix incorrect pixiObject scale in updatePixiObject 9 kuukautta sitten
spine-ue c85000b5f8 [ue] Add ResetPhysicsConstraints() to SpineSkeletonComponent and SpineWidget, closes #2615 1 vuosi sitten
spine-unity 02deca1cba [unity] Minor: whitespace formatting fix of last commit. 10 kuukautta sitten
spine-xna 86cd8668ca [xna] Removed spine-xna in favor of spine-monogame. 3 vuotta sitten
.git-blame-ignore-revs c858b1a9f3 Fix .git-blame-ignore-revs 2 vuotta sitten
.gitattributes a7dc2b1d8f gitattributes: set .cginc and .shader files to lf line endings to prevent Unity code auto-updater to create mixed line endings. 6 vuotta sitten
.gitignore 6cc8809406 [ts][pixi] Move pixi to pixi-v7 10 kuukautta sitten
CHANGELOG.md 5bd3f3aeb9 [unity] Added zwrite variant of URP Skeleton-OutlineOnly shader. Closes #2676. 10 kuukautta sitten
LICENSE 3ae685fff5 License header update in LICENSE file in top directory. 2 vuotta sitten
Package.swift 0d5c3e3b18 Spine iOS (#2504) 1 vuosi sitten
README.md 849e9acc7e Updated READMEs. 6 vuotta sitten
Spine.podspec 4f7fe00427 ADD: spine-ios support Cocoapods :Static Framework (#2658) 10 kuukautta sitten
SpineConfig.cmake.in 373a163c3f Add CMake Target Exporting & option to disable testing in the build (#2329) 2 vuotta sitten
SpineCppLite.podspec da8131e0e1 [ios] Fix version in podspec files, update example/export/runtimes.sh 1 vuosi sitten
SpineShadersStructs.podspec da8131e0e1 [ios] Fix version in podspec files, update example/export/runtimes.sh 1 vuosi sitten
flags.cmake 75a23e8167 [cpp] Refactor CMake build 1 vuosi sitten

README.md

Spine Runtimes

This GitHub project hosts the Spine Runtimes which are needed to use Spine 2D skeletal animation data with various game toolkits.

Licensing

You are welcome to evaluate the Spine Runtimes and the examples we provide in this repository free of charge.

You can integrate the Spine Runtimes into your software free of charge, but users of your software must have their own Spine license. Please make your users aware of this requirement! This option is often chosen by those making development tools, such as an SDK, game toolkit, or software library.

In order to distribute your software containing the Spine Runtimes to others that don't have a Spine license, you need a Spine license at the time of integration. Then you can distribute your software containing the Spine Runtimes however you like, provided others don't modify it or use it to create new software. If others want to do that, they'll need their own Spine license.

For the official legal terms governing the Spine Runtimes, please read the Spine Runtimes License Agreement and Section 2 of the Spine Editor License Agreement.

Documentation

See the Spine Runtimes Guide for detailed information about using the Spine Runtimes. The Spine documentation page provides further information about tools and data formats. For runtime specific documentation, refer to the README.md file in each runtime directory.

Bugs, enhancements, and tasks

Review our backlog of bugs, enhancements, and tasks in the spine-runtimes and spine-editor issue trackers. Our roadmap provides a more convenient view of the same issue tracker information.

Versioning

The default branch on GitHub is stable and works with data exported from the latest, non-beta version of the Spine editor. New development is done in an X.X-beta branch, which may be a work in progress. Important changes to the runtimes can be reviewed in the CHANGELOG.md file. Occasionally the Spine Runtimes are tagged with the specific Spine editor version they work with.

It is highly suggested to freeze the Spine editor version to match the Spine Runtimes source being used and to update them in lock step. See the Spine Runtimes Guide for more information.

Contributing

In order to merge your contributions, we need a signed contributor license agreement (CLA) from you. You can send a copy of the CLA to [email protected].

When possible, it is best to base your contributions on the current beta branch (X.X-beta). Please be sure to follow the style and formatting you find in the respective runtime code to which you are contributing.