tkyler

I assume you're talking V11 yea Bulva? I'm not reproducing it on my end....but seems that did happen to me a while back under some circumstance that I can't recall and has not happened since. Its working for for me for the 2 cases of "gear lever up on ground" and "levers pulled to idle while airborne and gear stowed. I'll keep an eye out still...and check the code again for anything obvious. -TK

I'm really excited by what I'm seeing with XP12...visually...though its still WIP on both my and Laminar's end. The following video shows testing of the rain effects and lighting issues. The rain effect is exaggerated in this video for purposes of testing...so the 'deluge' on the window is more than the sky is putting out. Also...the lighting between night/day...specifically through dusk/dawn isn't quite up to speed. Laminar is aware and as mentioned earlier...on their list at some point to evalute and hopefully tweak. In the following video of the rain effect...I also use the K/L keys to cycle through the time of day.....to just before and after sunset...and you can see how the lighting intensity is still needing some Laminar love....BUT....you can see the potential. The capture is 20fps...so the video looks a bit rougher than what I'm seeing on my end. https://www.dropbox.com/s/0y23n1th42r9b7i/rain_effects.mp4?dl=0 TK

Just an FYI for anyone interested.... just an example of some of the things the port process to XP12 entails...not just for me, but all devs. This image shows illuminated surfaces both at night and during the daytime. If you set these levels to look normal during the day, then they're currently a bit "blown out" at night. If you set them to look good at night, they look washed out..darn near off during the day. For myself...I have a way to code around this for all illuminated stuffs; however....because XP12 is in a public beta...there's a good chance this will get tweaked at some point in the near future..but of course this is just one issue amongst many issue being handled by Laminar. Tweaking the brightness of each of these elements takes a bit of time..and of course you have to check them in the sim....so when things change on Laminar's end, its causes another "round of tweaks" to be made. If I make my own tweaks in code to make these look more correct....then such changes would probably be nullified by any changes Laminar makes and cause me to have to "go back and change" all the stuff yet again. So the protocol is to "report it" and let the item wait its turn in Laminar's work queue. ...doesn't mean I can't work on liveries...or other special effects in the meantime....but just an FYI about the nature of the public beta and how us devs have to wait before we can make the changes we need to. -TK

all logged Bulva. -TK

thx. issue logged. -TK

There are definitely changes for V12 I have yet to address. I have already rolled into the obvious ones, like the rain effects and lighting changes, but the flight model is changed in V12 significantly as are the gyro behaviors...among other things. I'm moving through the port though...its definitely one of the bigger transitions compared to X-Plane versions past, but we're moving through it. -TK

I'm so sorry....total brain lapse on my part...I was responding "while on the move" and wasn't really thinking this through. Some manipulators are "command" type...and they are "on the command list" however, some are "push button" type, and those are NOT on the list. ...and indeed, this button is not a command type and there is NO command for it unfortunately. I'll add in these for the next update. It probably should have been a command type from the beginning. Again, sorry for confusion. -TK

You are correct that the command is NOT in the list of custom commands on the docs. sorry I missed that, I will get that fixed promptly. The command is: xscenery/mu2b60/manips/ap_button and that command will also turn on the Yaw damper at the same time. Here's a few others on that AP panel also: xscenery/mu2b60/manips/ap_yaw_button xscenery/mu2b60/manips/ap_soft_ride_button Seems I have several "manipulator interface commands" not present. I generate that list automatically via a script as there are so many commands in my code and my parsing script missed a bunch of these "manipulator" commands. Perhaps its time for a dedicated manual perusal of that list. Thx again for pointing this out. -TK

I actually did adjust the screens a bit for the update. Here's the GTN 650 and 750 UV mapping for 2.0.4. it all looked to fit in the bezel. The 650 header wasn't "cut off"...it was obscured by the Avitab black screen...with that fix, the 650 screen is fully visible now. That being said, I still did adjust the UV Mapping a bit to make it cleaner. -TK

Avitab / GTN screen conflict fixed. GTN "save config" preference fixed. Map light fixed. Checking a few more things, but I expect to get a 2.0.4 update out asap. TK

Thx. will look at that cabin VVI needle business; however, I have zero custom particle effects applied.,,,so that is default X-Plane particles. I will be doing my own particle effects soon enough though and hopefully we wont' see this kind of trouble. -TK

Thanks for reporting, that's still good info to know. I didn't expect something like that, so I'll look into this specifically. Thx Again. -TK

A total mismapping of the cockpit texture on my part....indeed a simple fix, but will need a new 'export' on my end. I'll get a fix out right quick. Sorry about that.....lot of options this guy. -TK

It does not....though the changes implemented in 2.0.3 will carry forward into the XP12 version yet to be released. I'm actively working the port to XP12 though and there will be a dedicated announcement when its ready. -TK

FYI, X-Aviation is located in Florida, USA and a hurricane is bearing down on them....MU-2 2.0.3 patch may be delayed as they prep and rush to evacuate. TK

This is by design. HDG isn't one of those modes that couples to any 1/2 configuration, so they're sync'd. As far as the copilot knob not being able adjust the HDG, that too was simply a design choice to avoid possible confusion that the pilot/copilot HDG adjustments were indendent of one another, but simple enough to implement...certainly for any shared cockpit functionality it would be necessary. Also, I'll peek at the copilot HSI course indicator / CDI issue. TK

The solution here the Marquise employed is the TCS mode (Touch Control Steering). This is documented for the 2.0.3 update which should go out soon...its in X-Aviation's hands, but they're also working through multiple product transitions to V12, so it should hit soon enough. The TCS is an effective way to alter IAS and VS values without having to look down or change/disable AP modes...and once you get used to it, dare I say somewhat preferred (by me anyhow) over a knob based solution...you can keep your eye on the instruments at all times while holding down the TCS button and changing the VS or IAS values. -TK

was a bug on my end Bulva. I tested for the "nav type" and accounted for VOR and ILS (LOC + GS), but "LOC" is its own separate "enumeration" in X-Plane when GS not present...in the XP radio ...and I simply forgot to add that to the list of navaids to test when the NAV is pressed. working for the 2.0.3 patch which I'm packaging up for X-A distro, pending their schedule...but at the least I plan to send it their way later today. TK

...and for updating the 'last working XP11 version to similar behavior in XP12?....neither will we....we've said it many times and this is not in debate. It is a bit more of a process because XP12 has changed quite a bit with regards to engine and systems, which means we have to audit everything and surgicaly remove code that clashes with XP12 functionality...and we put in a LOT of customization. As far as a discussion of charging a fee relative to "when its finished"., too subjective......I have enough statistical evidence that says to me that a lot of folks have really enjoyed the 737 for a lot longer than the price of a 2 hour anniversary dinner...(for newlyweds anyhow). To those who would argue about 'unsimulated things', all I'm going to say is Pffff. I've been a software 'consumer' for over 40 years, and not casually, I make my living from using software, 100s of titles over the years....and this stuff is always evolving, always changing...LOTS of software is missing things. I use what I can, enjoy the good parts, don't buy what I don't like and everybody has the same choice here...we're not hiding anything. I could easily argue that a lot of products lack "immersion", realistic lighting....or decent sounds. The flight sim dev community isn't like it was. Its more saturated, the bar is higher and the detail we have to put in is a heck of a lot more than PMDG had to in its early days when it had a monopoly on the airliner market. So what would we charge for? ...I can't say, but its true we have no incentive to keep on working for free in perpetuity. Have you noticed how everything is moving to the subscription model? There's a reason for that...and guess what, I have at least 8 software subscriptions...every month/quarter....how would you guys like that? (hint, you wouldn't). If we charge for any update, its fair to say that it would have to justify the deliverable for a majority of customers (cause it'll never be all). Probably....thinking off the top of my head...., includes more variants, the FMS more complete, animated everything, more robust failure interactions, etc...stuff like that. AND it wouldn't be a full price upgrade either, I never like that idea. So...feel free to discuss as much as you like, but I just wanted to throw out some of my thoughts for folks who haven't gotten to know me over the years through other posts. TK

quick update. Last week was a wash for the Moo XP12 conversion....the AP docs taking a bit longer than anticipated (but 95% done) ....and a few "transition obligations" were called in last week by companies I severed ties with but pledged "transition help" to not leave those groups hanging....including Laminar. I fully expect to have the next 2.0.3 patch out in 2-3 days with the GTN option for the windows guys...and will roll right into the MU2 12 update. -TK

...and today also.....almost done TK

I'll dig into this pretty quick Bulva. Working on the AP docs today so this is good timing. I put it on the todo list so I don't forget. Was dealing with some family stuff last few days. -TK

Thx Pils, that's a good list, will definitely give those procedures a try..

Hello all. Those who have followed know that the IXEG 737 develoment has been stagnant for a long time while I've worked on my MU-2 project and stabilize it after the release. That stabilization phase is nearly done. XP12 is imminent and I'll be porting the MU2 to XP12 beginning next week...and it should not be terribly long (I hope). After that, the 733 will move back into rotation as the primary focus of development with the port to v12 being the first priority. The IXEG is minimally operable in V12, but that's all we can say. We obviously had to make it baseline flyable in order to test/develop it with all the XP12 changes, which have yet to be addressed. As such, our official position for those who wish to try the V11 IXEG in V12 is "VFR joyriding only". I expect we'll set up a 'volunteer forum' where folks can give feedback as to their V12 observations as its better to have more eyes on this stuff; however, we request that nobody report any shortcomings of the V11 733 in V12. We are keenly aware of a lot of things that have to be changed....so we'll want to wait until we believe we've caught all we can find before other folks chime in; otherwise we'll end up with a massive stack of the same reports. So, certainly keep XP11 around if you wish to fly the IXEG seriously until we get it ported over. I've always kept "old version / new versions" side by side on my computer for these transitions. Long-time XP users know that after a major release to X-Plane, there is an inevitable debug period that goes on for some time, though many other devs have begun already, we're behind. ....but nice to have the process underway.....Below screenshot shows what the cockpit looks like in V12 daytime. -TomK