ST point errors

[USSRsniper 0]

Ok, foudn thread on the forum know what it is, but how do i fix it, so warnings don't appear again?

[DaSquade 0]

Wild step in the dark here, but afaik those errors are 'mapping' related errors. If you have properly unwrapped your model you shouldn't encounter the errors in a textured lod. Not sure but even if you encounter them they aren't the biggest problem to worry about ->EDIT: well depends, as if it is visible it can produce big problems.

You might encounter them (at least i do) in geo-fire and any other related non-textured lod, but since i think they are mapping related, this shouldn't be a thing to be consurent about.

Again, wild step in the dark, but this is what i had heard.

Not sure if you encounter them in your textured model res lods...if so how did you map your model?

EDIT: type (shouldN'T instead of should). Just encountered this error by the way as i accidently merged two edges in my UV map. Result is that it as streched mapped..If you don't fix it, this can have a big problem. Not only in color texture but especially in specular/normal map.

[USSRsniper 0]

Wild step in the dark here, but afaik those errors are 'mapping' related errors. If you have properly unwrapped your model you should encounter the errors in a textured lod. Not sure but even if you encounter them they aren't the biggest problem to worry about.

You might encounter them (at least i do) in geo-fire and any other related non-textured lod, but since i think they are mapping related, this shouldn't be a thing to be consurent about.

Again, wild step in the dark, but this is what i had heard.

Not sure if you encounter them in your textured model res lods...if so how did you map your model?

Ths, for some mroe detailed explanation. YEs, the warnings are only in geo lod, fire geo lod. Basically the onew that don't have textures on.

[Linker Split 0]

did you check if there aren't textures, or materials applied on them?

[DaSquade 0]

Texture and material free.

Somehow it isn't linked to mapping...meaning, even unmapped (freshly made) you can encounter these errors.

Imho, as long as you don't have them in your RES lods, nothing to care about.

Like above, IF you encounter them in a RES lod, depending on the location (visible or not, well in a good model it will be visible as hidden faces should been deleted anyway), fix them by remapping them.

-> Make sure you mapped them outside O2 or maybe copy/past the model in new file. Otherwise you will have an other 'section' witch i have been told not that good. A good model should actually never have more then 1 setion (weapon maybe two..model and muzzleflash etc). Less is better afaik .

[t_d 47]

afaik it means that the tangents cant be calculated. dunno when this is the case.

[armored_sheep 56]

afaik it means that the tangents cant be calculated. dunno when this is the case.

Correct. This warrning message warns the modeler that he might check surface for a normal map distorsion. Very offten it does not make sense, but the check is very simple and automatic.

More important are bad mapped surfaces with stretched pixels announced as "Singular mapping..." this might cause loading bad texture mippmap - GPU power loss. You can find those in Oxygen using menu structure/check faces - named selection with bad maping faces is made.

[sparky 0]

Well, mostly i get this error after the import of the model from max to O2. O2 tends to recalculate and reconstruct the faces, but not exactly as they were created in 1st place. I also get that warnings when i try to import a model (by objects) and after that I copy and paste them together.

this face is looking a bit suspicius to me...

Anyway the only way to prove my theory is that, people who use only O2 shouldn't have that problem, if they do then i'm probably wrong.

after a lot of tries, now the model has no warnings, although i haven't applied the textures yet, the UV map is presented.

BTW, and other annoying warning is about huge UVW points or something.

[armored_sheep 56]

Try to export triangulated meshes and disable automatic creation of squares (quads) during import. Quads are anyway drawn as two triangles on contemporary graphic accelerators.

[DaSquade 0]

Armored_Sheep, any advice regarding those ST errors on non textured faces, meaning like in geo-fire and other non texture lods.

Like i my post, you sometimes have it in fresh created (non mapped) stuff. Afaik it is nothing to care about, just wondering.

Thanks for your input by the way.

[Synide 0]

Armored_Sheep, any advice regarding those ST errors on non textured faces, meaning like in geo-fire and other non texture lods.

Like i my post, you sometimes have it in fresh created (non mapped) stuff. Afaik it is nothing to care about, just wondering.

Thanks for your input by the way.

i found the st errors went away when i re-UV'd the geo lod... even though it doesn't have a texture...

[MehMan 0]

I'm going to bump this:

Well, are these errors dangerous, as in, will they crash the game or cause serious preformance issues?

I'm afraid I'm getting quite a bit of these errors with my models and I don't know how to fix them, can anybody help?

Also, is there a way to fix them in 3ds max, or a way to detect them?

[DaSquade 0]

Not sure if there is an option in Max...

Not sure if it causes bad performence..

What i do know 99% of these errors is the result of bad unwrapping and normally should be noticable in your maps.

->colour maps maybe not that bad (if not noticable).

->shaders probebly more noticable and to be avoided imho.

Well once you know witch faces are bad mapped (ST errors) you should be able to fix them in your mapping (in max-modo or O2).

Good luck.