Oolite Bulletins

I thought display_name in shipdata was... I can't find the exact word, redundant, maybe. I thought displayName on a ship object was created from shipClassName + shipUniqueName (possibly via some rule in descriptions.plist). I honestly cannot remember if, how and when this happened, but display_name...

I am not sure it is a bug. OOShipRegistry.m in the source code contains the following inside the - (NSMutableDictionary *) mergeShip:(NSDictionary *)child withParent:(NSDictionary *)parent method: // Certain properties cannot be inherited. if ([child oo_stringForKey:@"display_name"] == nil...

Starting a new game works fine and the shipdata-overrides can be something as simple as Throw this shipdata-overrides.plist inside a Config folder in AddOns and that should do it.

display_name works for me on 1.91

Mixing tone mappers in the same scene is not a good idea, neither using thresholds. Thresholds in general tend to create artifacts, except in some rare cases and your proposal is no exception, unfortunately. Running your above code, the planet city lights with RGB value 0.0, 0.0, 3.9 look like this ...

And in what cases does something like this prove useful? When you are close to the sun? It is the one of the main ways used in cinema, photography and games to showcase very bright lights. As light source intensity increases, color tends to desaturate to white. This can be useful mainly for effects...

Thanks, now I get the point. Then the question arises: is it not possible to compensate for low saturation in SDR? Then sdr and hdr output images will be as close as possible to the original srgb image. Try this: Find the oolite-final.fragment shader inside oolite.app/Resources/Shaders and open it ...

OK, now you've made me go back and have a good look at it again. So here is what is happening with color saturation and HDR vs SDR in Oolite. I downloaded a screen test pattern image to use as basis for color accuracy tests. This will be our reference test image: https://i.postimg.cc/cL47GWDW/image....

https://siril.readthedocs.io/en/latest/_images/CIE1931-comparison.png . Then why do we need a wider color space? First, you can use textures originally made for DCI-P3. Secondly, certain visual effects can strongly distort colors (for example, a different spectrum of a Star, effects from shields, w...

There seem to be no references to this anywhere on our wiki. "Bloom"/"bloom" finds nothing. There doesn't need to be one. It's just a component of the new renderer and I'm just changing numbers in the oolite-texture fragment shader. Bloom is basically a depiction of strong light...

Having fun with the bloom shader. In this pic, bloom overdose.

Have you investigated the possibility of utilizing an abstraction layer from OpenGL to Metal? A very quick and dirty search reveals a project called MGL but I don't know how feasible it is to set it up for Oolite or, in general, use it. As for the fork proposal, I'd say that since the alternative is...

layer has been the first parameter in this method since its entry into the codebase in October 2014. It looks like the wiki had it wrong for a while.

Edit: Also, key is named property in the code.

Could someone please check whether Windows artifacts are ok as well? Confirmed, the correct PDFs are now packaged with the Windows installer too. In case it can be of help in the future, the Windows installer executables are accessible as LZMA archives by 7-zip. At least on Windows, I can open them...

Maybe after the PDFs are created the installer script that runs to do the final packaging overwrites them with the wrong ones by just doing a blind copy of the Doc folder? Seems like a logical explanation, maybe worth checking it out.