I managed to obfuscate it afterwards using crypto obfuscator for .NET but this is a trial version. I found the .NET Reactor free version inadequate and a professional license is said to be expensive. Surely there is an open-source alternative or really inexpensive alternative. Could you write a tutorial on obfuscating MonoGame projects alongside deployment? I think other developers would find this invaluable and not everyone knows how easy it is to reverse engineer !

Thanks

Do you have plans to update your XNA 4.0 install script to handle Visual Studio 2015 or provide a new page so people have the option of either Visual Studio 2013 or 2015?

The install script you have for 2013 works great and it would be nice to have the same option for 2015. I have no idea the time commitment or feasibility of setting up Visual Studio 2015 for XNA though.

-Brett

But I have been unable to find an up to date walkthough/tutorial on how to get started.

I have a DX shader (.fx file) from the max install called "StandardFX.fx"
Its fine in its function HOWEVER for the Ambient Occlusion map slot it uses (unwrap) Map Channel 1.

I am not a coder

but in the code is there an easy way to identify where this Map Channel is defined as #1 and change it to Map Channel 2 ??? (i.e. a different UV unwrap layout for AO)

thanks
Ivon
I can copy the code here if needed…

So, for example, the code you use to explain classes is:

Random random = new Random();

and the code you use to explain the creation of classes is:

Player player = new Player(string name);

The repeated use of the same word throughout the code is what kept throwing me off. If I saw the word "Player," I wasn't certain if it was referring to the Player class, the player object, or the Player constructor method. It was even more confusing while attempting to keep track of what variable belonged to what scope. For example, "this.name = name" in the Player constructor method.

Once I began to color code the different pieces, it all became clear. If "Player" was orange, then I knew it was referring to the Class. If it was green, then I knew it was the name of the object. If name was orange, then I knew it's scope was the class, while if it was blue I knew it was limited to the method, etc…

The colors I picked were arbitrary, and no relation to the automatic coloring used in Visual Studio. It was about learning how to "see" the code without being distracted by the actual text of the code, if that makes any sense, lol…

So I'm curious what you would think about color coding your tutorials, or making colored versions of them. If the reader had a color key to refer to, then they could jump between tutorials and be able to tell, quickly, if they're looking at a Class, a method, a constructor method, etc. Or do you think this would just be too confusing for beginners?

Anyway, hope it gives you some ideas!

I (and certainly many others) wish to see the next Monogame Tutorial coming really soon. I am at the end at your tutorial and i "just" (it's really cool already) know how to display an animate sprite but i'm far away to know how to use it.

Will you make next Monogame tutorials as you did in XNA tutorials ?

Or should i forget about using Monogame and go with dead XNA ?

Thanks.

Let's say I am frequently using angle and power. Could I do something like

angle, power = FindTrajectory()

void FindTrajectory()
{
//ask user for angle and power
return a, p;
}

Is that possible somehow?

P.S these are the best tuts on the web

Keep up the good work :)

Maybe an article\tutorial on the following would be of benefit to others besides myself?

I have started to use Blender for my modeling and I am lost as to how the scaling used in Blender (or other modelling packages) relates to the final size of the model as would be used in-game.

In Blender we have the BU - the blender unit - as a means of measuring something. A BU can represent whatever distance the user wants it to be, so for example 1 BU could represent 1 meter for me, but for you it could represent 5 meters. If I scale my model down by 50% I get a model .5 of a 'meter', if you scale it down by 50%, you get a model 2.5 'meters' in size.

Suppose for my game I have a texture 25 x 25 pixels in size and I require a cube which in-game will be 25 x 25 x 25 pixels onto which I want to map this texture. How do I ensure that my scaling of the cube in blender relates exactly to 25 x 25 x 25 pixels in size so that I can accurately UV map the cube without ending up with a distorted texture which would result from a cube size other than 25 x 25 x 25?

Looking forward to your feedback.

Thanks for reading.

I have the 30,000-foot view on how to make platformer levels— take a tileset, create collission rectangles, sprite rectangles/vectors etc., and code every tile or tile segment by hand. There is probably a better way than hand-jamming though, seeing how I have a knack for doing things the hard way the first time around quite often. =P

I also wonder, how to unload tiles/enemies/collectables etc., that are too far outside the viewport to even matter/interact with, and then, likewise, load that content when it is close enough to the viewport origin ?

A tutorial regarding 2D level creation, loading that level content as it's needed, and changing the viewport coordinates to follow a character or update via mouse coordinates would be great!

Your tutorials are awesome. They are clear, concise, and in in digestible sizes; tutorials sometimes assume, but more often go on and on and I get distracted. So, !Thank You So Much! for hosting this website! You're the man!