Holla,
Well done to you.
This may just compete against the real thing. Which of the two pictures is the model?
awexome-ly
bicyus wrote in Wed Apr 11, 2012 7:15 pm:Omega95, right but i think it will be better directly on scotth Airbus-aircraft project.
right for now, but i would move it, when new repo on Scoth Airbus-aircraft project is ready.
Also, notify us, when 3d cockpit model is ready, so we could all help on xml stuff
scotth1 wrote in Thu Apr 12, 2012 12:07 pm:bicyus wrote in Wed Apr 11, 2012 7:15 pm:Omega95, right but i think it will be better directly on scotth Airbus-aircraft project.
right for now, but i would move it, when new repo on Scoth Airbus-aircraft project is ready.
Also, notify us, when 3d cockpit model is ready, so we could all help on xml stuff
Yeah I think it is better to keep everything together, nobody can keep track of multiple projects or multiple repositories.
Simply create a new branch under the existing A320neo repository under the airbus-aircraft project is what I would suggest.
Git can handle "move" actions on files.
S.
awexome wrote in Thu Apr 12, 2012 11:54 am:This may just compete against the real thing. Which of the two pictures is the model?
i will propose, if you are doing rest of the cocpit to model the cockpit Door, to be able to open it.
omega95 wrote in Thu Apr 12, 2012 12:27 pm:I was trying to do that but then branches get too confusing sometimes, and I thought the a320neo repo is for files that can be run in FG, thus there're copies of files in other branches.
If we're trying to keep it together or something, can there be a development repository in the airbus-aircraft project where we can keep development files?
If you split development between several repositories how are you going to merge all the changes back together, that's exactly why branches were created, it's like a mini repository but you can merge everything back easily. It's up to you guys how you want to work, but my suggestion is just create a single development branch, work on that until everything is working fine, then merge that back to the mainline.
bicyus wrote in Thu Apr 12, 2012 3:40 pm:scotth we speak about somewhere to store files needed for the aircraft, but that are not part of it and realy don't need track or versions.
* Documentation (Tones of it!) fbw, aircraft, fmgc, pilot brief operation...
* Textures edition
* Development 3D models
* etc..
these files will in some future "OUTPUT" some files for the A320neo aircraft, but until then there are not part of the Aircraft directory.
omega95 wrote in Thu Apr 12, 2012 3:46 pm:I'd suggest a whole repo instead of a branch as then we can create further branches like 'flightdeck', 'cabin' etc. and have work based on these sub-groups there.
The nav display is common to the A320, A330 and A340 series, so ideally would be shared between all three. Using the C++ NavDisplay instrument available in FG 2.6, Scott has created a full-functioning display for the A380, which can be adapted for the A320 with minimal effort, I hope. (It's probably not possible to share the actual XML between the A320/340 and the A380, alas). Contact James or Scott before spending time on this task, please.
I was going to look at adding the C++ nav display to the A320neo, I'll wait until the new modelling of the cockpit is done, it's not too difficult, it adds waypoint, route path, VOR/NDB markers on the ND.
- Reestructure of Airbus FBW, Flight envelope
- Soft bank
- Hard bank
- Alpha min
- Alpha prot
- Alpha floor (full engines power, speedbrakes retraction)
- Alpha max
Users browsing this forum: No registered users and 10 guests