| 00:08.55 | yukonbob | re: material properties -- I'm not talking about colours + textures, but attributes (like the .density material) |
| 00:42.19 | yukonbob | as I understand, ray "properties" or attributes are actually set in the module that _is_ that ray (ie: xray properties are set in the rtxray program. is it as simple as that?). However what if some materials allow xrays to pass more easily than others (ie: a 'flesh' material wrapping a 'bone' material; the two materials shouldn't have the same xray signature). |
| 00:43.47 | yukonbob | does one just setup attributes for ea. material and have the rt[blah] poll the material for that attribute, and if not found fall back to a default, or bail (depending on design)? |
| 02:55.24 | *** join/#brlcad poolio_ (n=poolio@c-71-206-215-46.hsd1.pa.comcast.net) | |
| 04:00.34 | *** join/#brlcad louipc-north (n=louipc@cable-66-206-254-196.dyn.personainc.net) | |
| 06:51.06 | brlcad | yukonbob: you're on the right track, but only a few of the tools understand that material type |
| 06:51.19 | brlcad | it basically is just a simple material identifier (i.e. a number) |
| 06:51.40 | brlcad | that number relates to a material type and a density |
| 06:53.03 | brlcad | which are either specified as a simple identifier to density mapping in an external file (e.g. rtweight) or as a table embedded into BRL-CAD (e.g. g_qa) |
| 06:55.56 | brlcad | at present, rtxray doesn't handle multiple densities. it basically presumes everything has the same density which iirc is specifically scaled so that it ranges from 1 to 255 per pixel. |
| 06:56.12 | brlcad | would be trivial to add, but nobody has asked/needed to date |
| 08:34.50 | *** join/#brlcad thing0 (n=ric@124-169-76-156.dyn.iinet.net.au) | |
| 09:22.38 | *** join/#brlcad elite01 (n=elite01@dslb-088-070-115-067.pools.arcor-ip.net) | |
| 09:30.36 | *** join/#brlcad hegemon (n=hegemon@cpe-66-87-4-181.ut.sprintbbd.net) | |
| 10:59.51 | *** join/#brlcad Elperion (n=Bary@p54876466.dip.t-dialin.net) | |
| 11:53.58 | *** join/#brlcad thing0 (n=ric@124-169-76-156.dyn.iinet.net.au) | |
| 12:32.32 | *** join/#brlcad elite01 (n=elite01@dslb-088-070-115-067.pools.arcor-ip.net) | |
| 12:52.55 | *** join/#brlcad elite01_ (n=elite01@dslb-088-070-030-029.pools.arcor-ip.net) | |
| 15:37.55 | *** join/#brlcad Z80-Boy (i=clock@77-56-84-204.dclient.hispeed.ch) | |
| 15:51.23 | *** join/#brlcad MinuteElectron (n=MinuteEl@silentflame/member/pdpc.base.minuteelectron) | |
| 16:14.04 | *** join/#brlcad Elperion (n=Bary@p54876466.dip.t-dialin.net) | |
| 17:23.24 | yukonbob | brlcad: thx for that info... I also played with rtrange, and I'm not sure that the plot file it generates is "good", as well as rttherm, which always seemed to bomb on me. |
| 17:47.48 | brlcad | rttherm does a different sort of ray-trace (actual multispectral) so I'm not too surprised with that .. not that it'd be too useful to you regardless |
| 17:48.04 | brlcad | though it .. shouldn't crash if the inputs are right, maybe a bug |
| 17:48.08 | brlcad | rarely tested |
| 17:58.30 | yukonbob | how's the West Coast treating you? |
| 17:59.34 | brlcad | well, I'm sitting by a pool right now, drink sitting nearby, laptop in lap .. crystal clear blue sky |
| 17:59.42 | brlcad | it's horrible |
| 18:00.33 | yukonbob | enjoy it... where's your usual home? |
| 18:00.50 | *** join/#brlcad Z80-Boy (i=clock@77-56-84-204.dclient.hispeed.ch) | |
| 18:58.57 | *** join/#brlcad Z80-Boy (i=clock@77-56-84-204.dclient.hispeed.ch) | |
| 19:50.51 | *** join/#brlcad CIA-4 (i=cia@208.69.182.149) | |
| 21:22.05 | yukonbob | what's the way to poll which elem a pixel is in when doing rtX analysis? |