* Update hxvlc to 2.2.6
* Remove `arch -x86_64` as no longer needed
Since `cne-lime` got rebased with FunkinCrew's, which includes Apple Silicon (ARM64) support.
* Wtf
* Rename **Mac OS x64** to **Mac OS Universal** in the ReadME
Reason: **x64** is only powered by Intel/AMD, not ARM, so it will make the macOS users to think macOS builds still uses Intel.
* Enable videos for iOS
Since hxvlc 2.0.0 or newer, it fixed the video playback for iOS.
* Fixed the extension-androidtools import, when using extension-androidtools 2.2.X.
* Replace `start` with `wait` in `VideoCutscene.hx`
* Revert
* Nvm I think I found out why I guess
* Will this fix some actions deprecations?
* Oops
* F#CK
* I'm gonna lose it
* I forgot again
I'm going to scream into the pillow, If I keep forgetting to update those.
* Update macOS version to 26 in the macOS workflow
* Remove old hxvlc apis from the `VideoCutscene.hx` class, since hxvlc got updated to the latest
* Fix the f#cking conflicts
* Now it works
---------
Co-authored-by: Ralty <78720179+Raltyro@users.noreply.github.com>
To avoid having to do PR every time I update FM, I suggest simply using the latest and most stable version (currently 1.2.5), which fixes many bugs, including a crash that occurred every single time you exited a song.
* Improve documentation generation scripts
There is now a UNIX documentation generation script in the form of a
shell script. The Windows shell script has also been improved, and some
of the output of that script has been improved to match the UNIX one.
Because the scripts still use Lime to generate the documentation, the
shell script checks the kernel name using uname, and change the
documentation generation command ever so slightly. The reason for this
is that Lime only supports building to one platform at a time. This
makes manual intervention necessary, so the UNIX script checks for the
kernel ahead of time.
* Allow Linux-compatible kernels to work with UNIX doc generation script
Considering the variety of kernels available alongside ELF compatibility,
the UNIX documentation generation script has been modified to only check
for the Darwin kernel and assume every other kernel as Linux-compatible.
* Small consistency change in UNIX doc script when echoing pre-check message
* moving and small change
* cooler readme + docs generation guide
---------
Co-authored-by: ⍚~Nex <87421482+NexIsDumb@users.noreply.github.com>
Before anyone asks why vs cam, the code is public, plus i helped most of the audio backend rewrite in the mod too. :P
- Static sounds can now also seamlessly loop with AL_SOFT_loop_points extension
- Panning stereo sounds is now possible with AL_EXT_STEREO_ANGLES extension (although this was already implemented before)
- Improved streaming sounds, should fix most of the lagspike issues
- Streaming sounds should no longer regenrate if it's in the nearest timestamp (not for reversing though)
! You still can't access FlxSound.latency because of the new procedures that's not available in lime
If there's any crashes with this pls report an issue asap.
There was some critical bugs, such as:
- Hold notes were invisible just until a hold from player 2 (boyfriend) appears.
- Renderer skipping Independent strum/note/strumline cameras.
* Use sh alternatives and fix change directory in building shell scripts
The usage of the cd command in the shell scripts under building/ can
conflict at some point during the procedure. As far as I'm aware, it's
supposed to cd to the parent directory, but it does so strangely. On
some occasions, this may cause the directory to switch to /tmp
on Linux instead. This commit resolves that by instead using the
typical .. syntax, which is a shorthand for the parent directory of the
process.
Additionally, proper shebangs have been added that instead use
"/usr/bin/env sh", which returns the path to a suitable sh alternative:
that is, the closest program that can be found using 'sh' in the name.
This is one of the most recommended shebangs for a shell script, due
to 'env' typically being in the exact same position.
* Update cd in building shell scripts to use script relative path properly
The two prior versions would use the working directory's own parent
directory, not the script's. This commit simply makes it so that
changing the directory in the script uses its directory's parent instead.
* dont mind me
---------
Co-authored-by: ⍚~Nex <87421482+NexIsDumb@users.noreply.github.com>
