 | | Re: Proposed solution for mirrored parts and studs
|
|
(...) As you write below you can open ANY file. If no studs are mirrored, then no action takes place. (...) In stead of referencing studmirr.dat, why not simply use a mirrored reference to stud.dat? (...) No, same code. (...) Right. (...) If all (...) (21 years ago, 4-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: I need help with pov-ray
|
|
(...) Hmmm..tried that. It starts going thru the list on the bottom of the screen, then the colors.inc tab comes up and the error message appears. I tried to close colors again, but it always pops up when i try to render the file. -Spencer (who is (...) (21 years ago, 3-Jul-03, to lugnet.cad.ray, lugnet.off-topic.geek, lugnet.cad, lugnet.people.newbie, lugnet.publish)
|
| |
| | Re: I need help with pov-ray
|
|
(...) Close the file 'colors.inc' and try rendering the 'futurecar.pov' file instead. (see the tabs at the top of the screen?) HTH Allister (21 years ago, 3-Jul-03, to lugnet.cad.ray, lugnet.off-topic.geek, lugnet.cad, lugnet.people.newbie, lugnet.publish)
|
| |
| | Re: LSC Proposal 0.99a
|
|
(...) Works for me. -Tim (21 years ago, 3-Jul-03, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: I need help with pov-ray
|
|
In lugnet.cad.ray, Ahui Herrera wrote: SNIP (...) The LDraw site. (...) I finally got it to work, rendering car.dat and pyramid.dat with no problem. Now, however, i get this message: (URL) i try to do this file: (URL) not a deep link so plz wait for (...) (21 years ago, 3-Jul-03, to lugnet.cad.ray, lugnet.off-topic.geek, lugnet.cad, lugnet.people.newbie, lugnet.publish)
|
| |
| | Proposed solution for mirrored parts and studs
|
|
It's obvious that there is a lot of interest in the problem of mirrored studs, based on the volume of traffic in the ongoing thread. I have a proposed solution to the problem. My proposal is the creation of a small tool that automatically fixes a (...) (21 years ago, 3-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: PARTS.LST searching. (Was: Re: Part Fix 3959 Space Gun)
|
|
(...) Actually, I looked a bit further in the mklist.c code and it will READ up to 200 chars of part description, but then it truncates down to 64 chars before writing the part file. Apparently this is to be compatible with the old MAKELIST.EXE and (...) (21 years ago, 3-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Mirrored parts and studs
|
|
(...) Ouch--painful use of Dave! Oh, well. I knew my solution wasn't perfect, but it solved the immediate problem (while admittedly creating others). I'll still probably use it in my blasphemous clone.dats, if it's all the same to you folks. (...) (...) (21 years ago, 3-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Mirrored parts and studs
|
|
(...) Yes. But I'm not as willing as you are to see files changed, I guess (...) I think mirrored is more of a concern than misrotated, but that's just me. Would this meta work though? In other words, are there any parts that have studs *with logos* (...) (21 years ago, 3-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: PARTS.LST searching. (Was: Re: Part Fix 3959 Space Gun)
|
|
In lugnet.cad.dat.parts, Don Heyse wrote: <snip> (...) The PT currently limits you to, I think, 64 characters in the part name. I don't know wht this limit is imposed. I just test LEDIT with a long name and it didn't care. --Orion (21 years ago, 3-Jul-03, to lugnet.cad.dev)
|
