The errors right now are saying things don’t have a property called ‘…’ basically list every property which is in there…
When I fix that I get other errors including one nasty one which starts with an X followed by 4 more digits…
It doesn’t seem to matter what I do, I go through a list of about 6 different errors - I fix one - get to the next - and when I reach the end of the list, I arrive back at the first one… while I’m probably just unlucky, I can’t seem to break the cyclic redundancies of google…
Edit: the nasty error is X5204 Read of uninitialized components in r0, r1 and r2…I get that by changing from fixed point to float4 in the first 4 lines of Surf…
Obviously, this will only use the texture UVs from the inspector of the first Texture0 for all the other textures, but if they all use the same tiling/UV offsets it should be okay.
There were a few problems, the main reason I had my first problem was that I was not assigning a default texture to the textures… such as “White”…
EDIT:
Further more - case it helps someone else - you have to feed the UVs from the vertex shader to the fragment shader, else the fragment shader don’t know where its plotting the pixels…