| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 5,190
» Latest member: Lynn Lee
» Forum threads: 6,099
» Forum posts: 51,349
Full Statistics
|
| Online Users |
There are currently 1727 online users.
» 1 Member(s) | 1723 Guest(s)
Applebot, Bing, Google, Martin James
|
|
|
| Parts Numbering for VIDIYO Tiles |
|
Posted by: Gerald Lasser - 2021-03-01, 15:51 - Forum: Parts Authoring
- Replies (13)
|
 |
This will bring us a whole bunch of new patterned tiles. way beyond the 37 that we can accommodate in a given theme. Looks like it will go along the lines of the Nexo Knight Tiles, so shall we adapt a similar numbering, i.e. 3068bpv000? I am not sure if 00 would be enough for a hundred tiles.
|
|
|
| Parts with two colours |
|
Posted by: Manfred Schaefer - 2021-02-26, 10:38 - Forum: General LDraw.org Discussion
- Replies (3)
|
|
Hello,
there are parts that use more than one colour, e.g. the "MANTLE FOR MINI FIGURE", Lego number 6063290 (design: 50231)
This coat has two different colours (new dark red, medium lilac) on the front and back.
Only one colour can currently be used.
Are you planning to adjust the LDraw specification?
The current solution that I see is that the representation consists of two parts shifted into one another with different colors.
Or a special version would have to be created.
Greeting
Manfred
|
|
|
|
| Errors in LGEO? |
|
Posted by: Sylvain Sauvage - 2021-02-25, 21:18 - Forum: Rendering Techniques
- Replies (6)
|
 |
Hi all,
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.
Does that ring a bell to anyone?
|
|
|
|
| Using CommandLinesList and ExportFile |
|
Posted by: Bertrand Lequy - 2021-02-23, 21:11 - Forum: LDraw Editors and Viewers
- Replies (13)
|
 |
Hello.
I'm trying to use LDView command line to do batch pov generation. I have 2 problems
the first one is that the pov file I get using command line with ExportFile is not the same I get using the same command line and manual export.
Case 1 :
Code: D:\Installations\LDRAW\LDView64\LDView64.exe D:\LEGO\Python\data\3001.ldr -DefaultLatitude=20 -DefaultLongitude=45 -WindowWidth=504 -WindowHeight=563 -ExportFile=D:\LEGO\Python\data\3001.pov
vs :
Case 2 :
Code: D:\Installations\LDRAW\LDView64\LDView64.exe D:\LEGO\Python\data\3001.ldr -DefaultLatitude=20 -DefaultLongitude=45 -WindowWidth=504 -WindowHeight=563
Of course, the second line give me exactly what I want in the LDView window.
they're only two differences :
the first line of the header is not the same (it's not a problem, but it's strange)
Case 1 :
Code: // Generated By: LDView Copyright (C) 2018 Travis Cobbs & Peter Bartfai
Case 2 :
Code: // Generated By: LDView 4.3 Copyright (C) 2018 Travis Cobbs & Peter Bartfai
the camera settings are wrong in case 2 :
Case 1 :
Code: #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")
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 created a file named commandlist.txt :
Code: Common: -DefaultLatitude=20 -DefaultLongitude=45 -WindowWidth=504 -WindowHeight=563
D:\LEGO\Python\data\3001.ldr -ExportFile=D:\LEGO\Python\data\3001.pov
D:\LEGO\Python\data\3002.ldr -ExportFile=D:\LEGO\Python\data\3002.pov
D:\LEGO\Python\data\3003.ldr -ExportFile=D:\LEGO\Python\data\3003.pov
D:\LEGO\Python\data\3002.ldr -ExportFile=D:\LEGO\Python\data\3004.pov
D:\LEGO\Python\data\3002.ldr -ExportFile=D:\LEGO\Python\data\3005.pov
D:\LEGO\Python\data\3002.ldr -ExportFile=D:\LEGO\Python\data\3006.pov
D:\LEGO\Python\data\3002.ldr -ExportFile=D:\LEGO\Python\data\3007.pov
D:\LEGO\Python\data\3002.ldr -ExportFile=D:\LEGO\Python\data\3008.pov
My command line is :
Code: D:\Installations\LDRAW\LDView64\LDView64.exe -CommandLinesList=D:\LEGO\Python\data\commandlist.txt
LDview just pop up like usualy, asking me to open a file. I'm lost.
|
|
|
|
|
