art3mis Posted September 5, 2017 Share Posted September 5, 2017 (edited) I understand the need sometimes for back ticks to evaluate expressions but don't understand why parentheses are sometimes necessary ie $JOB/export/${HIPNAME}_$OS_mesh.fbx fails but $JOB/export/${HIPNAME}_${OS}_mesh.fbx succeeds. Why doesn't JOB as well need to be in parentheses? Seems inconsistent. Edited September 5, 2017 by art3mis Quote Link to comment Share on other sites More sharing options...
f1480187 Posted September 6, 2017 Share Posted September 6, 2017 Underscore is a valid character inside variable names (e.g: $HOUDINI_PATH), you need curly braces to enforce word boundaries. Or use non-valid characters as delimiters like "." as suggested default. Evaluate string with MMB to see if it is correct. 1 Quote Link to comment Share on other sites More sharing options...
art3mis Posted September 7, 2017 Author Share Posted September 7, 2017 Thanks. So the real issue is the use of underscores adjacent to variable names! Quote Link to comment Share on other sites More sharing options...
Guest tar Posted September 7, 2017 Share Posted September 7, 2017 You can create a linked field that displays the expression evaluated. Makes it easy to see valid delimters. Quote Link to comment Share on other sites More sharing options...
ikoon Posted September 8, 2017 Share Posted September 8, 2017 @marty please how did you link those channels? If I put relative reference `chs("file")` in the EXPANDED channel, it evaluates on MMB, but I see dotted outline. Do you have another trick please? Quote Link to comment Share on other sites More sharing options...
Guest tar Posted September 8, 2017 Share Posted September 8, 2017 @ikoon hip attached. Fields.hipnc Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.