Jump to content

kentwerickson

Members
  • Content Count

    88
  • Joined

  • Last visited

Community Reputation

2 Neutral

About kentwerickson

  • Rank
    Advanced Member

Recent Profile Visitors

1,311 profile views
  1. The Power levers should work with a regular axis. Nothing was actually changed in that. Have you tried re-assigning an axis? For the benefit of anyone else having the throttle control issue I reported above, I finally figured out a work-around by assigning custom commands to my trigger axes -- "throttle up a bit" and "throttle down a bit."
  2. I am not seeing any engine exhaust heat effect in v1.61. Running XP11.51+, Vulkan. Tested with all 3rd party plugins disabled. (Please forgive me if this issue has been reported elsewhere -- I've had a look and did not see it). EDIT: I'm not seeing the effect running OpenGL either.
  3. Oh my goodness this is even better! Thanks very much!
  4. That did the trick; thanks very much! EDIT: For others who may be interested, I just discovered that the plugin below also works (a bit better in my opinion because the brakes are applied more smoothly using the "gradual" option. https://forums.x-plane.org/index.php?/files/file/9487-progressive-braking-plugin/
  5. This would be the next best option if you know how (I lack such skills), and so long as it doesn't interfere with other functionality. Yet I'd much prefer to have this functionality native to the 340A logic -- doesn't seem to be problem for other aircraft developers. But maybe it's a Gizmo constraint introduced by changes in XP11?
  6. Thanks for the feedback. This I know, because the joystick button I have mapped for the parking brake (Toggle brakes max effort) still works with the newly updated 340A. This is the unfortunate/unexpected news, especially for me also being unable to control the power levers with my joystick; e.g., I cannot conveniently control my speed during taxi by easing the power levers into the beta/reverser range. I can still perform this action with keyboard assignments, but then it becomes difficult to track the exact position of the levers without constantly watching them -- just not conducive
  7. Thanks Goran, for your reply. The triggers on my Xbox controller are treated by XP the same as (regular) joystick axes. They can be reversed, response curves set, etc. There are several throttle control options available from the pulldown menu, including "Backup Throttle," "Throttle Vertical," "Throttle Horizontal," and then individual controls for Throttles 1-8. I have tried each of these options with the 340A but no luck -- no throttle movement at all. As I recall from the XP10 version of the 340A, I had to first move the levers with my mouse just a bit forward of ground idle before
  8. Firstly, thanks very much for the update! A few things I've noticed immediately (tested with all third-party plugins disabled): 1. It is possible to close the main cabin door with the stairs deployed (don't recall if this was possible in the XP10 version, or even whether this should not be possible in the real world - I'm guessing not). But either way, not a big deal -- just an FYI. 2. More critically, I can no longer control either the power/thrust levers or the brakes (hold brakes regular effort) with my Xbox 360 controller. In XP10, I used the left and right triggers for power con
  9. I had roughly the same problem. When I first downloaded the SMP v5.05 installer, SMP installed fine. On first launch, I then checked the configuration box for volumetric clouds -- nothing happened/changed, and afterward I was unable to clear this setting; i.e., the checkbox was "stuck" on. So I tried to re-install v5.05 (several times) using the same installer and began receiving the error above. After reading this post, I re-downloaded the v5.05 installer and this fixed the installation problem, but not the stuck checkbox problem. EDIT: I now see that the volumetric setting is mutua
  10. In other words I'm SOL. Well, I certainly don't blame Sundog -- you guys have been among the few notable exceptions over the years of standing by your products and offering timely fixes/updates, and I applaud you for that (as for the others, just one more reason I am still on XP10).
  11. Can you then post a link here, or send to me by PM, the v4.9.5 installer so I can try that? Thanks.
  12. No. This is among the first things I checked -- turned off all external aircraft lights (they are turned on in the images here because in order to save time while testing I had XP set to load the plane with the engines already running and ready for takeoff). Also tested to see if time of day matters -- e.g., day/dusk/night. No difference. Variety of reasons, including that I could not afford to repurchase all of my payware for XP11 (plus, I was not initially all that impressed with what I considered to be mostly incremental improvements in XP11). The Dash 8 is payware by FlyJSim, and f
  13. I've just discovered a strange anomaly with SMP v4.9.6.2. Compare the lighting on the prop blades in the two attached screenshots; the first is with SMP enabled, and the second with SMP disabled (no other changes). The second image is how the props should look. I only now just noticed this issue because I haven't flown the Dash 8 for quite awhile, and it took me quite awhile to narrow down the culprit to SMP -- or so I believe, and who'd have guessed??? (at first I had no idea what could be causing this issue, and tried lots of other things before realizing that the last SMP update was the
  14. Thanks very much! View from Half Moon Bay (CA) with evening fog rolling in is close to sublime! (XP10)
×
×
  • Create New...