tkyler

Thx Dion, those have been fixed and we are rolling along for more improvements. -TomK

The lights respond to the physical flap position at each of the fixed positions and are not affected by the lever position...so you have to wait some seconds for the flaps to reach their positions before the lights come on. If you observe the lever snapping into a flap detent and the lights don't come on (assuming power) after at least 10 seconds after moving the lever (some flap positions are slow to be reached), then let me know. I did not observe this when cycling through all the positions with the "lever snap code test" -TomK

FYI for hardware....I'm about to start a pinned topic on hardware interactions (The throttle 4 unresponsive is a known bug and already fixed for the next update) Keep an eye out for a pinned thread on hardware discussion shortly. -TomK

@danhenri there is a bit of confusion over the "pitch trim wheel" (the white guy) vs the "autopilot pitch wheel" (the silver guy on the AP panel)...which is what you are probably talking about? I don't have commands for that wheel yet, but have made a note to put one in. -TomK

vasanta is correct, it is not illuminating. The rotating beacon uses a quite complex default effect from X-Plane...which was done by Alex Gifford (aka propsman) and is about as good as it gets for non-LED effects IMO; however, it never utilized HDR 3D lighting at the time. I originally did have 3D illuminating lights in place, but X-Plane occludes the effect if the 3D lights are placed inside the lens. Placing the 3D lights outside the lens just look good so I left it out until a better "aha" moment struck me or XP12 improves upon it (which I have not tested)...the reflections particularly. I may give this another go, certainly I'd like the effect in. -TomK

Sorry guys. "pull" isn't "rotate" typo in my lever code from cut/paste. Fixed. Trying to blow through all issues before the weekend! -TomK

This may actually a mistake in my documentation. I have gone over the entirety of the "Supplement 25" for the SPZ system and can find no reference on how to turn off the FD once its been turned on the by SBY switch. I'm trying to get a hold of some MU2 owners who can verify what the true operation is. The documentation is a bit sparse actually. Indications though, are such that it seems it may be this way....in other words, the FD is intended to always be "at the ready". The excerpt below is from the preflight checklkist for the SPZ. You can turn it off by cycling the "FLT DIR" fuse behind the pilot left shoulder. and FYI, I am working on "Autopilot Documentation" with examples and these procedures going into the docs. -TomK

*sigh...Thx guys! -TomK

That switch (and its animation) is mapped to : sim/autopilot/servos_off_any I need to purge the commands I ended up not using. -TomK

Comprehensive performance analysis/tweaks is coming. I am tweaking the engine thrust at flight idle, which is a bit high and . I made contact with a Moo owner who will be getting me charts and such for performance tweaks.

This was simply my consolidating code to avoid divide by zero (rather than simple test). The lowest value should go down to 0.01 (0.01 works on my end)... I'd think that 1/100th of a second is enough to stay out of the way of your pedal feel? Have you tried values below 1? If you set it to 0.01 and it still feels weird, let me know. My testing felt "instant" with my pedals with that low value.

I'm simply going to have to test this more....because the GPS units are "Laminar's" and not mine...they respond to datarefs in ways I can't always control or unware of and indeed this has been a pain in the past. I'll try to get a bit more creative to get these behaviors more consistent. At the least, Austin is super supportive of my observations for XP12 and I'm due to "give him a list" of any concerns that require changes on his end. -TomK

Thanks for your inputs Jerry. Not seeing one in any of my reference pics, but I could have missed it OR it could have been added in differing models Can't say I ever noticed the sound in my flying the MU2. Its reasonably slow and quiet. Are you advocating for "click of switch"? or some kind of looping "clicking" while the wheel turns? I'll see what I can do here. ...seems first time around the 'avionics_on' turned on both GPS and was giving me headaches trying to isolate the units to the differing radio busses. I did talk to Austin at Oshkosh about this for V12 and he's amicable to expanding the bus isolation systems and admits is "light"...but there may be a way around it. Its on my list now. Thx, on the list They should illuminate only at "trim limits". They indicate "no more trim available" This is to simulate repeatability of concrete / runway casting seams. I know this is subjective. Are you advocating eliminating it? or reducing its amplitude or frequency? I'll hear arguments for amplitude or frequency, but not removal. Have never seen this one. Are you using the manip regions under the switches? (down arrow cursor) Fixed. simple togges the Avitab as if by mouse. Known issue. fixed roc? not familiar with that acronym. Will expand the commands for ON/OFF. unsure hold...that's an odd operation with the real parking brake. Can do This is a bit subjective IMO Jerry, mostly because of the diverse array of hardware and their own sensitivities. I got into a real MU2 at Oshkosh to play with the levers. There is a light click when pulling the levers up, depending on how hard you do it. The more audible click is when you push them forward over detent and the metal restraining pin "snaps down" under spring pressure...metal on metal. With auto stop, indeed there should be no sound when auto stopping..they are simple "at the limit". however, perhaps you're advocating for a sound here though? My sound is "For the lift itself" and so will not play until they are lifted. All that being said, I am about to start a new forum discussion on an alternative method of throttle actuation that discusses your concern above. I met with the CEO of Honeycomb while at Oshkosh and their Bravo hardware is a bit "weird" IMO when it comes to their detent and lever travel range...and even the salesman said they get a lot of confusion about it. I'll discuss it more in a bit, after getting these initial responses out of the way. Can do. Was saving a comprehensive "commands for everything pass" until the really obvious stuff was taken care of, but easy enough to add these in for the next update. -TomK

Back from Oshkosh and rested. This is fixed. Moving through my list as rapidly as possible for quick update. TomK

noted on these. This posting has been logged also. These shoudl be removed. The geometry of the window precludes rotating the Avitab effectively. It ends up conflicting with the window and shifting it over to accomodate the rotation, ends up occluding instruments. in the end, I decided on the one orientation. These commands will be going away. Thx for inputs, all will make the MU2 better TK

logged. Thx -TK

would be pitch wheel only. -TK

Thanks a ton Isaac. performance tweaks will follow behind all the usability tweaks, but having good flight data is really super helpful! Thanks again. We'll take as much as we can get. -TomK

This is a good one to put in a preference. On my list. -TomK

Below is the description....if the YD not turning on by itself with mouse...definitnely worth a peek on my end, smells like a typo in my OBJ file.

It is..there are click spots just below the switches. 3 of them, one under each switch and one in the middle to hold "both at once" If you hover the mouse just beneath the switches, you should see the cursor change. -TomK

You caught me with my pants down BULVA! I commented out the code that sets that to zero for a temporary test and forgot to uncomment it. DOH! This is an annoying one. FOR OTHERS....since the prefs are saved, uncheck the chocks preference and restart the flight..that may fix it as the prefs are loaded at "aircraft load" and since the prefs are saved, that should keep the chocks from being put in place and negating the steering until I can deploy the next fix.

Definity a bit subjective...in that some folks have described them as dim, etc....but I myself am in favor of 'more light' and its an easy tweak. I'll up the value until more people complain its too unrealistically bright than don't complain -TomK

Changes actually come pretty quick...just a bit of goofy timing with this Oshkosh trip. I'll easily be able to make very quick adjustments once back in the office and we can definitely get this thing tweaked. -TomK

thanks XST, I'm in agreement. X-Plane TPE implementation is new and I'm the only dev using it to my knowledge (but there are probably others). ...but they did not program an overspeed governor. This put me in a bit of a quandry as weaving one in to the existing behavior is fickle and tricky....and the alternative is completely rewriting the engine code, which is no easy or quick task. So....I'm going to keep fiddling with what we have to try and come up with a best compromise and on the side, begin playing with my own engine modelling. ...BUT...XP12 may surprise. I haven't tested any improvments there yet. Thanks for input....need another week to finish enjoying this Oshkosh trip and I'll be right back at it. -Tom