Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I don't believe you can do so directly but you could use the second <code>UV</code> channel to store your IDs. </p> <p>Here is a re-purposed <a href="http://docs.unity3d.com/Documentation/Manual/ShaderTut2.html" rel="nofollow">Unity normal shading example</a> using a "vertex ID" to determine when to apply the normal as a color. </p> <pre><code>Shader "Custom/ColorIdentity" { Properties { //_MainTex ("Base (RGB)", 2D) = "white" {} } SubShader { Pass { CGPROGRAM #pragma vertex vert #pragma fragment frag struct appdata { float4 vertex : SV_POSITION; float3 normal : NORMAL; float4 texCoord2 : TEXCOORD1; }; struct v2f { float4 pos : SV_POSITION; float3 color : COLOR0; }; v2f vert (appdata v) { v2f o; //here is where I read the vertex id, in texCoord2[0] //in this case I'm binning all values &gt; 1 to id 1, else id 0 //that way they can by multiplied against to the vertex normal //to turn color on and off. int vID = (v.texCoord2[0]&gt;1)?1:0; o.pos = mul (UNITY_MATRIX_MVP, v.vertex); o.color = v.normal * vID; //Use normal as color for vertices w/ ids&gt;1 return o; } half4 frag (v2f i) : COLOR { return half4 (i.color, 1); } ENDCG } } Fallback "Diffuse" } </code></pre> <p>Also, here is the dummy script I ginned up to assign completely arbitrary IDs. IDs are assigned based on a vertex's position on the y-axis. The bounds were chosen at random based on the mesh I had handy:</p> <pre><code>public class AssignIdentity : MonoBehaviour { public GameObject LiveObject; // Use this for initialization void Start () { Mesh mesh = LiveObject.GetComponent&lt;MeshFilter&gt;().mesh; Vector3[] vertices = mesh.vertices; Vector2[] uv2s = new Vector2[vertices.Length]; int i = 0; foreach(Vector3 v in vertices){ if(v.y&gt;9.0f || v.y &lt; 4.0){ uv2s[i++] = new Vector2(2,0); } else { uv2s[i++] = new Vector2(1,0); } } mesh.uv2 = uv2s; } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POVertex shader for only some vertices
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJerdak
    1. USJerdak
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 for the good advice. btw if he needs to transform each letter independently from the others, couldn't he simply create a Text Mesh for each letter?
      singulars
      1. PO
      1. USHeisenbug
    2. CO@Heisenbug Oh fine, go the easy route. :) But yes, you make an excellent point. The simplest solution would be making each letter its own text mesh.
      singulars
      1. PO
      1. USJerdak
    3. CO@Heisenbug I had thought of that, but wouldn't it break kerning? There must be a way to get at the polys underneath Text Mesh...
      singulars
      1. PO
      1. USBen Humphreys
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload