CCR Dive planner - bulk selection of dive points to change set point

[Ryan Holden]

Hello,

One thing I like to do in SS, is edit an existing dive log, but in the dive planner and change the mode to CCR to see the difference a CCR would have made on that dive in terms of inert gas loading, compared to open circuit. My dives have hundreds of data points, and changing the set point on each dive planner point, one at a time, is very time consuming. Is there a way, or could there be a way programmed, to change the set point on multiple dive planner points all at once? 

Previously I was able to set the dive planner default set point option to my desired setpoint (in SS preferences, Tech Setup), and when switching to CCR mode in the planner, it would instantly adopt this set point when setting my diluent gas, but recently (I'm not sure since which version this changed) the setpoint is set to 0 by default, and I'd have to go through each point manually typing in 1.3 every time.

SS Version 6.0.5459 CICD Release

Windows 11

[Michael Keller]

Hi Ryan.

On Thu, 11 Dec 2025 at 13:49, Ryan Holden <ryan.ho...@gmail.com> wrote:

One thing I like to do in SS, is edit an existing dive log, but in the dive planner and change the mode to CCR to see the difference a CCR would have made on that dive in terms of inert gas loading, compared to open circuit. My dives have hundreds of data points, and changing the set point on each dive planner point, one at a time, is very time consuming. Is there a way, or could there be a way programmed, to change the set point on multiple dive planner points all at once? 

Previously I was able to set the dive planner default set point option to my desired setpoint (in SS preferences, Tech Setup), and when switching to CCR mode in the planner, it would instantly adopt this set point when setting my diluent gas, but recently (I'm not sure since which version this changed) the setpoint is set to 0 by default, and I'd have to go through each point manually typing in 1.3 every time.

That's definitely a bug. I must have broken this when I changed the default setpoint behaviour, and I definitely did not test my changes for your use case, only for the use when adding a new segment.

I'll look into it.

Ngā mihi

  Michael Keller

--

GCS$/CC/E/IT d- s+ a C++ UL+++/S++ P L++ E-
W++ N o? K? w O(++) M-- V+ PS+ PE+ Y? PGP+ t
5? X R tv b++ DI++ D++ G e+++ h---- r+++ y+++

[Michael Keller]

Hi Ryan.

A fix for this is now available in https://github.com/subsurface/subsurface/pull/4652 - can you please test with one of the artifacts linked in the pull request and provide feedback?

Ngā mihi

  Michael Keller

[Ryan Holden]

Hi Michael,

I've tested it and it appears to be working fine now. Thankyou very much! :D