[Fixed] ZDBSP bugs

Bugs that have been investigated and resolved somehow.

Moderator: GZDoom Developers

Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.

Postby randi » Sat Sep 13, 2003 12:35 pm

ZDBSP is its own implementation and uses different split heuristics than other node builders. As explained in the docs, there are three different parameters you can adjust to alter the tree:
  1. The cost associated with splitting segs (default 8)
  2. The cost associated with using diagonal splitters (default 16)
  3. The maximum number of splitters to consider for each node (default 64)
User avatar
randi
Site Admin
 
Joined: 09 Jul 2003

Postby Hirogen2 » Sat Sep 13, 2003 4:43 pm

Just BTW, how is cost defined, in dollars?
User avatar
Hirogen2
 
Joined: 19 Jul 2003
Location: Central Germany
Github ID: jengelh
Operating System: RedHat-like Linux (RHEL, Fedora, CentOS, etc) 64-bit
Graphics Processor: Intel (Modern GZDoom)

Postby Cyb » Sat Sep 13, 2003 5:13 pm

cpu cycles?

generally you want to keep programs running faster, and in this case it's not like it's at the expense of something necessary, just a progress bar you see for usually less than a second, why is this so important to you?
Cyb
 
Joined: 15 Jul 2003

Postby randi » Sat Sep 13, 2003 6:21 pm

Cost is like "how bad/good is it to worry about this?"

The original bugs listed here are fixed in ZDBSP 1.2, so I'm moving this topic now.
User avatar
randi
Site Admin
 
Joined: 09 Jul 2003

Previous

Return to Closed Bugs

Who is online

Users browsing this forum: No registered users and 1 guest