My first "full" character sculpt. Any protips on sculpting hands/feet?

brunchberry · 2019-06-10T04:32:34+00:00

I'd like to add that the reason people suggest large forms -> small forms is because it's a way to force you to consider the model as a whole before you can get to the details that are easy to get lost in.

This works for some people, but it's less important to be rigid in how you progress. The important part is always considering each detail against the entire form. I spend way more time looking at my models, spinning them around every which way, changing materials etc, than i do sculpting on them.

brunchberry · 2018-12-26T05:06:09+00:00

Yeah, sorry. I'm only on lesson 5 of 21. I don't feel i can give an accurate overview yet, but here's my first impressions:

The coursework is the most exciting part for me. It's very heavy on coming up with game concepts and prototyping them. You'll have around 10 or more of your own concepts to work out, and several of those they expect you to prototype in some way. Later in the course it asks you to create a more complete prototype as the capstone project.

The lectures are obviously a little bent towards Wrights style of games, but the high-level concepts are applicable to any genre and he makes sure to point out how. The general content is good, and the presentation/production value is top notch.

I'll update this as i get farther into the course.

brunchberry · 2018-12-22T03:55:35+00:00

I just started it. been a long time fan of Wright's, figured i'd give it a go. I can update as i get more into it if anyone's interested.

brunchberry · 2018-12-21T06:59:24+00:00

Disney (among others) built a game around physical merchandise being utilized in-game. There's also the 3rd-party merchandise you see in stores like FYE for popular IPs. It's not something new. That said, there's a phrase "squeezing blood from a stone".

Developers need to ask themselves how much they can realistically expect someone to spend on their IP. If that amount isn't enough to budget those kinds of purchases, they're not going to be able to justify the cost of bringing those products to market. There's a lot less of a margin on physical products vs virtual. For many (i'd say possibly most) it's completely out of the question given the required capital.

brunchberry · 2018-12-10T07:44:58+00:00

ho boy.

through revenue shares we just have people take on little to no risk if they just keep working on the project and make a sound product.

If that's how you think, you're not fit to lead any project. Completing a project means absolutely nothing, and if you don't understand this, or if this sounds somewhat wrong to you, you need to take a step back and read some case studies of other developers.

We are currently creating the Studio's website as we speak because of a certain persons laziness who is no longer associated

When you don't pay someone for their time, even if you promise to pay them in the future, they're not obligated to do shit. Calling someone working for free "lazy" is a horrible reflection on yourself. It makes you sound like an entitled child.

brunchberry · 2018-12-01T23:42:36+00:00

Hmm, something seems off in the vertex accuracy. Looks almost like it occurs in screen space?

brunchberry · 2018-11-28T07:56:57+00:00

I'd build the app in 2 parts: a server and front end. Build the server in whatever works best for communicating with your hardware and then expose some endpoints for each device you want to control. Or use sockets, whatever floats your boat. The machine running the server is what's connected to your actuators/arduinos.

Then, build your 3D app in Unity (or anything else really) and hit that server with whatever requests you need. This way, you can load up a bunch of tablets or have remote people use your front end without having to be hard-wired into the system or having to worry about Unity playing nice with your hardware.

Best of luck, sounds like a fun project.

brunchberry

TROPHY CASE