SDK?

[jgoggi 65]

Hi, what about the SDK? Robert said 16 days ago that it was on the point of being released! Please, refrain from the usual sentence "legal items, that no one knows how long it takes to solve", it's no longer a good excuse....

[Paul Deemer 13]

Just for a second put yourself in their shoes. If it were your product would you take any chances that the SDK would be abused without the proper legal protections in place? I think Not! Like it or not the American Legal System works at a snails pace. Fact of Life.

[ESzczesniak 128]

I understand the speed of the legal system. It would be nice to hear an update though. The last piece of information stated that they expected to hear from their council almost a week ago and prior to that we were told it was ready for release with the exception of the EULA. Are they still waiting to hear from the lawyer, have there been even more legal issues, did they hear from the lawyer are awaiting further drafts, etc? Most of us, and definitely not myself, are not asking PMDG to give an SDK that doesn't protect them, could be abused or anything else. However, many people are eagerly awaiting and at last update it was supposed to be tied up about now or earlier. It would be nice to just see a couple sentences as to where things stand now.Eric Szczesniak

[Buzz313th 0]

The legal issues are tied directly to the EULA that would acompany the SDK. I doubt it takes a lawyer more than 6 weeks to compose it based on the legal goals setforth by PMDG. If there are any holdups, it has more to do with PMDG being "Up in the air" on what they want to say in the EULA.On the other hand, if PMDG has infact made it 100% clear to their lawyers what they want to say in the EULA and it's taking them this long to write a 5-10 page document, then it's time to find a new lawyer.JB

[flyguy172 0]

i thought they said it was cleared and ready weeks ago, what happened

[Mean Aerodynamic Chord 269]

God people! It will come! Just frikking wait!

[Houghton11 12]

This isn't a case that's trapped inside the American legal system....it's not like the SDK is in court or anything.The delay can probably be attributed to who/whatever PMDG's legal counsel is just going through every possible scenario (in terms of third party modifications, can people profit from it? are PMDG entitled to royalties?....) and making the appropriate entries in the EULA or whatever legal document comes with the SDK.Let's not forget, the NGX SDK will allow third party functionality within another system (the NGX itself) operating within another platform (FSX). Imagine the legal mumbo-jumbo that could come out of that (if PMDG makes royalties off a FS2Crew product or something like that...is Msft entitled?)These questions are all hypothetical of course, but they still need to be answered.Hence, the delay.There's entire firms devoted to technology law stuff like this, and it can take a pretty good amount of time to draw up the legal stuff behind a technology product (iTunes anyone?).I can only imagine how long it would take for a smaller firm or even a individual.

[Paul Deemer 13]

The legal issues are tied directly to the EULA that would acompany the SDK. I doubt it takes a lawyer more than 6 weeks to compose it based on the legal goals setforth by PMDG. If there are any holdups, it has more to do with PMDG being "Up in the air" on what they want to say in the EULA.

This isn't a case that's trapped inside the American legal system....it's not like the SDK is in court or anything.The delay can probably be attributed to who/whatever PMDG's legal counsel is just going through every possible scenario (in terms of third party modifications, can people profit from it? are PMDG entitled to royalties?....) and making the appropriate entries in the EULA or whatever legal document comes with the SDK.Let's not forget, the NGX SDK will allow third party functionality within another system (the NGX itself) operating within another platform (FSX). Imagine the legal mumbo-jumbo that could come out of that (if PMDG makes royalties off a FS2Crew product or something like that...is Msft entitled?)These questions are all hypothetical of course, but they still need to be answered.Hence, the delay.There's entire firms devoted to technology law stuff like this, and it can take a pretty good amount of time to draw up the legal stuff behind a technology product (iTunes anyone?).I can only imagine how long it would take for a smaller firm or even a individual.

Trying to second guess on this is really stupid. Neither you, me or anyone else besides PMDG knows the full details of what the issue is. If you recall RSR said if you haven't heard anything from him it's because he is not wasting time to come in here and make a post about something he doesn't even know the answer to yet. That seems pretty reasonable and self explanatory to me. If you also recall Ryan stated that their legal issues are not open for debate in the forum so why don't you just drop it?

[Guest]

SDK now basically means FS2 Crew and I guess we will have to wait around Xmas for the NGX SDK and middle-end January for FS2 Crew.

[ohsirus 240]

*Deleted* as my interest.

[DGK737 0]

Hi,would it be possible to publish a list of the already supported FSUIPC key commands with a link to the appropriate knob or button?I guess this would make the live for the home cockpit builder much easier.I use a lot of the Leo Bodnars' BU0836X boards that works very fine via FSUIPC and idle aircrafts. Also for project magenta SW.If you could publish a small doc with a pictures of each panel and marks with # on the knobs and then provide a list what command what # supports will make your 737 NGX product a super thing!I tried to use the key commands settings that you provide via the CDU. The problem is that this is all "function toggle" and NOT set to a value. e.g. "Autobrake" - you can define keys to toggle but if you use a 45° rotary know you need to set a value according to the knob position. It is really a nightmare to trigger out what works and what not using the long list of FSUIPC key commands.Any help are very much appreciated.Thanks

[steve inwood 67]

This will be another closure topic i see here ...I think it's high time people learned to wait...Steve

[Paul Deemer 13]

Orson Welles, We shall sell no wine before its time.

PMDG, We will not release the SDK until it's time.

[DGK737 0]

I fully understand that a SDK is an ideal solution, covering everything and this is the required basisfor all professional & commercial cockpit builders. And for sure this will need time, no other opinion here.But I guess there are a lot of "amateurs" or non commercial private home cockpit builders,who are looking to find their own "work arounds" - as we can see, from Steven Munn'sdriver for the GoFlight MCP Pro - What a brilliant Idea!May be not 100% perfect (at least 99,...) but satisfactory for the user and the use case.Also in most cases an SDK is a sophisticated not even easy to handle construct,that may be very hard for this kind of flight simmers. So why not making the live easierfor the PMDG customers? Such a simple list could not be a big deal ... and would have a big effect.(look at project magenta, Enrico has published the FSUIPC offset table and so everybody can make his own macro - this was the main reason for me to buy his SW...)Also in general: The 737 NGX is such a brilliant simulation and that sophisticated,that "learning to fly" a B737 becomes a real passion.But I will learn how to fly it and not to become a "mouse virtuose". I am more than confident that only simmers who already have a bunch of panelsand moduls will have fun with that level of complexity that 737 NGX offers.Managing 10 Sub-Displays via key commands and mouse clicks will make you that busy,that there is nearly not time left to listen to ATC and do flying.....So why not being customer oriented - provide a list with FSUIPC commands, keep the "early birds" busy and excitedand take the time that is required to launch a proper SDK!.... sorry I will not bother the great PMDG team, but what you are doing at the moment is offering a brilliant vine, let everybody enjoy the great flavor but keep the vine glass locked ... .... but may be I still think to much as a product manager ... forgive me...

[FS++ 683]

I agree with most parts of your postAs you mentioned, Steve Munn has done a great job interfacing that particular hardware panel.I will add…Pete Dowson provides access to the NGX via FSUIPC (registered version required)http://forum.avsim.n...x-737ngx-ready/We too as providers of voice control add-ons could have spent the last 3 months moaning and screaming about the whearabouts of the SDK.Because we believe PMDG owes us nothing, it would be just a favor if they released the SDK.After all, they build (and rather well) Aircraft add-ons, and not tools, sceneries or else.We set out to interface the NGX since late August. After 3 months, and thanks mainly to the Microsoft SDK, we have managed to give access to our virtual co-pilot to almost any button in the cockpit. There are things we can’t read of course, like FMA info displayed on PFD. And who says the SDK will provide this anyway.But it does the job, which is to fly the bird in a multi-crew environment. You can have your hands on the control wheel, and just ask the FO to adjust speed, heading, altitude, and various other items.There is a fully working time limited Demo for those who want to give it a go.Note: MCE now uses real recorded voices, unlike what you can hear on the old videos.http://www.multicrewxp.com