-
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 identification
- Thread starter GHD
- Start date
- Messages
- 34,981
- Country
ADE stores a data array generated by the GP Library. This includes the texture names and other data such as vertex coordinates, UV values and so on.
At which point is are things going wrong George - in the ADE tooltip or in the editor?
Don should be able to confirm how the library reads the data array and gets the texture.
At which point is are things going wrong George - in the ADE tooltip or in the editor?
Don should be able to confirm how the library reads the data array and gets the texture.
- Messages
- 12,244
- Country
It is displaying incorrect textures in FSX.
It is crashing when I enter the GP editor. You should have received the "call home" files.
- Messages
- 34,981
- Country
Passed the 'fone home' log to Don.
George, one file "didn't make it home". The log file was unreadable.
In the other, I compiled the enclosed airport without issue. As well, I edited the line in the location of the reported location of the cursor when the problem occurred. Since I didn't have the required texture, I got the "no texture" message - but no exception. When I substituted the texture, I experienced the issue that Tom and you reported moments ago.
Perhaps you would send me the textures and the two texture control files you used for that project and I'll try again. As well, unless the issue occurred immediately upon you attempting to edit that line, it would also be helpful to know what you were attempting to do at the time.
Don
In the other, I compiled the enclosed airport without issue. As well, I edited the line in the location of the reported location of the cursor when the problem occurred. Since I didn't have the required texture, I got the "no texture" message - but no exception. When I substituted the texture, I experienced the issue that Tom and you reported moments ago.
Perhaps you would send me the textures and the two texture control files you used for that project and I'll try again. As well, unless the issue occurred immediately upon you attempting to edit that line, it would also be helpful to know what you were attempting to do at the time.
Textures are identified by name with the help of the entries in the Textures_def and Lines_def files. A texture must be in both the Textures and Textures_Dpy folders for it to be recognized as being available to ADE_GPEditor. However, so long as the required textures are in the Textures folder at compile time, they will be passed to FlightSim and the display will render properly.
Don
- Messages
- 12,244
- Country
George, it appears that both logs report the same problem. At least they point to the same module and the same exception.
At this stage, I hope we've found all the general problems. So, when you encounter an exception in ADE-GP, by definition, it's an unusual situation. (An exception in any of my software indicates an unintended path through the code. That's the way I write software.)
While the ADE logs help narrow things down, they don't yet provide all the information likely to be required to isolate the problem. So, the most useful thing you can do when an exception is thrown is bundle-up the AD3 file, the texture control files and the exception message and send them along to me - e-mail or attachments - I don't care.
Obviously, there's still a "hole" in the line processing code. Whether it's due to how lines are processed or to unexpected/unhandled entries in the texture control files, we don't yet know. Should it happen again, please just send that material along.
Don
At this stage, I hope we've found all the general problems. So, when you encounter an exception in ADE-GP, by definition, it's an unusual situation. (An exception in any of my software indicates an unintended path through the code. That's the way I write software.)
While the ADE logs help narrow things down, they don't yet provide all the information likely to be required to isolate the problem. So, the most useful thing you can do when an exception is thrown is bundle-up the AD3 file, the texture control files and the exception message and send them along to me - e-mail or attachments - I don't care.
Obviously, there's still a "hole" in the line processing code. Whether it's due to how lines are processed or to unexpected/unhandled entries in the texture control files, we don't yet know. Should it happen again, please just send that material along.
Don
- Messages
- 12,244
- Country
That's a peculiar way to write software. Surely all paths should have exception handling rather than a catch-all.
I have had another two "Fone home" messages. I have determined that it was due to editing an existing line where the definition had been deleted from Lines_Def.txt. You can ignore them.
Edit.
What I don't understand is that there was another line definition missing but, since I didn't edit it I didn't get the error. However, the compiled file included these lines correctly.
Last edited:
George, your reading glasses must be very narrow to construe my statement that way. What drives you to "take shots" like that?
Stated another way, every situation I expect to arise is handled uniquely - including those that generate exceptions. The only time you will experience an unhandled exception (which is what I was referring to before) in my code is when something I don't expect happens. Should there be an unhandled exception, my goal is to isolate the cause and modify the code to handle the situation in a manner that leaves the user in control. Since I have over 100,000 lines of code spread across (now) 4 widely-used applications, I think the way I write and support code generally speaks for itself.
It's been clear to me from my initial investigation that the problem is related to the texture control files. That's why I asked for them. If you'd send them me, I could determine exactly what's happening and change the code so the situation doesn't just generate "Fone home" situations - which is an example of the type of exception referred to in my previous post.
Don
- Messages
- 12,244
- Country
I know exactly what texture control files are.
It is very easy to create the crash:
Create a GP line.
Save the ADE file.
Remove the texture and line definition from the def files.
Reload the project and edit that line.
This simulates the situation where one has received an ADE file from elsewhere but they haven't provided the textures and texture control files.
It is very easy to create the crash:
Create a GP line.
Save the ADE file.
Remove the texture and line definition from the def files.
Reload the project and edit that line.
This simulates the situation where one has received an ADE file from elsewhere but they haven't provided the textures and texture control files.
It seems to be a little more complex than that, George.
I have done exactly as you suggested, but no exception. I have also analysed the code in the module the log reported as where the exception occurred and can fine nothing amiss.
If the texture is missing, you should get a "no texture found" message - unless the exception occurs earlier in the processing chain.
Can any one else duplicate this problem?
Further info or the files might be helpful.
Don
I have done exactly as you suggested, but no exception. I have also analysed the code in the module the log reported as where the exception occurred and can fine nothing amiss.
If the texture is missing, you should get a "no texture found" message - unless the exception occurs earlier in the processing chain.
Can any one else duplicate this problem?
Further info or the files might be helpful.
Don
- Messages
- 12,244
- Country
The files are long gone.
I have tried every possible combination of missing textures and missing texture control files and have been unable to cause the editor to throw an exception. On the off-chance that it might be something in my debug system that was suppressing the exception, I repeated the exercise with the latest released software. Again, no exception.
If anyone observes what George reported -or any other unhandled exception - please immediately forward the AD3 file and the two texture control files to me directly - either as attachments to a post or by e-mail to don at stuff4fs dot com. Don't bother with "Fone-home".
I have no interest in these files other than as diagnostic aids. I will delete them when the problem is resolved.
Don
If anyone observes what George reported -or any other unhandled exception - please immediately forward the AD3 file and the two texture control files to me directly - either as attachments to a post or by e-mail to don at stuff4fs dot com. Don't bother with "Fone-home".
I have no interest in these files other than as diagnostic aids. I will delete them when the problem is resolved.
Don