VPI: walking a scope for unpacked arrays with vpiRegArray/vpiNetArray/vpiMemory can miss SystemVerilog int/longint arrays; also iterate vpiVariables
When you list unpacked arrays per scope with vpi_iterate(vpiRegArray / vpiNetArray / vpiMemory), at least one commercial simulator does not return SystemVerilog arrays of int / longint (2-state integer element types). Calling vpi_iterate(vpiVariables, scope) on the same scope does return them.
What they look like: - The parent has vpiType vpiRegArray. sv_vpi_user.h #defines vpiArrayVar as vpiRegArray, so this is the IEEE 1800 vpiArrayVar. - The elements are vpiIntVar / vpiLongIntVar.
Pattern that works: - Per scope, iterate vpiRegArray, vpiNetArray and vpiMemory, then vpiVariables. - From vpiVariables, keep only objects whose vpiType is vpiRegArray / vpiNetArray / vpiMemory. Scalars and vectors come back from it too. - Dedupe by vpiFullName across the iterators. - Count how many arrays came only from vpiVariables, so you can see whether it matters for your design. - Cross-check the walk against a static declaration list (from an elaborator or parser). Then a miss shows up as a count mismatch instead of a silent gap.
Once found, the elements resolve with vpi_handle_by_index and take per-element cbValueChange like any other memory word.