Advertisement Jump to content
  • Advertisement


  • Content Count

  • Joined

  • Last visited

Community Reputation

3554 Excellent

About Daaark

  • Rank
  1. The crappy embedded chips we have now are complete shit compared to what we had in the 90s. They pick up interference from everything else in your rig, and they often chug on simple tasks. A significant cause of android's keyboard lag is the crappy chip trying to replay the typing sound over and over. Lots of lag with embedded chips comes from waiting for sound data to be moved around and play. When the chips can't keep up you get stuttering, popping, or dropped frames. My almost 30 old SoundBlaster 16 is laughing at this. I wouldn't blame MS for this. Eventually it just got cheaper for OEMs to use cheap embedded parts at low or no cost than to include more expexpensive parts from other vednors. It also lets them keep the power requirements lower. The same thing happens in the GPU space. We get embedded chips and 200W PSUs.
  2. I work at 1 unit = 1 meter. But this doesn't matter. Whatever works for you. A lot of tools standardize on 1u = 1m though. A skeleton joint for the most part just rotates. When you attach a finger mesh to a finger join, and then move that joint 90 degrees, it just means all the vertices attached to it move 90 degrees too. It doesn't matter how big the skeletons or characters are. Every vertex just takes on the rotation from the bone(s) it references.
  3. No, Zen 5 is a simple 2D top down game. I play(ed) it until the micro-transations got ridiculous. It's a tile map and sprites. But that's beyodn the point, because he was talking about the look and style, not the code-base, which I know is something this community has a very hard time grasping. I had no problem making a 2D top down RPG 6 months into my programming career, because I was focused on getting stuff done, instead of coding just to code, like a vast majority of people who hang around places like this do. Like that nice article that was posted today of someone who screwed around for 9 years and made no progress, making the same mistakes most people who posts in communities like these make. Everything in Zen 5 and similar titles (they are flooding the mobile market) is standard stuff that have tutorials adnauseam (I didn't have access to those when I started). There is a billion and one tile map and sprites tutorials on the internet, and if the Op spends a month or to learning Java, he can have a sprite walking around a tile map in a day or so. Then he has plenty of time to implement a Zen 5 style game. But with an attitude with yours, I'm sure it's more than impossible in ten years. It happens in every creative community. Those who want to create, create, and those who can't just hang around those that can and talk about it every day for years, producing nothing. But it's fun to throw those buzz words around!
  4. This is the epitome of why this forum blows. If you're not going to leave a thread better off than how you found it, why bother posting? Zenonia 5 is an simple android top down action RPG. It's 90% design and 10% programming. It's not some big, insurmountable goal. For android you'll want Java (read a book and learn it all first, if you jump ahead, you'll spend your entire year stuck on trivial things) + libGDX (don't touch until you complete a java book) will cover your programming needs. RPG Maker (now available on steam) is a much better choice, but they don't seem to have android support. The developer says they have been working on Android support, but that doesn't mean it's coming any time soon, or that it will even work well. Character design is not a technical thing. Get a pencil and a notepad and start creating. Figure out what your game is going to be about first, and then design characters that will take on the roles needed. When your design is finished, you'll know exactly what you need and an start working on them in a paint program. Keep your game small, simple, and focused. If you want to finish it in a year and a half starting from scratch you'll have to dial it back to something small, like 1 town and one randomly generated dungeon. If you can finish that, you can use it as a nice base to keep working on another game after that.
  5. Daaark

    My new game - Worthy or does it suck?, sell or rot

    Both the web page and the game are a complete eyesore of bad clip-art and clashing colors. You can't mix photographic and non photographic texturing, it just looks like a a mess. You have no set style in game. It just a bunch of random art styles mixed together. You can't have shaded stuff and non shaded stuff in the same scene. For instance your fully shaded pig on top of a full bright raft. The color of that raft cannot possibly exist in that scene, unless it happens to be emitting light. The title of the game, flashing inside the skybox is probably the poorest choice graphically. It should be on a screen aligned quad. The colors in the title clash heavily with everything else in the scene. Also, the skybox being so close is also a poor choice. It's being used in the absence of a fully finished 3D scene. You can't just have 10 feet of water and then a flat wall with completely out of scale (and non matching) trees. The main menu and the game HUD bleed into each other. The game doesn't even work. When I try to walk, I just roll around in the terrain. Arrow keys to move also scrolls the actual web page. The camera is crazy and goes all over the place. Don't be discouraged though. Keep refining it until you have something nice.
  6. That attitude in general won't get you very far. There is always a new language, skill, or technique to learn when developing something!
  7.   You know, I never even thought of doing that, despite having done something similar with satellite images back in architecture school (obligatory "don't go to architecture school" warning). Guess I learned something new. Always work from reference. Some people use images in the orhto views, and some people throw up textured planes into the 3D views. Here are some popular figure references: There are also topology guides you can follow so you have a good idea of how your edge flow should be set up for good deformation.
  8. Most models, especially characters are modeled on top of reference pictures that are dragged into the 2D viewport. It doesn't matter what size they are, because the proportions will never change. Just drag them in, and line them up so that the front and side views match up. Don't worry about the scale until you are done. When you are happy with the model, remove the reference images and scale your model to whatever height you want. If you're using 1 unit to a meter, then your model will end up 1.8 units tall. You can use the same skeleton for all your characters with some exceptions. You can re-target, or even copy and paste the skeleton from one model to another. As long as the characters have the same number of joints.
  9. BlenderCookie, Youtube, and Vimeo. The official Blender books are expensive, and the software changes very quickly. Blender typically does a big new release every 2 months, so those books are out of date almost as they come out. Any cheap books you might find will usually deal with it before the big 2.5 redesign and will be almost completely useless. I think video is much better for something like Blender. It's not enough just to know what does what. It really helps to see the workflow and how people actually use it. You learn a lot more by watching someone model stuff then just reading what each button does.
  10. It's native windows + D3D? Look for a function called SetCursor(false) and change it. Or WhateverD3DDeviceIsCalled->ShowCursor(false);
  11. I googled it, and it looks like someone's example framework. Most likely, the author just told the program not to show the cursor. Do a search in the source code for the word cursor, and look for the line where they set the cursor visibility to be false. In XNA GS the line would contain IsMouseVisible = false. Comment it out, or change it to = true;
  12. Get a good book that assumes you know nothing about programming, and follow along with all the C# programming exercises. Then learn how Unity3D works, and you can import models and script their behavior. 3D modeling only seems hard until you understand how it works. After that, it's purely about creativity, and how much time you want to put into it.
  13. Learn C#, grab Unity3D, and then follow along their 3D platformer demo project at : You will also need to learn how to create content. I suggest grabbing Blender and learning how to model, animate, and export to unity using the videos at
  • Advertisement

Important Information

By using, you agree to our community Guidelines, Terms of Use, and Privacy Policy. is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!