 | | Re: Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) Because parts with inline POV code work with the version of L3P that we have now. Why not start by building a library of modified official parts, but with the explicit goal of eventually converting them into POV only parts when L3P or some (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest? [DAT]
|
|
(...) Here is my $0.01.... This is how I have started handling Ldraw/PoV parts: The 3626bp6f.dat is availabe on the parts tracker here: (URL) is some line wrapping happening here, I will need to fix it later) 0 Minifig Head with Female Eyes with Red (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Inline POV code in official parts?
|
|
(...) I agree with Steve on this issue: no POV code in offical parts with the possible exception of primitves. I feel this way for a few reasons: - It could be construed the POV is the Official rendering program of the LDraw.org library. This can (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) Why not just a library of POV code only parts, ala LGEO/Raves, only compatible with the LDraw.org library? We could host this project on Sourceforge so anyone who was interested could develop. I think if we do it Pov only, LDraw.org is more (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Repository of .dat files with inline POV-Ray code... any interest?
|
|
(...) Okay... then I'd like to open this up to a question for the community: Is anyone interested in working on a single shared repository of ldraw-compatible parts with inlined POV-Ray code? How many authors out there are comfortable with both (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: LDraw.org Config File (was: Edge line colors on img.lugnet.com)
|
|
(...) ... (...) ... I'm working on a Track Designer-like program; I'll be presenting it at BrickFest. My program, TrackDraw, can read and write LDraw files -- I've also created a color definition file (in XML) that is very much like Steve's -- so (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: LDraw.org Config File (was: Edge line colors on img.lugnet.com)
|
|
(...) hmm ... I suppose this will become a some sort of standard color chart for a handful of progs? are we sure that the ldraw colors are the right ones (makein' the devils advocate)? looking around I found at least three different values for (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: LDGLite outputting gobble-dee-goo to terminal window
|
|
(...) Less that a second for my Mini, but it is mini :) About 4 seaconds for my black tank car, which has 284 (?) parts. About 8 seconds to draw my GP30. The dat for the GP30 has 817 lines (not all of them are parts). Redraw the model every time... (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev.mac)
|
| |
| | LDraw.org Config File (was: Edge line colors on img.lugnet.com)
|
|
[XPFUT lugnet.cad.dev.org.ldraw] (...) A little more has happened on this: I emailed the authors of most of the LDraw-compatible software packages, and asked for buy-in on this idea. Basically, my thought was that we needed to have agreement about (...) (21 years ago, 29-Jul-03, to lugnet.cad, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Inline POV code in official parts?
|
|
(...) Yes, it's pretty much still the case. I would really prefer to not have any POV code in the parts library at all. But if there must be some, I think it should stay in the primitive files. (...) I think a better solution is to work on POV (...) (21 years ago, 29-Jul-03, to lugnet.cad.dev)
|
| |
| | Inline POV code in official parts?
|
|
What's the current plan for POV-Ray code in official parts? I have been out of the loop for a while, but my last understanding was that parts with inline POV-Ray code don't have any chance of getting certified on the parts tracker. Is this still the (...) (21 years ago, 28-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: LDGLite outputting gobble-dee-goo to terminal window
|
|
(...) Found a much more recent post on this indicating that it may still be a problem with current Macs... Also contains a bit more info as to what's really going on. (URL) The only workaround I can think of is to (...) (21 years ago, 28-Jul-03, to lugnet.cad.dev.mac)
|
| |
| | Re: LDGLite outputting gobble-dee-goo to terminal window
|
|
(...) (URL) guy found the same bug on his Mac. Writing to the GL_FRONT buffer seems to also write over whatever you may have stashed away in the GL_BACK buffer. The only workaround I can think of is to copy the image to regular system memory, or (...) (21 years ago, 28-Jul-03, to lugnet.cad.dev.mac)
|
| |
| | Re: Primitive substituion and part reviews
|
|
(...) They should not warrant a Hold review. Put comments in the review, and if you think the issue is serious enough, go for a NoVote review. (...) If the pattern allows, it would be good to add a color-matched ring primitive around the outside of (...) (21 years ago, 28-Jul-03, to lugnet.cad.dev)
|
| |
| | Primitive substituion and part reviews
|
|
To what extent, if any, should rendering errors caused by primitive substitution warrent a Hold vote on the PT? An example of this would be a disc shaped pattern surrounded by a ndis. Would it be appropritate to add a small, color matching ring (...) (21 years ago, 27-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: rotating models in MBC 0.4.1d Cocoa
|
|
(...) Sounds like the next release it going to be a good one! Out of curiosity, is there a bug in the train motor part? Chris (21 years ago, 26-Jul-03, to lugnet.cad.dev.mac)
|
| |
| | Re: rotating models in MBC 0.4.1d Cocoa
|
|
(...) As an update to this comment, I have now placed the glFinish() command and the timing loop into the render instance, and now I get correct behavior. It's clear that Cocoa creates a new thread for each instance, therefore as guessed before, (...) (21 years ago, 25-Jul-03, to lugnet.cad.dev.mac)
|
| |
| | Re: LDGLite outputting gobble-dee-goo to terminal window
|
|
(...) So you're saying that if I ask for the GL_RENDERER etc strings after a window resize I'll get the same ones I started with no matter what? (I added some code to check it anyway just in case) That really sux. Who designed that feature, (...) (21 years ago, 25-Jul-03, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
| |
| | Re: LDGLite outputting gobble-dee-goo to terminal window
|
|
(...) OK, I looked at the code above, and all it seems to do is tell its OpenGL context to update every time the window is resized. If their glut doesn't do this, then it is broken. As far as I know, there isn't any equivalent to this in Windows. (...) (21 years ago, 25-Jul-03, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
| |
| | Re: LDGLite outputting gobble-dee-goo to terminal window
|
|
(...) Found some more info. This makes it even more clear. (URL) it only shows icky Cocoa code. I may have to examine the apple glut sources to see how much of this is actually handled in glut. I wouldn't be suprised to find some bugs there. And I (...) (21 years ago, 25-Jul-03, to lugnet.cad.dev.mac, lugnet.cad.dev)
|
