Mark Raynsford

This appears to be a bug in the calculation of the inverse ray vector. The problem is that given a ray like the above: `(16, 32)` with direction `(1, 0)`,...

No, this is actually an expected property of the rays. See: https://tavianator.com/fast-branchless-raybounding-box-intersections/

This is actually caused by `NaN` values appearing in the computation. Covered here: https://tavianator.com/fast-branchless-raybounding-box-intersections-part-2-nans/

Waiting to hear from the author about whether or not anything can be done about this. I can't work it out from the second part of the article.

Ah, thank you! Sorry for the ridiculous delay in replying. I had no idea this had even been posted (I get far too many GitHub notifications for any human to...

I'll install the latest image later on today.

This set of options makes things a little less surprising: ```java final var module = new JacksonModule( INCLUDE_ONLY_JSONPROPERTY_ANNOTATED_METHODS, RESPECT_JSONPROPERTY_REQUIRED ); final var builder = new SchemaGeneratorConfigBuilder(SchemaVersion.DRAFT_2020_12); builder.with(module); builder.with(Option.DEFINITIONS_FOR_ALL_OBJECTS); builder.with(Option.FIELDS_DERIVED_FROM_ARGUMENTFREE_METHODS); builder.with(Option.FLATTENED_ENUMS);...

Thanks!

> As you already mentioned that does not happen so often... Think you may've misinterpreted that. I actually claimed that plugin updates occur more often than dependency updates. I can't...