Does any one know why Pov Ray wont render the Technic Gear 16 Tooth with Clutch Smooth/ and not smooth.
It will get to this point and stop
object {
LDX_48_slash_4_dash_4ri100_dot_dat_in_part (this line highlighted in yellow)
matrix <0.17,0,0,0,0,-1,0,0.17,0,0,0,10>
I have updated the part list and also tried updating just this part. LDview shows it just fine.
Cheers Jono

Jet another version of 3044 Slope 45 2 x 1 Double is existing and not in the library.

3044c @ bricklink

Would be nice somebody could make it.

Thanks in advance.

Hello all,

I've been working on part snapping for my LDCad editor. It's progressing nicely but I would love some feedback / opinions from people in order to fine tune things.

The current version works quite nicely with low connection point parts. The problem arises when you use parts with multiple valid snap points (e.g. the holes in 1xn tech beams). Currently it snaps based on z sorting, but there is room for improvement there.

I've uploaded short clip of the feature in action.

The used scene contains most of the parts with full snap information. Snapping is done 100% trough meta information on the existing part files. This is done using a shadow library, which acts like an auto include location. Content of identical named files in the shadow location are added to the official ones from the LDraw lib during loading. Information can also be inherited as a result all minifig torso/leg/hip/hand/arm parts have information by just creating 6 shadow files.

edit: second version, see below post.

Second version demo clip


All suggestions are welcome

LDView reports several missing files for the attached model. Where are the missing parts? Can someone fix it?

Thanks!!

[edit]

Also, where do I find part 4106? It seems to be referenced by another part, but is not rendered.


Mike

Attached Files

  building_074_mediumfactory.mpd (Size: 21.51 KB / Downloads: 0)

http://www.dexterindustries.com/dGPS.html

Hello. I am having trouble getting Pov Ray 3.6 to do a render of any ldraw model. I keep getting this error that opens up in another tab under lg_color.inc

[color=#33FF33]/********************/
/* SOLID COLORS */
/********************/

// 0 BLACK / 26 BLACK [ORIGINAL LGEO srgb]
// LDRAW
// PEERON <27,42,52> (LOOKS TOO BLUE)[/color]
#declare lg_black = texture {
pigment { color srgb <33,33,33>/255 } [color=#000000]((on this line it is high lighted yellow with a flashing marker))[/color]
finish { lg_solid_finish }
}

at the bottom of the Pov Ray window it states 'Parse Error; No mathching } in pigment', undeclared identifier 'srgb' found instead'

Ive used the all in one installer and from what ldraw states the parts library is up to date. Im using win 7 64 bit.
Does anyone know what this problem is and how I can either fix it or get past it.
also I have only used the colors that are on MLCad to do the model then exported it from ldraw to pov ray.My pov ray ini file states this:
;
Library_Path="C:\Program Files (x86)\POV-Ray for Windows v3.6\INCLUDE"
Library_Path="C:\Windows\Fonts"
Library_Path="C:\Program Files (x86)\LDraw\LGEO"
Library_Path="C:\Program Files (x86)\LDraw\LGEO\lg"
Library_Path="C:\Program Files (x86)\LDraw\LGEO\ar"

Cheers Jono

I'm looking for the 64227 (Set 8879) Power Functions IR Speed Control Remote.  I don't see it on the tracker.  Has anyone worked on this part?

um ok

Hello.
A new version of Buf3D (Android Ldraw Viewer) is available in

https://play.google.com/store/apps/detai...plus.buf3d

The news:
- Support for submodel selection (in MPD files & multiple dat files)
- Play Instructions (steps & parts in step)
- Specular light

Know bugs:
- In some models the instructions differ from original file. We continue to work to resolve.

I am starting to work on the new Technic axle pin long (11214). As you can see on this photo, there are several little differences with other existing long pins (middle slit is xhort, no slit on base but 3 (not 4) thin ribs there). I guess I must create a new geometry for this...
Question is, is it worth creating primitive(s) for this new geometry, that will probably be used only here? If so, create one primitive for base and one for tip, or just one primitive for the whole pin part?
For the record, confric8 is only used in 6558, confric9 in 32054, and confric7 (certified but still on PT) is not used at all.