tkyler
-
Posts
2,810 -
Joined
-
Last visited
-
Days Won
560
Content Type
Profiles
Forums
Latest X-Plane & Community News
Events
Downloads
Store
Posts posted by tkyler
-
-
You're correct, the right brake has a hard coded delay that's longer than the left one. When hardware is attached, I set the delay to 0.1s...which should be fast enough to follow your brake pedal application...and this is the case on the left pedal only atm.
The brake rate set in the prefs applies to when no hardware is attached, so that's why its not getting affected. I was probably playing with the values way back when and only set one (because I don't have pedals and was using one throttle lever to test)....and forgot to set the other. Its on my todo list now. Thx again.
-tkyler
-
Thx @daemotron The new V12 lighting requires some changes all around to light stuffs and seems I missed the tail beacon. Its on the list for a next update.....speaking of which isn't too far down the line. The IXEG port is almost ready to go and on a 'NASA style hold' while other logistics are being tended to...and I have some windows of time to chip on the Moo over the next 2 weeks. Again, thx for pointing out.
-tkyler
-
1
-
-
I'll ping Laminar on this, I think that error is coming from them and is Windows related, I'm not seeing this from the few Mac users I've ping'd. Flooding the log with a message like that, presumably from some flight loop is bad practice. Thx for reporting.
-tk
-
4 hours ago, meierzwo said:
Only the MU-2 does this, no Errors with Stock Laminar or other Third Party Planes.
Do you have the G500 plugin in the MU2 plugins folder? Have you tried moving that out of the folder temporarily for debugging? What does the log.txt look like if that's the case etc?
-tk
-
1 hour ago, Leo V said:
The versión is 1.33
Definitely not. I know this, I wrote the code and have all the old versions. That is an older version, 1.21 to be exact (which was pirated way back when). Your solution? Download the latest version available to you (1.33) as a customer from X-Aviation.
-tk
-
1
-
-
I am at a bit of a loss atm. The last version, 1.33 for XP11.....the loadcoroute function is not on line 662 as your error shows. The coroute loader handles both .flp and .fpl types. What version of the 733 are you on? That seems like it may be some error from very early versions of the 733. The coroute system was rewritten quite a bit for the later versions. ..indeed, we haven't seen a 'coroute bug' report in several years. Have you installed the latest 1.33 version (for XP11) from X-Aviation?
-tk
-
The battery key position is a custom dataref. I'll have to add a command to make that available for you. I've put it in my issues list. Thx
-tkyler
-
TBH I have not, for a few reasons.
- The engine (as opposed to prop) sounds totally dominate when on the ground, so I haven't distinguished much of a difference.
- I haven't found a really good 'side by side' comparison of the differences between the two
MU2 are rare enough birds, that we get our perception of sound mostly through YouTube Videos and in those cases, the wind direction can have an effect on how the sound hits the camera microphone....so REALLY figuring out how a 5-blade vs a 4-blade really sounds across the entire operating range has been a challenge. Usually you just get some "taxiing" videos.
Most folks absolutely focus on the loud whine/howl of the engine...that's their recollection of the Garretts sound.
If I had a really goood 'sound data' of both where I could hear the distinction across the operating range....and was sure the distinction was due to the 5-blade prop itself (rather than other, recording or environmental factors like echo/reflection/wind), then ceratinly I'd consider it.
-tk
-
I don't think so! i've put an entry in the Moo issues list so this will get revisited after the IXEG goes out.
-tk
-
4 hours ago, VirtualGAaviator said:
Sometime later, you're going to do a major lift on the project?
that's kinda correct Frank... though 'sometime later' is actually to begin asap after the bug-fix phase following release. The term "major lift" is probably somewhat relative to each individual though. This is more evolution than revolution. The plan is to prioritize the FMS/VNAV improvements first, then in parallel as able, swap the sounds over to FMOD and begin a new 3D exterior model. So for folks who spend 95% of their time enjoying the cockpit and don't care about the rest much....then elements of a "major lift" may not seem so major. For folks who live for VNAV descents, then they may see the VNAV work as a major lift etc.
Either/or, the plan is to continue on those elements listed above after release for sure and we'll evaluate other features along the way.
-tk
-
13
-
-
Been quiet here a while. Sorry for that. Yes, still on this every day
We have slapped a release date on our own calendars finally, but of course we're not tossing that date out because our crystal ball isn't the latest model. To at least be able to see a firm date is encouraging.
The delay since wrapping up the 3D/visual work is mostly due to my reworking of my code infrastructure to be more 'decoupled' and "libraryish", such that it can more easily be reused and applied to future work. Because we're wanting to do new projects while improving the 737 also, I needed my old code to be a bit more flexible and it was just easier to begin that process now. So hopefully the benefit of this phase of work will be seen with more rapid development down the line. I hope that's the case
.
Sorry for delay in reporting, I'm still happy to be doing this and ensuring I can continue to do so.
-tkyler
-
11
-
1
-
-
17 minutes ago, RogerH said:
Surely not much more.
Surely yes much more, and more than coding, hence the decision.
17 minutes ago, RogerH said:but it makes you feel like those using XP11, many of whom will be doing so for years to come, have simply been abandoned.
...indeed you have staying with XP11..... and I truly know how you feel, being that XP12 abandoned the IXEG and I've spent nearly a year chasing after it trying to catch up, but that was the only path.
-tk
-
1
-
-
1 hour ago, RogerH said:
Thanks for the info. I don’t plan on upgrading to XP12 - is there anything you can do for XP11 users
Unfortunately no. The XP11 version "is what it is".... too much has changed since XP11 and we have to move with majority to keep at this.
-tkyler
-
4 hours ago, ThorBrasil said:
Could you at least put the textures in PBR
There are elements of PBR in the cockpit already, though not to the extent of the cabin for sure. I will make a pass over that at some point to determine how to best thandle this. Our techniques at the time didn't have the 'power' we do today with Substance Painter. So yea, I'll give it a look, but it will be gradual process after other things are handled first.
-tk
-
7
-
-
On 8/2/2023 at 9:09 AM, randomdisplayname said:
Or does it work only after certain amount of ice has already built up?
unsure, I haven't examined closely as it has been (historically), a simple system that traditionally has just worked, but easily it could be X-Plane has made a change I didn't catch. Noted to check this before next release.
-tkyler
-
56 minutes ago, RogerH said:
Is there a dataref I can access to connect the ground power before switching it on?
There is not currently; however, I have made a note to add a command to do this for the upcoming V12 port+ patch....something like "ixeg/733/connect_gpu_to_aircraft, etc.
-tkyler
-
2
-
-
On 7/27/2023 at 1:59 PM, Pils said:
EAA AirVenture isn’t over yet. :-)
It is now (thanks Pils)...and I'm still making my way back home. We're pretty much done with the issues list for deployment and only have to get though technical infrastructure and deployment prep, but as mentioned before, that's not an overnight thing, but it is the 'final leg' of this route.
The plan is to get this 'port + compatibility patch' out, which I'm sure will result in plenty of issues reported, but then immediately begin addressing those issues and start the road towards our planned improvements.
The obvious 'improvement roadmap' consists of converting our sound work to FMOD, improve FMS operation and finally a new 3D exterior, these are the things to bring the IXEG into 'modern times'. I'm sure this work will roll well into 2024 and the goal is to just keep going. After those obvious items are addressed is when will think about any other 'options' to the product. Its enough of a heavy lift job to overhaul this thing from 2009 tech as it is.
-tkyler
-
11
-
1
-
-
On 7/24/2023 at 10:19 AM, OneOffRegistrationUser said:
can I please ask to confirm it is not working in current state
I haven't checked it yet TBH. It could be. I set all the requisite datarefs as you've noted and never thought about it much because it always worked, but certainly possible X-Plane changed some things I didn't catch until someone reported it and the yaw damper isn't one of those many take a peek at so it didn't cross my path much.
On 7/24/2023 at 10:19 AM, OneOffRegistrationUser said:and will be fixed "in two weeks"
It will be fixed in 'two weeks' probably
Yes, its absolutely on my TODO list to look at before the next patch Frank. I am on the final push to get the IXEG out the door and the MU2 will get is turn in rotation again and I'll make another pass over the issues...we'll get this one sorted out.
-tk
-
1
-
-
It was corrupt preferences! One of the more nefarious causes of unexplained behavior. Deleted them and Owen is back up and running!
-tk
-
2
-
-
@Tomlinson Sent you a PM. We'll take this private for a bit.
For others curious, will report back.
-tk
-
Thx for that. Next, turn on the "IGNITION CONT" and try that.
but beyond that, a few qustions also?
- Version of X-Plane?
- Operating System?
- Do you have any other plugins installed. XEconomy, etc.
- Are the engine intake covers removed?
- Are all the fuses pushed in?
- Are you familiar with the DRE (Data Ref Editor) plugin? we use it to debug X-Plane datarefs. You will need this to debug further.
-tk
-
Thx. Two observations. 1) I can't see any of your engine gauges, so I don't know whats going on there...I need to see those. . and 2) your trim wheel is "twitching", which suggests you still have hardware attached to your computer. Make sure you disconnect your hardware for this test, and then show the engine instruments in another video so we can have some feedback. Do not move the condition levers though (ignore my moving them below), leave them where they are. Show me something like this.
-tk
-
could you please post a screen recording of your steps using the mouse?
-tk
-
Lets try this again. "WHAT was the result of that troubleshooting test I suggested above"?
Cant get ghost throttles to show up
in Mitsubishi Marquise MU-2 v2
Posted
in your first screenshot, your "auto-stop power levers at detent" is not checked and the ghost throttles will not show in that situation. In the second screenshot series, you do have this checked; but your visibility is set to 'lift zone and below" with upper limit at 0.6...and your torque meters indicate that you're probably not in that zone. So both of your screenshots are configurations where i would not expect the ghost throttles to show..
Check the box "auto-stop power levers at dentent and then set the visibility to 'always' and see if they show for you then.
TK