For those who are wondering, this is the timeline I am going to be following for this series. If you have any suggestions please let me know! This is not set-in-stone (and I could totally be forgetting something). Monogame Tutorial Series Timeline 0. Introduction 1. Textures 2. Sprites (We're here) 3. User Input 4. Collisions 5. Camera(s) 6. Text 7. Audio 8. Rotations/transformations 9. Scene Management 10. Game Architecure (OOP) 11. Optimizations 12. Render Targets Some misc. concepts I might cover: - Effectively Debugging - How to ship your game - Sub-pixel precision
i dunno if im stupid or something but i cant seem to get past this part in the video, i keep getting issues with Microsoft.Xna.Framework, such as "cannot convert from 'System.Drawing.Rectangle' to 'Microsoft.Xna.Framework.Vector2'" when using sprite.Rect....so weird
ok so my ignorance is slightly less today, i had both Microsoft.Xna.Framework and System.Numerics libraries and Vector2 didnt know which to reference. fixed!
The video is nice, But you should not use deep inheritance, As it would make a whole tree of classes and the code will be just confusing, And you can do all of this in the first sprite class and use default parameters for the constructor for things you don't want in the sprite.
OOP is the more popular approach with Unity. Ecs is more performant and easier to wrap your head around. Less spaghetti code. Though ecs isn't perfect either. People use it for composition but composition isn't an outcome of ecs. It is a property of it. There are better and more performant ways to achieve composition. But I am still more on the ecs side than the OOP side. OOP is objectivly worse than ecs.
Here is the current timeline I'm going off of. If you have any suggestions please feel free to let me know! (The "Text" video will cover some UI/GUI aswell): Monogame Tutorial Series Timeline 0. Introduction 1. Textures 2. Sprites (We're here) 3. User Input 4. Collisions 5. Camera(s) 6. Text 7. Audio 8. Rotations/transformations 9. Scene Management 10. Game Architecure (OOP) 11. Optimizations 12. Render Targets Some misc. concepts I might cover: - Effectively Debugging - How to ship your game - Sub-pixel precision
my antivirus blocks my project for some reason EDIT: I fixed it by next to debug in visual studio it says Any Cpu, change it to 32 bit or 64 bit (depends on your cpu)
I don t know why but when I try to do the player = new Scaled(texture, Vector2.Zero); command it shows me that it cannot convert from a xna framework vector 2 to a systems numeric vector 2, so yeah but anyway thanks I started to learning monogame , and your videos are really helping me :)
For those who are wondering, this is the timeline I am going to be following for this series. If you have any suggestions please let me know! This is not set-in-stone (and I could totally be forgetting something).
Monogame Tutorial Series Timeline
0. Introduction
1. Textures
2. Sprites (We're here)
3. User Input
4. Collisions
5. Camera(s)
6. Text
7. Audio
8. Rotations/transformations
9. Scene Management
10. Game Architecure (OOP)
11. Optimizations
12. Render Targets
Some misc. concepts I might cover:
- Effectively Debugging
- How to ship your game
- Sub-pixel precision
Deep inheritance like this is definitely not the way to go. Really appreciate seeing the monogame stuff regardless, thanks for the vids.
Why?
Thanks for a superb tutorial. Looking forward to future tutorials
Always nice to see new Monogame tutorials, great job and am looking forward to future videos. Subbed.
yagt = yet another great/good tutorial keep it up man
you are crazy efficient with your explanations tysm
Loving the way you explain things. Keep up the awesome work
Thank you my lord. You teach so well.
thanks for this!
i dunno if im stupid or something but i cant seem to get past this part in the video, i keep getting issues with Microsoft.Xna.Framework, such as "cannot convert from 'System.Drawing.Rectangle' to 'Microsoft.Xna.Framework.Vector2'" when using sprite.Rect....so weird
ok so my ignorance is slightly less today, i had both Microsoft.Xna.Framework and System.Numerics libraries and Vector2 didnt know which to reference. fixed!
@@dennyTruffles keep going and good luck! ✨
The video is nice, But you should not use deep inheritance, As it would make a whole tree of classes and the code will be just confusing, And you can do all of this in the first sprite class and use default parameters for the constructor for things you don't want in the sprite.
OOP is the more popular approach with Unity. Ecs is more performant and easier to wrap your head around. Less spaghetti code. Though ecs isn't perfect either. People use it for composition but composition isn't an outcome of ecs. It is a property of it. There are better and more performant ways to achieve composition. But I am still more on the ecs side than the OOP side. OOP is objectivly worse than ecs.
what's next after tis episode? User Input? Ui and Gui? Side scrolling?
Here is the current timeline I'm going off of. If you have any suggestions please feel free to let me know! (The "Text" video will cover some UI/GUI aswell):
Monogame Tutorial Series Timeline
0. Introduction
1. Textures
2. Sprites (We're here)
3. User Input
4. Collisions
5. Camera(s)
6. Text
7. Audio
8. Rotations/transformations
9. Scene Management
10. Game Architecure (OOP)
11. Optimizations
12. Render Targets
Some misc. concepts I might cover:
- Effectively Debugging
- How to ship your game
- Sub-pixel precision
my antivirus blocks my project for some reason
EDIT: I fixed it by next to debug in visual studio it says Any Cpu, change it to 32 bit or 64 bit (depends on your cpu)
I don t know why but when I try to do the player = new Scaled(texture, Vector2.Zero); command it shows me that it cannot convert from a xna framework vector 2 to a systems numeric vector 2, so yeah but anyway thanks I started to learning monogame , and your videos are really helping me :)
Oh. Try removing "using System.Numerics" at the top and replace it with "using Microsoft.Xna.Framework"
@ thx :)
Whoosh over my head but ill get there
If you want some more help, I'd love to help you out in my discord server!