I found a strange effect/bug.
I launched quake, then started e2m5 map, after that I started my sm57_pulsar_se map, and I saw that one texture was replaced by another one through all the map. I restarted quake and this effect dissapeared.
But now I know, every time I start e1m5 before sm57_pulsar_se one texture changes.

Anyone knows why? 

..it's because one of the textures in your map shares the same name with one in e2m5. It's a bug in standard GLQuake, is that what you're using?

The one in e2m5 has the same name so GLQ thinks it's the same one and doesn't reload it; just loads the old one from its cache. 

its a "feature" 

it gives replay value! never play the same level twice! 

the only reason i started worrying was inability of q3map2 to compile the map properly. but ppl explained me that i shouldn't worry about that :) 

yeah, what xen said.
use fitzquake, it has this bug removed.
http://celephais.net/fitzquake/files/fitzquake075.zip 

I used glquake, simply it's the first time I saw this bug. Thanx for info.
vondur: I already have fitzquake, but it doesn't work with my videocard (voodoo2 12 mb) 

I just downloaded FizQuake, and it works great!
Then I tried it on my own convertion, in which I have changed the Enforcer for a selfmade Orb.
And although it works good in normal Quake, I found my Orb back as a shapeless jellyfish in FizQuake.
I have seen this before with MercBabe, which I had converted from Malice.

Whatever happened to the texture shape? 

i found that most every engine except standard glQuake displayed the malice models incorrectly, when running the TC itself. 

does fitzquake mesh the models? maybe that's why? 

Take a look at my Q1 ToolTips (section Engine Problems) http://user.tninet.se/~xir870k . 

fitzquake meshes models the same way glquake does. In both cases, there is a danger of the mesh being mismatched to the mdl (becuase of a model replacement in a mod.) I eventually plan on dealing with this problem. 

is of course, to make fitzquake remesh the models everytime it loads. it doesn't take very long to do, so most people won't even notice it. 

If you're still worried about your phantom q3map2 leak (post #1007) there's a thread on q3w that might relate.
http://www.quake3world.com/ubb/Forum6/HTML/027282.html?
Suggests upgrading to v2.5.12. 

I heard it said that this could be caused by improper placement of torches (or flames) partially within brushes. Are there other potential causes of this error as well? Does the flame model problem sound correct? I'd like to get rid of this error message as my map is approaching completion. 

For a quick explanation, take a look in my Q1 ToolTips, Engine Problems section.

For more details, check out post #729 in this thread. 

I sent you an email regarding E2M1a - it's fully vised! Your myrealbox didn't work. The mail I sent had no attachments but a CnP of the vis log. If you have a working address, I can forward it there. 

well, i tried 2.5.12, still no luck. entity still leaks. well, fek it cuz the map vises and lights properly. and it compiles fine in q1 compilers, this is what's important isn't it? :)
thanks for the help though! 

/me frantically opens Outlook 

Hopefully, you've got mail. 

So I've got WC3.3 and I want to map for Q1 but with n33t stuff like radiosity and texture-based lighting. Can someone explain all this new-fangled mumbo-jumbo to me or point me at a FAQ or something?

Cheers 

No mail.

Distrans and Lev - I just sent the zip. Hope it reaches you guys.

Sorry readers for off-line discussion. 

I've just re-sent it, I hope you'll get it now. I can't see how my MyRealBox account could prevent me from reaching you, though. Both my account seem to be working. And I don't get any rejects sending the email to you.

You haven't changed email address lately? 

http://www.orbiter-productions.com/alchemy/

that site has pretty much all you need for editing in Hammer... giving you the option of radiosity, surface lighting, coloured radiosity and surface lighting and more :) 

Cheers Starbuck. Blah, I already have all of that setup, I was hoping there was a more elegant solution.