custom library part errors
Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2011-11-03 03:54 PM
‎2011-11-03
03:54 PM
When I investigate into the 3D script, I can't seem to figure out what the problem is at the lines indicated in the error messages.
Could you look at the specific area of the script and see what the problem is?
Object is attached. Thanks a ton!!
AC15, build 3267, macbook pro 15, 8GB RAM, 120 GB SSD
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2011-11-03 05:03 PM
‎2011-11-03
05:03 PM
I haven't looked at your object yet, but sometimes just saving the part in AC15 (using a NEW NAME, so you don't loose it for AC9)... is enough...
Duane
Visual Frontiers
AC25 :|: AC26 :|: AC27
:|: Enscape3.4:|:TwinMotion
DellXPS 4.7ghz i7:|: 8gb GPU 1070ti / Alienware M18 Laptop
Visual Frontiers
AC25 :|: AC26 :|: AC27
:|: Enscape3.4:|:TwinMotion
DellXPS 4.7ghz i7:|: 8gb GPU 1070ti / Alienware M18 Laptop
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2011-11-03 05:26 PM
‎2011-11-03
05:26 PM
Hi
I had a look at the file and the main problem seems to be end positions for xwall objects. I have remmed out the offending lines in the 3d script so that you can see what is going on.
I would, however say that this has clearly been an object created from the modelling rather than from script and as such is somewhat inefficient and would be better coded as a single prism with a single material for the outside and this could be done by creating a fill for the object in section, cutting out the central space, dragging and dropping the code in to the 2d and 3d gdl areas and then editing the entity to be a prism.
Also, if you do do this direct modelling method, simplify things by working around the origin on a separate master model. This will tidy things up no end rather than having random 114' dimensions creeping in.
I had a look at the file and the main problem seems to be end positions for xwall objects. I have remmed out the offending lines in the 3d script so that you can see what is going on.
I would, however say that this has clearly been an object created from the modelling rather than from script and as such is somewhat inefficient and would be better coded as a single prism with a single material for the outside and this could be done by creating a fill for the object in section, cutting out the central space, dragging and dropping the code in to the 2d and 3d gdl areas and then editing the entity to be a prism.
Also, if you do do this direct modelling method, simplify things by working around the origin on a separate master model. This will tidy things up no end rather than having random 114' dimensions creeping in.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2011-11-03 05:30 PM