Jump to content

tkyler

IXEG
  • Posts

    2,812
  • Joined

  • Last visited

  • Days Won

    564

Posts posted by tkyler

  1. Thx @OneOffRegistrationUser (love the name...don't like typing it) :)

    ....for others.... these types of changes will be in for the XP12 update; however, what OneOffRegistrationUser has provided are effective patches for those interested in making the manual tweaks until the update comes out.    I'm currently making a hard run at the IXEG, but the MU2 is hard on its heels and nagging and will get more love relatively quickly....thanks again to OneOffRegistration user for providing some stop-gap options until then.

    -tkyler

    • Like 2
  2. 19 hours ago, Iain said:

    So again, thanks to the IXEG team

    Thank you for the kind words Ian.  We are certainly excited to be working on the IXEG again.  On the one hand, the initial port to XP 12 is a bit more labor intensive than anticipated...but on the other hand...getting everything ported to modern workflows and features is ceratinly a welcome change on our end, ensuring less development pain once we get this initial infrastructure change done.

    -TomK

    • Like 6
    • Upvote 1
  3. @OneOffRegistrationUser Thanks for those.  (got a nickname? :P)

    So a more comprehensive GUI/interactivity is in the planning for the Moo.  I had to learn enough imGUI to get basic Moo prefs in, but couldn't spend a whole lot of time on the GUI design as it can be its own monster.  For the IXEG, I'm having to get a bit deeper into imGUI as we're dumping the old, custom GUI.....and as I do, my comfort zone with it evolves.  My thought is that once the IXEG is ported and more feature complete...I'll turn my interest into GUI development for just these kinds of things.  In the meantime, I really appreciate your efforts and contribution!

    TomK

    • Like 2
  4. On 12/26/2022 at 3:57 AM, Tobi_ said:

    So when we can expect the 737 to work in XP12?

    We've learned better than to give dates; however,  we have a very well defined 'todo' checklist and are working towards this every day, full time, whereas in the past that was not the case.  As such, it'll be more than a few weeks, but less than several months, there is a LOT of stuff to test.  We customized a whole lot of things that have to be audited, assessed and in many cases, 'removed and patched over'.   We are very committed to this guy though and definitely have improvements coming not too far down the road.

    • Like 9
  5. 3 hours ago, Leviathan said:

    Only Tom can say what his plans for the MU2 are.

    well definitely to improve it where it needs it :)  ...Regarding the 750Txi, that's more on Garmin probably as RealityXP just 'ports' their simulator.

    As far as other plans...David has kindly offered to provide some performance data, which I'll seek to incorporate into the Moo.  I see my imminent Moo 'todos'  (things I'm unhappy with) to be...in no particular order or priority:   Flight model improvements (chasing numbers),  EGT, Fuel Flow, SRL behavior, performance, etc....more liveries, and the first 2-3 seconds of the engine starting sounds (gear whine).     To me, those are the basics at least.  Not quite sure what I'll look at after that just yet.  

    As far as timing, I am indeed full time on X-Plane...but the holidays and IXEG work have taken precedence while Laminar has gotten XP12 stabilized.   I'll tend to rotate every few weeks between projects and 'binge' the work and the IXEG is getting the binge treatment atm; however, the Moo's turn is coming back around quite soon....and I have a 3rd project in the works also that gets chipped on 'nights and weekends'....but won't take on any more than 3. Better to have a few quality pieces that I can maintain for years than get all strewn out with new models.

    -TomK

    • Like 5
  6. 16 hours ago, swapilot48 said:

    I have had surprisingly good luck with the most recent version of the Moo in XP12 RC6

    For the most part I myself have too.  The lighting even looks pretty good...but there are some areas that need touch-up due to X-Plane's new lighting system...but I'll admit even for stickler like myself, they're minor.   My real "todo" before declaring this 'XP12 compatible' is the flight testing, i.e. dynamics, trim and AP behavior.  It MAY be that those are all "in line" with the XP11 version and after verifying such, I'll just declare this 'XP12 compatible'.   Of course XP12 'compatible' doesn't mean  'optimal'.  I still want to get back to 'chasing the numbers' with regards to EGT/ SRL/FF/performance, etc. 

     

    16 hours ago, swapilot48 said:

    However, today I go to start the Moo and the RPM stagnates at around 18-19% and even though the ITT EGT and fuel flow spike, light off never occurs

    I encountered this myself just yesterday the first time and put it on my bug list; however, I have not been able to repeat it yet.  I've started / shutdown / restarted the engines several times now with no issues, BUT....it did happen .........  I just don't know the circumstances or sequence causing it yet.

    Can you not start it under any circumstances ever?  A fresh load of the aircraft for example?

    -tkyler

     

    • Like 2
  7. Looks like you're right that I accidentally broke this.  Its always the first thing I put in (mouse operations); however, with the number of people using the bravo hardware, I really reworked all the "lift lever" commands and ended up adding 'joystick criteria to the lift commands'.  Really sorry about this and putting in a fix (new command) for the next update.  With XP12 final, I'm going through and tweaking the lights and some basic flight testing and will include this in the next path.  Sorry  about that and thx for reporting.

    -tkyler

    • Like 1
  8. Thx for the report.  Can't say I've noticed it, but then again, haven't been looking for it.  I've noted it for examination.  This may be a Laminar issue...as they are fiddling with the rendering settings quite a bit and camera views involving the prop have, in the past, presented some challenges.

    -tkyler

    • Like 1
  9. So after a bit more research...the Autopilot maintenance manual does NOT mention the 20nm restriction, only the official "pilot manual" for the autopilot.  I find it possible that the pilot manual may be erroneous (or ambiguous as to other criteria not elucidated) and more inclined to follow the maintenance manual wording.  As such, I'll remove the 20nm restriction in the next update....unless I discover a reason otherwise...or some other operating mode where the 20nm limit has applicability.  

    -tkyler

     

    • Upvote 1
  10. OK, I found it.  its from the SPZ-500 operating manual of all places.  (I was looking in the MU-2 manual supplement previously).  So yea, you need to be more than 20nm from the station for NAV mode to engage. (See excerpt from Sperry docs below)

    This is documented in my MU-2 docs on autopilot usage.

    http://togasim.com/mu2docs/supplements/spz500.html#fd-mode-control-panel-mcp

     

    image.png

  11. that was poorly worded, sorry.  "I have already put it in place in my development work, so as to be part of a future update for V12"  It is not in place in the currently available version.

    With X-Plane's RC4, released today,  I think X-Plane is in a good place to resume Moo tweaks.  I'll probably release updates in two stages.  

    1)  Visual changes, i.e. the rain effects and tweaked lighting...which just looks nicer.

    2)  Flight model refinement.

    I separate out the flight model refinement because it performs reasonably well in XP12 and most users, (me included) enjoy the more visual and sensory aspects of simming rather than 'by the numbers', i.e "we put in gas....we fly....make sure no needled go red, and enjoy the ride"

    Chasing numbers always involves more in depth tweaks, longer testing period, and frustrations fighting X-Plane's default models and I don't want to withold some of the cooler XP12 visual features while flight testing/refinement takes place.  

    -tkyler

    • Like 5
    • Upvote 1
  12.  

    On 12/11/2022 at 8:07 AM, mirlo1 said:

    any possibility to add windshield rain by default?

    Its already in place.  you can see it in THIS VIDEO.  (if the link is working...seems to be down atm)....anyhow, the effect is a bit exaggerated for testing purposes.  I may put in a preference that lets you set how "much" rain you want on the windshield...its pretty subjective on how much rain one expect to see on the glass for a given level of rain.

    -tkyler

    • Like 2
  13. So just an FYI update.  I've been working on IXEG stuffs while Laminar tweaks the Release Candidates.  I've held off updating the Moo further yet because   1)....I've worked for Laminar...and I know the kinds of changes that can be made in the early RC runs and 2)...it actually runs tolerably in V12.   Once Laminar and most devs are suitably confident the lighting settings are stabilized or close to final,  I'll turn some focus back to the Moo to see where things stand and what needs attention.  The lack of liveries isn't lost on me, I know its a tough UV layout.   That will get addressed in some fashion also.

    -tkyler

    • Like 5
  14. Hi and thanks for purchasing!.   With regards to the MU2, the NAV mode does not follow GPS routes.   Refer to the Autopilot docs at the link below which explains the reasons and the (real life) workaround using GPSS.

    In particular, see the paragraphs regarding:  "HDG Button / GPSS Operation / NAV Button"

    http://www.togasim.com/mu2docs/supplements/spz500.html

    Other aircraft may have different AP behavior/modes, but i cannot speak to those, only the MU2s.

    • Like 1
  15. 10 hours ago, Finlayson said:

    When you open the MU2 preferences panel and click on the Reality XP drop down, the whole thing freezes and you get the following error message in the log:

    If you are using the OEM variant....no need to interface with the RXP pull down eh?.......BUT.....BUT.....I'm being facetious here...

    10 hours ago, Finlayson said:

    it would seem that the RXP drop down in the preferences panel should be hidden or disabled for the OEM variants

    ....you are exactly correct.  I'll look into this :)

    -TomK

  16. Laterally, the AP will track GPS tracks,  ILSs and VORs 'paths'.   Vertical modes are always initiated / controlled by the pilot manually as you state.  For lateral AP tracking purposes, a GPS track doesn't know if its its part of an approach/LNAV, an enroute segment, whatever...those are labels we put on the path....not the AP...its just a magenta line to "stay on" as far as the AP is concerned.  So if you can enter some LNAV approach on a GPS unit and get it to display as a 'magenta' GPS track, then the AP will follow it laterally in GPSS mode. Vertical still needs to be manual though.  In XP11, the GPS tracks do not display the approaches selected from the GPS units....they had to be entered 'waypoint by waypoint'.  I'm unsure if that's changed in XP12, seems I heard it was but haven't tested that functionality yet. 

    -TomK

  17. I foresee two 'events' with regards to the 733.  Event 1 is "port to XP12 'as is'.  Event 2 is 'upgrades beyond the port'.  The goal of event 1 is to get it to work in XP12 the way it does in XP11 given XPlane changes.   Those who have made 733 purchases since early this year will certainly get the XP12 port version for free as stated on the XA product page.  Beyond that XP12 port though,  we have not made any determinations about what may or may not constitute a 'paid upgrade' beyond the fact that it shouldn't be egregious or outlandish.   Regarding features 'beyond the xp12 port'... we have and hear arugments all the time for/against variants, cargo versions, etc and have not made up our minds yet about what may be next.  The obvious things todo are the FMS work and upgrading all the 3D/textures/animations. 

    As far as MSFS, a lot of us developers have kept an eye out on the whole market/dev process and a port is not a trivial thing, regardless of what Fenix / inisim is doing. We're talking multiple 1000s of man hours easily, and at my age and road traveled, that's a tall order.....regardless of the money potential.   I rather enjoy my little world in X-Plane and those users who also see the same value in it.  Perhaps Fenix, iniSim or someone else can do a 737-300.

    I can't speak for any other devs in the X-Aviation ecosystem, but for our part, we'll probably stick to X-plane with the 733...best I can tell from today.

    -TomK

     

    • Like 30
  18. On 11/10/2022 at 1:48 PM, Eli2204 said:

    Is the MU2 able to execute RNAV- LPV approaches with vertical guidance?

    Hi Elijah,

    No.  Those are GPS procedures and the SPZ autopilot does not take GPS generated signals.  ILS is the only approach vertical guidance option for  the older AP.

    Regarding the oscillation,  what approach speeds are you seeing this at .  I can try to simulate and look at the AP constants. I've had descent stability at 110-120 kias and TBH, haven't testes the AP constants a lot below those speeds.  

    Also...is this XP11 or 12? 

    TomK

     

  19. have you tried clicking on the "ipad" tablet (in the side pocket to the left of the pilot seat)?  Clicking on the tablet makes it animate "into" the bracket.  Click the pocket again to "animate it back.

    Your screenshot is showing the "2D popup" version of the Avitab, which is different from the 3D version.  The 2D version may be "popped out" of the X-Plane window and moved to another monitor, etc.

    -TK

×
×
  • Create New...