Thread: [brlcad-users] Weirdness with DSP objects
Open Source Solid Modeling CAD
Brought to you by:
brlcad
From: Alan C. <al...@et...> - 2012-01-21 19:20:24
|
I finally figured out how to get a dsp created and it draws it and all looks good. Trying to render it spews warnings and sure enough if I try and turn it into stl for example using the reference binaries I also get similar error reports: ERROR: NULL vertex_g pointer, file /home/jordi/Escriptori/brlcad-7.20.4/src/librt/primitives/nmg/nmg_mod.c, line 1404 ERROR: NULL vertex_g pointer, file /home/jordi/Escriptori/brlcad-7.20.4/src/librt/primitives/nmg/nmg_mod.c, line 1404 Is this an expected limitation ? I have the actual random data block I used to test this saved if it's useful. Alan |
From: Christopher S. M. <br...@ma...> - 2012-01-21 19:45:39
|
Hi Alan, On Jan 21, 2012, at 2:07 PM, Alan Cox wrote: > I finally figured out how to get a dsp created and it draws it and all > looks good. Trying to render it spews warnings and sure enough if I try > and turn it into stl for example using the reference binaries I also get > similar error reports: The warnings are cause for concern since they may imply something not set up or modeled right. If they're overlap warnings, then they're usually modeling errors and those can affect export. You'll have polygons that coincide with other polygons such that the exporter can't consistently resolve a solid volume. What do a couple of the warnings look like? > ERROR: NULL vertex_g pointer, > file /home/jordi/Escriptori/brlcad-7.20.4/src/librt/primitives/nmg/nmg_mod.c, > line 1404 > > Is this an expected limitation ? Not at all, it should just work. The only issue I'm aware of is if there are interior "voids" in the data, i.e., holes due to zero-values in your data file, there may be an issue. > I have the actual random data block I used to test this saved if it's > useful. That would be very useful, maybe attached to a bug report so we can continue the investigation there. Cheers! Sean p.s. Thanks for the f16 build warning report. That issue was already identified and fixed in our repo, so next source release will have it. |