Leaderboard

I have a confession. I was approached about 10 days ago to participate in a short-notice endeavor (X-Plane related) that was tough to refuse and had me put the IXEG work on hold for this time frame....so this short delay in our original time estimate is squarely on my shoulders.....but I feel was the wiser decision for my continued work in X-Plane. I'm back on to the IXEG tomorrow. This side endeavor will become known sometime today I suspect. The good news (hint) is that completion of this endeavor will allow me to continue on the IXEG development right after the V12 port version comes out, and not have to detour back onto any other work....and there is a bit of an 'Easter Egg' in this endeavor that reveals the two projects we plan on working on in 2024. So we'll roll out the V12 port and I'll jump right back onto the FMS and other improvements planned for the remainder of the year. So this endeavor delays the V12 port, but moves forward the follow-on work. Those improvments (FMS, new nav data, beginnings of new 3D exterior) will take the better part of 2023 I'm sure, but we'll start that immedately after the V12 port release. As far as time frame for the V12 port now.... I can't say exactly. we always feel "close" because all the big stuff is out of the way. My todo list largely consists of finishing the interior texturing (rear galley), putting in the wing flex and squashing Jan's list of 'mostly small' issues, that's the list. I am dealing with 3 graduations of my kids this weekend (and family get-togethers).... and they will get my time to celebrate their achievements. I'd like to be done within 3 weeks, that's all I'll say. Will we be done in 3 weeks? I don't know. If not, I'll certainly be closer than I am today and still moving! -tkyler

Hi folks, this is experimental 5B_GNS ACF adjusted with items below. Despite knowing that XP is doing some tricks with flight model and authors trying to compensate this fact - this is attempt to use some POH numbers in XP. Changes: - Propeller placement point moved 90mm forward for 5B version. - CG and it's limits aligned to MAC. - Payload stations added. - Static Gyration disabled. - Additional fins (on tanks and rear part of fuselage) added to flight model. I do not really think any major effect should be expected here. Just feeding my perfectionist's ego. Tested in flight loaded and empty - looks\feels OK. Any feedback will be really appreciated. xsMU2B60_5B_GNS.acf

On and off commands for the GPU already exist, I have bound then to a switch. Not at my computer right now, but I think it's connect_gpu and disconnect_gpu

Thanks, I will try it.

Laminar Research's feedback system is, and has been, offline for sometime. That doesn't mean they don't want community feedback. What features would you like to see in X-Plane 12? To make this thread convenient for Laminar Research (and 3rd party devs) to parse, I'd suggest refraining from comments, unless it clarifies a request. Also, please limit your request to 2 or 3 per post. Add additional request in subsequent post. Bullets are good. Finally, the "Like" (upvote/downvote) system could really be helpful. Let's see where this goes.

I'd second a native re-development which doesn't resort to Garmin's trainers - like the G5 and G500 by RSG. This would solve the issue with outdated nav data and missing cross-platform availability.

Yes....as far as I can tell. There's use of the phraseology in the maintenance manual of "turn battery key on (or connect external power)". The key essentially "connects the batteries to the busses", whereas the external power receptable also engergizes a relay that can connect the GPU power to the main busses also. Indeed there is a troubleshooting step in the maintenance manual for when connecting external power does not power the main busses, and the battery key switch does not factor in to those troubleshooting steps. As far as the torque gauges goes, they indicate 100% when unpowered. When connecting the GPU, which energizes the DC busses, they spring to life and 'indicate' I'm going to do a deeper dive into the electrical system at some point to try and get it as accurate as i can. These older analog wiring diagrams can be a challenge to interpret and take some time. Regarding the GPU toggle, I'll add that command (though I have no idea why I didn't when making the on/off commands. mind-blank apparently) -tk

You have the plugin locations switched. Xa plugins is global. Gizmo-avionics is for aircraft.

Was the AINS-70 used on DC10s of KSSU group, similar to the 757/767 FMS? (or better, wasn't the 757/767 based on that AINS?)

This thread (and this forum at large) are the correct place - although there will be an email newsletter when the plane is ready for XP12. We are in the final stages of updating, I am not going to dare and put a date on it, but the plane is flying fine and the remaining work is some 3D, some minor bug squashing and a final user-experience polish. Cheers, Jan

Did you read anything that was said above in the initial announcement? Anyone who purchased the product from the date the product page was updated will receive the upgrade for free. That promise has not been broken. We made ZERO announcements about a free update to existing customers anywhere. We did publish on the product page clearly made for new customers they would get a free update for X-Plane 12. There was a reason for that, and this is not uncommon in the software industry when products are in transition. A product page is an advertisement for potential customers. And, we are holding up that promise as was outlined in the announcement. A product page is not a means of communication to existing customers. We communicate by e-mail and forum announcements to existing customers, and always have. You're stretching things here.