• Advertisement
Sign in to follow this  

Unity When should I learn a new language?

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

If you intended to correct an error in the post then please contact us.

Recommended Posts

I apologise if this post is rather vague or doesn't have an obvious point to it. Hopefully I can tl;dr it.

I've been learning/using C++ for about 1 1/2 years, and Python for 6 months. I'm finding myself a great fan of Python, due to its simplicity compared to C++'s general bloated-ish feeling.
Recently I've been working on an RPG type game in Python. It's another one of the projects I start for a month or so, then just abandon. I don't want to abandon it, and I've documented it and stuff to try and keep myself going. It's not that it doesn't interest me, just other ideas have crept up. Same with my programming language I was writing.

I now want to fiddle around with 3D stuff. My assumption is that Python would not be optimal for this, namely due to the speed issues. I could go back to C++, but the small amount I've fiddled with it recently, it feels horrible to write in, to put it bluntly.

I was considering using this opportunity to maybe pick up another language like C# (which I dabbled in a few years back). I don't think there would be a downside to it: it would help me have a wider understanding of programming, wouldn't hurt any uni/career chances (I am still a..high school? student. I don't know how UK maps to the US), and would allow me to still have lots of fun programming. However, I start to wonder if I'm following the same trend as my projects: pick them up, play around for a bit, and abandon without finishing them (or in this case, using the language for a long time). Or I could be swatting at hot air.

tl;dr Is there a downside to learning new languages quickly (i.e. <1 year apart)? As a minor point, how can I stop myself giving up on projects for 'that new idea'?

EDIT: For the record, I plan on only really developing for myself and maybe releasing games I make to friends. So Windows development is my primary concern.

Share this post


Link to post
Share on other sites
Advertisement

I now want to fiddle around with 3D stuff. My assumption is that Python would not be optimal for this, namely due to the speed issues. I could go back to C++, but the small amount I've fiddled with it recently, it feels horrible to write in, to put it bluntly.

Python is fine for 3D. Download the 3D Python engine called [url="http://www.panda3d.org/"]Panda3D.[/url]
Don't forget: You can write the slow parts of your code in C++, and make it into a library, and have Python use the libraries. Panda3D is made for Python, and I don't know for sure, but I would guess that the slow parts are written in C++ to go faster. Plus, all the truly truly slow stuff, like displaying graphics, are ran on the videocard in something even faster than C++.

Besides, don't underestimate the speed of today's CPUs. Just because Python is 'slow-[color="#FF0000"]er' than C++, doesn't mean Python is 'slow'.
Also, do not decide "this will be to slow" until you can actually prove to yourself that it's too slow (using a profiler). Otherwise, you'll probably end up wasting your time on the parts that are actually running quite fine, because you are making clumsy guesses at what 'might' be too slow. And even if something is 'slow', doesn't mean it's "too slow".

Don't make guesses, make games, gain experience, and then when the computer tells you it's too slow, you ask the computer "what part of it is too slow"? It will tell you, and then those parts are the parts you try to optimize.

Share this post


Link to post
Share on other sites
Python is used for scripting lots of 3D Apps.

It's used as a scripting language option in Unity (called Boo there). And it's used as the in-app scripting language for a lot of 3D modeling apps. You can write out python code in Blender and have it operate on your scene. Or you can script the Blender game engine.

Share this post


Link to post
Share on other sites
It is also worth remembering that, since you are just starting out with 3D, it is very very very unlikely that you will even notice the difference in the languages speed. Also, if you have only been programming for 1.5 years, you really shouldn't be worrying about speed - firstly, you probably won't need the speed at this stage in your programming career and second, getting stuff done is much more important right now than getting it to run fast.

Get it working first, then PROFILE and only then optimize.

That is, only when you have found that your code isn't fast enough and you have profiled it to find the hotspot should you try to make it faster. Usually the best performance increases are achieved by using a more efficient algorithm or data structure (no amount of super optimized assembly will make a O(2^n) algorithm fast!).
In Python, you can also try Psyco (which will speed up number-crunching code without any effort on your part). If it still isn't fast enough, you could compile the hotspots with Cython (which can compile _most_ Python code to C; if you add type annotations it can generate some very fast code - a friend of mine uses Cython for heavy number crunching code for brain-computer interfacing research, for example). If that still isn't enough, you can always rewrite the hotspot in C.

My point is, even if you do need more speed than Python can provide out of the box, theres a bunch of options available. And if they're still not enough, Python will happily interoperate with C/C++ so you can wrtie just the performance-critical code in C/C++. Even the highest performance commercial games use some kind of scripting language for most of the gameplay code.


Python is used for scripting lots of 3D Apps.

It's used as a scripting language option in Unity (called Boo there).


Boo and Python aren't the same language. Boo is very heavily influenced by Python and looks a lot like Python, but it is still a very different language with different constructs and semantics.
Besides that, the rest of your post is true - Python is used by a lot of 3D apps, including some commercial games.

Share this post


Link to post
Share on other sites

Is there a downside to learning new languages quickly (i.e. <1 year apart)?

As long as that's what you genuinely feel like doing, go for it. Being exposed to a whole bunch of different languages is an advantage, in my opinion. Eventually, you'll want to sink more deeply into one of the languages you've learned, but that should come naturally once you find a project you're sticking with for a longer time. Or you'll find that you keep coming back to the same one or two languages, even when it's on different projects, and then you go deeper in those.

Share this post


Link to post
Share on other sites

My assumption is that Python would not be optimal for this, namely due to the speed issues.


Don't assume. Test.


tl;dr Is there a downside to learning new languages quickly (i.e. <1 year apart)?
[/quote]

Absolutely. Spending your time learning new syntax/environments means you're not spending the time getting deep knowledge of a language, facing difficult problems, or working with significantly large codebases.

With some experience, those downsides aren't so significant. For a relative beginner, its... ill-advised. Like has been alluded to by others, if it's what takes you to keep interested in things, then go nuts. But you'd probably be better served spending 2-4 weeks per language experimenting with them and then picking one to learn in for 2+ years. After that it's pretty vital to branch out.


As a minor point, how can I stop myself giving up on projects for 'that new idea'?
[/quote]

It happens a lot, and I personally wouldn't advise doing that. It's hard to get the drive and motivation to work on stuff. And to a lesser degree, working on a single project as a beginner can lead to a little head-in-the-sand sort of effect where you don't get good experience working in just that one silo. The most healthy thing I've found is trying to be consistent while working on your current project. If your mind is focused on the task at hand, it is less likely to have 'that new idea' and drive the wanderlust.

Share this post


Link to post
Share on other sites
There's not really a downside to learning another language, unless you're crunched for time for achieving mastery with a specific language for a job or something. You're not going to screw the learning process up or pollute your mind by learning languages quickly. When I started my current job I had to learn about 4 languages simultaneously.

Share this post


Link to post
Share on other sites
Thanks for all the replies. I have technically been programming for about 5 years, but was messing around for most of that. Heck, I only stopped really messing around (albeit more serious messing later) a few months back. I can see Panda3D, but I still feel there might be an issue if I want to make a Minecraft clone. (My goal :rolleyes:).

I'm wanting to try out C# again (I messed for a couple of months when I was 13~), mostly since I am still not liking C++, even though I am comfortable writing it (the actual look of the code is important to me, for some reason).

I guess I shall take this as a sign I still haven't found a comfortable base language..which I thought I had found with Python.:P

I feel this post has rambled, but thank you everyone for the feedback and advice. :lol:

Share this post


Link to post
Share on other sites
One problem that exists with Python regarding performance is that due to its GIL (Global Interpreter Lock), even if you write a multi-threaded application, your threads will never really truly run in parallel, since only one thread can own the GIL at any one point in time. And don't think I'm trying to scare you away from using Python; I'm a huge Python fan myself.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By Alexander Nazarov
      Hello. I'm newby in Unity and just start learning basics of this engine. I want to create a game like StackJump (links are below). And now I wondering what features do I have to use to create such my game. Should I use Physics engine or I can move objects changing transform manually in Update().
      If I should use Physics can you in several words direct me how can I implement and what I have to use. Just general info, no need for detailed description of developing process.
       
      Game in PlayMarket
      Video of the game
    • By GytisDev
      Hello,
      without going into any details I am looking for any articles or blogs or advice about city building and RTS games in general. I tried to search for these on my own, but would like to see your input also. I want to make a very simple version of a game like Banished or Kingdoms and Castles,  where I would be able to place like two types of buildings, make farms and cut trees for resources while controlling a single worker. I have some problem understanding how these games works in the back-end: how various data can be stored about the map and objects, how grids works, implementing work system (like a little cube (human) walks to a tree and cuts it) and so on. I am also pretty confident in my programming capabilities for such a game. Sorry if I make any mistakes, English is not my native language.
      Thank you in advance.
    • By Ovicior
      Hey,
      So I'm currently working on a rogue-like top-down game that features melee combat. Getting basic weapon stats like power, weight, and range is not a problem. I am, however, having a problem with coming up with a flexible and dynamic system to allow me to quickly create unique effects for the weapons. I want to essentially create a sort of API that is called when appropriate and gives whatever information is necessary (For example, I could opt to use methods called OnPlayerHit() or IfPlayerBleeding() to implement behavior for each weapon). The issue is, I've never actually made a system as flexible as this.
      My current idea is to make a base abstract weapon class, and then have calls to all the methods when appropriate in there (OnPlayerHit() would be called whenever the player's health is subtracted from, for example). This would involve creating a sub-class for every weapon type and overriding each method to make sure the behavior works appropriately. This does not feel very efficient or clean at all. I was thinking of using interfaces to allow for the implementation of whatever "event" is needed (such as having an interface for OnPlayerAttack(), which would force the creation of a method that is called whenever the player attacks something).
       
      Here's a couple unique weapon ideas I have:
      Explosion sword: Create explosion in attack direction.
      Cold sword: Chance to freeze enemies when they are hit.
      Electric sword: On attack, electricity chains damage to nearby enemies.
       
      I'm basically trying to create a sort of API that'll allow me to easily inherit from a base weapon class and add additional behaviors somehow. One thing to know is that I'm on Unity, and swapping the weapon object's weapon component whenever the weapon changes is not at all a good idea. I need some way to contain all this varying data in one Unity component that can contain a Weapon field to hold all this data. Any ideas?
       
      I'm currently considering having a WeaponController class that can contain a Weapon class, which calls all the methods I use to create unique effects in the weapon (Such as OnPlayerAttack()) when appropriate.
    • By Vu Chi Thien
      Hi fellow game devs,
      First, I would like to apologize for the wall of text.
      As you may notice I have been digging in vehicle simulation for some times now through my clutch question posts. And thanks to the generous help of you guys, especially @CombatWombat I have finished my clutch model (Really CombatWombat you deserve much more than a post upvote, I would buy you a drink if I could ha ha). 
      Now the final piece in my vehicle physic model is the differential. For now I have an open-differential model working quite well by just outputting torque 50-50 to left and right wheel. Now I would like to implement a Limited Slip Differential. I have very limited knowledge about LSD, and what I know about LSD is through readings on racer.nl documentation, watching Youtube videos, and playing around with games like Assetto Corsa and Project Cars. So this is what I understand so far:
      - The LSD acts like an open-diff when there is no torque from engine applied to the input shaft of the diff. However, in clutch-type LSD there is still an amount of binding between the left and right wheel due to preload spring.
      - When there is torque to the input shaft (on power and off power in 2 ways LSD), in ramp LSD, the ramp will push the clutch patch together, creating binding force. The amount of binding force depends on the amount of clutch patch and ramp angle, so the diff will not completely locked up and there is still difference in wheel speed between left and right wheel, but when the locking force is enough the diff will lock.
      - There also something I'm not sure is the amount of torque ratio based on road resistance torque (rolling resistance I guess)., but since I cannot extract rolling resistance from the tire model I'm using (Unity wheelCollider), I think I would not use this approach. Instead I'm going to use the speed difference in left and right wheel, similar to torsen diff. Below is my rough model with the clutch type LSD:
      speedDiff = leftWheelSpeed - rightWheelSpeed; //torque to differential input shaft. //first treat the diff as an open diff with equal torque to both wheels inputTorque = gearBoxTorque * 0.5f; //then modify torque to each wheel based on wheel speed difference //the difference in torque depends on speed difference, throttleInput (on/off power) //amount of locking force wanted at different amount of speed difference, //and preload force //torque to left wheel leftWheelTorque = inputTorque - (speedDiff * preLoadForce + lockingForce * throttleInput); //torque to right wheel rightWheelTorque = inputTorque + (speedDiff * preLoadForce + lockingForce * throttleInput); I'm putting throttle input in because from what I've read the amount of locking also depends on the amount of throttle input (harder throttle -> higher  torque input -> stronger locking). The model is nowhere near good, so please jump in and correct me.
      Also I have a few questions:
      - In torsen/geared LSD, is it correct that the diff actually never lock but only split torque based on bias ratio, which also based on speed difference between wheels? And does the bias only happen when the speed difference reaches the ratio (say 2:1 or 3:1) and below that it will act like an open diff, which basically like an open diff with an if statement to switch state?
      - Is it correct that the amount of locking force in clutch LSD depends on amount of input torque? If so, what is the threshold of the input torque to "activate" the diff (start splitting torque)? How can I get the amount of torque bias ratio (in wheelTorque = inputTorque * biasRatio) based on the speed difference or rolling resistance at wheel?
      - Is the speed at the input shaft of the diff always equals to the average speed of 2 wheels ie (left + right) / 2?
      Please help me out with this. I haven't found any topic about this yet on gamedev, and this is my final piece of the puzzle. Thank you guys very very much.
  • Advertisement