Sandcrawler Network

Unreal Modder's Haven => Unreal Engine 2 General Modding Chat => Topic started by: arramus on June 16, 2009, 10:04:49 AM

Title: Brushes to Static Meshes Tutorial
Post by: arramus on June 16, 2009, 10:04:49 AM
======================================================================

Here is a tutorial describing how to convert Brushes to Static Meshes.

We are going to:

1. Build a simple collection of Additive Brushes into a 'lattice' type laser.
2. Convert the collection of Brushes into a Static Mesh and save into your map.
3. Apply a Default Texture.
======================================================================

1. Open a map and construct a lattice of Additive Brushes on a criss-cross pattern.

2. Select all of these Additive Brushes in the 'Top' Viewport and right click for the selection menu. Select Convert > To Static Mesh.

In the new window that opens save as:

Package = myLevel
Group = laser
Name = laser

3. Select a Texture you would like to apply to your new Static Mesh from the Texture Browser. Now select the new Static Mesh from the Static Mesh Browser and below the image select Materials >
You are now ready to use this Static Mesh in your level as a standard Static Mesh or a Mover that can cause damage as it interacts with a player. The Movers, Triggers, and Usable Doors (//http://www.sandcrawler.net/forum/kfmod.php?page=tutorial-6) tutorial by Sandcrawler will provide support for that function.

(//http://static3.filefront.com/images/personal/a/arramus/49990/ojalqlbhfc.jpg)
Title: Re: Brushes to Static Meshes and Movers Tutorial
Post by: Joker on June 16, 2009, 11:14:54 AM
lol you made this today? :D Yay new tut, Thanks dude ! ahh you also forgot the enroach damage (laser beamz xD)
Title: Re: Brushes to Static Meshes and Movers Tutorial
Post by: arramus on June 16, 2009, 07:38:34 PM
That's for another tutorial... :mrgreen:
I've added the link for Movers, Triggers, and Usable Doors by Sandcrawler to the first post. Setting the Initial State, Encroach and Damage Properties should be common sense but may need a standalone tut if mappers get lost.