I'm making a map where I use GetPixel() to check wich material I have at this position, but Mape seems to return false color indexes when you use the function.
I have a TEXMAP.txt loaded, where water has the index 25. However in Mape water has the index 17. That's a problem, because I constantly have to switch between 17 and 25 when I'm done with Mape and want to test it in the engine.
I don't know why Mape uses other indexes as the engine. 17 is not even defined in the TEXMAP. :o
I have a TEXMAP.txt loaded, where water has the index 25. However in Mape water has the index 17. That's a problem, because I constantly have to switch between 17 and 25 when I'm done with Mape and want to test it in the engine.
I don't know why Mape uses other indexes as the engine. 17 is not even defined in the TEXMAP. :o
Attachment: TEXMAP.TXT (485B)
Does Mape even load a TexMap? I would think it just generated TexMap entries on the fly.
I don't know, but when you double click and load a different Material.ocg with a different TEXMAP, the indixes change, too.
It uses
C4TextureMap::LoadMap
, so yes, it should properly load the texmap...
Looks like a bug in mape.
What happens is that mape first loads the TexMap.txt, however adding all the texmap entries internally fails, because the materials and textures are not yet loaded. However, mape must first load the TexMap to see if
Edit: Should be fixed in master.
What happens is that mape first loads the TexMap.txt, however adding all the texmap entries internally fails, because the materials and textures are not yet loaded. However, mape must first load the TexMap to see if
OverloadMaterials
or OverloadTextures
are present in it, to know what materials/textures to actually load. Probably a second pass going over TexMap.txt after materials and textures are loaded would fix the issue.Edit: Should be fixed in master.
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill