Dashed volta lines come back as continuous after the score is saved.

Confirmed, with 3.6.0 and a 3.6.2 pre-release. And a 3.6 regression, works in 3.5.2

It does seem to get stored in the score though:

          <Spanner type="Volta">
            <Volta>
              <endHookType>1</endHookType>
              <beginText>1.</beginText>
              <lineStyle>2</lineStyle>                <<<<<<<<<<<<<<<<<<<
              <endings>1</endings>
              </Volta>
            <next>
              <location>
                <measures>1</measures>
                </location>
              </next>
            </Spanner>
 

3.5.2 does still show it (after having ignored the version warning)

I've checked various other lines, seems only voltas are affected

It's partially a regression. Yes, it survives save/reload in 3.5.2 - but only once. A second save/reload loses it. In its sense it is very similar to #316096: Glissando Reverts between closing and reopening file.

Chances are there are other properties that have long had this bug of losing their custom settings after two save/reload cycles, and now this will happen after only one. I'm investigating to see if I can find others.

https://github.com/musescore/MuseScore/pull/7453

Also fixes similar issues with line width, and line width on pedal lines, and the mmrest number offset, and tuplet font settings. All stem from the same cause, failure to manage the property flags correctly, so these settings were never marked UNSTYLED.
This makes them susceptible to being lost on save/reload but also on any other style changes.

There are a couple of relevant workarounds. In cases where you actually want to make a change to all voltas, you can hit the set as style button ("S" icon) - then the setting is remembered properly. But I guess you probably don't want all voltas dotted, just this special one. So instead, consider making not using a volta anyhow, but instead, a system line. You can add hooks as desired to make it look as much like a volta as you like, and since it won't play back either way, it shouldn't matter.

Came up also in https://musescore.org/en/node/317546, and, despite the title, also #317529: Multimeasure rests number position is not saved with SAVE function

Right, when I made the fix for this, I went through and did a pass through other elements to see if I could find other cases of the same thing going wrong. Actually for mmrest number position it was worse, never even written, but even if it had been, the same bug would have occurred on save/reload without the additional fix.

See https://github.com/musescore/MuseScore/pull/7597, which got mergd.

Automatically closed -- issue fixed for 2 weeks with no activity.