Since Fs2004 I am using the Aerosoft MCP / Eicas/ Efis hardware.Since 2 years Aersoft Australia stopped producing them.Like me there are certainly others wondering if the hardware will work with FSX or that we can put it away, which would be a pity.The same when Vista somes out.Does anyone know something ?

Can you try it with the demo?John

AFAIK the aerosoft hardware does need fsuipc. So when FSUIPC will be ready for fsX , it should work. (As there is no fsuipc for the demo, it wont work with the demo I think).If you have the PM software and no extra hardware to the extension ports or gameports, you even do not need the aerosoft hardware. It will be driven by the mcp.exe (it will need an extra setting in the mcp.ini file)regardsNorberthttp://home.wanadoo.nl/norbert.bosch/

>AFAIK the aerosoft hardware does need fsuipc. So when FSUIPC>will be ready for fsX , it should work. (As there is no fsuipc>for the demo, it wont work with the demo I think).The MCP747.exe program indeed uses FSUIPC. You can check that in the FSUIPC.LOG file. But I would be very surprised to see it work with FSX without changing a bit in the MCP747.exe. From my recollection, the introduction of FS2002 and FS2004 always have caused software updates for MCP747.exeAnd there are more depencies... If you are using the MCP with Level-D for instancee, you may have noted that the MCP747.exe uses the LVLDSDK.dll module (it's in the same folder as mcp747.exe). So we also have to wait for the Level-D dev team to upgrade Level-D for FSX. Regards,Nicohttp://www.nicokaan.nl

>But I would be very surprised to see it work with FSX without>changing a bit in the MCP747.exe. From my recollection, the>introduction of FS2002 and FS2004 always have caused software>updates for MCP747.exeThat would be a big pain in the *** for all the aerosoft747mcp users. Then we would need to stick to fs9. I doubt if Andrew MacLean would make an update. (or remove the added hardware to game/extension ports and use the build in driver of the project magenta mcp.exe.regardsNorbert

>But I would be very surprised>to see it work with FSX>without changing a bit in the>MCP747.exe. From my>recollection, the introduction>of FS2002 and FS2004 always>have caused software updates>for MCP747.exeI have no idea why he would say that. I was using the same version of firmware for the Aerosoft MCP747 throughout, I only just updated it a little while before I sold it a couple of years ago (I use a PFC MCP now).I am fairly sure the assorted updates in the firmware were to fix issues in the earlier stuff to do with things like the add-on rear connections, and some problems he had with the first officer's EFIS. I believe he was also involved with PM for direct support by Enrico's software, and that caused some other changes.I really do not believe that there were any specific changes needed simply because of FS versions. It is FSUIPC's job to paper over those!> ... So we also have>to wait for the Level-D dev>team to upgrade Level-D for>FSX."Of course, you'd have to do that in any case, not just for the Aerosoft MCP747.>Could you please respond to>this ?See above. I know at least one FSX Beta tester using his Aerosoft 747 MCP quite happily with my FSUIPC4 (as the new one will be called), and he has been doing so since the early Beta FSX releases.Regards,Pete

Nice to know FSX beta did work with fsuipc 4 and the aerosoft 747.Thanks for sharing.Norbert

>>But I would be very surprised>>to see it work with FSX>>without changing a bit in the>>MCP747.exe. From my>>recollection, the introduction>>of FS2002 and FS2004 always>>have caused software updates>>for MCP747.exe>>I have no idea why he would say that. I was using the same>version of firmware for the Aerosoft MCP747 throughout, I only>just updated it a little while before I sold it a couple of>years ago (I use a PFC MCP now).>>I am fairly sure the assorted updates in the firmware were to>fix issues in the earlier stuff to do with things like the>add-on rear connections, and some problems he had with the>first officer's EFIS. I believe he was also involved with PM>for direct support by Enrico's software, and that caused some>other changes.>>I really do not believe that there were any specific changes>needed simply because of FS versions. It is FSUIPC's job to>paper over those!Gerard,I hope you are right, but why did the FS2004 tab appeared in the user interface when moving from FS2002 to FS2004? Or is that just to differentiate from special add-ons such as PMDG and Level-D with ordinary FS2004 use? If so, can somebody check this with a FS2002 implemnetation, i.e. does MCP747.exe (the latest version) still work in FS2002?Regards,Nicohttp://www.nicokaan.nl