djm

My suggestion would be to submit details of the issue using https://github.com/trevorsandy/lpub3d/issues. That is what I did when I encountered issues and Trevor investigated and resolved the issues. If you supplyenough information (take a look at https://github.com/trevorsandy/lpub3d/issues/38 for an example), it will be very helpful to allow Trevor to diagnose and resolve the issue you are seeing. Regards, David

As an FYI for any users of LPub3D, an update (version 2.2.1) was recently released. This release seems to have addressed issues I had been experiencing with getting LPub3D to successfully render images using "faded" parts in versions 2.1 and 2.2. It appears to have also remedied an issue related to using POV-Ray to render images and POV-Ray is now successfully working for me to render images. My installation is a Windows 7, 32 bit machine, so you may not have been experiencing the same issues. The most recent version of LPub3D is available for download at https://sourceforge.net/projects/lpub3d/ Regards, David

Assuming you still have the original file, you might be able to use the "File/Export BOM" menu option. Export the BOM for the original file as an Excel spreadsheet. Export the BOM for the modified file as an Excel spreadsheet. Copy the content of one of the exported spreadsheets adjacent to the cells of the other exported spreadsheets. Some very simple comparison formulae on (a) the quantity columns and (b) the part # and colour code columns would quickly show you a summary of which parts were different (albeit without the actual location in the model). David

I revised the physical build of the trigger track, to eliminate a bit of a bump. The revised design now looks like: The spring in the NXT touch sensor is weak enough so that the weight of the train can push the axle down but strong enough to push the axle up after the train has run over the track. Building instructions are available for downloading. I've got a preliminary NXT program written (a joint activity with my son, to improve his programming skills) which successfully makes the switch move to the appropriate position for a train inbound to the switch. It requires two trigger track sections, one for the straight through and one for the turnout. Some additions are required to the program e.g. it currently assumes the switch begins in the straight position. Once the changes have been made, I'll make the program available for download. I may scratch an itch to see if I can come up with a mechanism to enable the touch sensor to be mounted horizontally. The premise being that it will reduce the mounting height required for the track. Regards, David [Link to my previous posting containing track building instructions].

Steamtrains, BR01 was created on September 11th and currently is sitting on 1439 supporters. There's Steamtrains, BR93, created on Septmeber 12th currently sitting on 392 supporters. His third engine BR52 was previously identified in this post, and currently has 393 supporters. David

@Mark Bellis has graciously given me permission to post building instructions for his design of monorail track curves and straights. There are building instructions available to download for; a curved track section a 16 stud long straight and a 32 stud long straight Regards, David [Link to the next of my posts containing building instructions]

Hi Mark, you would be more than welcome to link to (or upload if appropriate) those building instructions should you decide to progress a LEGO Ideas project. I would sound a warning that given the number of supporters Masa Hidaka gained (~1700) when he submitted his project , that the odds of one reaching the necessary level of support appear slight. Some good train projects on LEGO Ideas struggled to get enough votes so a monorail project may face an even tougher challenge. In the meantime, we can of course continue our design postings on EuroBricks - I am currently experimenting with building a "trigger" track section. The purpose of this section (if it works!) is to allow automation of a layout using NXT bricks e.g. changing the position of a switch for an inbound train. David

I think it was pulled because they forgot to include a more up-to-date ldraw.xml file. If only there was one available

@Mark Bellis has built a 4 track switch with a single servo motor (refer to pictures within his brickshelf gallery). I don't know whether or not it is able to go from any one setting to any other (e.g. from "A" to "B" directly and from "A" to "C" directly) or whether it has to step through each one (e.g. from "A" to "B" directly and from "A" to "C" but via "B"). David

It seems unlikely to me to be able to do this with one motor. I guess that there might be some cunning mechanical configuration where it could cycle between the three different settings using one motor but coming up with that would be way above my pay grade. David

Fully built double switch (please pardon the parts' colour selection!). Regards, David

This weekend I've worked on reverse engineering Masao Hidaka's monorail double switch, based on his youtube videos. I've got the substrate and gearing sorted and have created corresponding building instructions. The next step will be to add the track elements. In the meantime, here's a video showing the switch build-to-date in operation. Regards, David

@LEGOFUN, open the file "%ProgramFiles%\LEGO Company\LEGO Digital Designer\ldraw.xml". Check if the first line in the file looks something like: <LDrawMapping versionMajor="1" versionMinor="7" comment="MG beta 4.32 ldr-ldd_conver@gallaghersart.com LDD 4.3.6 Brick ver 1033"> or like <LDrawMapping versionMajor="1" versionMinor="7" comment="LDD 4.3.11 Brick ver 2670"> If it looks like the first one, you have not updated your LDraw.xml file. See the post from @SylvainLS above. When I restored the original LDD ldraw.xml file (i.e. the one that came with LDD) I see the behaviour you are experiencing i.e. missing parts. When I use the updated ldraw.xml file, the iissue you are experiencing goes away. Regards, David

Yes, if you switch to LDCAD, you can still use LPub. The tools MLCAD, LPub, LDCAD, LPub3D, etc all operate on LDraw files. If you try switching from one "equivalent" tool to another (e.g. from MLCAD to LDCAD) and decide you prefer your original tool choice, you can switch back and any changes to your model made with the newer tool will be visible in the older tool. As an FYI, within LDD I created a model with just the 15070 part in and saved it as an LDraw file. I then opened the "ldr" file using LDCAD and it successully shows the same part. That would suggest the issue is related to one of configuration on your machine. Regards, David

Assuming you have already selected the MLCAD menu option "File/Save As" and it has not solved the issue, might I suggest you go one step back. It was identified earlier in this topic that you need to get a more up-to-date customised part conversion file. Assuming you followed the instructions in that thread, after you had installed it did you then again save the model from within Lego Digital Designer as an LDraw file? The part conversion is done at the time your model is saved, so if you didn't save it after updating the conversion file, your LDraw model won't be as good as it can be. Regards, David P.S. I'd also suggest to look at using LDCAD rather than MLCAD for modelling with LDraw files. If you turn on "part snapping" (see "Basic brick placement using part snapping" within here) and consider whether to use it in "trackball" verses "spin" mode (see "The camera system" on the same page), your modelling experience will be more enjoyable.

This part looks promising to enable smoother curves. Refer to David

I saw this on BrickLink today, new for 2018. I don't think it has been identified in this topic before. Though it will be too pricey at the moment, having a 1x2 plate with round corners may result in smoother/more flexible curves, such as the "parts built" monorail curved track by Mark Bellis, especially if the 2x2 plates are replaced with 2x2 round plates. Regards, David

From Masao Hidaka's "how to" video to build a switch, I reverse engineered the switch as a LDraw design. I then created build instructions for the design and followed said instructions to test the build. Colours aside, the video below shows the build resulting from the build instructions. I am trying to contact Masao Hidaka to get his permission to make the build instructions available for downloading. Assuming his permission is forthcoming, I will post a link to the build instructions as appropriate. Based on another of his "how to" videos, I have also reverse engineered his monorail engine and carriage and created building instructions. I am seeking his permission to make the instructions available for download. Regards, David

I believe the newer design of the 20 tooth gear is the bottom right one and it has been out for a long while. I have some oldish LEGO and for my first attempt at the physical build, happened to grab a gear with the older design. David

From LegoMonrailFan's flickr pages, I reverse engineered the motor assembly and turned it into rudimentary build instructions. LegoMonorailFan has checked them for correctness and (after a tweak) they are available for download as a PDF file, The corresponding LDraw file is also available for download. Observations; the build space is tight. The 12 tooth double bevel to 8 tooth gear is one of the tighter (although valid) gear combinations. the 20 tooth bevel gear needs to be the mould variation without the two "knob" protutions on the back (see the image below) i.e. it needs to be the variation in the bottom right corner. The two "knob" variation (bottom left corner) will not work in this build. Regards, David

Go forward 70 centimetres (50 cm + 20 cm for circle radius) Turn left 90 degrees Go forward until the ultrasonic detector detects an object within the designated scanning ranged of the colour sensor (but no more than 20 cm). Scan the colour. If it matches, go forward X cm. If it doesn't match, stop.

Based on trial-and-error between myself and GREG998, if you are having issues with LPub3D not rendering all parts in the Parts List and/or the Bill of Materials, you may wish to try the following steps. This seems applicable to LPub3D version 2.0.20. Uninstall LPub3D. Reinstall LPub3D. During installation you will be prompted about whether to install a library now or later. Choose later. (Note my description is presently a little hazy as I am going from my recollection. If you want to help, please capture each screenshot during installation and PM me the images or a link to the images and then I can incorporate the screenshot into this description). Run LPub3D directly (i.e. invoke the executable rather than say double clicking on an ldr or mpd file) when logged in as the user id which will normally be used to generate build instructions. Exit LPub3D Follow the workaround instructions as specified in this post from the LDraw forums. Open LPub3D. Confirm (via the menu option Configuration/Preference in the Rendering tabbed sheet that the Preferred renderer is set to LDView, the LDView is installed checkbox is ticked and the Name field is populated with the path to the LDView executable. Try generating your building instructions! If someone who is currently having the issue wants to try the above and either let me know via a personal message or by posting as a reply to this thread whether or not this resolves the issue, I would appreciate it. I would especially appreciate getting screenshots of the installation dialog windows (see point 2 above) so that I can improve the description above. Regards, David

GREG998 and I have taken the issue diagnosis off-line. We shall post back with the resolution when we find one. David

So according to my post on the LDraw forum, it looks like I received that revision via the update within LPub3D. Can you try the menu option Help/Check for Updates... within LPub3D to see if it updates the version. David

Hmmm, apart from my typo in stating my version (I should have typed 2.0.20 revision 17 build 644), it looks like we have different revisions and build numbers; I have revision 17 and you have revision 0 and I have build 644 and you have build 645. Let me do some digging to see where I got my version from and I'll get back to you. The environment variables and preferences look to be appropriate. David