I got very frustrated with WC 1.6's lack of rotation w/o messing up the textures and the later versions of Worldcraft were a pain with the need for constant texture conversions. 

ok, I finally tried it out and nearly everything runs perfectly, apart from the aforementioned texture limitation problem ("over 1024 textures in a WAD, you are insane!") which means its not easy to use many different wads (ie. splitting them into two, three or even four pieces), including nehahra and my own project wad (though that'll definately be shrinking alot). the other problem is that the compilers call the log by default everytime a portion of vis is completed - which slows it down a huge amount (i'd guess x3-x4 though this behavior can be disabled)- in the readme you say its bengt's tools but to be honest I didn't check which versions.

Since I'm in the middle of something I don't want to go through the process of reconversion (since loading a .map in 3.3 makes it incompatible with 1.6 (most likely an easy fix editing within the .txt of the mapfile)). However this is a huge leap forward when you consider 1.6 has been around and used for almost as long as quake itself - great work.

As to all the other tools and adaption systems; they worked perfectly, possibly the only gripe that could crop up is having base directory as c:/program files/worldcraft but since its such a small utility to move I can't see anyone complaining.

All in all, a very useful set of tools that will eliminate the headaches from alot of mappers lives, I salute you. 

All in all, a very useful set of tools that will eliminate the headaches from alot of mappers lives, I salute you.

Thank you. I appreciate the feedback I have been getting on this. 

Absolute Newbie question. Whenever I run the map all the textures are missing. What am I doing wrong?

Other than that it seems to work great.

Thanks alot for this. 

Your map doesn't have its worldspawn properties pointing at the .wad you're using to make your level. What editor are you using? 

Napalm setup Quake directory in program!!?!?! 

I am using Baker's Worldcraft3.3 Quake fix and it turns out you need to have your Quake Directory somewhere in c:\ (i.e. c:\Quake for example) otherwise it can't write the GFX from the wad into the BSP. 

have the wad in the same dir as your compiler and the map file... or something like that. don't remember if the wad had to have the same name as the map too or if it was specified to qbsp. 

this requires vb6 runtime for win32 systems:

http://download.microsoft.com/download/vb60pro/install/6/Win98Me/EN-US/VBRun60.exe 

- I have a map done in WC1.2 back in the day.I have another done in WC3.3 with Qadapter.

- The first map has a button that opens a door. The second has a button that targets a light to turn off.

- The first ap was compiled with the tools that come with WC1.2. The second map was compiled with txqbsp and MH colured lighting tools.

- In the first map, the door dissapears. In the second, the light dissapears, or the light is off at the beginning and turns on when triggered. This can change every time i compile the map even if i haven't touched a single thing.

- Even if i delete all the entities involved into this and redo them from scratch (new entity--inputing the data manually) the problem is still there. haven't tried to change the variables (Ex: targetname ''door1'' for ''poor2'').

- I have seen similar things happening with other entities but less annoying. 

...are you using killtarget instead of target? 

And that doesn't explain why it goes and comes back on random when i compile it again. 

You might have to bite the bullet and upload the map file, there's not enough to go on from the symptoms... 

I'll try to get the error to show up again, and upload both a .map and .bsp.

*Distrans, forget what i said in #53. But i want to ask you something: I don't see how using killtarget there instead of target can lead to that kind of error, as the issue is about things that happen when the map loads, not when you trigger those entities. Could you explain, please? 

depends if the killtarget is on the door. doors fire their targets (and killtargets) when they open. 

...what necros said plus I assumed (probably wrongly) that In the first map, the door dissapears. In the second, the light disappears happened after the button was pressed. My mistake... 

While trying to reproduce those issues again to send you guys the files, i noticed which were their causes.

In the case of the WC1.1.2 map it was that there was a hidden triger_once triggering to the door hidden in a secret (the MH one) afar from the door, so that explains why sometimes the door wasn't open and sometimes was. It was hidden near some busy brushes so it took me 17 years to find it.

In the case of the recent map, it was just a case of cross-connected entities, which plagued too my second map for sm175. Since them i stopped placing simmetrical rooms in 0,0,0