For someone new to one of the best places to start is doing cockpit work. By working on these less complete aircraft you help move the ball forward on that aircraft. There are currently way too many aircraft in a very incomplete state that need tons of work. This approach has a number of things going for it that benefit the FlightGear community as well as someone new trying to become an active member of the community. It is much easier to do and gives you a giant advantage by the time you create an aircraft completely by yourself. We encourage new aircraft developers to start their 'career' by modifying and enhancing existing aircraft. Whatever you do, keep your initial project limited in scope and within your capabilities. Another alternative is to try modeling some cockpit instruments. It's a good way to learn and quickly benefit the community. The advice to start with modeling ground objects like buildings is sound. Much can be done (and in my opinion should be done) through smart use of textures and normal maps. Excessive 3D modeling is often unnecessary.Cockpit modeling is complex and poses some of the most difficult and frustrating challenges in aircraft modeling. Do not start with cockpit modeling, at least not anything more elaborate than very simple GA aircraft.Avoid anything with lots of compound curves.Avoid anything with lots of external detail.Avoid obscure aircraft where information is scarce. Don't rely on the cheesy little 3-views found all over the Internet- the resolution is too low to be useful and they are often not accurate. If fidelity is a factor, avoid anything where you cannot find clear high-resolution 3-views or engineering schematics.Some suggestions for those relatively new to modeling wanting to contribute models to Flightgear: There are many things required to develop an aircraft for FlightGear. Subforum related to: aircraft development right from within AircraftCenter.nas - otherwise, it is probably going to face the same destiny as the route manager code, which was almost re-implemented in scripting space by a few aircraft developers due to hard-coded resrictions that were never addressed. Ideally, this shouldn't be sub-classing the SimGear HTTPRequest APIs directly, but use the cppbind HTTP wrappers - so that these things can be directly handled from Nasal, e.g. Technically, the right thing would be to either expose these APIs to Nasal space via cppbind, or to at least make them better configurable via properties in the meantime. Will be checking the C++ code shortly and report back - but the bug report sounds like a good idea to me - the main guy behind the package management code should be Zakalawe who seems to be back again - so this is likely to get some attention shortly.ĮDIT: seems you are right: there's a ton of C++ code in $SG_SRC/package doing the whole thing in a hard-coded fashion, without the underlying logic being exposed to scripting space - so unless I missed something, this will unfortunately require attention from core developers and cannot be easily worked around without patching/rebuilding an updated binary. without requiring a patch/binary bug fix for issues like this one. such things are not performance-critical by being exposed to Nasal, and could be much more easily maintained that way, i.e. That sounds about right, even though I am not sure why people would hard-code such things. Heiko Schulz (fuselage, wings), Emmanuel Barranger (Instruments) The 727 is Boeing's only trijet aircraft. With a center engine that connects through an S-duct to an inlet at the base of the fin. It has three Pratt and Whitney JT8D engines below the T-tail, one on each side of the rear fuselage Intended for short and medium-length flights, the 727 can use fairly short runways at smaller airports. It can carry 149 to 189 passengers and later models can fly up to 2,400 to 2,700 nautical miles nonstop. The Boeing 727 is a mid-size narrow-body three-engine jet aircraft built by Boeing Commercial Airplanes. If I remove the top URL, then it works, is only the version 3.0 aircraft though I can see from the URLs. I found that xml file, it seems to do have some mirrors, but the aircraft center does not seem to try them:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |