BeerSmith™ Home Brewing Forum

BeerSmith Software => BeerSmith 2 Bugs/Support => Topic started by: vortex on September 01, 2012, 06:16:28 AM

Title: Milk Sugar Decreases Est Final Gravity
Post by: vortex on September 01, 2012, 06:16:28 AM
I am doing Jamil's Milk Stout Recipe Triple X and noticed that the Est Final Gravity was not coming up anywhere near what his was.  It came up as 1.010 and it should be near 1.022.

I noticed that when I removed the Milk Sugar (Lactose) that the Est Final Gravity went up to 1.012 and when I added it back in it went back down to 1.010. This seemed to be the case with the After Boil check box checked on the ingredient also.

Milk Sugar added at the end of the boil is not fermentable and should increase the gravity significantly when 2# is added to a 11 gallon batch.
Title: Re: Milk Sugar Decreases Est Final Gravity
Post by: Skippy on December 27, 2012, 11:14:58 AM
Beersmith does not calculate lactose additions accurately when using regular brewers yeast. 

However, some strains of wild yeast and bacteria will ferment lactose and the beer will finish a lot closer to what the software predicts with several months of fermentation.

A possible solution is to create a new ingredient category for lactose AND maltodextrin where you can independently specify SG and % yield for an ingredient.

Currently maltodextrin is in the misc category and adds nothing to the SG which is false.
Title: Re: Milk Sugar Decreases Est Final Gravity
Post by: m750 on January 14, 2013, 08:03:18 PM
Can we get a bug fix for both lactose, and maltodextrose?
Title: Re: Milk Sugar Decreases Est Final Gravity
Post by: 501_Adam on January 17, 2013, 09:55:36 PM
Bump.....
Title: Re: Milk Sugar Decreases Est Final Gravity
Post by: mm658 on January 18, 2013, 06:57:30 AM
This is a known bug that will supposedly be addressed in an upcoming release.
Title: Re: Milk Sugar Decreases Est Final Gravity
Post by: Greig on December 09, 2016, 02:02:38 PM
Sorry to raise the dead, but this still seems to be the case in Beersmith as of version 2.3.7. Any chance of a fix?