News | Forum | People | FAQ | Links | Search | Register | Log in
Screenshots & Betas
This is the place to post screenshots of your upcoming masterpiece and get criticism, or just have people implore you to finish it. You should also use this thread to post beta versions of your maps.

Need a place to host your screenshots? Upload them here:
http://www.quaketastic.com/
Username: quaketastic
Password: ZigguratVertigoBlewTronynsSocksOff
File size limit is 128MB.
First | Previous | Next | Last
Post Screenshots! 
do it... 
Amazing Detail Warren 
 
 
Omg 
so stoked! 
Lol That's So Modern Hollywood Meta 
Instead of a trailer, I'll offer you a trailer for a trailer!

Why not a screenshot for a screenshot? 
Warren 
Awesome.

related to that, I've been playing with qbsp a bit and trying to get it to load .obj's directly, like the q3 utils could do with misc_model, and it seems pretty promising. the disadvantage is there's no collision against the model, since I don't reconstruct brushes like you are. 
 
Too bad Quake doesn't have a weapon clip etc, because I wouldn't mind having to make my own collision.

Guess you'd need to do something funky with skip textured func_walls to make the collision for a misc_model? 
 
ericw - That sounds more useful than what I'm doing. :P Honestly, I tried that at one point as well - inserting model triangles directly into the BSP but I didn't understand the code well enough to get any real headway on it.

That code is ... well, let's face it, it's a mess. 
#12130 
ericw - that sounds awesome - does lighting work with them? I can see that being a good way to get things like decent dead trees and whatnot 
Warren 
I tried an experiment like that a while back - I wrote a program that took a bunch of triangles and stuck an extra vert on the back, pulled out a little to create a tetrahedron, which I then wrote out as a brush in a .map. An optimisation could be used when, depending on the topology, pairs, or trios of model triangles had a convex relationship and could be used in a single tetrahedron brush, which brought the complexity down a little bit.

It worked very well, but I found that when used on a large-ish scale, e.g. to create big cave systems, all those funky planes would caused the bsp compiler to go bananas and generate microleaks. Made no real difference even if i made sure all tetradedron verts were snapped to grid.

In these days of detail brushes however, it might not be so much of an issue... 
 
Yeah, that's the "spikey" option. It usually sucks but sometimes it works so ... might as well include it. 
Argh 
Sorry Ericw, I'll get back to that soon - got sidetracked with the Qonquer Jam. 
 
It worked very well, but I found that when used on a large-ish scale, e.g. to create big cave systems, all those funky planes would caused the bsp compiler to go bananas and generate microleaks.

I wonder if the next enhancement to the engine and tools should be increasing (or removing) the maximum number of unique planes. 
 
I wonder if the next enhancement to the engine and tools should be increasing (or removing) the maximum number of unique planes.

Don't know if this was an issue.

I just think the compiler wasn't really designed to handle that sort of geo. When it tried to make a bsp tree from several hundred non-orthogonal triangular faces, everything ended up being sliced and diced with floating point inaccuracy stacking up until it eventually plopped a great big Welsh salad on the table.

I haven't tried it though since detail brushes became available. It probably works a bit better now. 
 
maybe at that point it really is time to move on to bsp3. :S 
 
Interesting 
does the "standard" option simply take all the polygon planes in the obj model and define a brush with them? So that option would only work if the obj model is convex? 
 
Right, it treats each mesh in the OBJ file as if it's a set of planes and converts it into Quake MAP format.

It doesn't do any kind of automatic decomposition. The meshes need to be convex already or you'll get weird results.

I WANT to do some sort of automatic convex brush breakdown but ... it's a seriously tricky topic. 
 
maybe at that point it really is time to move on to bsp3. :S

I'd rather people bite the bullet and just embrace q3bsp, rather than add more cruft to the q1 bsp format. 
 
I'd rather people embraced UE4, rather than add more cruft to Quake. 
 
Right, it treats each mesh in the OBJ file as if it's a set of planes and converts it into Quake MAP format.

It doesn't do any kind of automatic decomposition. The meshes need to be convex already or you'll get weird results.

I WANT to do some sort of automatic convex brush breakdown but ... it's a seriously tricky topic.


Yeah, that would be the holy grail, but it's a massively tricky problem :/ 
 
I'd rather people embraced UE4, rather than add more cruft to Quake.

Don't throw the baby out with the bathwater. 
 
I don't know what I'm waiting for as this seems to work, so ... If you're feeling brave:

https://dl.dropboxusercontent.com/u/161473/OBJ2MAP/OBJ2MAP_PreviewA.zip

I don't have any docs written yet but it's pretty straightforward.

If you're using Trenchbroom, you can just paste the results directly into your map. If you're using Jackhammer, you'll need to load the resulting MAP file and copy/paste the brushes over.

This is also a test to see if this needs anything other than the EXE to run ... I think it should "just work". It needs .net but everyone has that these days anyway.

Windows only, suckas! 
 
I'd rather people bite the bullet and just embrace q3bsp, rather than add more cruft to the q1 bsp format.

i meant q3bsp. :(

is there any chance of seeing it implemented in quakespasm? ^_^; 
 
first we need to add light styles to it 
First | Previous | Next | Last
You must be logged in to post in this thread.
Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors.