Well, I got it downloaded and installed into the Sim, with the updated Engine Data from the new .cfg file. The fact that the airplane showed up in the Aircraft Menu without missing a beat this time looked like a good install.

 

OK... started the Sim at DIA, 16L. The Model really looks good, all the wheels are on the ground. Is it me, or are the wingtip and fuselage lights kind of sparse?

 

Flaps 20, move the throttles forward, at 140 pull the yoke back... voila, we're in the air. Gear up, flaps up... and away we go!

 

(Remember... I have little experience flying jetliners.)

 

If I didn't know any better, this is one of the smoothest airplanes I have flown. No jerky movement when I move the yoke, everything feels very stable and solid... turns, climbing and descending... wow!

 

Is this this the way it's supposed to fly?

 

So... I go out about 30 miles, do a 180, and come back to land on 35R. The Ga part kicks in, because I fly her all the way down only using the PAPI; no AP, or ILS. She was smoother than any number of landings I've done before, in any number of GA airplanes!

 

I think my problem with the last Install was that I tried to integrate the separate 787 Panel without all of the Updates, and by then I couldn't figure out what I had, and what I hadn't.

 

So, I'll try DL'ing the Panel again... but before I do, are there any words of wisdom from the pros out there? Is the current Panel offering complete, or are there Updates I need to get as well?

 

Cheers!

 

As far as the lights are concerned, the lights aren't supposed to be that bright, so that much is correct. As for the handling, if you are using the updated FDE, which you said you were, you should be good to go. I've never flown a real 787, so I wouldn't know. Nobody from TDS has flown a real 787, either, so the updated FDE was based on what was found in the FCOM as well as how the FDE designer felt that it should handle.

 

As for the panel, TDS didn't make a panel, so I don't want you to get the idea if you do come across a panel with the TDS name that they support it. They don't. I see the panel by Ray Long includes the TDS name, but it's not an official TDS panel. You can use a third-party panel if you'd like, but you really need to read the TDS 787 manual in order to get instructions on how to merge a third-party panel with the aircraft if you aren't familiar with installing panels on either TDS, SkySpirit, or Project Opensky aircraft. It's not as simple as just drop the panel in and off you go. XML codes need to be added in along with several lines from the original 787 panel.cfg into the panel.cfg of the panel you are trying to install.

 

If you have any other questions, feel free to ask.

Kevin,

 

After reading your post, now I understand a bit more how involved merging a Panel into this airplane is. For the time being, I'll just use what the Model defaults to... it works just fine for me.

 

Thanks for the assistance!

 

:smile:

Sure. Something you should know is that unlike most models that have been released, the TDS 787 along with the SkySpirit aircraft and some Project Opensky aircraft rely on XML for their animation, and the XML codes are placed in the panel folder and recognized by the panel as gauges. I think the Project Opensky 747 series started to make use of them, and as time went on, the animations got more and more advanced. What started out as wing flex and gear animation on the 747 got so advanced to the point where on the 787, you have a lot of ground service vehicles, drooping flaperons, spoilers, and even the lights. The idea was that if somebody didn't like the default parameters that were set, they could easily change it on their own.

"Open Source" aircraft; I wonder if that's the 'Open' in POSKY?

 

So, for example... I could add beacons and lights to the wingtips and fuselage through the Aircaft.cfg to be more 'flashy', just like any other airplane?

 

Sort of gives the End User the ability to 'fine tune' the airplane to their own individual tastes, just like the airlines do with the real thing... cool!

 

I could add beacons and lights to the wingtips

Alas no... because the wings flex, the lights are in the model code so not accessible to us.

 

I've had success with the panel linked in my first post.

All that needed checking was that the [VCockpitxx] sections of the original panel.cfg were present in the new one.

(So as to include the xml code for the nosewheel)

 

On which topic, I'm sure I noticed the nosewheel leg extend a bit, shortly before touchdown!

Not sure if that's played for... the model is full of nice little details. 

"Open Source" aircraft; I wonder if that's the 'Open' in POSKY?

 

So, for example... I could add beacons and lights to the wingtips and fuselage through the Aircaft.cfg to be more 'flashy', just like any other airplane?

 

Sort of gives the End User the ability to 'fine tune' the airplane to their own individual tastes, just like the airlines do with the real thing... cool!

 

Not quite. The original Project Opensky aircraft that were designed back in 2004, like the 757, didn't have the ability to edit things like that. With the XML codes, you can basically adjust how much wingflex you want, the timing for when the lights flash, things like that. I'll give you another example. On the Boeing 777 series, the way the flaperons were set up, they were linked to the thrust reversers, so when you engaged the thrust reversers, the flaperons would go up. This isn't realistic, as on the real 777, they're actually linked to the spoilers, not the thrust reversers. I was able to go in and make some adjustments, so that when I land, the flaperons would go up when the spoilers came up.

 

I've had success with the panel linked in my first post.

All that needed checking was that the [VCockpitxx] sections of the original panel.cfg were present in the new one.

(So as to include the xml code for the nosewheel)

Well, yes, that and copy the folders into the panel folder as well.

Well, yes, that and copy the folders into the panel folder as well.

Actually the best way to experiment with a new panel is to copy the whole panel folder into the aircraft folder, having previously renamed it as panel.ws or similar.

In the aircraft.cfg file you simply comment out the panel line and insert a new one saying panel=ws

That way if things go pear-shaped, it is easy enough to revert to the original.

Actually the best way to experiment with a new panel is to copy the whole panel folder into the aircraft folder, having previously renamed it as panel.ws or similar.

In the aircraft.cfg file you simply comment out the panel line and insert a new one saying panel=ws

That way if things go pear-shaped, it is easy enough to revert to the original.

Sorry, folders I was referring to was for the XML gauges. Copying the virtual cockpit lines into the panel.cfg is all good, but it won't do any good if you don't copy the XML gauges over as well. I didn't get specific because the names of the folders are different depending on the aircraft, but for the 787, there are two folders in the original panel folder that would need to be copied over into the new panel folder. Otherwise if you didn't do that, you wouldn't get the XML gauges, and the aircraft would revert to what is known as backup mode. Backup mode is quite possibly the reason why Alan initially had the wheels appear to be anywhere else other than the ground.

The panel link I gave above is already complete in every way, do try it. 

 

What this model really needs is

• a rework of the FDE, as performance information becomes available
• some paints for the GSV's
• some nice effects, and:
• a VC a la POSKY 777 ! (Who knows, maybe??)

Well, on a whim I downloaded the Panel WingZ recommended, and Installed it as per the Readme file included with the D/L. I also checked the .xml code against the Original, as WingZ also mentioned, and had to add one file to the new Panel folder.

 

Fired up the SIm, and the new 787 Panel shows up right as rain! Everything works, and all of the auxiliary panels show up, including the FMC!

 

Which leads me to another question... I have a payware add-on FMC (Eric Marciano's EasyFMC)... do I dare try and add it to this airplane using the provided Install utility, or just leave it be? Maybe let it be...

 

Thanks to all who responded... your input and 'education' made this Install painless, and gave me some valuable insight about the Airliner side of the Hobby!

 

Cheers!

 

Alan

 

The panel link I gave above is already complete in every way, do try it. 

 

What this model really needs is

• a rework of the FDE, as performance information becomes available
• some paints for the GSV's
• some nice effects, and:
• a VC a la POSKY 777 ! (Who knows, maybe??)

The updated FDE uses information that came out of the 787 FCOM to the extent possible. As for a virtual cockpit, that won't be happening unless somebody else decides they want to make one since Hiroshi, the guy who made the models, doesn't like virtual cockpits and isn't going to spend the time to make one. The virtual cockpit that you see in the Project Opensky Boeing 777 series was actually made by somebody else, so that's why it has one.

Have any of you noticed, when using the 2D Panel and hat switch for a 'look over the shoulder' view, how there's half of an airplane behind you? It's neat to look at...

 

How about we keep this Thread going, perhaps as an outlet for any new tips or Updates that come down the pipe...

 

If the FDE update is this file tds_787-8_fde_rev1.zip a lot still needs to be done.

 

The multiple contact points need to go (if you want your autobrakes to work)

 

Nose gear contact point is waaay behind the actual nose gear.

 

Static and pitch contact points need adjusting

 

Center tank needs to be move back (towards the c of g)

 

I have done all of the above including tweaking all the gear XML

 

Have just had a perfect AES pushback..

 

I am looking at adding effect strobes and beacons (effect strobes only lighting at flight flex)

 

This model is way too good to be left as is..... will report back soon.

I don't see the "excitement" about this aircraft.  It flies horribly on my system (compared to other models) and appears to have been hastily released as there are several "problems".

 

I just don't enjoy it at all and it was removed from my hanger.

 

gwillmot

Sorry to hear there are several "problems" - perhaps if you had been less ambiguous and listed things out to improve, like what Ed just did, we can fix them. Otherwise, you just sound bitter for the sake of being bitter.

 

Because this aircraft is released, does not mean it is perfect, set in stone, or off the table for changes. Hiroshi Igami is known for constantly making updates to models as imperfections, bugs, errors, etc. are pointed out, and this aircraft is no exception. But to say the aircraft was "hastily" released, is just a flat-out incorrect guess. The external model has been in development since before the 787-design was even frozen by Boeing. In fact, it started development when it was known as the 7E7.

 

With regards to the FDE, unfortunately with the rise of payware development, and fall of freeware development, we don't particularly have someone entirely dedicated to the flight dynamics as Project Opensky used to. If anyone wants to step up and take on a challenge like this, we are certainly open to potentially welcoming someone that has experience in the field and is open to development.

 

Virtual cockpits - unfortunately, those aren't made overnight and gauge programming in particular, cannot be learned in a short amount of time. I can model a virtual cockpit, but there's no point to me in doing so if the gauges are just MSFS default stuck in to fit the screens, with limited functionality - as people would just complain about that too. That field is almost unheard of in the freeware realm, and this area is often a scarcity even as payware. This is primarily the reason Hiroshi creates FSX-native models, so people can attempt to merge the model with a virtual cockpit of their choice, from another developer.

 

Again, we are open to new developments, individuals taking on challenges and learn something new to better the aircraft, but just complaining about something without being specific, or offering ways to improve it, is simply useless, and certainly doesn't make me want to personally continue freeware development any more-so than I do.

 

This aircraft, and all aircraft we make, are always open to improvements, and are never "off of the table," just because they have been released.