Nez: free, open source 2D framework

Hershil_Patel 2017-06-12 00:18:18 UTC #121

Thanks for the heads up on SpriteBlinkEffect. I have been trying to use it, but I have been running into issues. For reference, I essentially have the Nez (Portable) and Nez.PipelineImporter projects imported as shown from the youtube tutorial. Anyway, I tried using the SpriteBlinkEffect, but it caused a runtime error:

DirectoryNotFoundException: Could not find a part of the path 'C:\MyProject\MyProject\bin\DesktopGL\AnyCPU\Debug\Content\nez\effects\SpriteBlinkEffect.mgfxo'.

I tried pasting the mgfxo file into the correct place (I got it from the Nez repo at Nez/DefaultContent), but then I got the following error:

'This MGFX effect is for an older release of MonoGame and needs to be rebuilt.'

So instead I tried to build the files myself, but here I am not exactly sure what to do. I copied the .fx files into my Content folder (from the Nez repo in DefaultContentSource). I imported the nez/effects folder into my MonoGame Pipeline tool, and built it. When building the .fx files, I used the "Effect Importer - MonoGame" Importer and "Effect - Monogame" Processor. It built successfully, but I looked in the bin\DesktopGL\AnyCPU\Debug\Content\nez\effects\ and it has .xnb files instead of .mtfxo files. When I try to run it, I get a file not found exception again (because it is looking for SpriteBlinkEffect.mtfxo instead of SpriteBlinkEffect.xnb)

What is the correct process to create the SpriteBlinkEffect.mtfxo file in the Monogame Pipeline tool? What is the difference between .fx, .fxb, .xnb, .mtfxo files. Which should I use, and which importer and processors in the MonoGame Pipeline tool should I use to create the correct files? Thanks in advanced.

prime31 2017-06-12 01:03:36 UTC #122

If you are using MG 3.6 you will need to rebuild all the effects. When you rebuild them they must be put in the exact location as in the repo with the same file name.

Hershil_Patel 2017-06-12 04:13:25 UTC #123

Which files should I be building? When I try to build the .fx files, the result is an .xnb. When I try to build mtfxo files, it does not work saying:"Bad token CppNet.Token". Are the mtfxo files the result of building other files, or the files I need to build?

EDIT: I have learned more about the issue, it seems that building an .fx file with the Monogame Pipeline tool results ina .xnb file, which is more information than a .mtfxo file. I am still unsure if it is possible to use the Monogame Pipeline tool to get a .mtfxo , but I am going to try using 2MGFX for now. http://www.monogame.net/documentation/2/?page=2MGFX

prime31 2017-06-12 04:59:38 UTC #124

2MGFX will do the trick. All the compiled effects included with Nez are compiled outside the Pipeline Tool using 2MGFX directly.

hotdiggitydoddo 2017-06-28 22:39:40 UTC #125

Does anyone know how to use Nez to create procedurally generated tile maps? Is this possible by leveraging the existing Nez.Tiled APIs?

prime31 2017-06-29 03:56:46 UTC #126

There is nothing stopping you from using the Tiled API to make procedural maps. There is an example in the Samples repo that does the opposite: destroys tiles procedurally. You can achieve procedural generation by doing it just like that sample except fill in tile data rather than remove it.