• 13
• 15
• 27
• 9
• 9
• ### Similar Content

• While looking out for that pesky Terrator, our little alien is doing a bit of relaxed mining down on the new gas planet "Lelantos" this weekend....

• I have a native iOS game (objective c, XCode build) which I am considering to port to other platforms.
Core gameplay is based on solely on geographical maps, and custom drawing over maps. It also has Core Data. This part is complete in development.
What is not done yet is: monetization, gamification (leaderboards, challenges) and multiplayer functionality.
As I think more about it, I am tempted to think if this is the right time to move to a cross platform tool such as Unity. But before dedicating time to port my 5 years side-project effort in Objective C, I really want to know if its worth it.
- Does Unity support such plugins / assets that will fulfill all my above requirements?
- Unity Personal seems to have only 20 concurrent users - is it too costly scaling if I decide for extending to web and android platforms?
- What is the general workflow involved in publishing to iOS, Android, PC, and web platforms while using Unity? I mean to ask about various points of signing stuff, paying fees and getting certified.
- How long will it really take to port my entire Objective C project into Unity? I am somewhat familiar with C# but I am finding it hard fidgeting with Unity IDE as lot of things are focused around FPS and 3D while my game is still 2d - not much action involved. I seem bit overwhelmed by the list of features I see there. All in all, I do not want to lose my momentum while still making sure its portable to everywhere.
- Any assets I could use (for free to try basis in debug) that are relevant for my game?
- Last but not the least, are there any costs that I need to be paying upfront to Unity, for using it (apart from their monthly subscription model)? I don't understand their costing for multiplayer in conjunction with their subscription fees - if someone could kindly elaborate.
• By GytisDev
Hello,
me and few friends are developing simple city building game with unity for a school project, think something like Banished but much simpler. I was tasked to create the path-finding for the game so I mostly followed this tutorial series up to episode 5. Then we created simple working system for cutting trees. The problem is that the path-finding is working like 90% of the time, then it get stuck randomly then there's clearly a way to the objective (tree). I tried looking for some pattern when it happens but can't find anything. So basically I need any tips for how I should approach this problem.
Use this image to visualize the problem.
• By aymen
please any know how can i' calculate the centroid from any number vertices

• Good day sir/maam. I am developing a game for my thesis and im done with multiplayer and plan to start the implementation of AI but i dont know how/where to start. Please give an advice. I am developing it in C# using UNITY.
Im am now collected all pieces that has possible moves but i am stuck on which best move to select. I hope you will help me. This is link explained the game https://en.wikipedia.org/wiki/Game_of_the_Generals

# Unity the hardest thing about game programming

This topic is 4486 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

## Recommended Posts

Ok, mainly all my game programming has been done with engines that have everything taken care of for you, so that all you have to do is basically create your art and sounds, use the engine's loader and tell it what to do with what's been loaded. However, it's my belief, as is with the rest of the community(I think), that one should have an understanding of the lower level stuff that goes into an engine to effectively use it. This is what I have set out to do, but I am hitting a major snag. I am currently learning DirectX and I go through all these tutorials, and I understand the concepts presented very well. I can go through the code and understand everything that's going on. But whenever I try to implement the techniques into my own projects, I really have trouble applying what I've learned. Now I may be wrong here, but I think it just looks more difficult than it actually is. This is because everything done in a tutorial is presented as engine code rather as game code and makes things seem more difficult that it actually is because you only have to write, for example, object loading code once then you can just use that code for any object.
int main() {
//init
engineObject.render();
//clean up
}


The above would be using an engine. Now if you were to do the same thing, except using your own code to load the file, it would look more like this:
int main() {
//init
struct engineObject {
//properties
//vertices
//other stuff
};
//A cubic ass ton of code to load and render the world.
//clean up
}


Now my question is this: Once I have a loader, a renderer, an animator etc. done I can go back to where I started and treat my code just like an engine, right? I mean, obviously even after all that is done there will still be a great deal of work, but it won't seem AS insurmountable. Is this a correct assumtion or am I missing something? Thanks for reading and I look forward to the replies. -AJ

##### Share on other sites
The tutorials you're reading don't necessarily have 'engine code' but more likely 'reusable code.' Since good engine code -is- reusable code, I can see where you get the two confused :)

Fact is, if you just want to go and, you know, test some cool new Direct3D thing out, or mess with DirectSound, or whatever, you don't necessarily need an existing engine for it. Just could very easily hack something up that'll allow you to do what you want to do.

However, what you'll realize very quickly is that you do the same stuff over and over again in order to test something, and you'll identify great 'reusable code' candidates. Those guys you'll put into such constructs as your 'Object.Load' and 'Object.Render' calls.

Having reusable code is very nice, and will save you much headache in the future ;) It does not maketh for an engine though. But it will provide a clear starting point for you.

So my answer to your question : Don't get too bogged down trying to write an extensive engine. You'll end up like me writing tons and tons and tons of code doing all kinds of magnificent behind-the-scenes crap and end up with .. a bouncy ball (although, it is a very magnificently bouncy ball nonetheless ;)). Instead, when going through tutorials write good, clean, solid -reusable- code that gets you to what you want to do. This has three major benefits:

(1) You'll get to muck around with the tutorials quickly and easily
(2) You'll start learning good coding practices very early on.
(3) You'll have a good start to really understand what it means to make an engine, and if you're clever about it, a nice start to your own engine.

Again, in your case: good, clean and reusable code should be your goal. Making an awesometastic game engine will come later =)

Graf

##### Share on other sites
Before you start an engine think about the data formats you want to use and if you can get content in these formats

Once you know what you really want, go on and collect information about the different parts you need to implement

Some canditates for code reuse are:
- virtual filesystems

Then think about how you want to connect all the part of your engine:
e.g.:
- game code to game dll
- engine code to engine dll
- network into a sperate thread for reading, writing and de-/compression of packets
- content management systems, that keep track of the resources you have loaded for a level in order to release them on level change
- consoles are a good addition to make debugging a little bit easier later on
- GUI <-> game interaction
- input control
- render management

A renderer is more than just a loop to send 3d data and texture ids to the GPU.
In order to get decent results you need to consider a more complex shader implementation that gets associated with your 3d objects.
These objects need to be culled at runtime and sorted by shader/texture.

Sound and particle effects play another important role, however with particle effects I would be careful, since overuse of particle can make the scenery unclear and probably require too much attention by the player

Call of Duty 2 is a good example in my opinion although I respect opposing opinions.

If you look for some reuseable code components, I have a little library here which is still in development and shall be for free for non commercial objects.

Just pm me if you are interested