There is a regular 32-bit live-stack FITs from Sharpcap 4.1. This stack itself, as it is, opens in Siril 1.4.3 normally (with Autostretch it looks ok). Then I open it in FitsWork4 and scale it there (66%, but the exact figure doesn’t matter). After its saving there as 32-bit floating point FIT it becomes “a white sheet” for Siril 1.4.3, without any possibility to breathe life into it. Meanwhile any other soft opens it without any problems… Help! Here is the file.
The reason is quite simple. Your FITS file is:
BITPIX = -32
Siril therefore expects images with values in the range [0, 1].
But
17:05:12: B&W layer: Mean: 80676919.0, Median: 80630857.7, Sigma: 8241040.7, Min: 7897973.5, Max: 2250794199.1, bgnoise: 261786.3
The data fall within the range [0, FLT_MAX]. However, it is impossible to know this without first reading the data. Nevertheless, we want to avoid this step for performance reasons when processing large volumes of data. It is therefore preferable to save the FITS files in a [0, 1] format.