Afrikaans
Akan
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranî)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Vietnamese
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
While you follow along with this course, you might run into trouble and some things don't seem to work
out, even if you pay close attention and try to follow along step by step, it can easily happen that
you missed a small thing that ends up breaking your game.
But sometimes there are also pre-existing issues with your PC or your Unreal Engine installation that
can lead to issues that are hard to debug as a game developer or programmer.
Debugging and figuring out these issues by yourself is an extremely important skill to have.
So if something goes wrong, I do believe it's best that you try to figure it out by yourself at first
before asking somebody for help right away.
You can rewatch the video to double check that you didn't miss anything, and also use print strings
or other debugging methods, which I'll talk about more in the Crash Course section to figure out what
the issues are.
However, if all of those things didn't work out and you tried your best, it's totally fine to ask
other developers for help and advice.
And the best place to do so for this course is the Cobra Code community discord, which already amassed
over 2000 developers.
You can find an invite link attached to this lecture.
I prepared a category specifically for this course, which has a little forum where you can ask questions
and also search for questions that others might have already answered.
So before asking something, please make sure to double check that nobody has already asked the same
thing.
It's also very important to ask your question in a proper way to get a good answer.
That way, many people ask is to not ask the question at all and to just ask for help in general.
Or if somebody knows about x, y, z.
However, that makes it really hard for others to help you and engage you since they don't really know
what you're looking for and need help with.
Don't ask to ask, just ask your question right away and in as much detail as possible.
Mention the problem in my new detail and also talk about the things you've already tried to fix it.
People are much more likely to help you if they can tell that you're genuinely putting in the effort
and not just looking for somebody to solve their issues.
It also helps to attach images and videos to bring your point across.
I will of course, try to personally answer as many questions as possible.
However, with how much I have going on with the YouTube channel and other courses, it might take a
while for me to answer.
If you have more general questions about Unreal Engine or Paper 2D that aren't directly related to the
course, you can ask them in the other channels as well.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.