[brlcad-tracker] [ brlcad-Bugs-3401630 ] Raytrace of v4 database on version 7.20.0
Open Source Solid Modeling CAD
Brought to you by:
brlcad
From: SourceForge.net <no...@so...> - 2011-11-15 21:06:19
|
Bugs item #3401630, was opened at 2011-08-31 07:41 Message generated for change (Comment added) made by brlcad You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=640802&aid=3401630&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: Raytrace Group: other bug / workaround >Status: Pending >Resolution: Fixed >Priority: 7 Private: No Submitted By: Christopher Pitts (cmpitts) >Assigned to: Tom Browder (tbrowder2) Summary: Raytrace of v4 database on version 7.20.0 Initial Comment: When raytracing a v4 database on Microsoft Windows XP & 7 with vversion 7.20.0, the partition structure returned by the hit function does not have the pt_regionp data filled in correctly. This can be fixed by upgrading the database. ---------------------------------------------------------------------- >Comment By: Sean Morrison (brlcad) Date: 2011-11-15 13:06 Message: That was indeed related to the problem, but only half the picture. A fix was applied, however, that should get things working again. If you would, please test with a current checkout? ---------------------------------------------------------------------- Comment By: Christopher Pitts (cmpitts) Date: 2011-10-19 08:49 Message: I have tracked this to the db5_sync_attr_to_comb (db5_types.c) function called from db_recurse (db_tree.c) is resetting the comb structure when a version 4 database is opened. ---------------------------------------------------------------------- Comment By: Christopher Pitts (cmpitts) Date: 2011-09-02 11:02 Message: How did you ascertain that the pt_regionp data was not filled out correctly? We have codes that use various data out of the structure and the values are always 0 in 7.20.0. It worked fine in 7.12.2. Was the v4 file created on a little or big endian platform? It was created on a little endian platform from an ascii file several years ago. Did you perform the dbupgrade on that same Windows system or on a different system? If different, was it big or little endian? Same machine. ---------------------------------------------------------------------- Comment By: Sean Morrison (brlcad) Date: 2011-09-02 09:43 Message: Thanks for the report, but a few follow-up questions: How did you ascertain that the pt_regionp data was not filled out correctly? Was the v4 file created on a little or big endian platform? Did you perform the dbupgrade on that same Windows system or on a different system? If different, was it big or little endian? There is now code that reads in (incompatible) v4 files, but there are several potential "gotchas" given the uncertainty inherent in the data. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=640802&aid=3401630&group_id=105292 |