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.
Why are you concerned about the .mdl files? Presumably, you've generated all the files you need. The textures file remains because I expect it to be of some use.but why does the MDL's Folder disappear when i close GeoLock?
the Texture folder remains there, so when i go for the model the folder has gone!!!
Jim, I didn't appreciate what you were saying in your first point above until after removing the duplicate entries in the missing files list and updating the documentation as you suggested in your second point. Then I realized that reporting textures as missing simply because they were not located in a companion \texture folder was unnecessary. If those textures were not otherwise available, the original models would be affected and, so, why would you want to copy them. And, if they were available to the original models, they would be available to the copies via the same mechanism.
So, I'm going to eliminate the missing textures reporting entirely.
Tom, assuming the models were fully textured in the first place, the list of missing textures only included (as Jim pointed out) textures from folders in Flightsim's default search list (e.g., in the main Texture folder). Thus, those textures, will be available wherever you place the library. So, so long as you put the "local" textures in a companion texture folder to the library, all should be OK.I'm just the opposite - I place everything as library objects. That's why geo-locking the library files is so attractive.
The first step is to decompile the whole .bgl, which results in all the included models being placed in the MDLs folder. Only then do you get to pick and choose.Don, I assume this is intended behavior - when you select only one MDL file for the new BGL file, all the MDL files end up being saved in the MDLs folder. I do understand why this is true (the MDLs are created during the decompile, not during the compile), but it does cause a little confusion the first time (since it works differently from the Texture folder).
Also, there is nothing mentioned about the MDLs folder in the manual.
Not sure what you are saying, Ray. Tom's concern was the file size which, in an earlier version, was unchanged regardless of how many models were selected. Even when this was the case (corrected in version 220.127.116.11), the only models actually included in the new file were those selected. The rest was simply wasted space.As Tom mentioned we get all the mdl's when selecting one so i still have to get the model from the list of GUID's, if i know GUID number for the model i need
I'll take a look at the code - but I'm tied up on another project at the moment. If it's simple, I'll do it.Can Geolock be updated to do the same?
Sid, it looks like you are attempting to compile a FSX model for FS9. Can't be done with Geolock.
Turns out it was so easy I did it (displayed textures) right away.