Jump to content

GridiroN

Members
  • Posts

    26
  • Joined

  • Last visited

Posts posted by GridiroN

  1. Obviously could be pilot error, but I cannot figure out why the Mu-2 flies appx 5 degrees nose up, and about 80kn true too slowly. I'm fairly certain this is not expected behavior. If anyone has any tips, it would be appreciated. 

    I've tried changing the centre of gravity and the plane rebalances back to 5 degrees nose up. 

    I've tried trimming it out hard, same thing.

    950291912_X-PlaneScreenshot2022_10.13-15_07_35_52.png

    1263671772_X-PlaneScreenshot2022_10.13-15_33_42_75.png

     

     

  2. 6 hours ago, tkyler said:

    A favor....to help me understand user cases better.  I was laboring under the assumption that if a user had  "dual levers" intended for a common function (power or prop), then they would logically map those levers to "1 and 2" (throttle or prop).  So if you have multiple prop levers as mentioned in the previous post,  then why would you not map those to 1 and 2 to begin with?....i.e  what would you map the 'left' and 'right' ones to in another circumstance?

    -TomK

    When you start doing this, you start getting into territory where we're getting hardware restrictions. In planes without failures modelled, it really doesn't matter to have multi axis' and in cases where you do need to it (The AirFoilLabs King Air 350 for eg.), it's manageable my using the mouse instead. 

    The issue with your product is that it doesn't have a mouse clickzone for manipulation AND it requires more than 1 axis, making it difficult to manage unless you have pretty good hardware with many (useful) axis' (like a honeycomb or something).  

  3. 8 hours ago, tkyler said:

    What is your hardware configuration in this situation?  Single paddle assigned to prop etc? left or right unfeather button etc?

    So I actually managed to fix it by assigning both prop levers to individual axis'. However, if using the basic XP11 "prop" dataref (in which any number of prop levers are mapped to a single axis) only the left engine is manageable during a large number of procedures. 

     

    My HOTAS is a Virpil T50 mongoose (original version)

  4. 1 hour ago, Pils said:

    Please provide full flight plan inc. runway and approach selection.

    The video's flightplan was: CYOW/14 DCT IKLAX Q844 SYR DCT HVQ DCT HLRRY ONDRE1 KATL/27R

    Last time this occurred it was CYOW ILS 07 when the SID (Either MEECH or RIVER) lines you up near the other side of the ILS during the descent.  

  5. So, I've noticed this happen a few times. The plane will change the nav src at the inappropriate time. I'd say 3 out of 5 of my last flights. I had a hotkey setup on my hotas for nav src toggle button, and de-hotkeyed it to make sure it wasn't a "noisy" button signal, as this does happen sometimes. 

    During this flight in particular, there was no hotkey for this, which verified to me it seems to be the plane itself. 

    I've also included what I believe should be the correct log as this was the last flight I did. 

    Time stamp: 4min 50sec. Sorry, I didn't take the time to edit the video. 

     

    Log.txt

  6. 6 minutes ago, Cameron said:

    The TBM's checklist is the way it is because that's how the Garmin avionics do them.

    Likewise, the 650 is how the Pro Line avionics system presents them.

    While looking into any hiccups will definitely be done, wanting to change how they're presented to ultimately NOT be like the real thing won't be something we'd entertain.

    You've already done this by allowing the user to go to the Challenger menu and skip ahead or go back a checklist. My suggestion is simply to allow the user to expedite this process so they don't inadvertently break the FO. If the FO can go ahead or behind a checklist either by the challenger menu, or by completing the checklist, it makes sense (and doesn't break immersion of reality) to simply have, perhaps an option in the challenger menu to allow the user to pick the checklist and have the FO navigate to that checklist versus having the user have to go back and forth one by one themselves to find the correct one.

  7. Posting this at the request of Pilsner :)

    So, I noticed in my test flight that it is possible to screw up/confuse the FO in regards to the current or desired checklist by skipping some stuff, or ignoring his callouts. For example, I just wanted to get into the air and test a few things out, so I ignored some stuff, and just went. When I went to start a new checklist, I realized the FO was now somehow stuck reading 2 checklists at once, but also that there seems to be no intuitive way for the user to change checklists on the fly other than going up to the challenger menu and going through them 1 by 1. 

    I think it would be a useful QOL change to add back this system that was present in the TBM-900 product, as shown in the attached image. The CL650 has something similar to this, where you can scroll through checklist items and do the checklist yourself, however, I noticed you cannot move this up to the checklist menu and change the actual checklist like in the TBM; it just takes you back to the end of the checklist.

    Perhaps also, when changing checklists like this, the FO will abandon the previous one and start on whichever one the user picks. 

    1255592905_X-Plane2022-01-0914-54-24.png

  8. 42 minutes ago, GreenDot said:

    Thanks for confirming that. The blue box on the load manager does indeed coincide with the 3,400 lb. weight, but the scale goes to 3,600 lb. and you're able to load to this weight - and above - without the load manager giving you any warning. I actually loaded to 3,600 lbs. with two pax and full tanks. With 3,400 lbs and to 200 lb adults in the front, you'd be hard pressed to do anything with 4 pax and fuel to the tabs. That you can do in the 3,600 lb version so as always, have to be mindful of weight! I feel like I'm in the 172 that I fly now. :)

    As for the POH, I can certainly reference what was provided but have found the Cirrus POH for this model for some expanded learning.

    I believe this is because on this model the parachute system is very heavy (the pilot said it's like 276lb) and the operators are required to account for this, therefore...3400lbs MTOW approximate on this model to equal the naturally aspirated model. 

  9. 28 minutes ago, Coop said:

    Thanks for the report!

    Regarding keychain, we are fixing that.

    Regarding knobs, vents, etc. animations; these will be added in 1.0.1, the fundamentals are in the system but it appears the integration didn't make it into 1.0.0, this will be addressed.

    Regarding sounds, we will be addressing these quirks.

    Regarding glass reflection persist, bug logged, I'll make sure it gets wired properly into the persistence system

    Oh, and one more issue that as a Canadian is unacceptable :lol: : Making a Canadian registry in the registry editor appears to be impossible as it will not accept a "-". You can make American registries "N123NA" but you cannot make Other nations "C-XXXX" <- impossible. "D-XXXX" <- impossible. 

  10. 1 minute ago, Coop said:

    Thanks for the report!

    Regarding keychain, we are fixing that.

    Regarding knobs, vents, etc. animations; these will be added in 1.0.1, the fundamentals are in the system but it appears the integration didn't make it into 1.0.0, this will be addressed.

    Regarding sounds, we will be addressing these quirks.

    Regarding glass reflection persist, bug logged, I'll make sure it gets wired properly into the persistence system

    Cool stuff man. You guys really made your mark in XP11 for sure with this project. 

    • Like 2
  11. Hey TorqueSim, 

    Followed you guys for quite some time. This is my first product from you guys and overall it's quite impressive, though I do have some constructive criticism for you guys and hopefully you'll be able to address some of it for 1.01, or 1.02. 

    Over-all, I think it's a lovely plane. It flies beautifully. Visually it's also stunning and getting 2 models in 1 package is of course amazing. 

    However, I've noticed some issues: 

    • The key-chain levitates. Small animation bug. 
    • None of the knobs are animated. On an GA aircraft at this price point, it's absolutely necessary that the 3D cockpit is animated. Some of the knobs on the G1000 you can get away with because they're indistinct, but the CRS and ALT SEL knob should be animated. 
    • The sounds are really good but have some quirks. For eg. the baro knob sounds like's a weathervane from a 1920 farmhouse. Has a weird rickity creek to it. Some of the sound samples cut off when they should trail off...for example if I close the door, the sound of the engine immediately changes as if the door is closed before the door physically is closed. If possible, this should gradually get softer. And the sound of the flaps actuating immediately ends when the flap is done actuating; there is no trail off. Even if the flaps do sound like this in real life, a small trail-off would help it not *sound* wrong, even if it isn't wrong. 
    • The fuel pump(s) also appear to have no sound at all? Not sure if this is realistic or not.
    • The Glass reflection option appears not to be remembered between aircraft reloads
×
×
  • Create New...