Hello !I was wondering about the next update.When will it be (approximately) released ?Will it fix some of the things that have been mentioned here from day one (like some switch logic, GPWS harrassing etc.) ?Thanks for the info.Tero

Tero-It will (approximately) be released soon! :-) ;-)It will be fixing quite a lot of stuff in fact.Sorry I won't be more specific, but you know what a stirrup it creates when people see deadlines. We're very actively working on the next update, but we're purposefully keeping quiet about any release dates. Just hang on a bit longer!Thanks

Hello Lefteris,Thanks for the information. All I needed to hear! :)back to lurk mode...Tero

Hi Lefteris,Good to hear about the upcoming update. I'm really looking forward to it's release. If you don't mind, may I ask you a specific question about the next update? Will it include keybinding?In my eyes, what stops this bird becoming my favorite at the moment (and a lot of others too) is the mousecontrol of many import functions. If it isn't included in this update, will it become available anytime soon?With regards,Lennart

Hi Lennart-I am trying to be as vague as possible with the upcoming release on purpose, so I don't get innundated with tons of queries about specific things it will fix.However I can safely say that yes - it will have keybinding, at least for the EFIS and MCP panels, which are most frequently used by everyone.

Hi Lefteris,That's VERY good news! Can't wait! Thanks a ton.Lennart

Lefteris,>> keybinding, at least for the EFIS and MCP panelsAh no, I don't ask if the Autobrake switch could be included as well :).But if I read MCP and it has nothing to do with the next patch : Will you support the CPFlight 737 MCP in the future ? Would be great, because it has authentic layout compared to the Aerosoft 747 MCP.http://www.cpflight.com/images/mcp01.jpgMike

Mike, I am sure you will find PMDG happy to add support just as soon as their evaluation model shows up at Anthony's door. ;)Companies that sell toys should expect to donate some to developers to have them supported.Ray

I had asked the same question to one of the CPFlight guys a while ago and he just responded, talks with PMDG about that subject didn't lead to any result, so their unit will NOT be PMDG compatible.With NO offense intended in any direction, that's a pity. Maybe Aerosoft Australia will make a 737MCP, but who knows when. It seems Andrew McLean can't even get 747MCPs together, his unit can't be ordered since months.Back to mouse clickspot grabbing, sighMike

Blah... I doubt it.I have an MCP done with FSBUS, plus a LOT of other hardware.There's no way in hell I'm gonna go back to using mouse...see www.fsbus.de if you got interested :). You can create an MCP and the PMDG bird doesn't even have to have keyboard assignments (though with future in mind, it's highly recommended that they not only provide keyboard assignments, BUT also a complete SDK (like PICv2) so us builders can access the internal workings directly)Tero

Tero,sounds nice, but I'm afraid with my poor electronic knowledge that would probably lead to anything, but not an MCP. And how do you get the display values (Speed, Hdg, Alt, VS) into your MCP? If I understood, that display offsets is what would need PMDG support ??Mike

Mike->I had asked the same question to one of the CPFlight guys a>while ago and he just responded, talks with PMDG about that>subject didn't lead to any result, so their unit will NOT be>PMDG compatible.>woa Mike - before the spread of misinformation continues, I'd like you to tell me who that CPFlight guy was... I have been contacted by someone in regards to this, but it wasn't a direct email or call by anybody at CPFlight - it was someone they are associated with, so I never gave a direct reply either (I would know - I am the person responsible at PMDG for external hardware connectivity).>With NO offense intended in any direction, that's a pity.>Maybe Aerosoft Australia will make a 737MCP, but who knows>when. It seems Andrew McLean can't even get 747MCPs together,>his unit can't be ordered since months.Andrew McLean is making his MCP compatible with our software as we speak. I don't know about new units, but the ones in existence are going to be compatible, that's for sure.>Back to mouse clickspot grabbing, sighOnly until the next update, Mike...

Ouch, Lefteris, I neither wanted to stir up anything with this or spread out misinfo. The guy, that runs the CPFlight info mail (Claudio) only informed that talks didn't lead to a result and it will be not compatible. He didn't say HE himself contacted you. And how shall I know if CPFlight or any representative of CPFlight contacted you ? From my point of view talks that didn't lead to a result is a neutral sentence, I don't see any blame or offense for anyone in this. Could well be the problem is on the side of CPFlight themselves ?However, for me the end result was what counts. Your 737 is the most sophisticated Addon I ever had and will probably be for a long time, so I was just enthusiastic seeing that unit. Would be somewhat the cream on the cake to operate your NG with so much authenticity (but again, NO offense to Aerosofts 747 MCP intended).Thanks for making the keybindings possible, some of those I can use in my hardware already and regarding the MCP, I might indeed have to look into building something myself (as Tero suggested).Mike

Mike,And remember, you will always get heaps of help here at Avsim's home cockpit forum, and I can also assist you via direct email if needed.FSBUS is free, and it's easy to construct some of the basic elements of a real cockpit, say an MCP.You're right about the display problem. IF an addon uses FSUIPC default offsets, there's no problem at all in getting the displays to work... they just work :). If an addon uses an interface module of its own, problems arise. Like with the "old PIC767" hehe, that interfaces with FS through their own module, AND there's no information available about what the offsets are etc. Luckily, the new 767 (it will not be called PIC anymore) will most likely be put out with a complete SDK that enables a cockpit builder to read/write every possible switch, state, display, event from the SW. So it's all about the addon itself. The reason why Aerosoft has gotten their MCP displays to work is the fact that they worked together with PIC team to enable the data reading from PIC767 into their own interfacing module that's basically the core of the MCP SW.I don't know what offsets the PMDG uses. What I do know is that it uses FSUIPC, so the stuff should be available, and is most likely easily found (in case the developers will not assist at all) in a couple of minutes.Here are a couple of (lousy quality) shots of my current configuration. The MCP on top of the C monitor and the box on the right side (contains all of PIC767's crucial systems and a lot more) are self-made with FSBUS. The MCP took a week to construct, the box took two weeks.Terohttp://www.ee.oulu.fi/~partanen/k4.jpghttp://www.ee.oulu.fi/~partanen/k6.jpghttp://www.ee.oulu.fi/~partanen/MCPuus.jpghttp://www.ee.oulu.fi/~partanen/k5.jpg

Tero,whow, looks very nice. I'll have a look into the FSBUS manuals and see if I get any picture what needs to be done. Be prepared for some silly questions though ;).Some pics from my current setup. Still a bit chaotic, I'm waiting for a third monitor and PCI graphic card to arrive to display the overhead panel. Low quality pics, but at least Lefteris can get an idea for what does all that keybinding work :DMike.