PDA

View Full Version : IM.attachment.txt and im.txt - What do these do



ianwoodmore
July 1st, 2015, 12:21 AM
I'm running into some issues with a number of assets from various authors while testing them at TB 3.7. Over a hundred assets I believe have a similar situation.

Example

msgsapper kuid:439337:100856 Superliner I Coach Smoking 31545

a file named superliner_i_coach_body.im.attachment.txt shows with the following entry:

Name: a.limfront
Orientation: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000
Calculated or.: 0.00 -0.00 0.00
Position: 0.000000 -12.850000 0.890000


Name: a.limback
Orientation: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000
Calculated or.: 0.00 -0.00 0.00
Position: 0.000000 12.849999 0.890000


Name: a.bog0
Orientation: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000
Calculated or.: 0.00 -0.00 0.00
Position: 0.000000 -9.300000 0.550000


Name: a.bog1
Orientation: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000
Calculated or.: 0.00 -0.00 0.00
Position: 0.000000 9.300000 0.550000

These are the only attachment points in the associated mesh and it contains the orientation and position data anyway, so file appears redundant.

Is this a valid filename?
Is the information contained in this file used in someway by the mesh?

There is no script file, but this is an asset that has been modified via extensions container to be compatible with DAP's CMTMSystem3.

The problem I'm having is that AssetX and TANE CM see this as an invalid mesh when it is submitted because it contains .im.

Strangely TANE Preview Viewer displays the mesh without any problem.

WindWalkr
July 1st, 2015, 12:35 AM
a file named superliner_i_coach_body.im.attachment.txt

I suspect that this is the temporary output of some third-party tool, and should never have been included into the asset.



The problem I'm having is that AssetX and TANE CM see this as an invalid mesh when it is submitted because it contains .im.

Strangely TANE Preview Viewer displays the mesh without any problem.


It should be seen as a .txt file if that's the full name. As far as I'm aware, there's no validation rule against including random .txt files into the asset (although this isn't something that we encourage.)

chris

andi06
July 1st, 2015, 06:29 AM
AssetX does see this filename as a text file.

Perhaps there is an issue with the total length of the path+filename causing '.attachment.txt' to be dropped?

JCitron
July 1st, 2015, 09:13 AM
AssetX does see this filename as a text file.

Perhaps there is an issue with the total length of the path+filename causing '.attachment.txt' to be dropped?

This could be an issue if the user has used the default path for their data. C:\users\%loginname%\app data\local\N3V Games\TANE\.... etc., and this exceeds the maximum of 255 characters.

John

WindWalkr
July 1st, 2015, 09:35 AM
Perhaps there is an issue with the total length of the path+filename causing '.attachment.txt' to be dropped?

No, that's not likely.

chris

ianwoodmore
July 2nd, 2015, 02:42 PM
I've determined the cause of the im.txt error.
This is a creator's typo and should read lm.txt as for LM type meshes.
The creator seems to have given up on trying to get im.txt to work and the mesh-table points to the LOD0 .im mesh.

No further progress on im.attachment.txt other than these were received this way via download from DLS prior to any repairs I may attempt.

JCitron
July 2nd, 2015, 03:38 PM
I've determined the cause of the im.txt error.
This is a creator's typo and should read lm.txt as for LM type meshes.
The creator seems to have given up on trying to get im.txt to work and the mesh-table points to the LOD0 .im mesh.

No further progress on im.attachment.txt other than these were received this way via download from DLS prior to any repairs I may attempt.

I could see this as a typo if this was a one-off situation, however, I wonder if it is something else as I've come across this in a number of assets with this problem.

I was unable to repair the assets and deleted them, using the normal methods. Interestingly, the mesh.im is there but there is an error regarding missing LOD targets on some of these assets. Would repairing this, meaning rename this to Im.txt resolve this problem, or should I chuck the assets and wait for a replacement should that come along?

John