1984 Technic sets

Just a notification for part admins: I observed that bush #4265c has a "moved to" reference to #32123, which in turn moved to #31123a. Maybe #4265c hat to be updated?

Guys,

as you might know I'm slowly authoring all the missing Western parts from the late nineties, which are missing in the library. Sooner or later the "last part standing" will be "Cloth Tepee Cover with ... Pattern":



http://www.bricklink.com/v2/catalog/cata...=1#T=C&C=1

It will be fairly easy designing a flat version in LDPC, but how do wrap the cloth? Any ideas? How about a wrapper prog for this kind of job?

w.

Looks like there is an issue with definition of TECHNIC_CHAIN_TREAD_38, see http://r.jander.me.uk/index.php/2016/11/...nd-treads/ ...

"Every nation gets the government it deserves".

Joseph de Maistre

Hi Roland,

Having a model with instructions that use MLCad arrows, prevents me from editing that model in LDCad?
It does load, slow, shows a big green + , then loads the model showing blue plus-signs on the studs and the anti-studs are shown in red.
Removing the MLCad arrow and loading the file again is fine.

Can this be fixed?

Jaco

I'm pretty sure I've asked this before many years ago, but my memory is not getting better.
Is it "legal" to let the polygons in a pattern overlap? Of course you can't allow this with different colors, that would look terrible. If I can use primitives in a pattern instead of handmade polygons, the result will look smoother. But if I can't do it without overlapping, is there any reason to disallow this method? I can't see that it would affect the quality in any way, but that hasn't stopped the leaders of the LDraw community from issuing standards rules before.

I believe lightblue has become a lot brighter after LDConfig.ldr was introduced. To the better, I think. Much more like the IRL color. The problem is, the bold "lightblue" patterns on the serires 3005pv*.dat are now much darker IRL than the LDrawn versions.

Also, the"blue" print on the older series are darker IRL and have a slight touch of purple (I think).

A third issue is that many of these files were made as a compromise between portraital accuracy and readability in smaller scales in original LDraw.

A forth issue is that these letters and digits have been made with several different fonts. I have no idea how many...

About the color issue, I'm about to complete the 3005pv*.dat series now. Should I continue coding it lightblue or should I pick a better color? If sp, which one?

I've been experimenting with options for converting native POV-Ray CSG objects to OBJ format, and now have a potential workflow to achieve this as detailed below:

Convert CSG to an Isosurface using William Pokorny's ObjectAsIso macro
Convert Isosurface to mesh using Jaap Franks macro
Convert mesh file to mesh2 format using meshcomp v3.0 (WinMeshcomp30_beta3.zip)
Convert mesh2 to OBJ using mesh22obj.py (a Python script written by ingo)

For more details on this approach see this post:
http://news.povray.org/povray.general/th...ay.org%3E/

I'm wondering if this approach would be useful for converting LGEO based parts to other 3D formats (or even reverse engineer parts that don't exist in LDraw). Are there any parts that only exist in LGEO?

Hi,

For some time i've tried to work out why in LPub, I cannot use the option under: Configuration - Page Setup - Background - Picture. I select an image from my pictures folder but it either hangs the system or greys out the page entirely. Is there a format / size that the picture needs to comply with? I am using Windows 7 Home. Everything else works well, I can add borders etc, I am using LPub 4.0.0.11.

Any help would be much appreciated.

Kindest regards
Steve