Recently, a coworker posed a question to me:
\n“How do you pass the player position to a material in UDK?”<\/p>\n
“Well, couldn’t you just use the CameraWorldPosition node? The player and the camera are so close together the effect should be enough, right?” replied I.<\/p>\n
“That could work, but I want to do a far-back third-person camera,” he countered.<\/p>\n
“Oh…” I said.<\/p>\n
After attempting a solution that was, admittedly, rather hacky involving trying to programmatically derive the location of the player based off a known distance between the camera and the player, I opted for something that could be considered hacky, but is as close to a programatic solution as an artist can get.<\/p>\n
<\/p>\n
Looking into the situation, I thought perhaps I could use Kismet to pass the position of the player to a Material Instance using the Set VectorParam node… only to find out that node was taken offline back in 2010. Of course, with the clever use of “Append Vector” nodes, three scalar parameters can quickly turn into a float3, right?<\/p>\n
<\/p>\n
Do excuse the garish colors. They were chosen to best showcase what’s happening. This could certainly be used to implement more subtle effects.<\/p>\n
<\/p>\n
So that’s what I did. Here’s the base material (click to enlarge)<\/p>\n
And the kismet setup. I put a delay after the operation is complete, otherwise Kismet throws a “too many operations” error. The delay is .033 seconds, or roughly 1 frame at 30 frames per second. The delay is barely perceptible, and it minimizes the number of calculations that have to happen.\u00a0(click to enlarge)<\/p>\n Combining all that, you get this (video forthcoming):<\/p>\n![\"\"](\"http:\/\/www.oztalay.com\/matt\/wp-content\/uploads\/playerPos_material.jpg\" "\\"playerPos_material\\"")
<\/a><\/p>\n<\/a><\/p>\n