-
Posts
1,556 -
Joined
-
Last visited
-
Days Won
48
Content Type
Profiles
Forums
Latest X-Plane & Community News
Events
Downloads
Store
Everything posted by Coop
-
Updating nav-data is an optional thing for X-Plane, it brings all the procedures and waypoints, etc. to the latest version to match the real world. It can be necessary for online flying but isn't necessarily needed for flying offline. If you are interested, many people use Navigraph for their NavData: http://www.navigraph.com
-
That is quite odd, I can not replicate the issue, but I am investigating it. Can you try backing up, then deleting the preference files in "X-Plane 11/Output/preferences" - the ones that start with "X-Plane__________.prf" and see if that resolves the issue? (If it doesn't, restoring the preferences you back up beforehand will bring back the settings)
-
@Bourrinopathe Has a great summary there, it essentially boils down to this: Throttle (left lever) determines the power output of the engine in the normal range (not reverse or beta, then there are different control laws). Fuel control essentially determines minimum fuel flows (Fuel Cutoff: 0; Low Idle: low; High Idle: higher minimum than low idle) Prop will control your RPM In Beta mode, the throttle changes function and while the engine stays at idle, moving the lever will command a propeller blade pitch change to change your beta power output. In Reverse mode, the prop is set to reverse pitch setting; throttle controls the throttle.
-
There is a P-Factor that is determined by X-Plane as it runs - We are looking into making sure it is sufficient P-factor to represent the high torque of the aircraft.
-
Bug for KG FF is logged. No inertial separator annunciator is currently present, but that is a good idea for an addition.
-
Thank you for the log file
-
These are commands that can be triggered either using keyboard or joystick commands, which is set through the X-Plane keyboard command/joystick command window, respectively.
-
We are still working on this issue - there is a bit more debug information, so log.txt and screenshots from 1.0.1 are very much appreciated in finding the root cause.
-
Both plugins use libacfutils (An aircraft plugin library) XGS is using an older version of it, and it is loaded before our aircraft, so X-Plane decides not to load our version (since one is already loaded by XGS) but since it is an older version, it is not compatible. We are working on implementing a version of libacfutils that is linked statically with our plugin, so it is forced to load again, but that is still being worked on. Until we can get a static version of libacfutils working with our plugin, I would recommend using a different landing speed plugin, there are many available that do not rely on libacfutils, here is one that I have used: https://forums.x-plane.org/index.php?/files/file/7995-landing-speed-plugin/
-
The avitab will show automatically if the AviTab plugin is installed and active. It sounds like you have the plugin, but if you don't or need to update you can get it from here: https://github.com/fpw/avitab/releases or here: https://forums.x-plane.org/index.php?/files/file/44825-avitab-vr-compatible-tablet-with-pdf-viewer-moving-maps-and-more/
-
Pocket Rocket "Yellow Jacket Original" Livery View File This is the "Yellow Jacket Original" livery. This is the version of the "Yellow Jacket" livery that has a larger tail number on the tail but does not support custom tail numbers through the tail number management system. The included "Yellow Jacket" livery supports custom tail numbers. This was included in release 1.0.0 of the Pocket Rocket, but for simplicities sake, it is going to only be available via download in future versions. Submitter Coop Submitted 03/29/2019 Category General Aviation Livery For http://www.x-aviation.com/catalog/product_info.php/pocket-rocket-p-161 X-Plane Version(s) X-Plane 11
-
Version 1.0.0
37 downloads
This is the "Yellow Jacket Original" livery. This is the version of the "Yellow Jacket" livery that has a larger tail number on the tail but does not support custom tail numbers through the tail number management system. The included "Yellow Jacket" livery supports custom tail numbers. This was included in release 1.0.0 of the Pocket Rocket, but for simplicities sake, it is going to only be available via download in future versions. -
Yup, something was messed up in our state tracker - it should be fixed in the next release, hopefully coming out in the next few days
-
Odd, we are taking a look into this
-
Can you upload the "log.txt" file that is generated in the "X-Plane 11" folder after you run X-Plane? This will tell me more what is going on behind the scenes. Also can you screenshot what you are seeing?
-
Weird, can you screenshot what you are seeing? That doesn't seem to happen in non-VR variants, so that is quite odd.
-
Will look into this one, it should certainly not be that strong.
-
The Maintenance manager is located in the left sidebar tab. If you hover your mouse on the left side of the X-Plane window, the sidebar tab will appear. When the tab is clicked, the menu is shown.
-
Looking into it, thank you for reporting
-
It looks like your graphics card drivers are significantly out of date, can you try updating those? This has resolved the issue for other people with similar graphics drivers.
-
Not sure why that got changed, removed. This is being looked into.
-
Raindrops Keep Falling on My Head ( Inside the Cockpit!)
Coop replied to billd393's topic in Pocket Rocket
This sure is an odd bug - I will talk with the developer of the rain drawing library to see if he has any ideas. Until then, you can disable rain effects from the sidebar aircraft menu, disable rain effects. -
Not currently planned, but I have added this to our idea list.
-
Re 1: Already fixed - will be in next release Re 2: Should be fixed as well, will check Re 3: Yes, it should. Bug logged. Re 4: Still looking into this, but this might be an X-Plane bug as a whole, still being investigated. Re 5: This is an X-Plane command that we are not intercepting. Not sure about this as well, will look into it. Expect an update in the next few days, we have a large list of bugs already fixed, and more being worked on.
-
No, that wouldn't be it. We are trying to find where this issue is originating and will get a bug fix ASAP, once it is determined.