Several people have now stated otherwise.
You purchased a car. You went to another vendor to buy a roof rack. The rack is flawed and you go back to the car dealer with that problem. Your analogy is flawed.
4 Likes
The first response requested clarifying details which I provided. The 2nd response hasnât happened yet after I was thanked for providing the clarification:
I had this problem with some 3rd party airports. With others it works fine. I canât remember which ones because I wasnât aware that it has to do with 3rd party airports until now. As has been mentioned above itâs easy to work around this problem by manually tuning the frequency. Those frequencies can be found easily on the web, just google airport charts. Iâm not familiar with the SDK so I donât know whose job it is to fix this, but since itâs no big issue really I donât see why I shouldnât buy any more 3rd party airports.
1 Like
This seems to happen a lot. It seems to be really hit or miss whether the FMS will automatically tune the ILS frequency and automatically switch the CDI or not. Best I can tell, itâs not a location based thing nor is it related to 3rd party mods, scenery or airports. It seems to be something in the MSFS code. Like so many other features in the game, sometimes it works, sometimes it doesnât. And it seems to happen pretty randomly.
My local airport has 1 ILS runway. Itâs a default auto-gen airport with no 3rd party scenery. Sometimes everything tunes in automatically and works perfectly. Sometimes I have to tune the frequency and switch the CDI source myself or it wonât work. I also fly in and out of KSAN often. I have the KSAN airport from the marketplace. Just like my local airport, sometimes it tunes in the ILS automatically, sometimes it doesnât.
I just err on the side of caution. I always being up an approach plate and enter the frequency manually regardless of how it should be automatic. Then by the time I get in range of the localizer, if it doesnât auto-tune, I just hit the CDI source button and all goes smoothly.
1 Like
Following the end of that Orbx post, it appears the frequencies do exist even post-Orbx add-on installation, theyâre just not showing up in the TBM 900âs menu.
Mitigation: you can hand tune the NAV radio as you would in other aircraft and still conduct an ILS approach.
Is that correct?
They didnât shine on it, they just didnât directly address the problem of the TBM 900 menu.
To be fair, this is one of those interactions between MS-Asobo and a third-party that will never end well. Unless theyâre interested in burning bridges, neither manufacturer land the blame directly at each otherâs feet. Theyâll simply play the ticket game with you passing you between two queues, never to make progress or customer satisfaction. I get why youâre angry/annoyed. I would be too.
I think the lesson here, if anything, is that these are early days (a phrase to be repeated for the next couple of years, Internet Time and Agile Development notwithstanding), and you will find a lot more intersections like this where the customer is caught in the crack.
There is a mitigation. Unfortunately, thatâs all the satisfaction youâre going to get unless someone intimate with the TBM menu (maybe the Workingt Title folks?) can dig into this problem deeper for you.
1 Like
FYI, even if the car manufacturer âtook responsibilityâ, I can tell you, they did not repair the faulty unit. It would be sent to the nav system manufacturer for replacement or repair. Warranty of 3rd party components is administered by but not resolved by the car builder.
If Asobo provided you the add-on, included in the purchase of the base product, I am sure they would help you out by referring you or the problem to the 3rd party. The fact that their âparts departmentâ sells 3rd party product does NOT mean the car builder warranties those parts. In fact they DO NOT. the 3rd party parts carry their own warranty from the 3rd party manufacturer.
In short. NOT Asoboâs problem. Just like the âbugsâ caused by installing those 3rd party products. If it WAS a car we were talking about, if your car failed because you installed 3rd party parts, that would most likely VOID your warranty.
First of all, THEY (orbx) have not yet responded beyond John Clark punting to Greg Jones to respond post clarification, and Greg has not yet responded. You read the replies of a newbie who only VALIDATED the issue I describedârecall I did not say anything about the ILS frequencies not responding to manual input, itâs the fact itâs MISSING from the MFD that is the problem, and that problem as you state didnât directly address the problem. Itâs very desirable to be able to select any ILS freq from the MFD freq menu rather than needing to look it up from an outside source. I was never looking for workarounds and never asked for any.
âOk folks! Just did a couple tests here. Itâs obviously confirmed that the ILS frequency will not auto-enter into any aircraft from the MSFS flight plan screen.â
You purchased a third party Nav/Media AFTER MARKET system for your car and after installation realized the hands free controls on the steering wheel donât work. You think the car manufacturer should fix the problem and the OP thinks that no one should buy any more third party Nav/Media systems from ANYONE.
Both reactions are pretty unreasonable and illogical to be honest.
The rest of us are asking why you canât just use the controls that the Third Party Nav/Media system came with?
2 Likes
They didnât say it was a problem, but itâs obvious that the answer is âSomeone needs to fix the TBM 900 menu so that existing ILS frequencies show up regardless of whether the airport is default or add-on.â
That means NOT Orbx. Because they wouldnât be allowed to make official changes on default aircraft avionics that are Asobo-based. They may or may not want to fix the problem themselves. But the issue is at the moment, pointing suspicion to the TBMâs G3000 MFD subsystem. Thatâs Asobo property.
[quote=âwillisxdc, post:66, topic:323318, full:trueâ]
Asobo provides the SDK that 3rd parties use to create add-on airports, no? In my posted issue all three of the airport addons from Flightbeam, Orbx & I forget the other I bought thru the Marketplace in-sim are affected. The common denominator is the SDK. Itâs very easy to imagine whomever created the SDKâs airport section simply inadertently left out fields for ILS frequencies to map into the MFDâs frequencies table, thatâs all.
Is FSDeveloper the official forum for Third-Party Development? I know itâs down right now, but that may be the right forum to raise this because youâre effectively bypassing the obfuscation of the Ticket process, and presumably talking or making it visible directly to BOTH parties - Asobo and the after-market makers. Crazy, I know, but, what other choices do you have? Make it clear itâs a TBM 900 menu problem that isnât working correctly with third-party software. That put accountability on both parties.
Sorry folks but have to laugh a little because this whole thing started with a bit of mis-information KPDX is by Flight beam not OrbxâŠbut donât let facts stop anyone from arguing with one another sometime amusing
1 Like
As most manufacturers, that allow 3rd party accessories, do, with the caveat that it provides a road map. Doesnât imply that the 3rd party designer followed the map and does not imply compatibility.
This is where we need to stop. Software development and debugging is not well served by âimaginingâ what happened. If there is a perceived problem with a 3rd party add-on. Bring it to the attention of that developer. If he can confirm his code IS complying with the SDK requirements and should be performing as expected, then it is up to the developer and SDK provider to sort it out. Not the other way around.
Making guesses from outside the process just muddies the process.
Bought a 3rd party add-on.
Didnât work as expected.
Reported it to the 3rd party developer.
DONE.
2 Likes
agree with you 3rd party is the problem.
I would also change the subject line. The ILS frequencies appear to exist, itâs just how the third-party content is not being detected somehow by the TBM 900 menu.
They tried to force Agile on our Mechanical Engineering team (our VP of engineering a few years ago was a complete idiot and nearly killed the company) with no modifications due to the differing design timelines and methodologies⊠I think it lasted about two months, haha.
1 Like
If that issue makes somebody angry, Iâd probably suggest therapy or at least anger management⊠
Itâs not limited to the TBM. The ILS frequencies are not auto loading into the A320 FMS either. It does seem to vary from airport to airport. I havenât tried it on all, but the OP is correct is that it happens more often than not on most third party airports, why it doesnât happen on CYVR, I canât guess. Perhaps they are doing an extra step that is overlooked by most of the others.
The bottom line is just how important is to you. Iâm now on notice, and I routinely look up and jot down the ILS frequencies for that airport. For me itâs not a show stopper. For others, maybe different, but I canât say it rises to the level of âDonât buy any more 3rd Party AirportsâŠâ
Your making a HUGE assumption as to where the problem liesâŠ
Hereâs the process⊠The user has a problem with an Orbx airport. User submits bug report. Orbx debugs the problem and involves Asobo if necessary. Orbx solves the problem, possibly with Asoboâs help. Problem gets solved eventually depending on what the problem is.
If user decides to ask Asobo for help on it, Asobo will tell the user to work with Orbx, itâs ânot their problemâ. Is it possible thereâs a bug in Asoboâs software? Maybe. So what. Asobo is not responsible directly for solving Orbxâs issues for users. Asobo is responsible for fixing problems Orbx has developing software. To Orbx.
Man are people entitled these days⊠geez. Try working in a development environment someday of a hugely complex product. Stuff does not get fixed overnight. There are too many dependencies and too much other work to do.
Having developed approaches for an airport I developed, yep, the SDK is not finished yet and you kind of have to guess how to get things to work, and not everything does. Asobo has repeated this fact over and over and over. Not happy about the truth? Sorry. Let them finish please. Report problems and move on. Getting angry never solves problems, never has, never will.
(And I didnât mean to direct that diatribe at you directly @CasualClick, I just wanted to say we donât know where the problem lies. It might be with a plane, it might be due to something Orbx did. We donât know anything, because the SDK is not even close to finished, and it is even less documented than it is finished)
5 Likes
Truth.
As a pilot, part of the preparation of every flight is developing a ready record of all information that will be needed for the flight. Depending on a system to do everything for you at all times is a recipe for failure at some point, and in real life, well, thatâs a life or death matter.
I just had a radio failure today on a flight. Fortunately I had a co-pilot with me who handled the radio work while I figured out what was wrong (seems like there was some oxidation on the headphone plug, as cleaning it off and reinserting fixed the problem).
While Iâve got a GNS530 in the panel, I also keep two more EFBâs handy in case something goes wrong.
3 Likes