5 replies to this topic

[victor-tor]

I have such issue. For example I`ve made a clone of top nude mesh. I exported it and imported it then without applying any changes. And here how it looks in game.
There are two CAS screens in one: normal matching to the left and my mesh matching to the right



My TSR is 2.0.19.0 ver.
Thanks previosly for help

Vic

[BlooMbLURR]

It is a bug in TSRW

[BlooMbLURR]

It is most likly because the normals get flipped when exporting a mesh out of TSRW.
I still can not believe they haven't fixed this, especially for all those who made normalmaps in the past.....

Wat suposed to bring in depth is normally dark, it is now light
Have a look at both meshes in the mirror, and switch between the 2.
The normalmap(musclestexture) is now displayed the oposite of wat it original was.
Atleast on my version of TSRW(2.015)

[victor-tor]

Really? Oh no. Maybe there is any way to tell to TSRW producers about this issue?

[BlooMbLURR]

They know, its reported a few times
The reason im not using TSRW for clothing(till its fixed)
You could use s3OC or CTU to clone a file although they aren't as easy to use as TSRW.

It is also possible to fix the import issues by leaving the mesh out and replace the meshes with s3PE(or Postal) later.
Both programs however requiere you to create the slider files yourself, another thing that does take time, but possible.

[mossman1318826226]

I have the same problem that victor-tor originally asked about. For whatever its worth, with version 2.0.17 I was unsuccessful when I attempted to double-reverse the normals flip, by importing the flawed reversed-normals part into TSRW and exporting it back into a sims3pack. That does not necessarily mean that a double-reverse solution is not possible, but it didn’t work when I tried it.

What I am writing about is that I have now updated to the new TSRW version 2.0.22.0 and the problem persists (although possibly that could be an artifact of my using a Milkshape mesh that I originally created from a top imported from TSRW version 2.0.17.

I have consulted the TSRW tickets page at

http://trac.thesimsr...&order=priority

(I hope the above URL hotlinks correctly.)

That page has future milestones for bug fixes and also lists items that are not intended to be fixed. I had hoped to determine whether this item is something the developers planned to fix (or were capable of fixing). But I don’t recognize an item that seems to match the muscle normals problem. Do you recognize which ticket number corresponds to this problem? If it is not listed, does that mean that the problem is not on the developers radar screen?

Finally, thanks for the wealth of helpful information you have provided in this forum. I am awed by your patience and dedication in helping people here.

Moss