Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags
(2 edits)

Subject:POSSIBLE BUG

     Does your plugin have a bias against importing materials that are not "Lightmapped Generic"? There seems to be a problem with the plugin that has costed me 71 days of my time and so it seems that I cannot find a fix for the problem without contacting you. Perhaps there is a known problem with the creation of materials that are of the type "cable" for example? 

     It seems that after trying around 5 different ways of importing materials and textures there is a strange issue that occurs such as lighting making my scene look like a child with a giant crayon was let loose and assumed the white lightmaps were a paper.  If you are in need of the engine version I was forced to downgrade from 4.17 to 4.12.5 in order to start the plugin which costed me a few days of work I had already done only for the plugin to not actually import the materials I had made in the more updated engine. 

     This is a peculiar problem and as of today on 11/22/2018 I have come to the realization that the plugin may not know what to do with something that is not "Lightmapped Generic" casuing it to not create a vmt for materials labeled "cable" for example. Regarding the lightmap issue I have simply restarted my work several time to try to get a fix but now there isn't a lightmap problem anymore because what the plugin has done is create static meshes for the level but not actually put them in the level though I had an idea about what this was caused by and nope the brushes are indeed grouped.

I have created this account for the very purpose of contacting NT Entertainment and therefore I am new to this website and/or its way of functioning.

(1 edit)

I have experimented to see if the bias is the case and it seems that after editing the vmt to say it is "LightmappedGeneric" it proceeds to import that material but none other. I want to know if you are aware of this bug involving that of discrimination from non "LightmappedGeneric" vmts.

EDIT: I have done this with all the vmts in the folder. Now the plugin creates a material for them. 

I have no idea what to tell you, except that I can't reproduce your problem at all.
I just ran a test with a cable materials directory (so just "SplineRope" and a "$basetexture" field), and those all imported fine without needing to change or edit anything in the VMTs, so I have no idea what was going on on your machine. Any unknown types should default to the LightmappedGeneric handler anyway...

Deleted 5 years ago
Deleted 5 years ago