Forget to show some things in the video, you can access your gameinstance, gamestate, or even gamemode from anywhere in blueprints. There are useful nodes like "get gameinstance" that return the base gameinstance class. You can then cast that reference to the class of your created gameinstance to access it's variables and functions.
It would have been really useful to have had a video like this when I was first starting out with Unreal Engine. I think sharing this on the UE4 forums or reddit page might end up helping a lot of people new to the engine.
Great video! Wonderful explanation! I would enjoy a video explaining where one would look to find flow charts and documentation that helps one understand the framework.
This is an incredibly useful video. Most tutorials are very shallow and never even try to explain how an actual game works and where to store gameplay data. Insane that this only has 4k views
Great summary, Epic should link this summary under these 20+ docs of explanation for quick overwiew, ...if: - You'd add info about HUD class - You'd answer my question: so the best way to store user settings (options: key bindings, sound volume etc.) choosen by player would be in Game Instance? Since it persists ? And I'd make changes of these variables in Game Instance.
For settings, things like key bindings and resolution get saved inside an .ini file so you don't have to manually keep track of that. Things like sound settings are a bit different because they often end up being more unique (if you are using multiple sound classes) so you have to manually work with that information. Game instance exists for only the current session so while they will be saved when changing maps, when closing the game they are lost. So for that we would use save states that manually save files onto the users hard drive that we can load from. This is a more comprehensive answer for that : answers.unrealengine.com/questions/757917/proper-way-to-save-various-game-settings.html
Forget to show some things in the video, you can access your gameinstance, gamestate, or even gamemode from anywhere in blueprints. There are useful nodes like "get gameinstance" that return the base gameinstance class. You can then cast that reference to the class of your created gameinstance to access it's variables and functions.
"You don't have to care if you're not making a multiplayer game." I wish someone had told me this a week ago. This channel is invaluable.
It would have been really useful to have had a video like this when I was first starting out with Unreal Engine. I think sharing this on the UE4 forums or reddit page might end up helping a lot of people new to the engine.
The way the hierarchy is explained here is without a doubt one of the most important things you need to learn for UE4.
Thank you for this video! Have never seen anybody else talk about this. I wish this was the first video I saw when I started using Unreal Engine.
Same if I had started with his videos my game prototype would already be done haha
Amazing videos Casey. Hope will do some more in the future. Can't w8 to see them. I hope you are doing good. All the best.
Great video! Wonderful explanation! I would enjoy a video explaining where one would look to find flow charts and documentation that helps one understand the framework.
Thx for the info. I think this is very important because you should know where to put your code. Your videos are the best.
This video is nutz. Can help your organize the framework of your projects and start sketching the structure of the project. Props!
Amazing content! Very direct and useful!
Epic needs to hire you as their tutorial guy. Epic tutorials aren't this clear
This is an incredibly useful video. Most tutorials are very shallow and never even try to explain how an actual game works and where to store gameplay data. Insane that this only has 4k views
This should be on first page of unreal documentation with capitals
Great summary, Epic should link this summary under these 20+ docs of explanation for quick overwiew, ...if:
- You'd add info about HUD class
- You'd answer my question: so the best way to store user settings (options: key bindings, sound volume etc.) choosen by player would be in Game Instance? Since it persists ?
And I'd make changes of these variables in Game Instance.
For settings, things like key bindings and resolution get saved inside an .ini file so you don't have to manually keep track of that. Things like sound settings are a bit different because they often end up being more unique (if you are using multiple sound classes) so you have to manually work with that information.
Game instance exists for only the current session so while they will be saved when changing maps, when closing the game they are lost. So for that we would use save states that manually save files onto the users hard drive that we can load from. This is a more comprehensive answer for that : answers.unrealengine.com/questions/757917/proper-way-to-save-various-game-settings.html
This is what is actually needed. When you start is just a bunch of dogmas that you don't really grasp. I would have gone even more into the details
Useful video, thank you! However , the difference between Pawn and Character was not clear for me
Actually a very importnant topic, few talk about for some reason
This was really cool! Thank you!
It helped a lot, thank you.