Hi all,

I'm working on the foundation of what is highly likely to become LDCad 2.0, although currently it has little to nothing to do with LDraw specifics.

While doing this a lot of (boring) fundamental classes and tools need to be (re)written. I've done so for strings, list, etc and the OpenGL gui  engine is next.

Problem is I'm not yet sure on what kind of GUI to give LDCad 2.0. I know many people dislike the 1.x one, but I rather like it myself so I want to improve upon it but keep the basis the same maybe making it very dynamic so it can support different looks.

Anyway in order to write the support classes (window handling etc) I need to know what it should be able to do rendering wise etc.

For this I would like to gather some feedback about the current 1.x gui, in other words what is it people really hate about it or what kind of behavior are they missing.

I'm not talking colors though, as you can already change those in 1.x. One thing I'm thinking about myself is something like the blender gui which should be able to (nearly) mimic the 1.6 look as a default template or something.

Any thoughts/ideas/feedback is welcome.

LDCad 2.0 teaser

  out.png (Size: 12.98 KB / Downloads: 607)

Actually I'm working on the 75144 Snowspeeder.
So I would highly appreciate if somebody could generate windscreen 24248
thanks
roland

Hello everyone! I have been using LDraw many years now and I have managed to contribute to the library with some patterned parts in the past. Now I'm back and I have made my first 'real' parts (which isn't just a pattern on an existing part) using the LD Part Editor. However I'm shure that there are a few problems with parts so I am making this thread in the hope that it can provide additional help for these parts to be accepted and for my future improvement as a parts author

Here is the parts:
http://www.ldraw.org/cgi-bin/ptdetail.cg...30585a.dat
http://www.ldraw.org/cgi-bin/ptdetail.cg...30585b.dat

Hi,

currently the PT distinguishes new parts from fixes only by the (X) or (F) column. I'd like to see the PT grouping all new parts at the top of the http://www.ldraw.org/cgi-bin/ptlist.cgi list and the fixes with their subparts at the bottom, which would make it easier prioritizing certifying new parts.

Thanks, w.

Hi

I want to make some parts for Ldraw.

But it's very difficult for me

So, I'm finding anyone to make this.

Surely, I will pay for this

Can you email me?

[email protected]

Thank you

Hey,

here is a new release. It was intended to be released earlier, but now it has more value for you


As always, you can download LDPE from this page:
http://nilsschmidt1337.github.io/ldparteditor/

Changelog:
(11 new features and 5 bug fixes)

With this release you will be able to...

• ...select (and see in 3D view) elements producing an error or warning (when meaningful).
  
• ...benefit from improved usability for the "hover over right click menu-icon" in the 3D view.
  
• ...benefit from the fact that vertices which are close together are considered "as one" (when you add something; dist < threshold in LDU).
  
• ...customise the 3D distance below which vertices are considered the same when you add new elements.
  
• ...customise the 2D distance in pixels below which vertices are considered the same when you add new elements.
  
• ...see a warning if the value of a DecimalSpinner differs from the displayed value.
  
• ...drag&drop primitives on the text editor.
  
• ..."Select Connected..." / "Touching..." "...with same type."
  
• ...notice that closing a tab in the text editor close it also in the 3D editor, when the 3D and text editors share one window.
  
• ...select objects, regardless of the selection filter (but there are some special exceptions).
  
• ...benefit from more eye-catching buttons.
  

1. Rectifier: There was no difference in the result on the fourth filter. "Convert if possible/Do not convert if adjacent cond-line."
   
2. Text-Editor: The cursor jumped to the first line when the file was saved / the Save-button "stayed" in 'down'-position (actually, it was focused).
   
3. The 3D editor placed the tab of a newly opened part on the left of an already opened part, while in the text editor it was placed as expected on the right.
   
4. Selection issues with vertices which were close together on the screen.
   
5. The coplanarity calculation was incomplete.
   

1. Download the zip-Archive
   
2. Extract the archive content to the location of your choice
   
3. On windows, double-click "run.bat" to start LDPE.
   
4. On linux/mac, you have to excecute the shell script "run.sh" to start LDPE.
   

1. On windows, double-click "update.bat" to search for updates.
   
2. On linux, you have to excecute the shell script "update.sh".
   

• 64-bit Java Runtime Environment (JRE) 1.8
  
• OpenGL 2.1 compatible Graphics Card
  
• Operating System (64-bit): Windows [7 or newer], Linux [e.g. Ubuntu Linux >=14.4], Mac OS X [>=10.6]
  
• CPU: Multicore-Processor e.g. Intel Core 2 Duo or AMD Athlon II (>2.0Ghz)
  
• RAM: 4GB
  
• Video-Memory: 1 GB
  
• Free Disk Space: 100 MB
  

• Operating System (64bit): Windows 7,8,10, Linux [e.g. Ubuntu Linux >=14.4], Mac OS X [>=10.6]
  
• OpenGL 3.3 compatible Graphics Card
  
• CPU: Multicore-Processor with 4 cores (or more)
  
• RAM: >4 GB
  
• Video-Memory: >1 GB
  
• Free Disk Space: 512 MB
  
• For a faster start, LDPartEditor and the LDraw™ library should be installed on an SSD.
  

I'm having a problem when rendering part 32293 (Technic Steering Link 1x9) from LPub3D in POV-Ray with LGEO enabled.  When using LGEO, the part is shifted downward 2 LDUs, causing an overlap with the towball pins at either end.  


  32293_with_lgeo.png (Size: 30.58 KB / Downloads: 43)

When I disable LGEO, the part is rendered correctly:


  32293_without_lgeo.png (Size: 27.08 KB / Downloads: 42)

It is also rendered correctly when using LDGLite:


  32293_with_LDGLite.png (Size: 22.65 KB / Downloads: 42)

I see the same problem with I use LDView to export the model to a .pov file and render it directly.

As far as I can tell, I don't have an LGEO substitute for part 32293.

Any ideas what is happening and what I can do to fix it?

Thank you.

Kevin

Hi all,

Back from vacation I started a big project of 32000+ bricks.
The model is on 10 baseplates 48x48, so yes, it is bing.
I was able to model it though in LDCad (and turing to good old MLCad sometimes ;-)

Alas, LDView crashes very often when used as a renderer in LPub3D, so I turned to LDGLite for a change.
Works flawless, however the 4186 baseplate 48x48 does not render in the PLI.


What could this be?

LDView is able to render the whole model in LDView itself (although it takes a looooong time).
Getting to page 40 or so in the instructions in LPub3D, it starts to crash.
Anything to do about that? Or is it just a to big a model?

Topic for the Brickheadz theme.

We frequently discuss the anomaly of placing files representing subsections of flexible parts in the LDraw Parts folder to facilitate manual and LSynth construction of flexed renders.

The current header standards do not permit a '0 LDRAW_ORG Subpart' line in the header of a file in the parts folder.

I am proposing extending the header spec to allow a new quaifier to allow these files to be identified with a line like