Yes, I am on PC. Using the “Translate Cockpit View Forward” keyboard command (I have assigned it to “W”), I get blocked by the cockpit wall and cannot move into the cabin.
Did I misunderstand what you were suggesting?
1 Like
That’s strange then. Just give me until tomorrow and I’ll take a look at the exact settings I have for it. 
Thanks for your help
O.K., I figured it out. The cameras.cfg for the Asobo B787-10 is here (in my case, Store installation):
C:\Users\my_username\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\SimObjects\Airplanes\Asobo_b787\presets\Asobo\b787_10\config\cameras.cfg
If one saves a custom camera view in a position and then modifies the InitialXyz for this view in the cameras.cfg, such that the view ends up (after restart) outside of the cockpit, the restriction to the movement only in the cockpit is gone. Then you can move around freely to any position in the cabin you want and then save the custom view.
2 Likes
The passengers are modelled about 10-20% too large. The whole point of the privacy barriers is privacy - heads should all be at the level of the head rests. So either passengers are too large, or privacy barriers are modelled too low.
3 Likes
Apologies for the delay, well this is strange. The cockpit door now has a boundary applied since SU4 but I still have my cabin views from before.
And you say you’ve already tried editing the camera.cfg?
Yes, two posts up. Everything worked out fine.
1 Like
Shouldnt this all be possible without people have to modify things themselves?
I was really interested in upgrading my edition to PDL to get this plane but there’s so much not right with this plane, and im on xbox but for now I’d better buy a pmdg and things will work.
I would consider buying this plane if they put it in the marketplace as a single purchase but it seems MS doesn’t think themselves the product is good enough for charging people money for it!
Agreed. In this instance, a boundary has been added that wasn’t there before SU4. Opening the cockpit door shouldn’t put you outside, there’s a cabin door for that. And I’m a PC simmer but it still frustrates me to see Xbox (correction, now console) simmers have zero way to mod things and have to rely on official updates… whenever they eventually come, or in some cases, seemingly never. My brother on Xbox has the same annoyances.
1 Like
I’ve been trying to fly the 787-10 a lot recently (PC, MS Store), and I can only assume that Microsoft must still be trying to find artists to fix the artwork on first party planes.
The exterior model was glitched since 2024 released, and the recent update appears to have added some layers or masks on top of the old model, rather than fixing the old model. At first glance it looks much better, but after flying for a bit it becomes apparent that it’s more of a bandaid than a fix.
When you use the drone mode from various distances, the new paint disappears and the old paint appears under it (for example the jumbled blue and white on the under belly around where the wings attach to the fuselage). The doors appear or disappear, or the paint covers open doors. In other words, the old model is there with a new layer on top with conflicting LOD - and the result is 2 overlapping models using more resources than it should.
So I think they did what they could in a hurry - and I REALLY hope it was just a temporary fix, and that proper fixing of the model is still to come. It’s a Premium Deluxe plane, but is not behaving as one.
5 Likes
Also if n the exterior camera the elevators don’t visually move until you zoom in a little closer
Another indication that the old model is still there, just some sort of mask or layer on top, but with LOD it disappears while the old model remains.
1 Like
Good morning to everyone. I’m here to give a short positive report about the MSFS Airliner that in my opinion is growing good: the Asobo B787-10.
I decided to swap from MSFS2020 to MSFS2024 version (SU4) because of the new EFB (with charts and many other useful utilities) and the new B787-10. I love particularly the Boeing Dreamiliner and reading the bugfixes list I noticed that in the new one the ND-VSD was modeled. This excited me a lot because the B787 without the VSD is simply unthinkable.
After some days of B787 usage comparing some essential systems with the real ones from the manual I can say that the Asobo made a very good job and the B787 should become a very nice simulator for flights in normal procedures.
All the systemsneeded for a normal flight experience are well modeled and work fine. But something need a bit revision to reach the best. Let’s start.
The cockpit 3D model and the textures are nice but upgradable.
-The illumination are well modeled, uogradable but many illumination knobs and lights are working fine.
The only missing things I noticed are:
-the APU title above the APU startup panel on the overhead.
-the illumination of the CDU Key Pads (a well known bug).
-the glareshield lights are not modeled as a solid illuminated led stripe but only with illumination cones. In the ral one the cones are not visible and a lighted led is visible undere the Glareshilde blade.
-passing from External power to Apu power all the SCREENS are momentarily powered off and then on.
Avviamento di un’unità di potenza ausiliaria (APU) del Boeing 787 Dreamliner con batterie
-the fire tests (Engines, Apu and Cargo) are not implemented but the modeled switches and buttons are animated. Many other sysytem used in abnormal procedures present the same situation ( e.g. the alternate flaps and gear, flight recoder, cockpit fwd lights test, EEC Eng Mode, Window Heat Backup, Cargo Temp, ELT, Flight Control Surface, RAT etc…).but We’re speaking about the normal procedures. I’ve to test better the Pressurization Panel and the Air Conditioning Panel.
-the Fuel Jettison System and his indications on the system page are modeled and works but no fuel exspulsion is simulated in the external model.
The HUD is wonderful and very well impemented.
The PFD presents all the indications I found in the manual for normal procedures. The fPV also is implemented with the heading indications on the horizontal center line.
Only the magenta line on the horizon centerline indicating the Mcp selected Heading if the FPV system is selected is missing and the meters selected altitude indication above the Selected Altitude in feet is too big and goes outside the font rectangle.
The ND are well implemented too and all the indications are the same explained in the manual and the VSD also.
What is missing is:
-the VSD Corridor (a couple of cyan dotted lines parallel to the track line indicating the portion of VSD visualized below );
-the cyan airport map symbols should be a little bit bigger with an A letter inside the indicating wich Alternate Airports is selected in the FMC.
-a better airport quality map with cyan and orange zones with specific gates, taxiways and runway indications.
-the pos function selectable from the ND drop menu should be modeled (is a green line indicating the radial bearing from the FMC-CDU selected VOR Station starting to the aircraft position symbol)
-Some indications regarding the ETOPS operations.
The Normal Checklistes pages are well modeled and wonderfulto use.
The system pages are also well modeled and present all the normal indication as i the FCOM but the system peges titles tag should be in amber during startap operation when one of the parameter is not in a normal range.
-On the STAT page before the startup a list of the shed systems in white should be present in the Status Messages square at the bottom and on the Elechtrical Page Shed System square. The EFIS/DISP, MAINT and CB pages are not modeled but are no essential for normal operation.
The essential functions of the FMC-CDU system for normal flight procedures are implemented in joint with the standard BOEING-EFB.
What is missing a lot are the COMM pages functions (ACARS and CPDLC system linked with Hoopie or VATSIM) and the Radio-Control Panel system pages wich are only two: VHF Radio and Transponder (all the systems are impemented or will be released in the B787 V2 by the Horizon Simulation but only for the MSFS2020 Asobo B787. They are also working on a compete version of the Original Boeing EFB). Wonderful would be the messages aside the PFD. Ok hope in the future Asobo will model it.
Th GPWS and the Weather Radar are basic but working as the TCAS system. They surely need some more details to be implemented. I’ll test them a little bit more accurately and report.
As mentioned maybe in the future We can see more systems and more bug fixed.
That’s it at the moment. This is not a study level aircraft but for me is a very good Normal Procedures B787 Simulator. THANK YOU Asobo.
Hope this helps to give Asobo the right motivation in developing better and better this wonderful piece of technology.
This little review is a personal opinion and I’m not a pilot but a Sim Enthusiast only. So forgive me…I actually need to speak about this Airliner and about the Great Job Asobo made.
Greets to Everyone.
P. S. Ah forgot to say that the VNAV Speed mode is not buggy, it activates only pushing the R and L mouse buttons together on my PC.
11 Likes
Thanks very much for your scholarly review of the 787-10, my goto airliner.
I would invite you to take a good look at the autopilot, which has been a plus in the evolution of the simulation. The 787 AP is a generation ahead of the 777, 747 etc…
In SU4 I and another pilot noticed some degradation of performance especially in turning off the AP and transition for me to the ILS and the other pilot to thrust reversers… button on throttle inop (I verified).
There is also trouble when you transition from VNAV to the ILS… used to be smooth transition initiating the GS but now hit or miss. Spent hours on this… seems to vary with the airport.
Have also spent a lot of time perfecting VR in the cockpit and and using FOV limitations of 90% in Virtual Desktop Streamer with 40% sharpening in OPENXE Toolbox. (See below screen shot).
I use the small font in the ILS numbers in the flight director as the eye chart.
Anyway, keep up the good work… Oh and can you give a reference to the manual you cite?
3 Likes
Hi A68yoSniper….Glad You appreciate…I’ll take a look at the things You’re questioning….regarding the manual please contact me in private.
Many Thanks
Gioc
1 Like
I think I have found “the” bug in the AP as there is a very nice video on the ILS transition by I believe a 787 Captain that shows an automatic transition from VNAV to the GS:
This now seems to be gone in SUD4. Have to do it manually. It is around 14-16 minutes into the video. The Captain gives a nice discussion of all the factors that come into play in the approach.
I have to try other airports than SFO.
2 Likes
I’m increasingly disappointed by the state of this 787-10.
Currently (SU4 v1.6.34.0) during cruise, the throttles are oscillating way too much, spooling half way down, then all the way up, then 1/4 down, then all the way up, and so on.
This happens also if you try Autoland (LAND 3), and almost always either slams itself in to the runway, or is applying power when it should be going to idle so you float too far down the runway.
I’ve done my best with the first party “premium deluxe” planes, but tomorrow I’m moving on to 3rd party purchases. Until Microsoft decides it’s worth fixing the very large and growing fleet.
5 Likes
Yes, is disappointing. I had an actually stall today based on this funny action while on a standard approach. Not sure what is going on. Flying the approach again. Have been flying a lot of approaches because of that bug I found in the VNAV/ILS transition. It is now replicated. If you look at their change log they did a lot of things on this plane but missed a few essentials.
BTW, this is the VNAV/ILS Bug;
2 Likes
Reading this just fixed my issue of missing TO T/D info on my CRZ page. SimBrief has FL400 the FMC had FL410. I’ve added this to my notes now.
For those flying the 787 here is a video of the ILS/G/S bug. Further validation would help getting MS to fix this. The bug link is in this thread.
1 Like