FlyingHigh wrote in Wed Apr 10, 2019 2:42 pm:You know, I'm going to try this again next event. I'm going to install each aircraft from every hangar I can find
as noted several times before, this is not a good idea... install only those that are needed for your flight... on another flight, you might need a different craft that you already have but this one from a different hanger... this may be necessary because different people have their own ways of doing things... they may change the properties sent over MP or they may change the control keys and even the flight properties or FDM... in some cases, the 3D model has been changed and the point of origin (0,0,0) may not be the same... in that case, you might see craft sunk below the terrain or even standing on their nose if the x,y,z coordinates have been flipped around... some craft put 0,0,0 on the nose of the craft... others put it at the center of gravity... some flip x and y... it all depends on the modeler and how they created the 3D models of the craft...
side note: this thing with the properties sent over MP is one of the reasons why you might see a craft flying with its engines on fire, or maybe no nose cone, or even landing with its undercarriage raised... this is why you should have the same craft being used and not all of them that you can find in a "spray and pray" install method... especially when it comes to MP because while you know which craft you are flying, FG has to select one that matches the name and that one may not be the same one being flown by someone else out there in MP...
we have seen at least those three problems over MP, too... i named them specifically because of that... in the nose cone case, the craft has three different nose cones depending on the model being flown... the properties being sent over MP did not select the proper nose cone... this problem had been there for a while but it really came to light when some of the MP code was rewritten... the solution was to fix the craft to use the opposite logic for the nose cone... the one with the engines on fire was similar but in that case, the properties had to be reworked so they were actually being transmitted instead of being chopped off because the data packet was too large...
FlyingHigh wrote in Wed Apr 10, 2019 2:42 pm:and also install each aircraft into my "MyAircraft" folder per all the advice of you, Josh and Wlbragg and I'm sorry if I forgot anyone who also made suggestions.
this is fine but for those craft in FGAddon, you don't need to do anything other than to click the [install] button in the launcher and wait for the craft to be downloaded and installed where the launcher places it... there's no need to move it or rename it... if a craft installed in this manner doesn't work properly, it should be reported so that others can take a look at it and figure out what is wrong... in some cases, it could be a damaged archive... in other, it may be an unsupported archive... in any case, other eyes will generally be able to suss out the problem and trigger a fix... that fix could be the addition of code to support an unsupported archive format or it could be that the hanger's archives get updated with new revisions of the craft in it... it all depends...
FlyingHigh wrote in Wed Apr 10, 2019 2:42 pm:The "simply install the aircraft and then you will be able to see its model in MP" idea is simply wrong. It doesn't work like that, clearly there is much more going on under the hood than that kind of advice implies.
the key here is the word "install" and what that implies... learning how craft need to be installed is a step that should not be overlooked... in most cases, it is as simple as downloading the craft from somewhere, unarchiving it, and placing it in a certain directory that FG has been pointed to... if one downloads a snapshot from a git repository, they may need to remove "-master" from the craft's directory name... that is only if they have downloaded the snapshot of the "master" branch, though... if they download the snapshot from the "Issue-123" branch, they would have to remove "-Issue-123" from the directory name the craft is in... other repositories may or may not append similar branch names to the craft's directory, though... it depends on the repo and maybe even the maintainer's repo configuration settings...
remember, there're 100+ cats here and they are not so easily herded
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."