There is an update to the A380 Milestone 1 available from the wiki page
http://wiki.flightgear.org/index.php/Airbus_A380
Enjoy
S.
scotth1 wrote:There is an update to the A380 Milestone 1 available from the wiki page
Gijs wrote:The file does not include all of the files. Is it intended to overwrite/extend the CVS aircraft?
scotth1 wrote:It is possible I left something out when packaging it up, are you getting some errors?
Liam wrote:Nice improvement
Liam wrote:The liveries are not correct however, the fuselage appears painted on the top instead of the sides, the tail is on the fuselage, etc.
Scaling image 'D:\FlightGear\data\Aircraft\A380\Textures\Common\buttonlight.png' from (34,32) to (32,32)
Scaling image 'D:\FlightGear\data\Aircraft\A380\Textures\Panels\ecam\sd_doors_01.png' from (342,237) to (256,256)
Scaling image 'D:\FlightGear\data\Aircraft\A380\Textures\Common\keyboards.png' from (300,200) to (256,256)
Scaling image 'D:\FlightGear\data\Aircraft\A380\Textures\Instruments\pedastal1.png' from (1152,1024) to (1024,1024)
MATERIAL "skin.001" rgb 1 1 1 amb 0.243379 0.243379 0.243379 ...
MATERIAL "skin.001" rgb 1 1 1 amb 1 1 1 ...
Gijs wrote:Ambient coloring
The lighting settings changed in CVS (and thus next release), making this plane very dark when looked at from certain angles. This can be solved by copying the RGB value of each material to the AMB value. For example:
- Code: Select all
MATERIAL "skin.001" rgb 1 1 1 amb 0.243379 0.243379 0.243379 ...
should be
- Code: Select all
MATERIAL "skin.001" rgb 1 1 1 amb 1 1 1 ...
Liam wrote:does this apply to every texture of the model? and of every model including interior/wings/nontextured (except lights/contrails I presume)?
also, will there be a visual difference for 1.9.1 users?
Gijs wrote:Ok, first congrats on this awesome plane! Nice to see it in FlightGear. Fahim, thanks for the amazing work you did the past year(s), and see you soon
Gijs wrote:I do not feel like I am the right person to check the flight behaviour, as I can in no way tell you if it is realistic. However, it does fly like one would suppose it to fly.
Therefor I only listed some technical-bugs/tips.
Gijs wrote:Texture resizing
- Code: Select all
Scaling image 'D:\FlightGear\data\Aircraft\A380\Textures\Common\buttonlight.png' from (34,32) to (32,32)
Scaling image 'D:\FlightGear\data\Aircraft\A380\Textures\Panels\ecam\sd_doors_01.png' from (342,237) to (256,256)
Scaling image 'D:\FlightGear\data\Aircraft\A380\Textures\Common\keyboards.png' from (300,200) to (256,256)
Scaling image 'D:\FlightGear\data\Aircraft\A380\Textures\Instruments\pedastal1.png' from (1152,1024) to (1024,1024)
Gijs wrote:Ambient coloring
The lighting settings changed in CVS (and thus next release), making this plane very dark when looked at from certain angles. This can be solved by copying the RGB value of each material to the AMB value. For example:
- Code: Select all
MATERIAL "skin.001" rgb 1 1 1 amb 0.243379 0.243379 0.243379 ...
should be
- Code: Select all
MATERIAL "skin.001" rgb 1 1 1 amb 1 1 1 ...
Gijs wrote:Liveries
The real problem is not the mapping, but the use of two different texture layouts. The Airbus livery In the Textures/Livery/House/ directory is quite different to the ones in Textures/Livery. That also explains why the house livery looks fine.
Gijs wrote:Framerate hit
The exterior view does not have much effect on my framerates. Looking around in the cockpit is a different story. The framerate hit is quite noticeable. You might want to take a look at the model/textures to see if anything can be improved.
Gijs wrote:Views
As said to Fahim, I (and probably most others) prefer the helicopter view to be behind the aircraft, instead of infront (looking backwards). This can be easily achieved by placing a - in front of the 75 meter offset of the views. With that offset, the plane does not fit into the screen anymore, so something like -110 would probably be better.
Also, the walk view seems to be broken.
Gijs wrote:File/directory structure
As said before, I do not like the directory-tree of this aircraft. I do not know if it is like this from the first drafts by Ampere?
Compared to other FG aircraft it is very chaotic, with .xmls, model and textures being spread all over the place. Using sort of the same structure as the majority will make it easier for developers to use things from this plane on other planes, as well it will be easier for new developers to understand (as all documentation is aimed on the general structure). Ofcourse you are free to use whatever structure you like, just my two cents.
Gijs wrote:Looking forward to further improvements. It looks very promising!
Cheers,
Gijs
Users browsing this forum: No registered users and 2 guests