We ran a bit of everything. Sometimes we get away from motion because the guys are false starting. However, we ran a bunch of stuff.
I agree we should've run it more. I am saying Bijan was a large part of the problem. For all his greatness he doesn't always understand when its time to quit trying to hit the homerun and take the yards that are there. I can see how Sark got lured away from him. Of Bijan's 12 carries 8 of them were for virtually no gain. 1 for 1 yard, 6 for no gain, and 1 for a 1 yard loss. He was trying to dance and bounce runs when it wasn't there to do. Take the 3 or 4 yards and move on. As a playcaller that is extremely frustrating.
Meanwhile TCU was plugging away the whole time. There was this misconception that TCU was running the same as we were, but they weren't. This is their yards gained each rush. -2, 5, 4, 6, 4, 2, 4, 2, 5, 2, 3, 5,-1,-1, 4, 6, 5, 12, 9, 2, 14, 5, 0, 1, 4, 6, 0, 11, 1, 7, and 4.
TCU was always getting positive yardage in the run game outside of three runs in the first half and 2 in the second.
My point to @lilMAC25 is that even if we had stuck with the running game in that particular game it doesn't mean we automatically win. Bijan wasn't seeing the field the way he usually does, and more carries may not have translated into more wins. It could've translated into more 3 and outs. It is all speculation. We ran it 33 times vs Bama and totaled 79 yards. Again, I agree that Sark should ride his two horses, just disagree that it would automatically mean a W, especially when your RB is struggling like he was.