I've been having some struggles with Google Groups as well. Not much we can do about it, we don't have any control over how it works.
What are you trying to achieve by converting to NGon here?
The convert to NGon functionality only works on surfaces that OpenVSP tessellates itself -- it 'knows' which quads were split into triangles. An imported STL file does not have this information, so it has no hope of working.
The 'Convert to NGon' button is really just meant as a debugging feature. I had planned on removing it before releasing 3.45, but I left it in just in case. There really is no user-centric use case for it.
If you want it to 'work' though, there is a workaround. Import the STL. Then run CompGeom. This will create a new MeshGeom that is essentially identical to the imported one -- but with some internal variables set (that currently are not set in the import). Then, you can run Convert to NGon on that MeshGeom. Of course, since OpenVSP doesn't know about the original structure, the converted NGon mesh will still be triangles.
Rob