The Roadway Estimator function is understandable as a 'standalone' feature; the Room Estimator function is not. Roadway designs are theoretically-based calcs, generally about finding spacing that can then be applied to real life curved & intersected roads & paths. Room designs are typically specific to a bunch of varied areas of a building, and apply therefore to specific areas of the final output.
A large proportion of my design projects involve layouts for every room in a building or tenancy, and many of these are very simple in nature, but still require care. For instance, a rectangular Staff Lunch Room may be fairly obviously needing 6-8 fixtures to get a uniform result in a 2x3 or 2x4 layout. With the optimised fixture, dividing the room width by 2 for fixture spacing and then halving at the walls is a small calculation, and doing a similar function for the room length is another small calculation.
As it stands, the way AGi32 functions to do this involves a great deal of manual work from the user that it should be able to handle all by itself. ElumTools takes all the tedious work from the user and provides an optimised layout (even with non-rectangular spaces). AGi32's process is much more clunky. Given that we don't know the dimension of each new room we're designing the process works a bit like this: