there was this post on the Studio forum about rendering errors in POV-Ray. I’ve a déjà vu feeling with these errors.
Studio uses LDView’s code to export to POV-Ray and also uses LGEO for the exported 3D models.
I checked for 608p03: Studio’s .inc is the same I have from LGEO (which I believe is up-to-date, it’s been a while I have used it but, if I’m not mistaken, the last updates are “only” Darat’s high-def ones).
So I think it’s an error in LGEO… or it maybe something in the POV-Ray code/options but then I don’t see what it could be.
Hi everyone! For a while, me and my friend, Lehvak Nuva've been working on bionicle parts Stud.io mod. Recently, he asked me to share his parts on LDraw, so I took best ones and put them here
#declare LDXCameraLoc = < 447.158142,-351.187286,-446.14975 >; // Camera Location vector
#declare LDXCameraLookAt = < 4.58077876387164906191,10.17561232900345657981,-3.57247258550586366255 >; // Camera look-at point vector
#declare LDXCameraSky = < -0.35355329881115843405,-0.86602543005723520153,0.35355341802042911103 >; // Camera sky vector (<0,-1,0> will usually work for standard "up")
vs :
Case 2 :
Code:
#declare LDXCameraLoc = < 707.842224,-354.348816,-707.842224 >; // Camera Location vector
#declare LDXCameraLookAt = < 2.24497200047949263535,8.84444866651756456122,-2.24497200047949263535 >; // Camera look-at point vector
#declare LDXCameraSky = < -0.24184478580022841787,-0.93969260886871053273,0.24184478580022841787 >; // Camera sky vector (<0,-1,0> will usually work for standard "up")
Obviously, in the first case, the camera is too close and my renders are cropped. I bypass the problem by tweaking LDXCamAspect and angle, but the result is not what I want and what I've set up. I can go with it for now, but it's strange.
The other problem is that I'm not able to use the -commandLinesList functionnality.
I've just been making up my mind whther to use stud.io or LDCad for my MOCs. After studying the documentation from Roland Melkert and doing the first test constructions, the decision is pretty clear. As LDCad is, for example, much more flexible in placing parts and, even when working on bigger models, much faster, this will be the way to go.
Concerning the use of flexible parts, I have one question:
When for example placing a rubber band I would like to see an information about the length of the current path. I saw a video tutorial from Roland Melkert which showed this feature (see attachment).
Until now I could'nt figure out how to make LDCad show this information. In my app the last line in the info window is missing.
Can anybody give me a hint? I'm using LDCad 1.6d.
By the way is this the latest version of this great app?
nominations for the 2021/2022 LDraw.org Steering Committee election will close at 11:59 PM GMT on 28 February 2021 and elections will start on 01.03.2021. Only those candidates who have been nominated, seconded, and have accepted as outlined, will be eligible for election. So if you are a candidate that has not yet accepted or declined, please consider deciding. The list with the candidates as well as their status can be found here:
Hello all! Thank you in advance for any responses!
I've been building with real bricks for years but after repeated requests for instructions I've finally had a go at creating some. My first model is almost built digitally, but I am going insane in the last step of adding curved hoses. I'm aware that Studio struggles in this regard, so have downloaded LDCad, but try as I might to follow the online guides, it just isn't working for me! I've attached a couple of images: I create the part, make sure it's rubber type, make sure it's nested in the upper right corner (don't know what that means!). I can move the end, but can't seem use the insert key to add new nodes. When I do this it just goes see-through as in the photos (before I click it says "Invisible part selected, click anywhere to add it"). Any help? I'm guessing it's going to be tricky to export back into studio as well, but we will get there when we get there!
I do note that there are two types of hose 14301 - one seems infinitely extendable, and has a spanner (this is the one I'm using), the other is fixed length but refuses to flex.
![[Image: 53075pb02.png]](https://img.bricklink.com/ItemImage/PN/11/53075pb02.png)
