I'm trying to create some text using txt2dat and this font:

https://github.com/sammdot/roadgeek-fonts



The characters are not curvy so there's something going wrong here. Does anyone have advice on how to get better results? Here's my command line:

I'm asking for an unofficial part. I need a "no left turn" roadsign, but it should use the modern snap-on clip instead of the old single piece design with the rectangular base from the 1970s/1980s.

Also, are the actual signs the same size, or are the old ones and new ones different dimensions?

Thanks!!

[edit]

I was able to do it myself. It was not very hard.

Hello to all,
I will upload the Space police III models that I made .
You can use it freely, I give it 'Free ONLY for NON-Commercial Use' .
At the time are referred as "Unofficial model" but only because they were not verified by other people.

Here are some notes for possible improvements.

They collected all the models of the Space police III series.

There are 15 box-sets that I organized in 1 mpd for each one.

If there are moving parts (hooks, trailers, tippers, ...), I created more ldr files for a single object in order to simplify a possible next animation.
In order not to complicate the archive, however, the wheels have been incorporated into the one file ldr of the vehicle.
In the mpd file of a box-set, each vehicle has its own independent structure (ldr file).

The basic idea is to assign names to the following :
xxxx [x ] - [ yyy ] - [ z ] - [ u]
xxxx [ x ] is the code box ( four or five digits)
yyyyyy is the option code for the second box , if the vehicle is a combination
z is the progressive optional for different independent models inside the box
u is a letter optional for the parts that make up the model , and that can move between them.

As for the choice of colors, I tried to respect those provided by Lego, but it is possible that some have escaped me.

I did not use stickers: I do not like in real life and I prefer not to use them even in the virtual world.
I did not realize the minifiugres in the box-sets.

Ldr files were introduced in the steps for building: do not reflect the official ones of the instruction manual.
The models are built bottom-up.

The vehicles are all oriented with the longitudinal axis x and muzzle in a positive direction.

Some parts, used to build the models, are not yet available in the official version LDraw.
What follows is the list of the missing parts in each model.

In box set 5974 is missing the part 32008 (Minifig flipper, used as deflector of the jet engine).
In box set 5980 is missing the part 59616 (Shell 6 3 x 12 x 5, used as railing).

Now stop write, it's time to load the models!
I hope you enjoy them as I liked building them!

Michael Heidemann Wrote:You can use MPDCenter to combine what you need into one single LDR file!
But there is no possibility to split that file later again into its components.
So for viewing purpose you can have what you like.

I have a couple of questions regarding Blender:

1. When you export a multi-model scene (such as an MPD file or other file with sub-models) to Blender, is the result a single large object? Or can each model be modified individually?
2. Which versions of LDraw parts get exported? Low resolution or high resolution?
3. Can I create scripts or macros in Blender that generate meshes? For instance, a script that generates a road surface in the shape of a spline?
4. Which is the best tool to export to Blender at the current time?

I'm trying to figure out how to better space multiple steps on a single page.
By default LPUB will centre the steps on the page, but I would like them to be more evenly spaced.
Where should I look for a local value that will help me to increase distance beteen steps? Or is there a better way to do this?

A long time ago I created a POV-Ray road generator.

http://lib.povray.org/searchcollection/i...Tag=SharkD

I was wondering if someone could create a native LDraw version of it. I'm not that familiar with parts authoring or "real" programming languages.

The tricky bits are the center dashes, so they could be omitted I guess.

Thanks!

[edit]

P.S. I also could never figure out how to calculate the proper amount of banking around a curve given a certain speed limit.

Hi,

a beta of the LDraw All-In-One-Installer 2015-01 can be found here:

http://www.holly-wood.it/tmp/LDraw_AIOI_...bit_v1.zip

This AIOI does no longer contain SR3D as well as Sticker Generator. LPub has been upgraded to LPub3D. Please note that the LDraw Parts Library as well as LGEO haven't been updated so far. This beta focuses mainly on the LPub3D upgrade.

Please test and send me your .logs, which can be found in the c:\Windows\LDraw folder, if you encounter any errors.

Thanks, w.

Hi all,

I'm (finally) nearing the end of implementing file reloading in LDCad 1.5 which leaves only one major 1.5 feature to add; namely editing shadow (part snapping) information.

This means I'm basically adding a (very basic) part editing mode to the main editor. I don't want to go full part editing support with LDCad (as LDPartEditor and others are much better at it) but I'm open to suggestions on part reviewing options etc.

so if anyone has some ideas on this, feel free to let me know as I'm still in the planing stage of this feature meaning everything is fair game

screen shot of a part being edited in the current editor (it's readonly and a bit of hack still though).

Some notes:
Part editing will only be available after enabling an 'advanced' option.
The shadow source and the part's source are shown joined as that is the way they are loaded/compiled internally. I'll add some separation line or something though.
Visualization of the snap data is the temporary one (available through F11 in the alpha's) and will be replaced by nicer / interactive ones.

Attached Files

Thumbnail(s)
   

Hello all,

Just wanted to share some thoughts about the current LDraw colors / LDConfig.ldr

The thing is I think we need additional 'material types' to be used with new colors.

Take for example rope, people usually use black (0) but imho it should have its own number with a 'nylon' finish just as 256 has a 'rubber' finish.

And speaking of rubber the modern pneumatic hoses in technic sets seem to use a more plastic like rubber, I think those need a different 'finish' too.

And a minor thing: Shouldn't the file use dos line breaks instead of Linux ones as dictated by the standard?

Thoughts?