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
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
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
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
Now that you've got an understanding of how to actually analyze your game data through the profiler,
and there is so much more that you can do with it, to be honest.
And it's worth having to read through the documentation regarding the profiler, which you can find
by clicking help and unity manual waiting for this to open.
Then it's working in unity analysis and profiler.
OK, here you get all the information regarding your profiler, etc. And you can go through any of these
talks about why you should profile your application, how to do it, how to connect a device to the
profiler, and all the different information you need for that, your common profile markers.
So what is the play a loop?
What is the ed loop?
As it says here?
It's all contained in the others inside of unity.
So it's all contained within this section here.
That's all Ed elements and and the profiler collect ed stats, etc. The script update markers.
What do all these things mean?
Waiting for target AFPs graphics, present frame process commands, wait for commands, etc. And most
of these are going to be visible when you move over to timeline.
You can see these.
OK, this is what these elements mean and click off there to get rid of that.
OK.
And back and script scripting markers.
So garbage collection multithreading markers.
So when it's idle or when job until it's complete, most of this is talking about like, for example,
the jobs and the loading.
And that can the things that whether it is idle or sometimes be marked as complete semaphore, wait
for signal.
So that's that one.
OK, that explains what's up in all of your physics markers and what they mean.
And then kind of performance warnings.
Then the profiler window, it'll actually go through what each of these elements mean and how to actually
read these and what each element is used for an hour to understand it.
OK, so for example, CPU usage, we've got all of these elements.
OK, so a good bit of reading for you to go through.
I've pretty much covered the basics, but there is so much more that you can do with it.
Now you've got an understanding of how it works.
It's worth doing.
Not been reading up on it in order to use in your own projects.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.