Recently to learn fusion 360, I used lego models to train with this models
Fusion360 is free for learning an can be used during 3 years with only a email address like Maya, 3dsmax,...

My fusion 360 models https://grabcad.com/stephane.ramauge-1

I'm using the tutorials of DK https://grabcad.com/dk/tutorials to build my first parts and models.
DK made lot of pieces in .IPT format (inventor) format. IPT Part numbers follow Bricklink convention.

Maybe someone with python or java skill could make a script to translate .ldr instructions into instructions to build
models using a fusion360 shared library ?

A fusion360 or inventor assembly is series of components with coordinate, rotation, colors like in a LDR models.
A series of script can import nut, screw in .STL format from a online tools dealer for example. 

I think it's possible to parse a .ldr file and translate *.dat from it to .ipt files or fusion360 library component.


With an organized shared library (convention name, scale,...) like ldraw library but for CAD programs (*.IPT files for example) a script could replace the <piece1025.dat> of a ldr file by a <piece1025.ipt>


For example 


Ldr file :
 
colour  x y z a b c d e f g h i piece1025.dat 




Fictive fusion script : 

Insert <piece1025.ipt>

coordinate   x y z

Transform a b c d e f g h I   

 Insert piece9990.ipt

coordinate .......
 

So with the help of a develloper it could be possible in fusion360 to load and  ldr file, translate the instruction for fusion, insert the good piece at the right place and finally construct the model  



Example script for fusion :

http://codefoster.com/f360api/
https://www.autodesk.com/products/fusion...i-preview/


It's just an idea 

guys im trying to add the wedo 2.0 hub into a model. i have noticed that the object is shown in the building isntruction but its not shown at the PLI. does some one know why? it is due its too big, or it cant find the object in a library?

the object is: 19071c01.dat

Guys when I make the building instructiins I add an axe but it does not shows me the length. I can enable the description to all PLI , but it add to much text to all PLI and I'm only interested in the length of the axe.

I'm using lpub 2.0.2

Is there any work around? Done in lpub3d?


Edit: I'm thinking I can add extra text using the edit menu add text option. This is tedious but it may work. I have not tested yet


Any other ideas, that it does not involve edit the jpg and make a new pdf file?

During some discussion with various folks at BrickCon, I have a few points I'd like to open up to discussion:

- The main site would do well as a wiki. We have so many drive-by contributors that the wiki concept would work better than the front-end/back-end we have currently. It would also alleviate the admins from much of the theme coding and article maintenance. That said, the contributor agreement would mean no anonymous editing (currently disallowed on the wiki anyway.

- I'd like to bring back the MOTM and SOTM. I think it generated a small amount of traffic to the site. I could even automate it to some degree since LDView is installed on the server.
 and brigl can be use for machines that can handle it.

- The PT needs an overhaul. This was painfully obvious during the server shift last summer.

Thought?

P.S. I have a few more ideas that were brought up but I can't remember them right now.

I'd like to make your connection spec official  We can still have the separate connection library and the bar for making it official can be lower and easier to update but I'd really like the connection data to be part of the official library.

I'm also leaning towards making you flexible connection METAs official as well.

I think these 2 areas are the 2 biggest areas where the official library falls down.

Thoughts?

I have been looking through the various META commands (such as LPub commands for PLI and Callouts) but I have yet to find a META command that informs an instructions renderer of how to properly orient parts for parts lists and BOMs. 

A nice way of orienting parts is to position it with the center at (0,0,0) and placing the camera somewhere along the vector (10, -7, 10). It seems like MLCad does it this way, and I believe this gives a nice view of most parts.

This approach does not work with technic plates (where you can't see the holes), panels with stickers (where the stickers face away from the user), 1x1 bricks with 1 or two studs on sides, and many more, where this normal orientation makes it hard to determine the part.

I have made a crude hack and placed the camera along (10,-15,10) to help out with some of the situations, see this example BOM where 98087 and 47905 can be distinguished (The page currently loads slowly due to lack of optimizations for line type 5 - I am looking into that), but a better approach is needed.

Is there already a commonly used META command for this purpose? I have not been able to find it, but I might have looked the wrong places.

And is there already a library for this kind of positioning of parts? And how does LPub get around this issue. Does it handle this internally?

Hi all,

I've been looking into Studio 2.0 and fiddling around a bit with the instruction maker.
Now I am looking for something like rotation steps.
Is this possible? Can't seem to find it.

Thanks.

Jaco

Hi all,

I came across some cheap sets Dimenstion startpack 7117x.
For PS4, WiiU and Xbox.
Is is worth investing? Partspack / minifigs?

Tnx

Jaco

Guys I noticed that ldcad has permanent helpers and not permanent helpers.

I did not.find how to modify it to use it as a single arrow and not  X y z arrow.

By the moment I have made a bin with arrows .dat files to add to the models for buffer exchange.

Is there any tutorial out there?

guys i was wondering if someone could let me knwo if there is any way not to overlap the rubberbands in ldca when they are in a crossing section