Direction of slashes in model shaders

(DickDastardly) #1

Hi all,
I’ve recently dowloaded the latest version of q3map2 and I noticed that md3s using shaders I’ve made in the past no longer work properly. After a bit of experimentation I found that if I reverse the direction of the slashes in the shaders (i.e from \ to /) everything works again.

I wrote a tutorial covering making and skinning a simple md3 which you can check out here:

http://www.mikesteven.pwp.blueyonder.co.uk

Obviously I need to update paragraph 2.0 but I need to know the version of q3map2 in which the behaviour changed so I can say “If you’re using version x or later have your slashes 1 way, and if you’re using an earlier version have the slashes the other way”. Does anyone know which version this was? (I’ve looked through the readme and this forum and I can’t find anything which refers to this).
Cheers,
DickDastardly

(digibob) #2

You should ALWAYS use ‘/’ style slashes, as this is gauranteed to always work.

(DickDastardly) #3

Thanks for the response, but when I used “/” slashes in the shader with previous versions of q3map2 (the last one I downloaded before the most recent was probably a couple of months old) they didn’t work - I only started using “” slashes because I found they worked that way round.

When I updated to the most recent q3map2 those md3 shaders which had worked in the past suddenly didn’t work (until I changes the slashes to “/”). So the behaviour seems to have changed at some point.

(ydnar) #4

The only reason you would have had to use \ slashes in shader names is if you exported your MD3 with Pop’N’Fresh or its ilk that couldn’t manage to emit correct shader names.

If in doubt when needing to export a model for use in a BSP, use the ASE format, and name your Max materials the exact shader name you wish to use.

y

(DickDastardly) #5

Hi Ydnar,
I did use Pop N’ Fresh for the exporting so that was presumably what necessitated using slashes the wrong way round (i.e. “”). However, as I said above, since I upgraded q3map2, “” slashes no longer work, but if I change them to “/” then all is fine.

Originally, all I wanted to know was which version of q3map2 the behaviour changed in (so I could update my tutorial), however, it’s just occurred to me that all md3s which have been released in the past using shaders with “” slashes will no longer work properly in a map compiled with the most recent q3map2.

Would it be possible to change things in a future version so that either type of slash works? (Otherwise there’ll be a lot of people who’ll need to update and re-release their md3s).
Cheers,
DD

(pazur) #6

wolf needs for model2(props_decoration or script_mover) a “/” slash like in the original models.shader file