Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Platforms
PCXboxPlayStationNintendo
Games
ActionStrategyRole Playing GamesSimulatorsSport Games

Game Forum / Action Games / Doom / October 2003

Tip: Looking for answers? Try searching our database.

bsp node builder

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
bob brozewicz - 21 Oct 2003 19:29 GMT
with bsp 5.1, is there a way to send the output to a text file for viewing?
Signature


bob brozewicz
brozewicz.rf@verizon.net [home]
brozewicz.rf@mellon.com [work]

Andre Majorel - 21 Oct 2003 22:24 GMT
> with bsp 5.1, is there a way to send the output to a text file for
> viewing?

What part of the output is it you want to save ? Messages are
printed to stdout so bsp foo.wav >bsp.out should do the trick.

The BSP data itself is not in text format, so you can't view it
so simply. There's a nodes viewer, NodeNav, but it's DOS only.
Some years ago I looked into porting it to X and, as is often
the case with interactive DOS software, it promised to require a
lot of effort.

 ftp://3darchives.in-span.net/pub/idgames/
   utils/level_edit/node_builders/nodenav.zip  # The original version
   utils/level_edit/node_builders/nnav081.zip  # The DJGPP port

Signature

André Majorel <URL:http://www.teaser.fr/~amajorel/>
If we don't believe in freedom of expression for people we
despise, we don't believe in it at all. -- Noam Chomsky

bob brozewicz - 22 Oct 2003 06:24 GMT
> > with bsp 5.1, is there a way to send the output to a text file for
> > viewing?
>
> What part of the output is it you want to save ? Messages are
> printed to stdout so bsp foo.wav >bsp.out should do the trick.

sorry, i should have been more clear, i want all the output that is sent to
the screen, aka, the error messages. like the one listed below. i even
played around with the "-o" switch. cant find anything in the readme file
about this switch.

btw, is there a listing of errors produced by bsp and suggestions on how to
fix them. or is learn as you go?.

       Copyright (c) Rational Systems, Inc. 1990-1994

       Warning: Linedef 2 has no right sidedef

       Warning: Linedef 3 has no right sidedef

       Warning: Linedef 4 has no right sidedef

E:\bsp>

this is the output  i get with the command listed above. i also tried
veriations of the command and i still get the same results. i just want the
errors.

 * Doom BSP node builder ver 5.1
   Copyright (c)   1998 Colin Reed, Lee Killough
                   2001 Simon Howard
                   2000,2001,2002 Colin Phipps <cph@cph.demon.co.uk>

   Opened PWAD file : mymap.wad. 11 dir entries at 0x517E.
   Creating nodes using tunable factor of 17

   Building nodes on MAP01

   Loaded 16 vertices.Creating Segs... done.
   Map goes from (768,-512) to (-256,256)
   LRR-R5 NODES created, with 6 SSECTORS.
   Found 16 used vertices
   Heights of left and right subtrees = (3,3)
   Creating Blockmap... \|done.

   Saved WAD as mymapc.wad

> The BSP data itself is not in text format, so you can't view it
> so simply. There's a nodes viewer, NodeNav, but it's DOS only.
[quoted text clipped - 5 lines]
>     utils/level_edit/node_builders/nodenav.zip  # The original version
>     utils/level_edit/node_builders/nnav081.zip  # The DJGPP port
Andre Majorel - 22 Oct 2003 14:31 GMT
>> In article <cWelb.9468$Fc5.3383@nwrdny01.gnilink.net>, bob brozewicz
> wrote:
[quoted text clipped - 9 lines]
> below. i even played around with the "-o" switch. cant find anything
> in the readme file about this switch.

Nope, the -o serves to set the name of the output *wad*.

> btw, is there a listing of errors produced by bsp and suggestions on
> how to fix them. or is learn as you go?.
>
>         Copyright (c) Rational Systems, Inc. 1990-1994

Oh, good, a compiler that inserts messages in the output of the
executables it creates.

>         Warning: Linedef 2 has no right sidedef
>
>         Warning: Linedef 3 has no right sidedef
>
>         Warning: Linedef 4 has no right sidedef

I don't think so, but grepping for "stderr" in the source files would
give you the list.

 "Creating compressed blockmap... "
 "Error: Could not open output PWAD file "
 "\nWarning: Bad sidedef in linedef %d (Z_CheckHeap error)\n"
 "\nWarning: Linedef %d has no right sidedef\n"
 "\nWarning: Linedef %d is 2s but has no left sidedef\n"
 "Trouble in SplitDist %f,%f\n"
 "Trouble in SplitDist %f,%f\n"
 "Error: Cannot open WAD file %s"
 "Input was not seekable and failed to create temp file"
 "%s does not appear to be a wad file -- bad magic"
 "Unable to read wad directory entry \"%s\" in %-.8s\n"
 "Failure writing %-.8s\n"
 "Failure writing lump directory"
 "Failure writing wad header"
 "out of memory (cannot allocate %u bytes)"
 "out of memory (cannot reallocate %u bytes)"
 "Couldn't find any Vertices"
 "Linedef %ld has vertex out of range\n"
 "Trouble in GetVertexes: Renumbering\n"
 "Couldn't find any used Vertices"
 "Couldn't find any Linedefs"
 "Couldn't find any Sidedefs"
 "Couldn't find any Sectors"
 "Couldn't pick nodeline!"
 "Trouble in ComputeIntersection dx,dy"
 "Trouble in ComputeIntersection dx2,dy2"

Most of them are pretty self-explanatory, and those that aren't
probably can't be remedied by an ordinary user anyway.

The error messages you got (Linedef x has no right sidedef) mean that
you created a single-sided linedef (i.e. a wall) and either
forgot to give it a sidedef, or put the sidedef on the wrong
side. If a linedef has just one sidedef, it must be on the right
(assuming you're looking at the linedef as if it was pointing
away from you).

                              x  end vertex
                              ^
                  left side   |   right side
             second sidedef   |   first sidedef
                   (if any)   |
                  x  start vertex

> this is the output  i get with the command listed above. i also tried
> veriations of the command and i still get the same results. i just
[quoted text clipped - 18 lines]
>
>     Saved WAD as mymapc.wad

OK. The problem is that the error messages are printed to stderr, but
">" redirects only stdout. Ways around this :

- If you're running Unix,

   bsp blah blah >/dev/null 2>bsp.out
   
 will send the error messages to bsp.out and throw away the other
 messages.

- If you're running some Microsoft OS, you're screwed because
 command.com won't let you redirect stderr. You'll have to use an
 external program like http://www.teaser.fr/~amajorel/stderr/.

   stderr bsp -q blah blah >bsp.out

Signature

André Majorel <URL:http://www.teaser.fr/~amajorel/>
If we don't believe in freedom of expression for people we
despise, we don't believe in it at all. -- Noam Chomsky

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.