-
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.
Texture Error
- Thread starter DeanP
- Start date
Dean, I suspect there another texture required for this aircraft. Generally, in SAMM's Models folders there are two texture folders for each static model, one labelled as the aircraft title, the other with the same label suffixed with ";All". Often, this ";All" folder is empty but I suspect in your case it is not. That's why SAMM offers to copy the required textures to the add-on scenery folder for you - so you don't have to bother with these details. Have a look at TexturesUsed.txt in the Models folder.
Don
When you create
Don
When you create
That was it Don. I made three static aircraft of the same plane with three different liveries. They all seemed to display fine, but this one got the error. I compared the texturesused file and only five of the many textures were in there. What is odd is the other two liveries had all of them. I'm not sure how this could happen, but I just started using this program. I copied the missing textures from the other livery and things work well now. I will have to watch for this again. Thanks for your help.
Dean
Dean
- Messages
- 542
- Country
Hi,
I am a having a similar problem to this in P3D, ie am getting the error "Attempting to open a non existent directory" with the path being for several of the static model texture files in P3D root/Texture and P3D root/Scenery/Global/Texture.
I am not sure why this is happening as all of the textures in "TexturesUsed.txt" are present in the activated texture folder in the P3D Addon Scenery folder. I have put the texture folders and the produced static aircraft bgl in an active airport folder, as that airport is why I created the models, and it was just easier than making a new directory.
I have a number of aircraft in the static bgl library, which was created with the SAMM library maker, and probably about 1/3 of them will produce this error of the missing directory. As I say, the required textures are already present in the addon scenery directory, so why is P3D trying to find the textures in P3D/Textures or Global/Textures?
For example, one of the models, "DC10-10 Water Tanker.mdl", only uses 1 texture, "AI MALCONTENT DC10-10.BMP". Despite the model appearing correctly there are 2 error messages that pop up and need to be closed regarding the missing texture directory.
I have noticed that, as mentioned above, the error messages all seem to be for aircraft which only have one texture folder present, and not the second texture folder with the ;All suffix. I suppose copying the texture folders to the directories mentioned in the error messages would fix the issue, but I would rather not if there is another solution.
Any ideas please?
Cheers,
Scott
I am a having a similar problem to this in P3D, ie am getting the error "Attempting to open a non existent directory" with the path being for several of the static model texture files in P3D root/Texture and P3D root/Scenery/Global/Texture.
I am not sure why this is happening as all of the textures in "TexturesUsed.txt" are present in the activated texture folder in the P3D Addon Scenery folder. I have put the texture folders and the produced static aircraft bgl in an active airport folder, as that airport is why I created the models, and it was just easier than making a new directory.
I have a number of aircraft in the static bgl library, which was created with the SAMM library maker, and probably about 1/3 of them will produce this error of the missing directory. As I say, the required textures are already present in the addon scenery directory, so why is P3D trying to find the textures in P3D/Textures or Global/Textures?
For example, one of the models, "DC10-10 Water Tanker.mdl", only uses 1 texture, "AI MALCONTENT DC10-10.BMP". Despite the model appearing correctly there are 2 error messages that pop up and need to be closed regarding the missing texture directory.
I have noticed that, as mentioned above, the error messages all seem to be for aircraft which only have one texture folder present, and not the second texture folder with the ;All suffix. I suppose copying the texture folders to the directories mentioned in the error messages would fix the issue, but I would rather not if there is another solution.
Any ideas please?
Cheers,
Scott
Last edited:
Scott, this will probably not solve your problem, but should at least explain what is happening. I'm travelling at the moment, away from my development system, and will be for the balance of the week. So, I'm "winging it" a bit.
TexturesUsed.txt is not a list of all the textures used by the model (that can be obtained by opening the .mdl file itself). Rather, it is a list of the custom textures used by the .mdl so that you will know which textures to copy if you don't let SAMM move those textures to the "final" texture folder. If the model uses textures from, say, the FSX\Textures folder, then those textures are not saved with the model since it is assumed they will be available from the main \Textures folder when the model is subsequently rendered, in your case P3D\Textures.
So, you should be checking whether the missing textures are available in the P3D textures folder.
I could, of course, have designed SAMM differently, but it didn't seem necessary at the time - on the assumption that such textures would be carried over from one version of Flightsim to the next.
If the missing textures are actually in the P3D\Textures folder, then it would seem my P3D implementation of SAMM is deficient. Unfortunately, since I don't have access to my development syste?m, I can't check. If this is the situation in your case, please post again (or e-mail me) in about a week, and include a link to the aircraft for which the difficulty exists (so that I can attempt to duplicate the exact problem you are reporting) and I'll investigate further.
On the other hand, if the problem is due to the mising texture(s) not being in your P3D\Textures folder, then this is probably a circumstance I can "fix" in SAMM. As an interim solution, try to obtain a copy of the missing texture(s) from the version of Flightsim for which the aircraft was designed and copy that/them into your P3D\Textures folder.
In any case, it will have to wait for a week or so.
Don
TexturesUsed.txt is not a list of all the textures used by the model (that can be obtained by opening the .mdl file itself). Rather, it is a list of the custom textures used by the .mdl so that you will know which textures to copy if you don't let SAMM move those textures to the "final" texture folder. If the model uses textures from, say, the FSX\Textures folder, then those textures are not saved with the model since it is assumed they will be available from the main \Textures folder when the model is subsequently rendered, in your case P3D\Textures.
So, you should be checking whether the missing textures are available in the P3D textures folder.
I could, of course, have designed SAMM differently, but it didn't seem necessary at the time - on the assumption that such textures would be carried over from one version of Flightsim to the next.
If the missing textures are actually in the P3D\Textures folder, then it would seem my P3D implementation of SAMM is deficient. Unfortunately, since I don't have access to my development syste?m, I can't check. If this is the situation in your case, please post again (or e-mail me) in about a week, and include a link to the aircraft for which the difficulty exists (so that I can attempt to duplicate the exact problem you are reporting) and I'll investigate further.
On the other hand, if the problem is due to the mising texture(s) not being in your P3D\Textures folder, then this is probably a circumstance I can "fix" in SAMM. As an interim solution, try to obtain a copy of the missing texture(s) from the version of Flightsim for which the aircraft was designed and copy that/them into your P3D\Textures folder.
In any case, it will have to wait for a week or so.
Don
- Messages
- 542
- Country
Thanks for the reply Don. You know, I actually ditched the aircraft bgl I was using, as it was kind of experimental, but I will be making more. The one I made had a lot of pretty "heavy" (performance wise) aircraft, and when I kept adding more aircraft to the airport I tipped it over the edge and P3D crashed from a lack of VAS. It was looking great before that happened though. I think it was one or two aircraft in particular which caused the OOM error.
Regarding using pretty detailed flightsim models, I don't seem to be able to adjust the LOD of a lot of them. It always seems to stay at a LOD of 100, and this is not adjustable. I suppose some models can be converted and others can not?
Anyway I love the program, and I will keep playing.
BTW here is a pic of KAFW airport which is what I was making the statics for.
Cheers,
Scott
Regarding using pretty detailed flightsim models, I don't seem to be able to adjust the LOD of a lot of them. It always seems to stay at a LOD of 100, and this is not adjustable. I suppose some models can be converted and others can not?
Anyway I love the program, and I will keep playing.
BTW here is a pic of KAFW airport which is what I was making the statics for.
Cheers,
Scott
Scott, I'm now back from my extended trip. I'm assuming from your last post that you have managed to overcome the earlier texture issue. If not, we should probably move that aspect off-line because I'm going to need a lot more information/interchange to diagnose it, including the actual aircraft and a detailed step-by-step summary of what you did with SAMM. I suggest you email it to me at don at stuff4fs dot com.
Regarding the LOD issue, SAMM can only produce LOD versions for those LODs implemented in the original aircraft model. Once again, if I need to investigate this issue, it would be best to do so off-line. Please e-mail me the aircraft model and identify the LOD(s) which you are unable to generate.
Don
Regarding the LOD issue, SAMM can only produce LOD versions for those LODs implemented in the original aircraft model. Once again, if I need to investigate this issue, it would be best to do so off-line. Please e-mail me the aircraft model and identify the LOD(s) which you are unable to generate.
Don