Repository navigation
Releases
Version 2.1
This primarily adds WebP lossless image support. It also has a few code and documentation cleanups, fixes a bug where padding would be added twice to each line in the BMP bottom-to-top writer, and changes the code so it won't emit compiler warnings under stricter warning settings. (Specifically, it fixes unused variable warnings, and silences a warning about using a nonstandard extension.)
Version 2.0
This makes some major changes in how the code is organized:
- I now have source subdirectories.
include/contains public headers (organized how they install systemwide),lib/contains the library portions of the raytracer (those implementing functionality used by it), andsrc/includes the programs demonstrating it. - In accordance with that, I have moved some build logic into subdirectory meson.build files (in
include/andlib/). Note that I have not moved the build logic for the demonstration programs themselves, as that would cause the built executables to show up in$BUILDDIR/srcinstead of$BUILDDIR/and I don't want to have to type out$BUILDDIR/src/raytracerevery time I need to test it. - I now build most of this program as a library which is linked against the programs, which avoids building parts of the program multiple times.
- I have moved the vast majority of functionality so that it is in a namespace named
rt, to avoid name clashes with anything else. This change is why I have bumped a major version.
Version 1.3.6
This release optimizes the bitmap::write_as_bmp_btt() method so that each line of the image is buffered before write. In the gradient-test program, it made BMP images write about 5ms faster. It also makes the raytracer delete the file when exiting due to a Ctrl-C press instead of leaving an empty file.
Other changes:
- The quirks code is rewritten in C++, and now contains line printer functions
- If a command-line argument has already been converted, it will return the same result created before instead of having a duplicate copy (which wastes memory).
- The argument parser was refactored so that the case-insensitive "string ends with" code is implemented as a method.
- In the multithreaded renderer, the thread creation code was rewritten in a slightly cleaner way by requesting the vector create them in-place instead of having a creation call on our side.
Version 1.3.5
This makes improvements to line remaining counter functionality that should improve performance. The line counter is now lockless, and where supported, it can avoid rewriting the whole line for a counter update (which may improve performance on Windows).
This also contains the buildsystem fix mentioned in the previous release.
The raytracer-1.3.5-win-x64.exe file is a standalone build of the raytracer depending only on system libraries. It takes about 1.3x as long to run as the Linux version, though.
Version 1.3.4
Bugfix: I forgot to return in the success case in reconv_cli_arg() in quirks.c.
Now I should be able to build for Windows.
Errata: I had a slight error in meson.build. Correct the first instance of 'gradient-test.c++' to 'gradient-test' (fixing the executable name), and after the dependencies: deps clauses put install: true. I have attached a patch which will do this automatically.
(Update: The Windows build here works, but it performs significantly worse than the Linux build. I'm not sure if this is platform differences or compiler differences.)
Version 1.3.3
Switches back to the bottom-to-top BMP writer, because I think I have fixed the bug. If I don't think of any more problems, I will upload a Windows build of this program here when I get a chance.
Version 1.3.2
This adds minor cleanups to the build system. You should be able to set whether dependencies are built as static or shared/dynamic (i.e. DLLs on Windows) with a single option (default_library).
Version 1.3.1
This adds a few bugfixes for building on Windows with Microsoft Visual C++. It doesn't recognize the file.c++ extension, so I have to manually tell it that the files are C++ so it actually builds. This also adds subprojects to enable building optional features on Windows more easily.
Version 1.3
This implements multithreading, which provides a major performance boost! The way it works is by adding a second variant of camera::render() which takes a second argument specifying the number of threads to use. It then gives each thread a range of lines to work through, divided (mostly) evenly, except that the final thread gets a slightly larger chunk of the image. Multithreading causes a slight overhead in locking access to the remaining line count variable, so it will fall back to the single-threaded renderer when only 1 thread is requested.
By default, the program will use all threads available for high performance.
It also has a minor bugfix to make a camera::render() job wait for for a running job to complete if it is called twice on the same object while a render job is already running on that object. If you need to render multiple jobs at the same time, create separate camera objects for each one.
Version 1.2.2
The primary purpose of this update is to fix a use-after-free. When bitmap was returned from a function, it would have the pixel data deallocated, even though a dangling pointer was copied to a newly-allocated object returned.
Other things this release does:
- Implement preparations for multithreading, such as a command-line argument
- A bugfix for parsing a type given in the form
-tpng: I had an off-by-one error which would cause it to parse incorrectly. - Implement a fallback if variable-length arrays aren't available (which is a GCC/Clang extension in C++, optional standard in C11, and the Microsoft Visual C++ compiler notably omits VLA support for both languages). It uses alloca() which creates an array on the stack. This should help let it compile on Windows.
- Windows bugfix: implement a manifest to make the raytracer run in UTF-8 mode by default. This simplifies programming for me.
- Implement code to retrieve command-line arguments from GetCommandLineW() on Windows. This is used as a fallback if the program does not start in UTF-8 mode, so that non-ASCII filenames should still work.