• 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.

Exception Thrown by Latest Release

G

gadgets

Resource contributor
Messages
9,388
Country
ca-britishcolumbia
Hi Arno. There appears to be a problem with the LOD Editor in the latest release.

After importing any FS9 aircraft model, as soon as I click on the Generate LODs icon I get a "Value of '0' not valid for Value" exception. Clicking on Continue exits the editor. This worked OK in the previous development release. As well, the LOD combobox displays 0 and 1 only. That model has 5 LODs.

The problem seems to be restricted to aircraft .mdls. I can import a FS9scenery model and use the LOD Editor normally. But, I would note that the LODs are displayed as 24, 63, 126 when, in fact, they are 25, 65 and 600.

Don

EDIT: Further input. The problem appears to be in the import of the aircraft. If I import the aircraft and export as a .3ds file and then import that file into Gmax, I have only two LODs - 000 and 001. Once again, I was able to do this successfully in the previous release. Finally, following click on Export, a standard file specification dialog is displayed. If you select the folder by navigating to it using the Explorer box on the left hand of the dialog, all is well. But, if you type the destination folder directly into the box at the top, it is ignored and the file is exported to the folder from which it was imported. (It's hard to understand how this could be a MCX problem given that you apprear to be using a standard Windows dialog, but I have not noticed anything similar with other applications.)
 
Last edited:
Hi Don,

The problem with the LOD values being slightly differently is a known problem that is on my list.

I haven't made any changes to this part of the tool recently, so it can't be a recent issue. I guess your aircraft LODs might have wrong values as well. So wrong that multiple of them become LOD 0. I'll check if I can reproduce this with some FS2004 MDL files I have here. But I think it is quite model specific.
 
Arno, perhaps its an initialization issue, but I did not have similar problens with the previous development release.

I just re-downloaded and installed the latest release to make sure it wasn't an update issue. Same result.

I've tried several models - including the defalt C-172 - all with the same result.

DOn
 
Hi Don,

OK, let me try the default 172 as well.
 
Hi Don,

No problems here with the default 172. But I notice some variation in the bounding boxes depending on the optimization settings. How do you have those settings set? Are all true as default?
 
Hi Arno. sorry, I missed your earlier reply. I suspect whatever the issue was, it was related to some setting or other that I had changed. (I changed just about every setting in my attempts to export animations.)

I say "whatever the issue was", because with today's develoment release, it no longer exists. LODs are now being properly imported.

Should I keep trying to figure out what setting created the difficulty or do you now know?

Don
 
Hi Don,

I improved the FS2004 LOD code a bit earlier this week. So if it works fine with you in the latest release, I would say we call this issue closed.
 
I won't spend any more time on it.

Please note, it used to work for me in the third earlier development release back. It suddenly stopped working - coincidentally after loading the second release back. But, I had also changed a bunch of settings in desperation - trying to get MCX to do something it turns out it doesn't do.

So, unless you did something in the second release back that created the problem (you've already said you didn't change any code that should have affected this area) or changed something in the latest release that fixed a "settings issue", I suspect the problem I experienced is still lurking in the code.

Anyway, all's well that ends well. Thanks.

Incidentally. in the settings window that pops up during aircraft model import, a few animations are named but most are just hex numbers. Are these numbers the offset in the DICT section?

Don
 
Hi Don,

There was an issue based on the CollapseModelPart setting as well that I fixed. I think that might have been part of your problem. Just let me know if you have similar issues in the future and I'll check again.

What you see in the form are the offsets defined for the variables, these are defined in the DICT section indeed.
 
You must log in or register to reply here.
Back
Top