Edited by SciFi on Mar 28, 2015 at 06:30 AM

Just so I'm clear, what you're trying to do is create a set of pre-made mini structures that people can download and use to create their own maps? If so, sounds like a pretty cool idea that a lot of beginner map-makers can use.

So essentially like Forge, but with totally custom assets? Interesting concept, I'd love to see how this goes and how versatile it could be :3

As someone who doesn't have a steady hand when drawing stuff or stuff like that, i am interested in this.

cool

models could be a bit more detailed but the concept is pretty good. Maybe we can get some people here to contribute their skills to make more modular pieces?

You can see how there would be issues with sealed world rules, however, I think that if a modeler has the knowledge to delete the faces where the sections connect, you can use vertex snaps to move pieces into place. Then if you made something really different, you can use the Boolean tool to connect pieces (might affect uvs, but it's fixed easy enough).

It would be cool if these had multiple texture variations.

Edited by SciFi on Mar 28, 2015 at 06:27 AM

My only comment on this is that if these are going to be small pieces that you re-use a lot then you need to make them as low poly as possible. I see that you've got an extra edge loop running along the center of that concrete road piece. That would be fine if you intended to mirror a texture across the seam for like road markings, but looking at the texture that's applied to it I see that you don't seem to intend for it to be a mirroring seam. I may be wrong about that since you say these are just temporary textures, but I make it a point to over-evaluate things.

You could make two sets of these; one as OBJ models for use in 3ds max for BSP's, and one as compiled scenery with collision. For the compiled scenery one you could also supply a simple empty box map for people to place the pieces in. I say this because it will be so much easier to rapidly test a map configuration without having to go through the map compilation process, errors and all.

I personally think this is a really good idea since most of the available stuff on halomaps seems to be just assorted scenery. People new to Halo modding will also hit a brick wall when making their first map if they don't know 3DS Max. Having these as scenery will be a great way to allow them to try their ideas without having to get frustrated with 3ds max first. I really approve of this.

All Halo ce BSP's must conform to the sealed world rules.

The rules in question are as follows:

1. Your bps, must have no overlapping, intersecting or illegal faces.

2. Every BSP must be a sealed mesh, meaning it should have no holes of any kind regardless of how small or wide your holes are.

3. It is possible to compile your bsp even if it has holes, by assigning special material symbols to the geometry within the standard shader roll out. This can be particularly useful of geo which has been intended to be unsealed.

I.E A piece of glass, a decal, or plane which has been designed to use no collision.

4. The whole point of adhering to "the sealed world rules" is to incorporate physics/collision into your game level since both the collision and the aesthetic model are compiled within one entity you must conform to these rules in order to end up with a successful level export.

Note: Models such as, vehicles, weapons, scenery pieces, e.t.c do not require you to seal every piece of mesh, however if you need said item to have collision you can twin your aesthetic model with a separate collision model or use your aesthetic model as your collision model.
Edited by SS Flanker on Sep 21, 2014 at 01:48 PM

Just to make sure you don't confuse him, you can actually have multiple SEPARATE BSP's intersect each other in level geometry, just make sure they are each linked to a different node. Like, if you wanted a rock to stick through the ground and be part of the BSP instead of scenery, but you don't want it to be sealed to the floor and cost a lot of triangles. What you do is you make another node(bone/frame/node w/e you want to call it) and name it something like "frame misc", link that frame to the level's root frame, and link the rock to the "frame misc". This doesn't cause issues and is the best way to do certain things. This is ALSO why you are able to have intersecting collision geometry on bipeds/weapons/vehicles/scenery, cause they are linked to separate frames.
Edited by MosesofEgypt on Sep 21, 2014 at 02:33 PM

You just link all sealed objects to "frame"

Edited by SciFi on Mar 28, 2015 at 06:24 AM

You seem to be missing the point. The end result of what can be made with these isn't meant to be a finished level. The point of all this is to make it easier for people to test their level layout ideas before starting on it in 3DS Max. This is especially true for people new to the HEK who don't know how to make new levels from scratch or in 3DS Max. Think of it like rapid prototyping.
Edited by MosesofEgypt on Sep 21, 2014 at 06:08 PM

I believe you may be misunderstanding Jesse. I think what he meant was that were these pieces to be used in 3DS it would be a simple matter to connect them using the Vertex function, were the ends open for such a thing to be applicable. If you're just creating scenery there's no need; end users can just delete the faces themselves. Nothing's free ;o

Edited by SciFi on Mar 28, 2015 at 06:23 AM

Credit to maniac, alits94 and ally for originally teaching me all this.

Edited by SciFi on Mar 28, 2015 at 06:21 AM

Maybe you should make longer variants of the same pars?

I agree.

Btw, decided to eye ball model your art work sci-fi picture thingy.

It is crap, because I am used to blue prints, not rough averages.

Edited by SciFi on Mar 28, 2015 at 06:20 AM

Thanks, it was hard, since there wasn't really a true sense of scale. So I just went with what I felt like would acceptable.

I added my own flare to certain pieces such as those arrow shaped base, but when you are eye ball modelling, is wise to have a bunch of references displaying info from at least 8 different angles of the object you want to model.


Btw, I can maybe go 1 better than the actual model.

ask me how

Edited by SciFi on Mar 28, 2015 at 06:19 AM

Hold up there. 8 is a bit much. 3 is really all you need. Having an Othographic Projection of the Side, Front and Back is about all that you would actually require. Some people prefer to have a top view as well but 8? that's a bit much.

8 perhaps is a little too much, I mean you have, top, down, left, right, front & back.

But going on modelling for weapons experience, you can never have too many references.

Edit: 26/09/2014

BOOP: https://mega.co.nz/#!1IVihRzI!LUzyEIxBzmjFm3Lpd7HWnKfD7wDFYoBZD5cjkjpNrzg
Edited by SS Flanker on Sep 26, 2014 at 10:07 AM

Edited by SciFi on Mar 28, 2015 at 06:17 AM

Link hates everyone sorry.

bump.