IntroductionHi, my name is Pankaj Kholiya, and I am a Senior 3D Character Artist. I've been working in the game industry for the past 8 years. I worked on titles like Call of Duty: Black Ops 6, That Christmas, Ghost of Tsushima Director's Cut, Star Wars: Outlaws, Alan Wake 2, Street Fighter 6, and many more. Currently, I'm working as a freelancer for the gaming and cinematics industry.Since my last interview, I made a few personal works, was a part of a Netflix movie, That Christmas, and worked with Platige on Star Wars: Outlaws and Call of Duty: Black Ops 6 cinematic.The Breakdancing Clothing ProjectIt all started when I witnessed a dance battle that a friend organized. It was like watching Step Up live. There, I got the inspiration to create a break dancer. I started by gathering different references from the internet. I found one particular image on Pinterest and decided to recreate it in 3D.At first, the idea was to create the outfit in one pose, but along the way, I also decided to create a dancing version of the character and explore Unreal Engine. Here is the ref I used for the dancing version:Getting StartedFor the upcoming talents, I'll try to describe my process in a few points. Even before starting Marvelous Designer, I made sure to have my base character ready for animation and simulation. This time, I decided to use the MetaHuman creator for the base due to its high-quality textures and materials. My primary focus was on the clothing, so using MetaHuman saved a lot of time.After I was satisfied with how my MetaHuman looked, I took it to Mixamo to get some animations. I was really impressed by how good the animations worked on the MetaHuman. Once I had the animations, I took the animation into Marvelous Designer and simulated the clothes.For the posed character, I adjusted the rig to match the pose like the reference and used the same method as in this tutorial to pose the character:ClothingFor this particular project, I didn't focus on the topology as it was just for a single render. I just packed the UVs in Marvelous Designer, exported the quad mesh from Marvelous Designer, subdivided it a few times, and started working on the detailing part in ZBrush.For the texture, I used the low-division mesh from the ZBrush file, as I already had the UVs on it. I then baked the normal and other maps on it and took it to Substance 3D Painter.AnimationThere are multiple ways to animate the metahuman character. For this project, I've used Mixamo. I imported my character into Mixamo, selected the animation I liked, and exported it. After that, I just imported it to Marvelous Designer and hit the simulation button. You can check my previous breakdown for the Mixamo pipeline.Once happy with the result, I exported the simulated cloth as an Alembic to Unreal Engine. Tutorial for importing clothes into Unreal Engine:Lighting & RenderingThe main target was to match the lighting closely to the reference. This was my first project in Unreal Engine, so I wanted to explore the lighting and see how far I could go with it. Being new to the Unreal Engine, I went through a lot of tutorials. Here are the lights I've used for the posed version:For the dancing version, I've created a stage like the ref from the Step Up movie: Some tips I found useful for the rendering are in the video below:ConclusionAt first, I had a clear direction for this project and was confident in my skills to tackle the art aspect of it. But things changed when I dived into Unreal Engine for my presentation. More than half the time on this project went into learning and getting used to Unreal Engine. I don't regret a single second I invested in Unreal, as it was a new experience. It took around 15 days to wrap this one up.The lesson I learned is that upgrading your knowledge and learning new things will help you grow as an artist in the long run. Approaching how you make an artwork has changed a lot ever since I started 3D, and adapting to the changing art environment is a good thing. Here are some recommendations if you are interested in learning Unreal Engine.Pankaj Kholiya, Senior 3D Character ArtistInterview conducted by Amber Rutherford

Macworld Super-weird bugs in Messages are nothing new, but this latest one is a real head-scratcher: If you try to send an audio message with the phrase “Dave and Buster’s,” it won’t work. Why would that specific phrasing cause a problem? A coding expert has cracked the case. I won’t say “and the reason will shock you,” but if you’re anything like me, you’ll find it interesting. First, let me explain what happens when the bug triggers. At first, the audio message (“I’m off to eat lunch at Dave and Buster’s,” as an example) appears to send normally. It shows up in the Messages thread to the recipient, along with a transcript of the content. No problem is flagged. It’s at the recipient’s end that we spot the issue. Initially the recipient sees the ellipsis icon, indicating that something is being typed or sent… but this carries on, and carries on, and eventually disappears. And at this point there is no indication that anything has been sent at all: no message, no message transcript, no message failed notification. In fact, if the recipient didn’t happen to have the app open, or had it open but was in a different conversation thread, they never would have known something was supposed to be on the way. This bug is new to me, and the first time I heard about it was when it was discussed on Monday in the blog run by Guilherme Rambo, a coding and engineering expert. Rambo, in turn, heard about the bug on the Search Engine podcast, which devoted its May 9 episode to the subject. Rambo reproduced the bug, guessed the problem must be at the recipient end, then plugged that device into his Mac and started looking at logs. And from that point it doesn’t appear to have taken long for him to work out what was going on: iOS’s transcription engine was recognizing the name of the U.S. restaurant chain, changing it to the correct corporate branding (“Dave & Buster’s,” with an all-important ampersand), and then passing that into the XHTML code used to send a transcript with the audio message. The problem isn’t being caused by the words Dave and Buster’s, but by the ampersand character between them, which has a special purpose in coding and prevents the code from being parsed correctly. The phrase “Dave and Buster’s” doesn’t cause a problem in the U.K. because iOS doesn’t add an ampersand (or even an apostrophe).David Price / Foundry As you can see in the image at the top of this story, a seemingly successfully sent audio iMessage ending with the phrase “Dave & Buster’s” appears as sent but never actually appears on the recipient’s phone. After a while, the audio message disappeared from the sender’s phone, and the recipient was completely unaware that the message had ever been sent. With that in mind, it’s a short leap to recognize that other brands could cause the same issue—they just haven’t been spotted doing so up to now. Rambo notes that “M&Ms” will do the same thing. For U.K. iPhone owners, in fact, “Dave and Buster’s” doesn’t trigger the bug because that chain is evidently not well enough known here and doesn’t get its ampersand added by autocorrect. To reproduce the issue, I had to ask a friend to send me a message about the supermarket chain M&S. Sure enough, this caused the hanging ellipsis followed by an unsent message. At the time of writing, it seems almost certain that any phrase iOS would recognize as containing an ampersand would cause an audio message to fail, and when I put it like that, it’s surprising the bug hasn’t been more widely reported. But here’s what happens when a U.K. user tries to send a message about the supermarket chain M&S, complete with ampersand.Karen Haslam / Foundry On the plus side, one would imagine it’s a bug that should be easy to patch in an iOS update. The transcription feature in Messages simply needs to be told to “escape” special characters so they don’t mess up the parsing process. And as Rambo notes, this isn’t a bug with any security vulnerabilities; indeed, it shows Apple’s BlastDoor mechanism working correctly. “Many bad parsers would probably accept the incorrectly-formatted XHTML,” he writes, “but that sort of leniency when parsing data formats is often what ends up causing security issues. By being pedantic about the formatting, BlastDoor is protecting the recipient from an exploit that would abuse that type of issue.”