most matrix functions are converted over, no benefit to converting over the project/ortho because they would be scalar anyway but may need to move them regardless.
working for both neon32 and neon64
Update math_backend.cpp
further sse simd additions
avx2 float3 added
added normalize_magnitude
added divide fast to float3 may copy to float4
move static spheremesh to drawSphere (initialize on first use) so platform has a chance to load the math backend
all float3 and float4 functions and isas
completed all options of float3 and float4 functions in isas and math_c
neon still to be done but that will be on mac.
Update math_backend.cpp
mac isa neon update
added float3
restructured the classes to look more like the final version of the x86 classes
linux required changes
Update build-macos-clang.yml
Update build-macos-clang.yml
Revert "Update build-macos-clang.yml"
This reverts commit 29dfc567f4.
Revert "Update build-macos-clang.yml"
This reverts commit 2abad2b4ca.
Update CMakeLists.txt
fix macs stupid build
remove god awful rolling average from frame time tracker....
use intrinsic headers instead
each isa implementation now uses a header for that isa's intrinsic functions these are then used in the impl files. This will make it easier for matrix functions when those are implemented.
fixed comment saying 256 when it should be 512 for avx512
consolidated initializers for function tables
Update neon_intrinsics.h
fixes for some neon intrinsics no idea if this is the best way to do these but they work at least
v_cross is especially messy at the moment we basically just do it as a c math function need to look into getting this done correctly
and from Marauder, hardened filename entry for con::evaluate/compileexec. if the string forwarded along is not a real filename, consider it an eval block
for context Strings, use c_str(),
for triggers, use Con::getCurrentScriptModulePath() as otherwise, the "%this =" and "%obj=" injections will be treated as within the global scope. which is not allowed.
Ensured CodeBlock::smCurrentLineText is cleared at the end of execution
Tweaked and cleaned up the context lines passed along for further debugging data in the event of a script assert
Adds additional context on eval and evaluate calls to better isolate script executions that are throwing errors, such as via command fields or eval() calls.
added fix for font cache (stb required size to be read switch back to libpng knocks the stream off)
Added extra control over the rendering of guibtimaps
If guibitmaps are a child of buttons the profile colors now affect how to the button is rendered.
strings that are arguments for a function need to be put into the global string table. PrecompileIdent does this for the function name etc so it pulls from that during compiled eval
the conversion functions were making assumptions that were wrong based on mant being 0 and the out being 0 completely on small numbers also if the sign was flipped it rounded to 0. Also simplified
Fix for "|" in text for popupctrl
If 1 was found it was just assuming all other bars existed for a colour input.
there could be a cleaner way to do this but the direct approach allows for clear safeties.
while it still remains a good idea to port as many NULL compares and assignments over to nullPtr as feasable, we do still need to sort out how to better support scripted empty, false, and zero assigns for things like objectIDs.
this means we'll need to both fully convert the backend of the parser to support that kind of thing, but also alter most if not all exisiting NULLs. up to and including things like SAFE_DELETE. while that's certainly feasable, given there's aproximatel 400 nullptr assigns/checks prior to this commit, and roughly 1800 of the prior, if it terminates in a script call and not an aip one direct, we'll be dialing that back until such time as fork fully fopcused on converting and resolving any lingering mismatches is completed.
Turns out ConvexFeature::collide assumes the second round of testVertex calls will only add one entry to the collision list at a time and was erroneously only changing the last object and material reference.
by request,
adds a per object-instance onadd for datablocks if an object instance *also* defines a class.
be mindful not to mix up which namespace is in use there, as you can not tag two different core class instances the same scripted class
implements the same with the same restrictions for simobjects in general