A Question For Those Who Understand Q1 Vs Q2 Rendering.
#18889 posted by damage_inc on 2017/09/09 01:05:03
After many hours I found what I think is an acceptable way to convert Q1 textures to Q2(this was a request of sorts)
When I say acceptable I mean, a non destructive conversion! Which was every tools way of converting previous, hehe.
Here is a sample: https://media.discordapp.net/attachments/355836262847873045/355847674475446272/side_by_side.jpg
The jpeg straight out of the .wad on the LEFT, my converted .wal file on the right.
I think the conversion looks decent enough? But in Q2 I just think it looks like poop.
Thoughts?
#18889
#18890 posted by Spike on 2017/09/09 03:57:05
Q1 and Q2 have different palettes. You cannot convert from one to the other without destroying information.
Your .wal is thus slightly less bright etc.
On the other hand, if you use .tga instead then you can avoid the palette thing entirely, but this won't work in vanilla, obviously (most q2 engines are fine with a .tga instead of a .wal, but its best to provide both in case someone insists on vanilla/sw).
Lighting
#18891 posted by Qmaster on 2017/09/09 04:00:49
Due to palette differences, the texure will shadow differently.
Quake 1's versatile palette:
https://quakewiki.org/w/images/0/09/Qpalette.png
Quake 2's restrictive palette:
http://fabiensanglard.net/quake2/quake2_palette.jpg
Now, Q2's palette is more bland because Q2 relies heavily on colored lighting. Try using light color to correct it maybe. :)
Not Just Palettes
#18892 posted by Spike on 2017/09/09 09:24:59
Q2 was designed with old opengl in mind.
it has no fullbrights (nothing can glow in the dark).
it has no overbrights (brighter areas cannot oversaturate, resulting in flatter dull lighting)
it has rgb lighting, but this mostly just means that they went crazy with it, thus anywhere even near sky becomes orange, which reduces effective palette variation even more.
Moving To -bsp2
#18893 posted by Redfield on 2017/09/11 06:50:46
No not moving literally, I'm still stuck here in the Canadian wilderness...
My AD map which is almost finished the beta stage has gotten a little bigger. Sometime at the point it grew from 10 000 brushes to 11 000. I got an error message (tyrutils v0.15.10) "Too many vertices... compile with bsp2..."
It wasn't a leak since the map still does full vis/no leak detected/no pnt file, and adding the bsp2 tag has fixed it. I guess it literally had too many vertices. Is there anything I should know now that the map is in this format? Everything seems to be working fine. I guess I'm stuck with it at this point since I won't be deleting details this time.
Thanks
#18894 posted by PRITCHARD on 2017/09/11 07:00:45
My understanding of BSP2 is that OTP will tell at you and your map won't work in old engines. I'm not aware of any engine that's actively developed that doesn't support BSP2.
WTF Android
#18895 posted by PRITCHARD on 2017/09/11 07:01:47
*yell not tell! In what world is it okay to "correct" a perfectly spelled word?!
Its All New To Me.
#18896 posted by Redfield on 2017/09/11 07:06:56
I figured as much, I'm mostly learning this stuff as I go, and have gotten lots of great tips from the masters.
Since its an AD map the player will have to use Quakespasm, Mark V, or Darkplaces anyways, so I hope no one gets mad at me... I'm actually surprised how well it performs in Darkplaces on my machine with integrated graphics.
Thanks.
If you get too many vertices on a sealed map then it's time for BSP2.
Pritchard
#18898 posted by Mugwump on 2017/09/11 14:44:47
It's easy to make typos on these tiny virtual keyboards. Since tell and yell are both valid words, Android proposes them both to choose from above the keyboard. If you forget to pick one, it's not Android's fault... ;)
Sorry for the OT, guys.
#18899 posted by PRITCHARD on 2017/09/11 15:36:01
My phone is large enough that the keyboard is actually very reasonably sized for thumb use. I decided to just turn off autocorrect completely anyway, if I really need it the suggestions bar is still there...
In OTish news, what do people think about hiding small items in total darkness? Right now there's a rotten health hidden in a little alcove that's pretty easy to spot but unlit. Should I throw a little light in there or is it okay to have something you'll only really find by accident like that?
Don't Worry About Using BSP2
#18900 posted by Orl on 2017/09/11 16:29:46
Many engines support it, and it's no different from bsp29 other than increased limits on just about everything. Nobody will be mad at you :)
#18901 posted by Mugwump on 2017/09/11 17:22:42
hiding small items in total darkness
That's a no-go in my book, unless it counts as a secret - but a secret for just a rotten health might be a bit of an overkill.
That said, wouldn't the fullbright parts of the health box make it noticeable?
Didn't know you could still use the suggestions bar with autocorrect off.
#18902 posted by PRITCHARD on 2017/09/12 09:03:55
Suggestions bar depends on your keyboard. I use Google's "GBoard" on my phone.
And there are no fullbrights on the health pickups in AD's medieval set.
I think you're right about it being a no-go. The fact that I wasn't sure about it should have told me all I needed to know about the placement...
#18903 posted by PRITCHARD on 2017/09/12 10:23:57
Does anyone have advice on how to build something like this out of brushes? I want to make it hollow on the inside as well.
Thanks!
#18904 posted by Baker on 2017/09/12 10:54:27
Round and hollow? example
#18905 posted by Baker on 2017/09/12 11:06:36
Duke of Ontranto
https://www.quaddicted.com/reviews/fc1.html
In pak, see ---> progs/barrel.mdl
Live action -game fc1 +map fc1m2
Pritchard
#18906 posted by Qmaster on 2017/09/12 13:48:55
In JACK, create cylinders stacked, in vertex mode use CTRL+E (or maybe it was ALT+E), scale edges as needed. It helps to have both mating brushes selected...this works for donuts as well as cylinders.
#18907 posted by PRITCHARD on 2017/09/12 14:33:50
I don't remember reviewing fc1... It's been a while since I played through any maps in quake actually.
Those barrels are decent, actually. I ended up figuring out how to make them out of brushes by looking at the wireframe in qme.
@qmaster
#18908 posted by PRITCHARD on 2017/09/12 14:36:09
I use TB2, but I was able to achieve a (probably) similar effect with the basic vertex manipulation there. :)
Now i just have to cut my beautiful new barrel up into little chunks so it looks cool when you shoot it to bits!
@Pritchard
I'm not sure if you know this but a protip i recently found from Sleepwalker was: You can use CSG Merge to merge faces in Tb2! Make the diff sections of your geo then use merge to quickly extrude the brushes. Try it.
Also there are barrels in Hexen 2 that could probably be used as a template. I wonder if the map source is available?
AD Entity Models In TB
#18910 posted by Kim Smoltz on 2017/09/13 12:24:28
Hey, I loaded up the AD .fgd file and made a symlink of the "progs" folder into Trenchbroom's root directory assuming it would be able to find the models there, but it seems that it can't, where do I need to place it so that Trenchbroom will find them?
#18910
#18911 posted by PRITCHARD on 2017/09/13 14:02:06
You don't need to symlink anything. Just make sure that TB knows where your Quake directory is and select the mod's folder here!
There are essentially two places where you need to set up your mods (at minimum): Under the map tab, where you select the mod folder, and under the Entities tab, where you select your entity definition file such as a .fgd or a .def
Hope that helps :)
If I wanted to take away a players weapons after the end of a map, like what happens at the end of each episode in quake, what's the best way to do that?
Also is there a way to change the name of the start map that is automatically loaded when quake starts, or does it always have to be called "START" ?
|