[brlcad-tracker] [ brlcad-Bugs-3401643 ] g-obj does not output facet data

[SourceForge.net <no...@so...>]

Bugs item #3401643, was opened at 2011-08-31 14:56
Message generated for change (Settings changed) made by brlcad
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=640802&aid=3401643&group_id=105292

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Geometry Conversion
>Group: other bug / workaround
>Status: Pending
>Resolution: Fixed
>Priority: 6
Private: No
Submitted By: Christopher Pitts (cmpitts)
>Assigned to: R. Weiss (r_weiss)
Summary: g-obj does not output facet data

Initial Comment:
Running g-obj  with version 7.20.0 shows "triangulated successfully: 100%"  but no facet data is sent to the output.

g-obj havoc.g r.t_bum1

output from g-obj:
......
didn't find trapezoid for hole-start point at:
	10530.2 80.2126 2513.42
nmg_stash_model_to_file('tri_lone_hole.g', x16c5e40, lone hole start)
nmg_stash_model_to_file(): wrote error.s to 'tri_lone_hole.g'

bombing

FAILED in triangulator: /r.t_bum1
# BRL-CAD generated Wavefront OBJ file (Units mm)
# BRL-CAD model: havoc.g
# BRL_CAD objects: r.t_bum1
Tried 1 regions, 1 conv. to NMG's 1 conv. to tri. nmgper = 100.00% triper = 100.00% 
Tried 1 regions, 1 converted to NMG's successfully.  100%
                  1 triangulated successfully. 100%


----------------------------------------------------------------------

Comment By: Sean Morrison (brlcad)
Date: 2011-09-02 16:53

Message:
Presume that's a typo and you ran with the -o option to specify the output
file?

Have you tried other (simpler) database files or was the failure specific
to havoc.g?

That said, there are several situations where polygonal conversion of our
traditional CSG files is highly problematic (i.e., it'll fail) ..
particularly for a model like our havoc example database.  That particular
region failure in havoc is a known issue that has already been fixed (but
not yet publicly unveiled).

It's an ongoing development effort to improve our tessellation performance
(which changes and improvements occurring pretty much every month for the
past year) with a LOT more to go, but things are slowly improving.

Related:
https://sourceforge.net/mailarchive/message.php?msg_id=26694114
https://sourceforge.net/mailarchive/message.php?msg_id=26894272


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=640802&aid=3401643&group_id=105292