Also FSX is the world where I go to when I need to relax and forget all my real life problems. I really admire all the developers that contribute to that little world of mine and make it better with every quality add on. My only way to say thanks is by showing them support with my hard earned money!

+10000000

Scott,I just discovered that if I disable REX weather engine before loading the Piper Cub I don't get any SimConect error.Can you confirm that this is a known conflict?I'll do some more testing tomorrow and report back.

I don't have this product but am curious to know how the virtual crew it models compares to FS2Crew.Do they use the same style as FS2Crew?

Ramirin,I spoke with the coder on our team that created that simconnect failure test you are seeing, and he is confident there is an error in simconnect, but said, if you are certain it is working, then you should be able to right-click and remove that message.Have you checked out our FAQ here, at the very end, it shows how to fix simconnect w/o having to uninstall FSX:http://a2asimulations.com/forum/viewtopic.php?f=65&t=19370One of our testers does have REX and does not have any conflict issues, so take a look at the link above.ScottA2A Simulations.

I don't have this product

Shame on you, Bryan. :( (kidding)Seriously, it's close to it although you can only trigger a "next" action with actually doing something or you can just listen what happens.E. g. if the stewardess enters and offers drinks Fs2Crew opens a dialog while the A2A Heidi goes ahead with serving the stuff either way.While you later would switch Fs2Crew to the descent and approach checklists, the A2A senses the flight status of the plane and triggers the necessary cabin announcements for example. So you interact with both products, but differently. Intersecting sets will surely be present.The A2A doesn't run any checklists to follow. The FE announces his items to you, so that you are aware, but the FO for example remains silent (but announces things like flap settings) and doesn't ask for any items.There's no briefing action involved too. But the A2A crew reminds you about some things regarding the status. So advancing the throttles on the ground will lead to a 'we have to set flaps 25 first' for example. Later, a 'our engines are running hot' may come up when you forgot about the water injection or are just running too high power settings.I'd say the interaction with Fs2Crew planes is more transparent to the user, but also requires the management of the additional popup windows, while the A2A runs all the time (with Accusim enabled) and senses your intentions while not using any dialogues.An example for that sensing are the cruise messages from the Captain. I think if I stay on one altitude for a certain time (like I did on a real flight or just in my traffic pattern for the touch&gos), the Captain will hold hold his speed, while in Fs2Crew you as a user would trigger the speech by pressing a button.After reading the philosophy thread about the new CotS addon, the room for Fs2Crew to plug in there may also get widened since A2A fully focused on the atmosphere and 'alive' character my eyes, intentionally avoiding additional dialogue popups. So some parts of the plane drive the Captain and force him to act in responsibility.But I'd be happy to see some checklist actions and alive FO too, so maybe you want to take a closer look there, Bryan. :smile:Since quite some features can be accessed through the new LINDA software, I guess that some SDK-like approach for your soft would be possible too, but that's just a layman's assumption of course.

Just to add some information on the "Simconnect error" discussion. I have a dual-boot system withWin Xp Pro x32 and Win7 pro X64 with the B377 installed in both versions as well as the otherAccu-Sim aircraft.In Xp, I can load an accusim aircraft exactly twice, be it from the GUI or the inflight "Load"menu or ending a flight and beginning a new flight. Any combination...for a total of 2 times.The 3rd time I load an accusim flight I get the "simconnect error" message. Every time.If I am flying in an area with dense scenery and my Xp system bogs down as terrainand/or textures are loading I will sometimes get the error message.On my Win7 boot I can reload accusim aircraft 6 or 7 times before I will get that error.Now my Win7 boot uses exactly the same hardware but of course the memory management/availability is different, among other things.My point being that anything that disrupts the flow of FSX data for an extended period can,it seems, cause the simmconnect error message to appear. Loading 3rd party addons couldperhaps play into this scenario.Also, the hires textures of some of the accusim aircraft caused my Xp system to lockup orexhibit problems until I reduced the texture size. OTOH, the Win7 system did not showthese "problems". Paul