Problem Inputing Surfaces into Component Definition

I think a lot of people are familiar with the parametic truss tutorial by David Fano. Basically my definition is doing something similar to that. I am trying to apply a series of actions to all incoming surfaces, but the way the input surfaces were created is having an effect on the success of the definition and i don't understand why.

I am having trouble with my definition based on the input surface(s) i connect at the start. The situations i have created are below:

they are also labeled on the attached screenshot

A (successful) - i create a series of individual planes in rhino. i then bring them into grasshopper with a surface geometry component and connect it to my definition

B (successful) - i create a plane and then use the divide and subsrf components to subdivide the surface. i then input those subdivided surfaces into my definition.

C (unsuccessful) - i create a series of surfaces in rhino by spliting a single plane into a larger number of smaller pieces. i then input all the resulting surfaces into grasshopper with a surface geometry component.

D (successful) - i create a series of randomly placed planes. i then bring them into grasshopper with a surface geometry component and connect it to my definition


Basically I want to create a rectangle based mesh in rhino. The mesh is going to be quite dense and quite large with randomly sized rectangles. I then want to input all the individual rectangle surfaces into my definition which will put some sort of hexagon onto all of them. It is not feasible for me to create individual planes for all the mesh because the number will be way too high.

Thanks in advance for any help!