Eagle3D

Am 17.10.2012 01:20, schrieb fred:

I've been playing around with eadgle3D (povray based) and it is very

impressive.

 

My first issue is I dont know how to add components from eagle libraries

to eagle3D

 

I see from the writers web page that this should be possible but

I seem to be a bit slow on the uptake for some reason

 

Does anyone know if there is a step by step guide or howto for this?

There is NO possibility to add EAGLE libraries to 'eagle3D' other than

learning the POVRay syntax and manually creating all the necessary

POVRay files yourself. This is a LOT of work and consumes a LOT of time.

'eagle3D' already converts all copper to POVRay properly, but the 3D

information for the REAL components CANNOT be automatically created,

because it doesn't EXIST anywhere. For the typical package, 2-8 hours

should be necessary to create a DECENT model (going down a bit when

getting the hang of POVRay), meaning that the library creation work is

going up by a factor of ten, roughly. This is the reason why I never

REALLY bothered to use 'eagle3D' - MUCH too much work for a nice, but

NOT a really important result.

Andreas Weidner

'eagle3D' already converts all copper to POVRay properly, but the 3D

information for the REAL components CANNOT be automatically created,

because it doesn't EXIST anywhere. For the typical package, 2-8 hours

should be necessary to create a DECENT model (going down a bit when

getting the hang of POVRay), meaning that the library creation work is

going up by a factor of ten, roughly. This is the reason why I never

REALLY bothered to use 'eagle3D' - MUCH too much work for a nice, but

NOT a really important result.

 

Andreas Weidner

 

That's a slow process. I suggest you have a look at eagleUp :

http://eagleup.wordpress.com/

(check the first two videos)

Creating a model takes less than 5 minutes, and many are already available

(in native format, or from the manufacturer with a couple of conversions).

The default rendering is basic, but you can use the models for mechanical

tests, not only for static images. With advanced renderers you can get nicer

images if wanted.

Jerome

In article <2eeda27c41998cf7c0a8cd8e9fc@news.cadsoft.de>,

jerome.lamy@gmail.com says...

http://eagleup.wordpress.com/

 

sorry. nothing related to google is acceptable.

OK - I've been able to spend some time with this now and have discovered

it is quite easy to use the generic components supplied with 2 simple

cut and paste actions into the 3duser.dat file. 2 minutes per component

tops.

That makes a HUGE difference and the whole thing much more of a complete

solution. I'm really impressed. I've got almost all my board visualised

now. I may even be able to get away without having to create new

components.

Its just a shame I had to work so hard to find out how easy it is!

Essentially a more efficient way to do it would be to be able to assign

a simple package alias and have the ULP scan just an alias name list

(look in the V50 ULP release about line 1923 - a function poked in there

should do it. Then perhaps a simple app to display the provided images

with a box to allocate the actual package name as an alias .... if I

ever get time!)

but perhaps the extra stuff in this .dat file is needed for something I

dont understand yet. (I know what it is - no need to explain)

So anyway thanks for the pointers guys.

OK - I've been able to spend some time with this now and have discovered

it is quite easy to use the generic components supplied with 2 simple

cut and paste actions into the 3duser.dat file. 2 minutes per component

tops.

That makes a HUGE difference and the whole thing much more of a complete

solution. I'm really impressed. I've got almost all my board visualised

now. I may even be able to get away without having to create new

components.

Its just a shame I had to work so hard to find out how easy it is!

Essentially a more efficient way to do it would be to be able to assign

a simple package alias and have the ULP scan just an alias name list

(look in the V50 ULP release about line 1923 - a function poked in there

should do it. Then perhaps a simple app to display the provided images

with a box to allocate the actual package name as an alias .... if I

ever get time!)

but perhaps the extra stuff in this .dat file is needed for something I

dont understand yet. (I know what it is - no need to explain)

So anyway thanks for the pointers guys.