Developer postOriginal post (opens in a new tab)

1.6.3f hotfix

Greetings! More of a "lukewarm" fix here than a "hotfix", but as they say: better late than never.

8k resolution rendering is now actually functional (for better or worse). I made a very silly mistake that stopped resolutions larger than 4,096 from being allowed in the Y axis in the last patch! I still strongly recommend that nobody use >4k resolutions for producing content, it's just far too much overhead and liable to make Keysight crash on lower-spec systems, but I don't want to actually enforce such a restriction in code.

Also fixed: Channel colour mode breaking on time-offset Pulses and Particles. This one actually slipped through since version 1.6.0!

Finally, I added a debug console command to switch Keysight to output a BMP image sequence rather than an actual video when performing a render-to-video operation. Similar to 8k rendering, I strongly recommend ignoring this feature; it's intended for a single person who wanted completely uncompressed frame output! A single minute of 8k footage rendering to a BMP image sequence will create 354GB of files.

Happy Keysighting! <3

Full 1.6.3f changelog:

--- SMALL ADDITIONS ---

Added debug console commands:
render-jpg
render-bmp
"render-bmp" switches render-to-video to export intermediate frames in .bmp format rather than .jpg, and disables video exporting to just keep the frames around. "render-jpg" switches things back to normal

Added 8k resolution to dropdown selector for render-to-video resolution

--- CHANGES ---

Changed high-resolution warning on render-to-video to kick in if internal resolution is above 4k (rather than above 8k)

--- BUG FIXES ---

Fixed Y-axis custom resolution input not allowing >4096 for render-to-video operations (whoops!)

Fixed being able to click "cancel render" in a narrow window between rendering and exporting, causing all kinds of chaos

Fixed Channel colour mode not functioning properly on time-offset Pulses and Particles