.mtr Problem

[Springheel]

I committed two .mtr files to CVS a few days ago. All I did was paste a new entry at the end, but when I look at them now they look like this:

 

textures/darkmod/mansion/floor/manfloor01{    qer_editorimage  textures/darkmod/mansion/floor/manfloor01.tga    diffusemap      textures/darkmod/mansion/floor/manfloor01.tga        specularmap      textures/darkmod/mansion/floor/manfloor01_s.tga    bumpmap          textures/darkmod/mansion/floor/manfloor01_local.tga}textures/darkmod/mansion/floor/manfloor02{    qer_editorimage  textures/darkmod/mansion/floor/manfloor02.tga    diffusemap      textures/darkmod/mansion/floor/manfloor02.tga        specularmap      textures/darkmod/mansion/floor/manfloor02_s.tga}textures/darkmod/mansion/floor/manfloor02cen1{    qer_editorimage  textures/darkmod/mansion/floor/manfloor02cen1.tga    diffusemap      textures/darkmod/mansion/floor/manfloor02cen1.tga        specularmap      textures/darkmod/mansion/floor/manfloor02cen1_s.tga}textures/darkmod/mansion/floor/manfloor02cen2{    qer_editorimage  textures/darkmod/mansion/floor/manfloor02cen2.tga    diffusemap      textures/darkmod/mansion/floor/manfloor02cen2.tga        specularmap      textures/darkmod/mansion/floor/manfloor02cen2_s.tga}textures/darkmod/mansion/floor/manfloor03{    qer_editorimage  textures/darkmod/mansion/floor/manfloor03.tga    diffusemap      textures/darkmod/mansion/floor/manfloor03.tga        specularmap      textures/darkmod/mansion/floor/manfloor03_s.tga}textures/darkmod/mansion/floor/manfloor04{    qer_editorimage  textures/darkmod/mansion/floor/manfloor04.tga    diffusemap      textures/darkmod/mansion/floor/manfloor04.tga        specularmap      textures/darkmod/mansion/floor/manfloor04_s.tga}textures/darkmod/mansion/floor/manfloor05{    qer_editorimage  textures/darkmod/mansion/floor/manfloor05.tga    diffusemap      textures/darkmod/mansion/floor/manfloor05.tga        specularmap      textures/darkmod/mansion/floor/manfloor05_s.tga    bumpmap          textures/darkmod/mansion/floor/manfloor05_local.tga}

 

It's as if all the hard-returns disappeared. I suspect that's what is causing Demi-god's problem. I'll go through and fix it, but can anyone tell me why it might have happened in the first place? I was using notepad, if it matters.

[oDDity]

It doens't matter anyway. As long as the shaders are still separated by curly braces and the words by spaces, new lines don't make any difference.

[Springheel]

textures/darkmod/mansion/floor/manfloor02_s.tga}textures/darkmod/mansion/floor/manfloor02cen1{ 

 

So it will know that the above isn't one long path?

[Fingernail]

Yes, due to the } at the end.

[Springheel]

Ok, then...if that's the case I have no idea why Demi-god's textures don't work. I still find it quite a coincidence that the only ones not working are the ones that were scrambled.

[Renzatic]

I use notepad to make my material files too, and it only messed up the formatting once when I was converting an .rtf file to .mtr.

[sparhawk]

You should not use notepad because it can not handle unix linefeeds. Take a real editor.

[oDDity]

Yes, context . It's free.

Edited April 1, 2005 by oDDity

[sparhawk]

I'm happy with XEmacs, but I guess this would be a nightmore for most of you so I don't really recommend it. It's one of the best editors though.

 

XEmacs

[Renzatic]

ConTEXT has alot of Doom 3 packages available for it too, so it's really useful for people that wanna use it for making material files. I've had it for awhile, but I haven't really gotten into it just yet.

[Springheel]

You should not use notepad because it can not handle unix linefeeds.

 

What the heck are those and why would we need to have them in a .mtr file?

[sparhawk]

I store everything with unix linefeeds. This means that the textfiles have only 0x0a as a linefeed. Windows uses 0x0a 0x0d as linefeeds. Any decent editro can handle it but notepad is not a decent editor. Since we are using it this way all the time, we should stick to it. And it is easier this way to use all the files on Linux without conversion. Though I think that the linux version of D3 can probably handle both ways anyway.

[pakmannen]

You can change the encoding in notepad when you save as.. Works for me anyway (not that I use notepad for coding stuff )

 

I'm guessing unix uses unicode?

[sparhawk]

Uniox doesn't use anything. But the usualy way to store flat ASCII files is to use the linefeeds I posted above. Unicode would be a binary enconding. There are certainly editors (I guess) which can support this, but it's not the native format.

[pakmannen]

Alright, but when you save as unicode (or UTF-8) the linefeeds are saved correctly anyway.

[sparhawk]

Unicode doesn't work, because D3 uses flat ASCII files IMO.

[pakmannen]

UTF-8 must surely work? I was under the impression many used this encoding format, even on Linux?

 

It's mentioned here for instance: http://www.cl.cam.ac.uk/~mgk25/unicode.html#linux

[sparhawk]

UTF-8 is supported, yes. But that doesn't mean it's the default format.

[Ishtvan]

This is a dumb question, but what's the best way to convert to Unix linefeeds after you've written a file from scratch in notepad or something.. can you just "save as" and choose ASCII or something?

Edited April 3, 2005 by Ishtvan

[sparhawk]

The way I usually do this is via FTP. If you have a flatrate like me than this is a rather convinient way to do.

 

Upload the file as ASCII to a UNIX FTP of your choice, switch to binary transfer and download it again. Of course this works only if the target FTP is a unix machine, because the FTP protocoll converts textfiles to the native format.

 

The other ways to do this would involve some unix scripting. At least that's how I do this usually. I don't know of an editor where you can specify this, because most editors that I use simply store it the way they loaded it.