Xforce Keygen Inventor Nesting 2013 Activation

0 views
Skip to first unread message
Message has been deleted

Toccara Delacerda

unread,
Jul 9, 2024, 4:04:36 PM7/9/24
to gowalilre

I've had this problem a tonne of times, and struggle (almost) every time I run a nest. I started writing this post, but have now I've now solved it, so I'm posting for future reference for myself and others.

Xforce Keygen Inventor Nesting 2013 Activation


Download Zip https://urloso.com/2yN0Hm



I'm having problems adding source files to nests. I click the "Sources" button, select my files, and I get a prompt about source file material mapping - then no matter what I click (whether "Yes" or "No"), the "OK" button is greyed out, and I can't proceed any further.

Starting here, I add my source files - you can see them appear in the browser on the left, and in the "Sources" dialogue box. But I get the Material Mapping warning - From what I understand, this isn't unusual.

I typically work with multiple instances of Inventor - Usually 2. I'm a consultant, so I have an instance running my own vault projects, and the other is running the project for one of my clients. Normally this doesn't cause too many problems - those you do encounter are easily identifiable.

To clarify... There are two instances of Inventor - Instance 1 runs the client's vault project - this is the instance that gets priority to things like the VBA editor and probably other things like the registry etc. The second instance runs my own vault project. When I try to make changes to the VBA editor, or when Inventor normally makes changes to the registry - this instance will either error, or have no effect.

In this case, I discovered that while I was trying to load source files, Inventor has had a file resolution error, which would normally be presented with a file dialogue box where the user could re-associate the file... Now that error is weird in the first case, because the files are all stored where they belong, Secondly because that dialogue box didn't appear. It wasn't until I closed the active instance that I saw the second (idle) instance of Inventor with a stack of file resolution errors that were not visible in the active Inventor instance.

It LOOKS as though the Nesting application has started a new background application process, but has attached itself to the first instance of Inventor which has the wrong project file - hence the file resolution errors. This also explains why the dialogue boxes appeared on top of the first instance - where I wasn't even using the nesting utility...

Plot twist... It worked for a little while, then went back to the original problem... I didn't catch the exact moment - I got an error which seemed trivial, so I didn't think anything of it. After it happened, I closed Inventor and re-started it, but the problem didn't go away. I needed to re-start my PC to resolve the problem. It adds to my suspicion that the problem is occurring in a separate background application...

1. Whenever we re-run a nest all of the sheet numbers in the tree change for the portion re-run. Sheets which have been custom named revert to a random number (even if the nest layout on that sheet did not actually change). Is there a means to prevent this from happening (or at least only if the sheet layout changes)?

2. I have noticed that if I have multiple nest studies if I source a new part it automatically wants to bring the part into every nest study when in reality I only want it in one. Is there a way to change the settings such that Inventor does not automatically assign it to any study and you have to manually select which one you want it in? This would prevent me from having to unselect it from several nest studies.

3. It appears that the "Best Size" and "Best Mix" packing options do not work. Only the "As-Listed" option works which can be very annoying as it requires carefully arranging the plate list to ensure that all of the parts are nested on the correct plates (I spent hours doing this). It appears that this has been a known issue with 2022 for over a year, are there any plans to fix it in 2022? Has it has been fixed in 2023 or 2024 (we are considering upgrading)?

4. Are there plans to update the nesting module such that Inventor will nest part model states other than the master? First let me say that I love model states, but this nesting incompatibility creates problems. There are many instances where I may use a secondary model state of a part in an assembly. There are also instances where I need a RH and LH version of a part number where the only difference is opposite "A-Faces" defined. Maybe there is a way to work around some of these issues and if so I am open to suggestions.

5. I also occasionally have issues with creating a 3D model when using the 3D source option (the default). It will run as if it is going to create the 3D model (and sometimes a new window with the assembly being generated pops up in Inventor) but suddenly it closes. The .inest file will remain open but the assembly model being created will stop/crash. Please note that this problem is inconsistent. It will be working fine then suddenly start happening with no explanation... It is as if something goes wrong with the .inest file. Also note that the second option to simply create a 3D model by extruding a 2D shape still functions fine (you just have to select it). This is sufficient but getting the parts formatted to meet my needs takes longer.

I am using Inventor for woodworking and have been running into an issue using the nesting utility to get an idea of material needs. I model everything as a solid multibody which is then made into components at which time a sheet metal template is assigned to each body of the model to assign it's thickness for the nesting utility to read it correctly. An illogic code runs in each file that is executed from the top level assembly that automates the flat pattern process. This has worked successfully using traditional assemblies, but I have been running into issues with multi-body models where each model gives as error that "A dependency is out-of-date", I'm guessing because everything is derived off of a base component.

Does anyone have advice on how to get past this error or what may be causing it? 100% accurate nests are definitely not necessary, but it could greatly speed up estimating and material ordering to have at least a pretty good idea of how much board to order. Any advice on woodworking with the nesting utility and multi-body modeling?

Q2: your workflow to create components from a multi-body part, results in derived parts that only contain a body.
In order for the nesting utility to recognize that body, you will have to make sure that you are using a Generic CAD provider. Can you verify on the ribbon Manage > Providers if the Generic CAD provider is checked for IPT files?

The bigger problem I see with your workflow is that that body more than likely will NOT be the flat body you are after, but will be the folded body unless your last feature in the parent part would be an Unfold feature to which you then later can apply a projected sketch in the derived part. That projected sketch can be recognized by nesting utility.

Do you have an inest template set up with all your thicknesses, materials, and packaging for all of the materials you are using? And do these match what are in your sheet metal defaults? If your material, thickness, rule, etc. do not all match what they are supposed to be and do not match between the inest and part there will be issues. I don't believe I have seen the out of date prompt, how are you going from multibody to parts?

Nowadays 98% of my designs are multibody parts - sheet and solid ( I try no to mix those two types in one file). All the drawings are made manually. Also, my other designers are starting to learn the multi-body approach in their designs. We are creating mainly prototype machines.

Dumb it down or remove features if you want to protect intellectual property.
Looking at your problem from a distance without having a file to test, it does not sound right to me that a sheet metal part with an Unfold feature in it (I think that is what you mean with "unbend") would not be recognized in nesting when treating it as a generic part.

Some of the custom materials do not get recognized during import. See also attached screenshot.
So it is a problem with mapping Inventor materials for nesting and not a multi-body problem IMO.
I don't have an immediate solution for you but logged a defect in our database so that our developers could look at it. For your reference the defect number is TRUNINV-2165.

I am using nesting, for the first time, to work out how many sheets of plywood we need on a job. One of the items is a trapezoid 1398mm x 2990mm so it will fit on the 1500mm x 3000mm sheet but the nesting software keeps saying the part may not fit on any nest & leaves it off. I have tried to alter the orientation by adding Deviation & increments to the Shape properties but it has no effect. Does anyone know how to get the part included into the nesting study?

I would look at your lead in's and lead out's lengths. If there are close or touching the edge some nesting software will "error". I am sorry I don't use this nesting software so I can't test this idea out.

Got it working, I had to set a 10 degree deviation on the material then unbind all the other items so they stay horizontal / vertical. The software then rotated the trapezoid so the short edge was aligned to the sheet. It still warns the item may not fit but now includes it in the nest & sheet count.

I was expecting to leave the all the items bound to the material then just unbind & rotate the trapezoid but the software just did not like this, it worked the other way around but it's not very intuitive.

Autodesk Inventor Nesting can save us time and money by limiting the amount of remnant material that gets wasted. I would have loved to have this years ago. As soon as it was first released, I started to use it to find the capability and limitations.

We had a great audience on the day, who were enthusiastic and engaged in the topic. I was worried that the intro was a bit long, but it did seem to help people understand what applications nesting can be used for and what Inventor is capable of.

b1e95dc632
Reply all
Reply to author
Forward
0 new messages