 | | Re: Spot the bug
|
|
(...) Use i i.s.o. j - it's easy when you know where to look ;-) (...) Wish I could see it... /Lars (23 years ago, 4-Mar-02, to lugnet.cad.dev)
|
| |
| | Spot the bug
|
|
In this bit of code I wrote months ago, I finally discovered the bug. Or two. Can you? if (mRendererType->IsGL()) { // different 4x4 matrix convention requires transpose GLfloat m[16]; for (int j=0; j<4; j++) { for (int i=0; j<4; j++) { m[i*4+j] = (...) (23 years ago, 4-Mar-02, to lugnet.cad.dev)
|
| |
| | My LDraw Inliner
|
|
Since I have troubles with all inliners I've found, I decided to make my own. I also included the Delphi 4 source if anyone likes to study it. (URL) and Carsten: Sorry, your inliners won't work on my system. They should work, but I don't know why (...) (23 years ago, 4-Mar-02, to lugnet.cad.dev)
|
| |
| | Re: *** LDView Version 1.9.2 Released ***
|
|
I installed the 23.11 driver, after that i see the model (the standard car.dat). Except sometimes spikes apear from it, as if some coordinates lie far outside the model. After a few spins it lockes up the whole system. I also tryed the asus driver (...) (23 years ago, 3-Mar-02, to lugnet.cad.dev)
|
| |
| | Re: ** MLCAD V2.12 **
|
|
(...) Was just about to email you & tell you this when I saw your post 8?) Thanks ROSCO (23 years ago, 3-Mar-02, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: ** MLCAD V2.12 **
|
|
Wow! What great new features!! Both two things I have been waiting to see for some time!! (...) Under "Edit" > "Sort" (...) Under "Edit..." > "Add" > "Autosteps..." I also just noticed something else new. I am not sure if this has been added in the (...) (23 years ago, 2-Mar-02, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: ** MLCAD V2.12 **
|
|
Some strange problem occured during packaging the new version. I've tried the executable in the zip-file and in my case it crashed all the time ... no idea what's going on. However I repackaged everything and now it seems to be fine ... Please (...) (23 years ago, 2-Mar-02, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | ** MLCAD V2.12 **
|
|
I happy to announce that MLCad V2.12 is out now. The most importand change in this release is the bug-fix for the unsolicted crash of MLCad, some corrections for LDR and two new things: - Sorting of parts in a model by color, name or position - (...) (23 years ago, 2-Mar-02, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: A study on a train front....
|
|
(...) Excellent use - I had a feeling someone would find an imaginative use for these - hence (URL) one seems to have more potential uses than the related parts with "wings". Chris (23 years ago, 1-Mar-02, to lugnet.trains, lugnet.cad.dev)
|
| |
| | Primitives based on other primitives?
|
|
Hello! I noticed in part tracker this part from Paul : Part 4-4ring9 - Hi-Res Ring 9 x 1 Its based on another primitve 1-4ring9. My question is: Does it make sense? IMHO this is only slowing down programs and isnt really helpful. Any comments on it? (23 years ago, 1-Mar-02, to lugnet.cad.dev)
|
| |
| | Re: DirectX and .dat
|
|
Thanks all, I am going to concetrate on them normals then. I even got some ideas on how to determn the correct direction for them by examening base lego parts. But first things first, back to math class for me :) Roland (...) (23 years ago, 1-Mar-02, to lugnet.cad.dev)
|
| |
| | Re: Inline POV-Ray code? [DAT]
|
|
I see now that your problem is difficult to solve. Sorry I tried to put it into a nutshell, Steve. My preference would be to design an auxiliary file for each case, and markup the LDRAW part in a very general way, so that future programs could (...) (23 years ago, 1-Mar-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: Inline POV-Ray code?
|
|
(...) Right! I have always thought of the "0 IFNDEF L3PPOV" as a way to utilize most of the normal LDraw lines (that L3P can convert to equivalent POV code) and only replace a small tricky curvy section by some POV code that would look better. This (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: Inline POV-Ray code?
|
|
(...) When I wrote this message, I was trying to figure some rational way to mix LDraw and L3P/POV-Ray code. Something like: 0 IFNDEF L3PPOV (ldraw code) 0 ELSE 0 #if (STUDS) 0 LDRAW 0 1 16 0 0 0 1 0 0 0 1 0 0 0 1 stud2.dat 0 LDRAW END 0 #end 0 (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: Inline POV-Ray code?
|
|
(...) I'm not following. Are you agreeing with the idea of using embedded POV-Ray code, or having separate file libraries? I *think* you agree with the second, am I right? The one thing we gain by having embedded POV-Ray code is the ability to have (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: Inline POV-Ray code?
|
|
In a nutshell, 'namespaces'. Switching among parts libraries to get different versions (or different data) should be an application capability, not the individual part file. (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: Inline POV-Ray code?
|
|
(...) Well, if thats how you really feel, then why even bother to "write up a spec/reference page on 0 IFDEF" at all. The instant you put the line: 0 IFDEF <code> in a part file you're blessing a non-ldraw extension. The <code> is by definition a (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: Another stupid part-authoring question (Primo?!?)
|
|
(...) Yes, the stud is hollow. The studline substitution would leave a hole 56 (or at least 48) LDU across... big enough to fit a microfig-scale capital ship. -- Tony Hafner www.hafhead.com (23 years ago, 28-Feb-02, to lugnet.cad.dev)
|
| |
| | Re: Inline POV-Ray code?
|
|
In lugnet.cad.dev, Don Heyse writes: [snipped things down a bit] (...) Generally, yeah. But mostly to the extent that I haven't thought it through enough. (...) That could work, but IMO only pushes the issue to the side. To some extent, LDraw.org (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: New tool: LDDesignPad 0.3 for LDraw
|
|
Hello Ryan, i looked at the problem and you are right. I will fix it in the next version because current one is almost bug-free and in want ti implement one or two more features. Thanx for telling Carsten "Ryan Farrington" <ryanjf@ifriendly.com> (...) (23 years ago, 28-Feb-02, to lugnet.cad, lugnet.cad.dev)
|
