 | | Re: Another LDDP plugin question.
|
|
(...) Yeah, that's all I had to go on. I had the most trouble getting the exported function name decorations to match. Never did that before. Since all your DLLs seem to have the same symtom would you mind contributing the source for one (or more (...) (21 years ago, 8-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Another LDDP plugin question.
|
|
(...) For ldglite I've been emulating LEDIT, so that means the same position as the previous part, but unrotated. This works pretty well when you're building in LEDIT mode because it's right where you're working and it's easy to move it to someplace (...) (21 years ago, 8-Jul-03, to lugnet.cad.dev, FTX)
|
| |
| | Re: Another LDDP plugin question.
|
|
(...) What would the position and matrix be? I see two possibilities: Same position amd mtrix as previous part 0,0,0 and Indentity Matrix Of course we could add the ability for the user to choose between the two or input desired default position or (...) (21 years ago, 8-Jul-03, to lugnet.cad.dev, FTX)
|
| |
| | Re: A Plea from a greenhorn (Re: WOULD YOU PLEASE...)
|
|
(...) Ok, after this thread and some off Lugnet discussion, I've come to a firm opinion. I will refrain from ANY part modfications on non Official Library parts and then subsequent posting on the PT. I will modify parts and Email them to the authors (...) (21 years ago, 8-Jul-03, to lugnet.cad.dev, FTX)
|
| |
| | Re: Another LDDP plugin question.
|
|
I am using Delphi 3, which is (besides Delphi 1) the only version I've got. I haven't experienced writing DLLs before the LDDP plugins. The only info I had was the sample included with LDDP. Niels (21 years ago, 8-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Another LDDP plugin question.
|
|
(...) Ok I fixed the problem in the ldlist plugin and replaced the zip file. Turns out I had to use the WINAPI convention and add an alias to the .def file to make LDDP happy. I wonder if it's a similar calling convention problem with the track and (...) (21 years ago, 7-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Another LDDP plugin question.
|
|
(...) I think he might have mentioned an older version of Delphi. Anyhow, I suspect it may be an issue with Delphi vs gcc. I got my ldlist wrapper plugin working in ldglite, but it doesn't work in LDDP. I added some debugging and saw LDDP call (...) (21 years ago, 7-Jul-03, to lugnet.cad.dev)
|
| |
| | A Plea from a greenhorn (Re: WOULD YOU PLEASE...)
|
|
(...) I agree, it is a little frustrating. I'm still a fledgeling author, and I need to learn what I'm doing wrong. Having somebody come through and make these edits before I get a chance to look is not making me a better author. I need to be able (...) (21 years ago, 7-Jul-03, to lugnet.cad.dev, FTX)
|
| |
| | Re: Another LDDP plugin question.
|
|
(...) I have no idea what the problem could be unless Niel used an older version of the plugin code. This shouldn't be an issue with Delphi. --Orion P.S. All the current developers at the LDDP project are using Delphi 6 or higher. As far as what (...) (21 years ago, 7-Jul-03, to lugnet.cad.dev)
|
| |
| | Another LDDP plugin question.
|
|
I'm not sure what the problem is, but I'm running into memory problems with some of the LDDP plugins. I wonder if it's some sort of incompatibility with a particular version of Delphi used to build the plugins. Orion's plugins don't exhibit the (...) (21 years ago, 7-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: WOULD YOU PLEASE...
|
|
(...) I agree that it affects every line in the part but my point is the triviality of the moving the part. If the origin is 1 LDU off of what it should be, it's fairly trivial to move it. -Orion (21 years ago, 7-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: WOULD YOU PLEASE...
|
|
[crossposted to lugnet.cad.dev, with followup-to set there as well -- this thread isn't about posting LDR files to lugnet] (...) If anyone is not sure about the general rule/protocol/guidelines on this: for new parts (not fixes), you should *always* (...) (21 years ago, 6-Jul-03, to lugnet.cad.dat.parts, lugnet.cad.dev)
|
| |
| | LDDP plugin API suggestion.
|
|
(...) It looks like ldlist gets the LDRAW path from the LDRAWDIR environment variable, and this made me think about the LDDP plugin API. Doesn't it make sense to pass the LDRAW path to the plugin via an argument to the ProcessText() fn? This way the (...) (21 years ago, 5-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: PARTS.LST searching. (Was: Re: Part Fix 3959 Space Gun)
|
|
(...) Heh, I already borrowed the idea of narrowing the search as you type from ldlist. I also already added drag and drop support from ldlist. But I need a better screen shot to show that in action. (URL) now that I think about it, I should (...) (21 years ago, 4-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: PARTS.LST searching. (Was: Re: Part Fix 3959 Space Gun)
|
|
(...) LDList makes a partlist of it's own, and saves the keywords too. You can search for a part by AND-ing separate words, or exact quote. (URL) (Both .exe and Delphi source) You're free to use any ideas you can get from it. -- Anders Isaksson, (...) (21 years ago, 4-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Proposed solution for mirrored parts and studs
|
|
(...) I'll look into that. I thought it would be easier to reference the other file, but thinking about it again, I guess I should be able to multiply the mirror matrix by the stud matrix to get the correct final matrix anyway. (Or would that be (...) (21 years ago, 4-Jul-03, to lugnet.cad.dev)
|
| |
| | 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)
|
| |
| | 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)
|
| |
| | PARTS.LST searching. (Was: Re: Part Fix 3959 Space Gun)
|
|
(...) Right now it seems to be listed on the parts tracker as "Bar 1.5L with Handle and Female Stud". I just added a PARTS.LST search capability to ldglite: (URL) there's nothing in that name that would help me narrow the search to find the part. (...) (21 years ago, 3-Jul-03, to lugnet.cad.dat.parts, lugnet.cad.dev)
|
| |
| | Re: Mirrored parts and studs
|
|
(...) A fair point, but how often would that happen, realistically? Enough to be a problem? Even if one or two parts eventually turn up like that, why would the whole system have to be jettisoned for those few exceptions? (...) I'm not sure that (...) (21 years ago, 3-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Thanks to all the parts developers
|
|
(...) I want to join to the thanks... As I have done a few (easy) parts, I know how tedious it can be... And thanks to the hawk-eyed part reviewers, who help to keep standards high ! Philo www.philohome.com (21 years ago, 3-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Thanks to all the parts developers
|
|
(...) I would like to do so as well. It sounds like a lot of work. -Mike (21 years ago, 3-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Thanks to all the parts developers
|
|
(...) Of course I join to part authors praising. Part authors can't be praised enough, especially as new parts quality is so much high. And of course we want Willy Tschager's space parts to be certified and released as soon as possible. Damien (21 years ago, 2-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Mirrored parts and studs
|
|
(...) After thinking about it for a while, I totally agree. If anyone wants to make perfect rendering with stud logos lined up correctly (how often does this occur?), I assume this person must have the knowledge to inline that part locally at (...) (21 years ago, 2-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Mirrored parts and studs
|
|
(...) Correct. There's no way to know if they actually face the right direction, so I just figured that horizontal mirroring was more likely to be correct than vertical (although I could be wrong). (...) You can, but my code that decides which (...) (21 years ago, 2-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Mirrored parts and studs
|
|
(...) Actually that does help a bit. It looks like you aren't concerned with whether the logo faces the same direction as on the actual part, you're just ensuring that it's readable. That makes me feel better about my solution. By the way, why do (...) (21 years ago, 2-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Thanks to all the parts developers
|
|
(...) thx to you kevin for makin' pov-rendering a piece of cake. toying around with all this cryptic pov-code was never easier. w. (waiting to see his space parts certified, especially the crater plate - reviewers please!) (21 years ago, 2-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Mirrored parts and studs
|
|
(...) I don't actually do any transformations in LDView to get the logos right. I just detect the mirroring (by tracking negative determinants and flipping the mirrored bit every time I see one) and modify my texture coordinates to un-mirror (...) (21 years ago, 2-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Mirrored parts and studs
|
|
(...) Yeah, I did a search for determinant and found your note. I tried the on-the-fly fix in ldglite with the L3 structs and it seems to work, although I'm not sure I'm applying the fix correctly. Is it really as simple as multiplying some matrix (...) (21 years ago, 2-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Mirrored parts and studs
|
|
(...) We definitely don't want to do this. It's unnecessary, because the sign of the determinant in the matrix specifying the sub-part tells you whether the sub-part is mirrored. The above might allow the program to do less math, but that's not an (...) (21 years ago, 2-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Mirrored parts and studs
|
|
(...) Yes. That's what LDView does. --Travis Cobbs (21 years ago, 2-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Mirrored parts and studs
|
|
(...) Umm, my math is really rusty. Can the sign of the determinant also be used to detect mirroring? That could be handy. Don (21 years ago, 2-Jul-03, to lugnet.cad.dev)
|
| |
| | Thanks to all the parts developers
|
|
I just wanted to say thanks to Steve, Chris and all else that are involved with the developent, review and approval of the parts in the parts library. Programs can come and go, but without the parts library we'd have nothing. I think that the parts (...) (21 years ago, 2-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Mirrored parts and studs
|
|
(...) Wait a minute. Doesn't L3Input.cpp build a threaded tree structure before outputting a single POV part? I would think you could traverse the array Parts[0...nParts] and look for toplevel parts from the PARTS directory. Then for each toplevel (...) (21 years ago, 2-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Mirrored parts and studs
|
|
(...) My view is that there is nothing _serious_ wrong, but that a fix should be welcome. Anyway. Since we are only talking about studs, the rendering programs _could_ simply remember to fix any mirrored studs (can be done by multiplying the (...) (21 years ago, 1-Jul-03, to lugnet.cad.dev)
|
| |
| | Re: Mirrored parts and studs
|
|
(...) My only concern about letting the rendering programs do this is "how they know which way to orientate the logo". Coding this within the .dat file (either with a correctly orientated stud.dat or with metadata) is preferable to storing this (...) (21 years ago, 2-Jul-03, to lugnet.cad.dev)
|
