The _sch is empty

Hi @Matthew Guthaus. May not be related, but I think what @Tim Edwards was asking, was to try two files with different basenames, BUT the same extension. In the clip, it looks like you're using different basenames AND different extensions. Does moving

sram_2_16_scn4m_subm_lay.sp

to

sram_2_16_scn4m_subm_lay.spice

give the same results?

@Mitch Bailey: I don't think that matters. I've sort of figured out what the problem is, and it's mostly due to the fact that the routine that prints the error message was originally supposed to run only when a file is being read (and so which file it is, is unambiguous). I repurposed the routine to be able to run in the middle of LVS, and it is not looking at the right variables to distinguish which file it's supposed to be reporting the error on. It should be simple to fix.