Hallo Robert, Am 18.06.2017 um 22:01 schrieb Robert Helling: > Hi, > >> On 18. Jun 2017, at 21:31, Stefan Fuchs <sfu...@gmx.de >> <mailto:sfu...@gmx.de>> wrote: >> >> Just back from my family holiday... >> I can reproduce this issue under Windows 10 with a build based on >> latest master. >> It behaves exactly as Willem is saying: After Subsurface start the >> Subsurface generated VPM-B ceiling in the profile for any logged dive >> is crap. After you once start the planner the result looks different >> and better but still not 100% sure if it is correct. >> I somehow have the feeling that the VPM-B calculation is not feed >> with correct (init) values unless you once start the planner. > > didn’t have time to investigate this. But it could be that my recent > cleaning up the planner patches did the harm. Could you check that by > undoing those? >
I did a quick test build: When using master and reverting commits https://github.com/Subsurface-divelog/subsurface/commit/b1ccd2fc43a309631ead61465e50d63f76844571 https://github.com/Subsurface-divelog/subsurface/commit/57ee5a5477c92ff4dd7b8975b1866c988556d14e https://github.com/Subsurface-divelog/subsurface/commit/7b18be2a50e3c94fa1e9ae30c92bbb3eee3593d6 I have the same result as with 4.6.4 release. So the issue seems to come from these changes. Best regards Stefan -- Stefan Fuchs E-Mail: sfu...@gmx.de <mailto:sfu...@gmx.de>
_______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
