thevirtualfer, I really believe the C172 needs an enhancement in systems, models and textures. But keep in mind it is the default aircraft, and you cannot change a lot the default aircraft or people with low-end PCs will complain about low FPS.
This is my proposal: do not modify the default aircraft, but create a new alternate version. For example, c172p/c172-detailed-set.xml, which loads c172p/Models/c172p-detailed.xml which loads c172p/Models/c172p-detailed.ac This way, you do not modify the default files and you don't need worrying about providing a model for low-end machines with a reduced number of vertex.
This is my TODO list for this project (I'm working right now on some of these points)
- I believe the textures in your shared directory do not match the textures you are using in Blender. COLOR_interior_temp is missing, and COLOR_interior_test has a transparent background. You are UV mapping the interior to the transparent areas and I don't think this is what you intended: the interior is transparent in the version you are currently distributing. Can you check if the textures in your shared directory are correct?
- I'm creating this c172p-detailed-set.xml model as an alternate version of the default C172P. This way, we can have the default C172 and the "more detailed" C172.
- Since I'm using a different *-set.xml, I can set the default values of MASTER and ALTERNATOR to false, and MAGNETOS to OFF. This implies you cannot start the C172 just pressing S, as usual: you have to set MASTER ON, switch MAGNETOS to BOTH and then STARTER. That is to say: you have to follow a real checklist. What do you think about this change?
- Transponder! The current model doesn't include a transponder. I'm looking for a shared model compatible with OpenRadar. Maybe is the kt76a compatible with OpenRadar? According to this link, it is:
viewtopic.php?f=75&t=19826 But the configuration documented in this link does not match the configuration recommended in the wiki:
http://wiki.flightgear.org/Transponder And I'm not sure whether the kt76a described in the first link is the same kt76a we currently have in git.
- Liveries are not working and I'm not sure why. Probably, you renamed the exterior model. I have not checked this.
- The version currently in GIT includes support to ALS secondary lights, and your version doesn't:
http://wiki.flightgear.org/ALS_technical_notes- The order of the radio stack seems awkward to me. I'm used to the order (from top to bottom): RADIO CONTROL, COMM1, COMM2, ADF, DME, AUTOPILOT, TRANSPONDER. Currently, the ADF is between the radio control and the COMM1. This is not completely unreal, I have seen some cockpits in the internet with the ADF below the CONTROL. But I prefer COMM1 below the RADIO CONTROL, because all aircraft I've seen in real life are like this. Any opinions about this order?
- The seats are VERY low poly. They really need some round angles!
- I think the bags next to the doors are a very nice touch. A proposal for a extra nice touch: if you click on them, a window with the checklists will open!
- There is an instrument currently not modeled, but I don't know if it is interesting to you: the outside air temp gauge. It is on the top of the windshield:
http://www.cruik.org/blog/ventubes/ventube-out.jpg