Baseplate underdetailing was Re: LDView Bug

[Jean-Philippe Ouellet]

(a) doing it will require to adjust nearly _all_ baseplates,
which will be tons of work, and we can need the energy currently IMHO
better in fighting down the PT backlog further

Not just baseplates. If we are going to start modeling these things at all, I believe we should model them everywhere, and (as far as I can tell) EVERY PART WITH A STUD would need to be remodeled. Because this requires too much scenario-specific attention to be able to be done programmatically, EVERY PART WITH A STUD would need to be edited by a human. Such an undertaking is absolutely insane.

See these parts:

everywhere there is a stud, there is one of those bottom things.

parsing time increase

Just as with stud groups, this is negligible.

in the future we should find an analogous way to turn on and off that feature
like we currently can toggle the stud representation (detailed, rough, primitive-substituted, none, as just a line, etc.)

Substituting studs themselves is easy because it's just one dat file that you can directly substitute. In this case, many (most) surfaces on which these stud-underside-bumps appear are just one giant poly for the underside of the piece, so an LDraw viewer would need to calculate (based on where studs are on the top of the brick) how to subdivide that polygon (and avoid creating T junctions while doing so) and then place the inset studs appropriately. This is a somewhat overwhelming undertaking for a very very small gain. If anyone really wants to do this, more power to them, but I certainly don't see why anyone would.