MonoGame | open source implementation of the Microsoft XNA | Game Engine library

Was able to get rid of the compiler optimizing by adding an [unroll] before the loop which allowed the setting of the walls variable and subsequent parsing of the array in the vertex shader.

This is one of those classic problems with collision detection, where the collision occurs at some point along the object's path but the object moves far enough that the next tick doesn't fix the problem, leaving the object - your ball in this case - to fall forever outside of the viewport.

To solve this you need to not only change the vertical velocity but also have the ball reflect off the collision point. You're already bouncing the velocity vector, you just need to add position reflection. The simple way is to just take the amount of overshoot and subtract it from the limit, putting the ball back in bounds:

Looks like I've solved it myself - I simply needed to update Visual Studio to the latest version, which I was apparently not using. Once I did that, all programs worked again.

One option is to add it from the terminal with

I'm wanting to have a "news" tab in a game that would just pull and display tweets from a twitter account. Is this possible in monogame?

It is possible in .NET as long as you have an internet connection and use the correct API. Monogame being a game framework is just another dependency of your .NET application.

Should I use the Twitter API?

Yes, I would recommend using the Twitter REST API for the same. You can get the text data (in JSON) of the content you need.

The hard part would be to render the tweets in Monogame. You cannot render HTML or run javascript inside Monogame, so you will have to implement your own UI for "Twitter News Feed" from scratch for displaying the tweets.

My idea is that every time a sprite is initialized it is added to the list and when the draw function is called, every sprite in the list is rendered with a foreach loop.

The need for having common objects that need to be updated and drawn along with the Game object is very frequent. You can have multiple approaches for implementing it. Monogame even has it's own implementation of it using the abstract class GameComponents and I have mentioned it in the end.

The problem is if I change the properties of the sprite, like position or color, then I have to refresh the list, and that's not the best way.

I believe this problem is due to the fact that the objects in your list are value types and not reference types (equivalent to pointers in C#). In this case, you have the following approaches to try:

1. Instead of using the generic type List, use a LinkedList in System.Collections.Generic, and you should use it as follows:

I went through your logic and have prepared a sample code. Please read the following before you go through it.

1. In order to simulate real-life motion, you need to implement the physics accurately. Although your implemented velocity and position seems mostly correct, the gravity needs to be treated as acceleration, and therefore adding its value to the position (as done in your code) is incorrect. I assume that this is the reason why you aren't getting your expected result since the value of increment on the Y-component of position is far greater than it should be.

2. Instead of keeping PosX, PosY for the position, Velocity_X..(), Velocity_Y..() for velocity, I would advise you to use struct Vector2 as shown below in my code, which is included in the Monogame framework and has a lot more helping functions built-in. This will help in making your code shorter and cleaner.

3. I did not understand why you used the Cosine of the given angle in your implementation of Velocity for both its X and Y components. My code below is ignoring this.

You can see my code below. Here the bouncing object Box is of the type struct PhyObj with all the needed Physics of motion implemented within it.

Solved and posted the answer here:

https://community.monogame.net/t/install-parse-failed-manifest-malformed-only-on-some-devices

In short the answer is:

On older api versions (<25 and therefore you should ALWAYS do this to support them?) it seems Android requires that:

the fully qualified Namespace of the Activity Name property must be lowercase.

The T parameter is a convenience in which say, you may pass raw bytes instead of colors.

In short, just stick to Color[] for T[], the framework will handle all the details such as computing the stride/pitch and so on when using raw bytes.

In your case you could just do the following:

• use GetData to get colors from source tile
• use SetData to set a region rectangle the size of source tile in the target texture

To initalize it outside Draw, I suppose LoadContent could be a good place since GraphicsDevice should be not be null at this point.

And if somehow you have to do it in Draw, use a simple bool NeedsRefresh as a guard, check if it's true, if yes then generate your stuff and set it to false; the code block would run only once.