OK, but that is not the track you sent me, which was Sonar0001.sl2. This one looks the same in 2.0.33 and 2.0.34:

Could you please check sonar0002.sl3 (second link in the email). Here are the screenshots of it in 2.0.34 and 2.0.33.

Is there any idea? Or is it better to use 2.0.33 for a while?

Yes, I know what is happening here. There was a change in 34 that means in some cases depth data is not being imported into the standard track view. Specifically, this happens where the primary channel has no depth data but another channel does (in your case downscan and sidescan). There was a reason for this change to address a different issue, but we should be able to revert to the previous behaviour in the next release.

Thank you, Matt. So will be waiting for 2.0.35 then.. )

Have same issue through zero depth on primary channel on some tracks. Looking forward to 2.0.35

Maybe it can be added to track properties - channel to use?

Looks reasonable.