• 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 compile error

jyarddog

jyarddog

Messages
2,388
Country
us-washington
does this indicate a problem with my computer? Tried to save by 'export scenery' to a folder on desktop. Nothing showed up afterwards.... probably due to compikle errors. Bob
 

Attachments

  • screenshot272.jpg
    screenshot272.jpg
    120.2 KB · Views: 456
Are there more errors when you scroll up or is this the only one?
 
Here is the rest of the report. As I open the library I get some errors such as 'This is an empty object.' and also 'unsupported command in line 206'\

This is a library in an FS9 scenery. I was going to go in and correct the transparancies the export scenery which I assume writes the entire library with the corrections I made. I could then overwrite the old with the new library with the good trans's.

The jpg here shows what I get when doing 'export scenery' without changing anything. It seems identical to the report I get when making corrections and then exporting scenery. Of course- when I export scenery and get these messages I fid no resulting bgl where I wanted it to be or anywhere. i.e. failed to export.

I then tried to make corrections to each object individually and exporting object (fsx type mdl) i did all ten objects and made a library out of them and named the library exactly as the orignal library and replaced it.

I was succesful in the transparancy correction, but there were some objects missing in the scenery now. I took this out and reinstalled the old library for the meantime.

In the past I had a non functioning bgl problem; so i went to another program to see if I could still compile an xml into a bgl - I can. I assume then my bglcomp is woroking fine. could it be a scasm reader?
 

Attachments

  • screenshot273.jpg
    screenshot273.jpg
    408.6 KB · Views: 436
I thought that "export scenery" meant we can modifiy each object in the library then export the entire library with the mods, keep the same library name and overwrite. <----- We would then have the same library but with the "fixes" we made.

If not What is "export Scenery" for then? Bob
 
In fact, it boils down to the fact that it compiles into a bgl instead of an mdl.
And that is about all that can be said about the difference between the two AFAIK unless you have a geolocated object.
 
Export scenery indeed exports all objects and not only the active one. And if placement information is there it will also be exported.

About the error, are you sure there are no other errors when you scroll up? I expect some errors while creating the mdl files, since bglcomp can't seem to find them.
 
Great, I'll have to try that with a library I want to add LODs to.

Your missing objects appear to be due to the fact that they cannot be found by the compiler - as Arno says, we would need more of the error message closer to the top of the file - something other than just "MDL file cannot be found".

Thanks,
 
What I found was there were two objects with attached effects. I tried to compile them to xtomdl and also makemdl- - they would not show in FSX. So- I removed the attach points from each object. Bingo - both exported to fsx mdl (xtomdl) with no errors and they now show up - albeit- lights will not shine at night now or at all- which I can make my own lights and place later. Bob
 
Now- onto to the next. Found a library in this FS9 thing that has the people with the rectangle around them and also some fences. found no attach points in any object. Fixed the folks and the fences. compile by "export scenery" - After I got done I had the bgl and replace the orig with the new one I made. I think but not sure I think the fixes on the people and fences were there but a whole mess of bldgs were gone!!! These were bldgs that were in this library. It's like plug a hole in the dike and another one pops up! :banghead: Bob
 
Any errors in this case? Without such information it's hard to say what is going on.
 
I thought maybe it was a missing LM but it is there in the texture folder. groundcrew.bmp and its LM. There is also a groundcrew2.bmp and its LM but these do not pertain to the mdls involved.For any who open this zip which has the lib and the bmps, when in MCX #'s 6 & 14 do not appear. I'm not too worried about that.

The problem is.... 1. fix the transparencies, 2. 'export Scenery', Use this bgl to replace the original, using same filename, 3. in FSX now inst ead of seeing the people with the proper trans.... there are no people at all showing. I've done this before with repeated success. Why not now? I didn't notice any error messages.
 

Attachments

Last edited:
Missing textures have no influence on exporting an object.

Could it be the people were rotating to the user view in the fs2004 format? That is not supported for fsx mdl files.
 
Arno- I just found that yes indeed the people rotate to user. Now- I thought that after I fix the trans, this would nullify the rotate to user and they would show up as I have seen in the past.

Evidently now that the trans is fixed they will not show up because rotat to user is still there and since I modified them they now don't show? Is my guess correct?

I have one morfe file to fix which has fences. If I fix those.... as I have tried the fence, I thibnk, will show but anything else in the library will not show up either.

If I open these libraries they will show up in Instant Scenery, but then I'd have to go place each object where it used to be. so - it seems to me that when I fix transparancies the existing placement file does not see thse objects any longer. Bob
 
Last edited:
Is MCX saving these converted objects with a different GUID? If so, the old placements will not show up. You must change the GUID back to its old number before compiling in MCX.
 
I just checked. It doesn't seem like the guids are changing. checked the guid, fixed the trans, went back and check the guid again. --- same.

If I export scenery doe sthis change the guid?
 
Rotate to user is not supported for fsx mdl files, so after fixing the transparency you will loose that feature. So the people will be static polygons only visible from one direction.
 
You must log in or register to reply here.
Back
Top