• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSXA System.ArgumentOutofRangeException Closed-Unresolved

Milton_Shupe

Resource contributor
Messages
331
Country
us-newmexico
This is a pesky little problem that has now cost me a day and a half of work.

Background: Converting an FS9 aircraft to FSX native (EDIT: using gmax and FSXA direct export). Finished all the exterior animations, tags, visibilities. Exported fine 5-6 times as tests. Started in the interior model, got all animations, tags and visibilities done except VC. To save time, I had cloned exterior control surfaces, props and gear to the interior model and re-linked, then used the animation manager and attachpoint tools to reapply those things.

Somewhere in the clone process, I also cloned some flap hinges unknowingly. They are duplicates. EDIT: They are NOT animated parts.
So, now I have an exterior model and interior model that individually export fine (sometimes), and I have some extra parts that belong to neither, root parent is the scene, that also exports fine.

Problem: If I try to delete those extra parts, my exports fail with the attached message.

What I have done:

1) No modeldef changes in 10 days (its also backed up)
2) Checked Animation Summary to ensure all tags, animation names, and key frames are correct (no negatives, no out of range numbers)
3) Checked Trackview: No scale issues on any part; no Notes of any kind.
4) Dropped back 15 saves to where i cloned parts and problem exists right after the clone
5) Went back further and all is well (represents minimum 6-8 hours work if I start over)
6) Tried merging exterior and interior only to new scene without extra parts-same export problem
7) I can export the extra parts fine alone, or with either the exterior model or interior model and export works without errors
8) I just cannot delete the extra parts.
9) I have successfully deleted 7 of the 8 sets of parts and I can still export as #7 above
10) Tried linking the parts to the exterior model, and to the interior model, export fails either way.
11) I checked all the gmax root folder files to see if any updates of any kind have been done. I see none. I also checked all the cfg files, root paths, etc and see nothing that has changed.
12) Viewed successfully exported mdls in MCX and it reports no issues loading, and none in the various object viewers.
13) Exterior model size is 30,278 triangles, 25,945 vertices

EDIT: Other things to consider:

1) FSTools does not always start with gmax; I almost always have to start it manually. It runs out of the FSX Gmax Game Pack Scripts.

2) Second, after the attached message is displayed and all other export failed messages, when I go to close gmax, it usually (not always) freezes my system hard requiring a power off re-boot.

Next Steps:

1) I can always start over if not resolved; I do not want to carry these problem parts forward
2) Looking for ideas to find the solution to this issue


EDIT: Well, I finally worked through about another 20 senarios with no resolution. So, I decided to go back to the beginning. Now I get the same error on the beginning of the series. That makes me think this is system related. I will go test other previously successful conversions.

EDIT2: I successfully exported other aircraft earlier conversions without issue. :-/ no, :) So, still confused on this one. That tells me there is a "triggering" object/UVW/material/link/tag/animation causing this in this scene only.

EDIT3: I am attaching the gmax1.2 source if anyone would like to look at it.

EDIT4: I went back 7 versions, grabbed an exterior model that exported successfully; got the most recent interior model merged to that. Deleted 7 of the 8 cloned parts that were causing issues. Also deleted another part from both models that on occasion would show a UVW mapping error.

So far, I have been able to export both ext/int models without the error. I do not export the 1 set of cloned parts; ignored that. I have proceeded to complete all animations, visibility tags, and exports continue to work. However, the warnings after export show many of the interior model parts as being pruned from the animation scene. However, all interior animations are working fine. Confusing.

Also, I still get a gmax lockup on occasion when closing it, sometimes just a 10-30 second wait before it closes, or it will lock up the system hard requiring a power off-reboot. This may be unrelated to this problem as I had the slow gmax FSX closes before this project.

Curious if when you merge in another interior model, does that get accepted by the GUID friendly name (both should have been the same.) Also, is there a way to homogenize the two models to eliminate the list of pruning messages.


Suggestions appreciated
Thanks in advance
 

Attachments

  • ms-2017-apr-17-004.jpg
    ms-2017-apr-17-004.jpg
    83.1 KB · Views: 482
  • AC520_20170416-16aShupe.zip
    AC520_20170416-16aShupe.zip
    969.1 KB · Views: 256
Last edited:
Hi Milton,

Using the SP2 SDK when I compile the model as is, I get a single MDL file (Export Skin, Flag Duplicate Parts, Process Textures, Export FS10 Materials, and Export Animations are checked). When I remove the flap hinges I get a proper export of the exterior and interior models. The only errors listed are:

WARNING: Degenerate poly detected in file (GMaxExport) mesh (c_gear_door_rf)
WARNING: Face vertex 0 x=-0.128975 y=0.276952 z=-0.058098
WARNING: Face vertex 1 x=-0.063393 y=0.279401 z=-0.06229
WARNING: Face vertex 2 x=-0.063393 y=0.279401 z=-0.06229
WARNING: Degenerate poly detected in file (GMaxExport) mesh (c_gear_door_rf)
WARNING: Face vertex 0 x=-0.129156 y=0.294499 z=-0.050683
WARNING: Face vertex 1 x=-0.063574 y=0.296948 z=-0.054875
WARNING: Face vertex 2 x=-0.063574 y=0.296948 z=-0.054875
WARNING: Part information for trimtab_elevator_key indicates that it is deprecated!

I get this box twice, I assume for the exterior and interior models.

I can then save this file, and load that into GMAX. The models still get exported OK.

I don't know if this is a difference between the SP2 and FSXA exporters or something else.

Hope this helps,
 
Milton, do you still use that system of groups? I wonder if that is messing you up? I have heard of issues of people being messed up with use of 'groups'.
 
Perhaps a silly question, but when you "cloned" those hinges, did you perhaps forget and cloned them as an "Instance" or "Reference" instead of "Copy?"
 
Hi Milton,

Using the SP2 SDK when I compile the model as is, I get a single MDL file (Export Skin, Flag Duplicate Parts, Process Textures, Export FS10 Materials, and Export Animations are checked). When I remove the flap hinges I get a proper export of the exterior and interior models. The only errors listed are:

WARNING: Degenerate poly detected in file (GMaxExport) mesh (c_gear_door_rf)
WARNING: Face vertex 0 x=-0.128975 y=0.276952 z=-0.058098
WARNING: Face vertex 1 x=-0.063393 y=0.279401 z=-0.06229
WARNING: Face vertex 2 x=-0.063393 y=0.279401 z=-0.06229
WARNING: Degenerate poly detected in file (GMaxExport) mesh (c_gear_door_rf)
WARNING: Face vertex 0 x=-0.129156 y=0.294499 z=-0.050683
WARNING: Face vertex 1 x=-0.063574 y=0.296948 z=-0.054875
WARNING: Face vertex 2 x=-0.063574 y=0.296948 z=-0.054875
WARNING: Part information for trimtab_elevator_key indicates that it is deprecated!

I get this box twice, I assume for the exterior and interior models.

I can then save this file, and load that into GMAX. The models still get exported OK.

I don't know if this is a difference between the SP2 and FSXA exporters or something else.

Hope this helps,

Thanks Tom, that is interesting. I have been on a roll today finishing up the bulk of the heavy lifting, and now doing some final tweaks to wrap this up. I have not had a single failure in 18 saves or 12 exports. Scary, huh?
I have not tried deleting that last set of hinges yet. On a roll and do not want to mess that up. I will do it when done. :-)
 
Milton, do you still use that system of groups? I wonder if that is messing you up? I have heard of issues of people being messed up with use of 'groups'.

LOL Bill, I have not used grouping of the exterior and interior models for years now. I do use them for large inanimate groups of parts like turrets, complex bomb sights, even pilots with animation. After 15 years of wrestling that grouping bear, I think I have it well sorted out. Haven't had an issue with groups for years now.
 
Perhaps a silly question, but when you "cloned" those hinges, did you perhaps forget and cloned them as an "Instance" or "Reference" instead of "Copy?"

Bill, I am certain it was a straight copy. Instances show up in bold, not sure about refs as I never use them.
When I use instances and need to do something different with one item, I use the Make Unique and move on.

Thanks for your input.
 
I am going to call this thread closed - unresolved for now. If I make new discoveries, I will post results back here. Thanks to everyone that gave this one a look. Greatly appreciate you and this site. :)
 
Back
Top