godot-fmod - Godot with FMOD integration

Age	Commit message (Collapse)	Author
2020-07-26	CI: Install master version of psf/black	Rémi Verschelde
	Until https://github.com/psf/black/pull/1328 makes it in a stable release, we have to use the latest from Git. Apply new style fixes done by latest black.
2020-05-18	GLSL: Change shader type specifier from [vertex] to #[vertex]	Rémi Verschelde
	The added `#` prevents clang-format from misinterpreting the meaning of this statement and thus messing up the formatting of the next lines up until the first `layout` statement. Similarly, a semicolon is now enforced on `versions` defines to prevent clang-format from messing up formatting and putting them all on a single line. Note: In its current state the code will ignore chained statements on a single line separated by a semicolon. Also removed some extraneous lines missed in previous style changes or added by mistake with said changes (e.g. after uniform definitions that clang-format messes up somewhat too, but we live with it).
2020-05-10	New lightmapper	Juan Linietsky
	-Added LocalVector (needed it) -Added stb_rect_pack (It's pretty cool, we could probably use it for other stuff too) -Fixes and changes all around the place -Added library for 128 bits fixed point (required for Delaunay3D)
2020-04-02	Replace more occurrences of NULL with nullptr	Rémi Verschelde

2020-03-30	SCons: Format buildsystem files with psf/black	Rémi Verschelde
	Configured for a max line length of 120 characters. psf/black is very opinionated and purposely doesn't leave much room for configuration. The output is mostly OK so that should be fine for us, but some things worth noting: - Manually wrapped strings will be reflowed, so by using a line length of 120 for the sake of preserving readability for our long command calls, it also means that some manually wrapped strings are back on the same line and should be manually merged again. - Code generators using string concatenation extensively look awful, since black puts each operand on a single line. We need to refactor these generators to use more pythonic string formatting, for which many options are available (`%`, `format` or f-strings). - CI checks and a pre-commit hook will be added to ensure that future buildsystem changes are well-formatted.
2020-03-27	Renaming of servers for coherency.	Juan Linietsky
	VisualServer -> RenderingServer PhysicsServer -> PhysicsServer3D Physics2DServer -> PhysicsServer2D NavigationServer -> NavigationServer3D Navigation2DServer -> NavigationServer2D Also renamed corresponding files.
2020-02-13	Remove obsolete GLES3 backend	Rémi Verschelde
	Due to the port to Vulkan and complete redesign of the rendering backend, the `drivers/gles3` code is no longer usable in this state and is not planned to be ported to the new architecture. The GLES2 backend is kept (while still disabled and non-working) as it will eventually be ported to serve as the low-end renderer for Godot 4.0. Some GLES3 features might be selectively ported to the updated GLES2 backend if there's a need for them, and extensions we can use for that. So long, OpenGL driver bugs!
2020-02-11	Better format generated shader headers	Rémi Verschelde

2020-02-11	Untested support for compute shaders	Juan Linietsky

2020-02-11	Custom material support seems complete.	Juan Linietsky

2020-02-11	A lot of progress with canvas rendering, still far from working.	Juan Linietsky

2018-11-20	Remove trailing whitespace	Rémi Verschelde
	With `sed -i $(rg -l '[[:blank:]]$' -g'!thirdparty') -e 's/[[:blank:]]$//g'` (+ manual revert of some thirdparty code under `platform/android`).
2018-10-27	Dont use equality operators with None singleton in python files	lupoDharkael

2018-09-28	-Lightmap and lightmap capture support for GLES2	Juan Linietsky
	-Added hint to not show some properties when running on low end gfx
2018-09-23	-Rewrote GLES2 lighting and shadows and optimized state changes, did many ↵	Juan Linietsky
	optimizations, added vertex lighting. -Did some fixes to GLES3 too
2018-07-27	Running builder (content generator) functions in subprocesses on Windows	Viktor Ferenczi
	- Refactored all builder (make_) functions into separate Python modules along to the build tree - Introduced utility function to wrap all invocations on Windows, but does not change it elsewhere - Introduced stub to use the builders module as a stand alone script and invoke a selected function There is a problem with file handles related to writing generated content (.gen.h and *.gen.cpp) on Windows, which randomly causes a SHARING VIOLATION error to the compiler resulting in flaky builds. Running all such content generators in a new subprocess instead of directly inside the build script works around the issue. Yes, I tried the multiprocessing module. It did not work due to conflict with SCons on cPickle. Suggested workaround did not fully work either. Using the run_in_subprocess wrapper on osx and x11 platforms as well for consistency. In case of running a cross-compilation on Windows they would still be used, but likely it will not happen in practice. What counts is that the build itself is running on which platform, not the target platform. Some generated files are written directly in an SConstruct or SCsub file, before the parallel build starts. They don't need to be written in a subprocess, apparently, so I left them as is.