simmerluke

Thanks all for the replies and I understand now that the outboard display units are simply duplicated. Must have been there since day one but it's not something I'd noticed until very recently and now upon casual panning around the cockpit it's not something I can 'unsee'. Nice to hear that there might ultimately be something in the works to correct it. Fingers crossed!

Hi all Just looking around the Asobo 787 flight deck for the first time and noticed that the first officer's display seems the wrong way around, which looks a bit odd when flying from that side. Is there a button in the real 787 flight deck (or the sim) to reverse this? Thanks

For me this 10-view limit for custom cameras is really limiting in larger aircraft so *please* increase it, or if for some reason you can’t then at least open the API up so that someone else can… For the moment I have to ‘fudge’ the fixed camera files to give an extra 10 which is a real pain in the rear!

I have now been able to solve the problem by looking through the Turtle Beach support pages and learning that for X-Plane the 'PC' mode is not recommended and that the 'Legacy PC' modes are what should be used. These have removed the error messages and the product images now also appear with the sim's joystick set up, so all is solved. Thanks again for the replies. Luke

Hi Phil, thanks for your message. I have checked both of these points and it is/was set up correctly. I’ve not had mine long either but have been using it successfully with MSFS and it works quite happily once X-Plane is running. Just the message on XP12 start-up suggesting that something’s wrong ‘under the hood’.

I've just successfully configured the VelocityOne Flight Yoke in X-Plane 12 and it is working just as expected, but now every time I launch the sim I get a BE ADVISED message: Error reading joystick configuration (.joy) file: Resources/joystick configs/VelocityOneFlightYoke - Windows.joy Errors were: Unknown axis (Axis 3) Unknown axis (Axis 4) Unknown axis (Axis 5) Unknown axis (Axis 6) Unknown axis (Axis 7) Unknown button (Button 20) Unknown button (Button 21) Unknown button (Button 22) Unknown button (Button 23) Unknown button (Button 24) Unknown button (Button 25) Unknown button (Button 26) Unknown button (Button 27) Unknown button (Button 28) Unknown button (Button 29) Unknown button (Button 30) Unknown button (Button 31) Unknown button (Button 32) Looking at the in-sim control setup, the unknown axes and unknown buttons are not shown so don't seem to exist. I'm not sure if it's related but there doesn't seem to be any image of either the yoke or throttle in X-Plane, even though the pictures for it do exist in the joystick configs folder. Any help would be appreciated as clearly something is not quite right! Luke

Hi Bob Thanks for the refresh on information re. FSUIPC, which I was aware of for four engines. As mentioned above, I'm not actually using FSUIPC for the throttle axes themselves, only for the reversers. The reason for this is that I was unsuccessful trying to get it actually working. I believe I understood basically what I was doing but the result (just with two engines) always seemed to be that throttles didn't move with the position of the levers and had a mind of their own. There seemed to be no logic at all, regardless of what settings I used, so I reverted back to P3d axes. A couple of questions with this in mind: 1. Is there any way of achieving 'double' engine control without using FSUIPC? 2. If using FSUIPC, might anyone who has the Boeing quadrant working successfully have a screen shot of the relevant pages that I would need to program? Presumably if I can get this working for two engines, the process to extend it as per your message to four should be straightforward. Thanks again for your help.

I have the Boeing TCA pack with one Throttle quadrant which works satisfactorily in P3d with two engine aircraft such as the PMDG 737/777 using the P3d axes for the throttles and FSUIPC to set max reverse thrust with the reverser toggles. With lack of space for a second quadrant, for the PMDG 747-400, is there a way to assign the left throttle handle to engines 1&2 and the right throttle handle to engines 3&4? From what I can see within P3d, each axis can only be assigned to one function at a time. Any help appreciated.

I can only speak from my own experience with regular MSFS crashes and state that, having driven myself potty looking all over the internet for solutions, I was finally able to eliminate them almost completely by updating my installed Visual Studio package. The suggestion came from an extremely comprehensive walkthrough post on the MSFS forum from August of last year. I don't claim to be any expert either however I am now at least able to run the sim regularly for entire flights which is definite progress! Luke

I actually had this issue prior to SU5. Could rarely if ever sit at any menu or the marketplace without a crash within five minutes. Oddly, rarely if ever crashed in-sim. Haven’t updated yet but was hoping this update was to at least improve this situation…

Hi I am new to P4AO, but am familiar with the basic principle of scenery layering with scenery.cfg and add-on.xml files. Within my P3Dv4 installation, if I use P4AO to reorder any scenery within the scenery.cfg (light green) then the new order is immediately reflected in the scenery.cfg file, but the order of files in the add-ons.cfgs (dark green) do not change or match that shown in P4AO. Is there something that I might be misunderstanding with the way that add-ons work or are displayed in P4AO? Any help would be appreciated. Luke

I can only give my subjective thoughts having recently made a similar(ish) change on my particular system. I recently had a chance to upgrade without too much cost from a 1060 (6Gb) to a 1080Ti (11Gb) and having tried various scenarios in P3D I was slightly disappointed (but not entirely surprised) to find very little gain in either frame rates or smoothness. I suspect that going from a 1080 to a 1080Ti would see less gain. Now X-Plane on the other hand, that was a different matter. Much smoother overall experience swapping views etc.

Agreed - one of my few remaining gripes with P3D (they've gradually fixed most of what was on my list over time, but unfortunately never this one).

Personally I'm hoping for an autogen loading fix, as I'm currently back to 4.0 as for me at least this was a vast 'improvement' on 4.1.

I have a vague memory of renaming a file (adding .off) which removed a sinking tyres problem at VHHH in P3D v3. Might have been VHHH_EXCLUDE-BACK.bgl in the VHHH-TERRAIN folder. Can't remember for certain. Haven't got any elevation issues with it in P3D v4 though.