Krazer

I see where the center offset ".5*(ratio-1.0)" is used in the calculation of the final pixel location in both Find_Scale_Space_Extrema and Do_Subpixel_Refinement. However I was more questioning why is it...

Thanks for the reply. I was just checking to make sure there wasn't some mathematical/reliability/quality of result reason for the choices that were made. Performance will be a little arbitrary...

Maybe you can setup a group and add a few people to it so items can get merged as needed (however I currently only see 1 outstanding). I wouldn't mind...

try to put ```` #ifndef _XCR_XFEATURE_ENABLED_MASK #define _XCR_XFEATURE_ENABLED_MASK 0 #endif ```` at the top of hastyNoise.cpp

Yeah that just means there are more errors then the first ones. I never tried to compile it in mingw. Although you would assume gcc to be the same everywhere...

checked in some fixes to https://github.com/caseymcc/HastyNoise/tree/mingw, I need to verify everything still works on the rest of the platforms before I merge it.

are you compiling for 32bit?

Without the code it will not generate on 5+ as VS2017 (which is VS15 not 17) is no longer supported. You should be able to remove the cmake build directory...

I think I need to set the build directory based on the target os, https://github.com/caseymcc/UE4CMake/blob/76db68259430c2ecdd0763402a467fd15091c760/Source/CMakeTarget.Build.cs#L268C57-L268C73 I think what is happening is the cross compile is trying to use the build...

On quick glance the above looks correct, however calling it from a plugin may be an invalid assumption (I haven't actually tested it, just assumed it would work). It may...