I started in machine code, after about 6 months I was given an assembler. It was like the moment at the end of The Omen 3. A great white light came on and exploded in my brain.
No more counting instructions to work out relative branches! No more memorizing opcodes!
Did some work in Forth, still love that language. Always end up talking like Yoda though, "Use the Forth you must"
Later C came out, I looked at it and laughed at the muppets that used it. At the time I was working on early PC's and the 8086 was very,very slow at stack operations. C is a stack based language, so anything written in C was slow as a dog.
As processors advanced, that changed and I started using C
I did some work in Occam, but I could only hold 8 levels of code in my head. Enough to write fast code, not enough for the big bucks.
I guy I worked with at Digital Integration could hold 32 levels of code in his head, he got dragged off to the states on loads of money.
Then I did some work on a super computer, that required I learnt Fortran.
Used Pascal ( barf ), Ada, Java, and a few other minor languages before C++ got big and I started using that.
My point is that it's not where you start that matters, if you have the talent you will end up doing something you probably have never heard of.
On a more practical level, C# is a good clean way to start. It's free, lot's of documentation to learn from etc. You can use Unity with it, IF you must.
The format is close enough to C++ for it not to look foreign to you.