Worldcraft toEntity

[nordkril]

Hey guys,

Going through some BSP tutorials and Worldcraft's toEntity button is causing me some grief. I can tie a brush to a new func_door entity the first time round (the door works after compiling), but if I reselect the brush/entity and try and alter its properties it's as if it isn't an entity any more (I get the VisGroup menu instead) - even though it has been coloured purple in the editor.

Once in a while I will hit 'toEntity' and it will warn me that it is already an entity, so why doesn't it detect this the rest of the time?


Created the door brush


toEntity dialogue


Door brush is now tied to func_door


No entity properties


Any help would be appreciated,

Thanks.

[MadGypsy]

The answer is so simple bro.

A: It's all messed up

Sorry (lol) I couldn't resist. I honestly have no idea why you are having this problem. If you are using Worldcraft 1.6, update it to Worldcraft 3.3 w/ Quake Adapter. By "update" I actually mean uninstall & delete 1.6 and get 3.3 instead.

WC 3.3

[Baker]

One of the keyboard shortcuts (shift-Q ?) clears your current selection.

I've learned to press that before selecting anything because in my experience, if something else is somehow selected (it isn't always entirely clear what is selected with all the lines on the screen) it won't select what you click without clearing your current selection.

As far as I recall.

[nordkril]

That worked great - thanks Baker! Time to learn some shortcuts methinks .

The answer is so simple bro.

A: It's all messed up

Sorry (lol) I couldn't resist. I honestly have no idea why you are having this problem. If you are using Worldcraft 1.6, update it to Worldcraft 3.3 w/ Quake Adapter. By "update" I actually mean uninstall & delete 1.6 and get 3.3 instead.

You're right there - whenever I make a cut on a brush the lines turn black for some reason. Don't remember it doing that when it was installed before. I was already rocking 3.3. with the Quake adapter - but thanks for the suggestion.

[MadGypsy]

You should consider learning Radiant. I used Worldcraft for a long time. It gave me the skill-set for building simple maps and it is (IMO) a great beginner tool. However, it's basically a 3rd party ware that is "hacked" to make maps that will run Quake-style.

Current Radiants are a "branch" of the original software used by ID. It's not incredibly different from the Worldcraft workflow. It is however more stable and "native". It is also capable of making maps for more games and has support for more current standards (like shaders).
`

[nordkril]

This is my first time mapping, so I was using Worldcraft in conjunction with some tutorials to learn the basics of BSP. But as I've just worked my way through a whole set of generic tutorials meant for the original BSP editor, I guess I've got most of the basics covered!

I'll definitely take a look at Radiant when I get the time - as a bonus it runs on Mac OSX too so I think it would be worth it for the multiplatform supports alone. Thanks for the heads-up!

[EDIT]
Wow, just been going through this Radiant tutorial here (also on this forum somewhere I believe?) and I must say I am really digging some of Radiant's features - definitely a keeper!

[golden_boy]

nordkril; Worldcraft is fine and great maps have been made with it, but if you fancy ever using the Quake 3 map format for Quake maps or mapping for any other game that uses Radiant, it is worth to also learn Radiant.

It is also worth using Radiant if you're ever on a team where not everybody uses Worldcraft - Worldcraft 3.3 doesn't output the standard Quake 1 .map format.

However if you fancy Source mapping, it might be worth learning Hammer which developed from Worldcraft.