wlbragg wrote in Sat Oct 23, 2021 5:23 pm:These types of subtle issues can be very difficult to find. Not knowing exactly what all you did without going through all the commits, which would take considerable time to sort out, makes it a real challenge, at least for me. I would recommend you review your change and even roll them back and institute the changes one at a time until you find the culprit. I've had to do this before myself. Seriously, this particular issue can be a bitch to find without the procedure I outlined above. I've had weeks and months go by looking for something so subtle I didn't even know it was a problem. I looked briefly at the files and didn't see anything outstanding. But there is some substantial refactoring to sort through.
Another method to find the issue.
Both variants call main, remove main and see if the now load. If so, then you've narrowed it down. You can do the same to either set and start eliminating all the tag pairs until you find the issue.
These are the things I would have to do to find it myself.
In a sense, you are right. The only thing is, I based the refactoring of the files based on the code architecture of the 757 code. The 757 calls main in all the set files. Thus, I do not think that could be the case. What I can say however, there are tags in the 757 code set files not in the set files of the 737. But then again, they were not in the 737 to begin with and the original stuff was able to work.
The 757 is YaSim as well, so that too is not an issue. If the code structure is the same, then the code should work.
The only thing that does come to mind would be the code inside Nasal scripts. I didn't look at the Nasal scripts yet, but do Nasal scripts normally call XML files?
Does acididently setting the location of cockpit or passenger weight to be located outside of the aircraft prevent the aircraft from showing?
How does variant-type tag work? Some of these things do not even show on FG Wiki.