Subject:
|
BFC checking program (was Re: Some Words To BFC)
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Fri, 7 Apr 2000 14:41:22 GMT
|
Viewed:
|
2183 times
|
| |
|
|
Steve Bliss wrote:
>
> The primitives should be the first thing fixed, in any case. :) I
> think it would be safe for the cleanup program to assume that primitives
> are BFC-ready. Which could be a help for automatic cleanup of part
> files.
I'm assuming that you're calling "BFC-ready" primitives that have all
faces in the same direction. Primitives are not closed volumes so you'll
always be able to see the backfaces.
> Some technical points:
>
> I don't think this issue (to INVERTNEXT or to clone primitive files)
> will be decided on technical issues.
I agree technically it doesn't make much difference, I just think it's
easier to have another set of primitives (in another directory of with
another name) but that's how I feel.
> I think the key issue is which approach makes it easier to code DAT
> files, and maintain the parts library. Unfortunately, I don't have much
> of an opinion here, except that having extra files means parts authors
> have more to learn about p-files, and there would more files which would
> need to be maintained. From a language point of view, the difference
> between the two approaches is strictly syntactic. And if the cleanup
> program can detect inversion automatically, then neither approach puts
> any burden on the author.
Me too.
> > If anyone wants to take a look, just ask. I don't have the time to
> > create a web page and make something official so I'll need some help to
> > finish the program.
>
> I'm asking. :)
I have uploaded the program to http://gerf.org/~leo/editor.zip (source
+ precompiled exe) there's no homepage or docs so please read this
before you ask any questions.
This program was going to be a new editor to create parts easily with
solid primitives and CSG but I never got very far so there's a lot of
weird code that you can ignore. I haven't touched this code for a while,
I tried it today and it was still compiling but there might be some
hardcoded paths to my LDraw dir somewhere in the program.
The algorithm is not perfect but is a good start, it detects most
wrong faces and fixes them. There are several other algorithms that can
be implemented to make the detection work better, if someone wants to
continue the project I can list some ideas.
The code is just for testing purposes so it inlines all primitives
before checking what's wrong. An idea I just had is to ignore the studs,
I don't know if there are any parts where it would make things worst but
that's an idea that should be easy to try or even add as an option.
Almost forgot: Run the program, open a file and click on the red
triangle icon to fix the backfaces, then you can use the zoom/rotate
tools to view the part from different angles.
I hope to be able to help the comunity with this.
Leonardo
|
|
Message has 2 Replies:
 | | Re: BFC checking program (was Re: Some Words To BFC)
|
| (...) Umm, it's a little more than that, but facing the faces is a very important part. Basically, I meant: 1. All polygons wound correctly 2. All subfile references clean Good point about primitives not being solid. I don't think a renderer (...) (24 years ago, 7-Apr-00, to lugnet.cad.dev)
|
Message is in Reply To:
| | Re: Some Words To BFC
|
| (...) The primitives should be the first thing fixed, in any case. :) I think it would be safe for the cleanup program to assume that primitives are BFC-ready. Which could be a help for automatic cleanup of part files. (...) Some technical points: (...) (24 years ago, 6-Apr-00, to lugnet.cad.dev)
|
61 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
