PerryMakes

8048 - Buggy [Vers 01] - Theme: Technic LXF File Errors: 2x 32580 Flex Rod 7m is impossible to position correctly due to limitations with LDD. Hopefully that gets addressed in an update at some point. 3647 (8 tooth gear) -was- able to be placed correctly, but I'm not thrilled with the appearance. Maybe some fiddling with the gears upstream would fix this, but I'd already spent too much time with this as it were... The front assembly wasn't able to be pushed in completely due to collision detection. I played with it for a while in order to get it fairly close... but like the previous issue, it was time to move on! No stickers. Cheers ~ Perry

Uh oh ... what's the difference between 60483 and 74695?? I finally got LDD Manager up and used it to generate the source parts for my next model. LDD has some strange behavior with regard to this part.

I'm still unable to get LDD Manager working on my system (WIn7 x64 + Office 2010 x64). I've installed the 2003 runtime, but that doesn't appear to produce any positive effect. That's great news though... meaning the model should be entirely complete! Regards ~ Perry

I'll second the request for Unimog parts - those are going to be essential... but in the meantime, I'd also like to see these two get some love: 32136 Technic, Pin Double with Axle Hole 2739 Technic, Link 1 x 6 Cheers ~ Perry Edit: Superkalle pointed out that 32136 is available as 32005 and 2739 is available as 32138. So essentially both parts are already available... yay!

(second session with LDD ... decided to kick it up a notch, and I definitely got that! At least now I know what the hinge align tool is for :) 8262 - Quad Bike - Theme: Technic LXF File Errors: found the parts I thought were missing (thanks for the help!) obviously no stickers Cheers ~ Perry

It seems to me that until you can do something as simple as combine chain links around gears and tracks around sprockets, LDD cannot be taken seriously as a day-to-day design tool. And it seems that rather than add that functionality, the solution the developers have taken is to remove the geometry from the application (i.e. 3711).

Done. By the way - I wasn't really saying that Access/Office was a poor development platform. I agree completely that it's very good at what it's good at (ummmmmmm... yeah). I will often times create a RAD prototype using the Office suite before expanding it in a more robust, full-featured environment (C#/VB.NET, C/C++, Python, Ruby, etc...) after procuring funding commitments from the customer. Having something tangible for the customer to see and interact with does wonders for that process! I'm just wondering why you've stuck with version 2003, which at this point is two versions old.

I was disappointed to not see this bug fixed... I'm quite sure that it was reported that at least one of these two pieces have a collision bounding box issue, but I'll report it again if it was misunderstood or accidentally overlooked... You can see that all panel fairing pairs except for 64394 + 64680 can be placed next to one another. Poor 64394 + 64680. They must be lonely... never being able to touch. Never knowing the comfort that comes from being forever bound by a trusty 2780. (I'll stop there... it's usually at this point where I start getting strange looks from my girlfriend, who's no doubt having second thoughts by now :) LXF File

Sorry... forgot to mention that I'm running x64 version of Office 2010 - which I think may be the culprit responsible for my problems (not the OS being x64). When you install the Office 2003 Runtime package (<complaintBox> wow that's old... any reason why you're still developing against this runtime???</complaintBox>) a test database is installed ("C:\Program Files (x86)\a2003rttest\a2003rt.mdb" on my system). I'm unable to successfully load that database normally - so I tried launching the .mdb while holding the SHIFT key (bypasses the startup screen). I'm presented with the following screens: http://www.brickshelf.com/gallery/PerryMakes/LDDManagerProblems/lddmanager1.png http://www.brickshelf.com/gallery/PerryMakes/LDDManagerProblems/lddmanager2.png http://www.brickshelf.com/gallery/PerryMakes/LDDManagerProblems/lddmanager3.png You can see on this last screen that the runtime has several 32bit Dlls that are most likely throwing a wrench into the system. Finally, when I try running the VBScript to launch LDDManager Access opens and displays this message... http://www.brickshelf.com/gallery/PerryMakes/LDDManagerProblems/lddmanager4.png EDIT: photos are now deeplinked (I wasn't aware that folders needed to be approved by admins!)

I apologize for my lack of willingness to read 14 pages of most likely non-related material to get the answer to a very quick, simple question... Is getting LDD Manager working on an x64 Win7 box a helpless cause? I've had zero luck. Any suggestions before I pull out a 32bit XP disc and fire up VMware? There are many other things I'd like to do with the next hour, but if that's the only way, I'm willing to sacrifice ;) Cheers ~ Perry

20200 - Space Designer (LEGO MBA Kit 1) [Vers 01] - Theme: Master Builder Academy Helicraft.lxf 20200 - Space Designer (LEGO MBA Kit 1) [Vers 02] - Theme: Master Builder Academy Rocket.lxf 20200 - Space Designer (LEGO MBA Kit 1) [Vers 03] - Theme: Master Builder Academy SpaceFighter.lxf Errors: none that I'm aware of, but as mentioned above this is my first go at this! Cheers ~ Perry EDIT: I originally had these modeled separately, but was trying to following directions exactly! You can now download them individually.

Okay... who's going to be the first with a "murder saw" built for their Unimog? ;)

Add my support to the list. Contacted both eBay with a report and the seller... but I took a very different approach, in hopes of getting as much information as possible - something that people are reluctant to give when they think you are "out to get them." Here's my email to him and his response: -------------------------- Dear rower_24, I'd like to know, before dropping 4 bills on this, what are the features you've changed to make it better than Jergen's Lil' Devil? Everyone's complaining that you stole his design, but what they don't understand is that you've CHANGED it... duh! So it's obviously not the same thing as what he designed... so it's a NEW product. Some people just don't get it. But I would like to know what I'm going to be getting that's better. Thanks in advance and Cheers. -------------------------- Could you link me to the thread where everyone is complaining about it? To be honest I have not changed much, I have added some attachments to hold everything together better and some color schemes. I removed some parts that I felt were unnecessary and simply increased the weight. There was probably a change of about 100 parts or so. The main thing that you're paying for is the time to put it all together and the time it took to source all of the parts. Let me know if you have further questions. - rower_24 -------------------------- From his response I'd say that it's a pretty cut-and-dry instance of thievery. Please excuse the method I had to take in order to get a truthful response ;) Cheers ~ Perry EDIT: I should add that I -did not- send a link to this discussion. The fact that he's unaware of this says two thing... 1) he's a TERRIBLE Googler 2) he's not aware of and not part of the general/common community built around this hobby. Probably a good thing :)

VERY nice job.