Search the Community
Showing results for tags 'LDView'.
Found 4 results
-
I am currently working myself through this great tutorial using MLcad 3.4, LDView 4.1 and POV-Ray for Windows 3.7: [Guide] Rendering LDraw models using POV-Ray http://www.eurobrick...showtopic=65876 Now I want to gain more control of the the lights, so I've added a light.dat in the source .ldr file in MLCad. In LDView this light.dat is shown and I can switch it on and off and I can play around with "replace main lights". When it comes to the POW export I do not see any difference in the .pov file which is created. It always has the three default lights and I wonder where the only one light.dat is which I have inserted in MLCad. This is the //Lights section in my .pov file: // Lights #ifndef (LDXSkipLight1) light_source { // Latitude,Longitude: 45,0,LDXRadius*2 <0*LDXRadius,-1.414214*LDXRadius,-1.414214*LDXRadius> + LDXCenter color rgb <1,1,1> } #end #ifndef (LDXSkipLight2) light_source { // Latitude,Longitude: 30,120,LDXRadius*2 <1.5*LDXRadius,-1*LDXRadius,0.866026*LDXRadius> + LDXCenter color rgb <1,1,1> } #end #ifndef (LDXSkipLight3) light_source { // Latitude,Longitude: 60,-120,LDXRadius*2 <-0.866025*LDXRadius,-1.732051*LDXRadius,0.5*LDXRadius> + LDXCenter color rgb <1,1,1> } #end Is there any option in the export settings for the pov export of LDView to overwrite the default lights and just use the light.dat from the source .ldr? Anyone any ideas? Thanks in advance, HoMa -
Over at brickset a new version of the LDraw "All In One Installer" (AIOI) was anounced: http://brickset.com/...1-now-available On ldraw.org the full package is available: http://www.ldraw.org/article/104.html Before running this new AIOI I have some questions regarding my existing (and working) setup: I have downloaded and installed the latest parts update als complete package a few weeks ago (http://www.ldraw.org...test-parts.html) ... would the new AIOI overwrite this? I have downloaded various unofficial parts over the past months ... I want to keep them and does the new AIOI overwrite this? I run MLcad 3.4 ... 3.5 is out now. What are the differences/improvements? I run LPub 4.0.0.11 ... This seems not to be supported any more and the newer LPub3D 1.2.3.443.2 is part of the AIOI. If I run the new installer, will my old LPub will still be available in parallel to the new LPub3D? These are my major questions. I would be happy about clear answers and experiences of others upgrading a running LDraw setup. Thanks in advance, HoMa P.S. And a big big thank you to all the volunteer workers who helped out to update the LDraw world!
-
For attending my duty („ ... you must (if you win) share how you did the render…”) I prepared some comments on my entry for the rendering contest. Hope these comments will inspire you to create and poste some more nice renderings or even will encourage you to engage with rendering. Superkalle proposed to open a new topic fort his. So please feel free to poste further questions/comments/remarks here. I would highly appreciate if other participants in the rendering contest would poste some tips regarding their entries here too. Papacharly -
I'm in the process of creating the build instructions for Akiyuki's Cup-to-Cup GBC module (refer to this forum post). I appear to have encountered an issue with the LDraw PF Medium motor, which is causing LDView to crash. I'm wondering whether someone would be willing to take a couple of minutes to run the following simple test to see whether they see the same behaviour and post their outcome of the test. Obviously the real build instructions are more complex than just a medium motor! I have simply distilled the build instructions down to the point to identify the part that appears to be causing the issue. My machine is running Vista (Business), SP2 Build 6002. 1) Use MLCAD to create an ldr file that contains only a PK medium motor (part # 58120). 2) Open the ldr file from step 1 in LDView. A screenshot of mine is show below: 3) Exit from LDView. It is at this point that I am seeing LDView crash: Any feedback will be appreciated. Regards, David
