 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
You need to add a value to the "message" key of your worldspawn brushes. The "message" will be the name of the level displayed in-game when you hit tab, and in the saved game menu.
That does look intimidating. But by "in the future" you mean "not yet", right? As in, for now I can continue exactly as before?
No, this is as of now. I can also give you access to dropbox if you want to try the intermittent alpha builds. You'll need a dropbox account and you'll need to give me the associated email address. I can't select objects in 2d view or move them around using the mouse (I can only move objects with the arrow keys).
Anyone else having this problem? Nope, changing tool mode doesnt do anything for me. I think I pressed tab to get a little hand icon and then after that it stopped working?
I can't get the info panel to display in TB2 with any maps. Using the Toggle Info Panel menu item has no affect. Wonder if it's a Windows 10 issue? Incidentally, TB is an astonishing piece of software.
Win7 x64 same issue here.
I thought I was just blind or doing something wrong. You are right. Though for me it is not related to TAB, but to cycling views with SPACE.
It is all good until I change the view. After that strange things happen. Some brushes don't react at all, some could be selected only in one of the side views... is it possible to add x/y/z letters to existing color-coded arrows, btw? Another thing I noticed - some brushes are not displayed. https://www.youtube.com/watch?v=4QCNUwRV5aY&feature=youtu.be Brushes disappearing in orthographic views is part of same issue or it needs separate entry?
That's okay, thanks for the video.
I wonder why all these bugs show up just now. We have had all those alpha builds and it seems like noone has really tested them. Maybe I should stop doing alpha builds. https://pbs.twimg.com/media/CdhlNGxW0AEmRVB.jpg:orig
Overall, TB is quite impressive. :) Before that, I've wildly copied and pasted brushes until it crashed. Then I tried the same in Microbrush until it crashed. TB reached 64k brushes before crashing when cloning them, Mb reached 512k brushes before the crashing clone. We're probably both hitting 32bit memory address bounds or something like that. As I associate more data with my brushes for texturing, my total count before a crash will probably decrease, too. I suppose you're on Windows? Memory consumption is a weak point of TB, I have beens squandering memory to be honest. It is something I'd like to improve in the future. On the other hand, "64k ought to be enough for anybody", ask Bill Gates!
It would be nice if the compile tools and engines adopted handling such large numbers of brushes normally... think of all the possibilities for detail modeling, not necessarily larger maps... mmh.
the quake bsp / visportal system really does not scale well as maps become more and more detailed.
There is a reason games abandoned this model 15 years ago I haven't been using the alphas very often which is why you rarely get bug reports from me.
I would bug test more but I don't want to risk losing work at the moment One could harness the ease and expressiveness of brush-based modeling in conjunction with other ways of doing the vis work, too. I recall many approaches to these issues from lectures I've attended. BSP and vis portals are just two flavors.
In the Quake domain, there might be some room for extending the concept of detail brushes a bit, so that the compiler and engine identify complex parts that could be made into models that go through a different rendering pipeline, etc. What I meant was a bit of daydreaming that some underlying fundamentals are changed with a lot of effort. :P Yes, if you mean like how the Quake 3 and Doom 3 engines have much more efficient ways of dealing with detailed brushery than Quake 1 then I agree.
Darkplaces has q3bsp support for quake 1. That's probably as good as we're gonna get.
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |