Unfortunately, recently the relationship between these two companies fell apart when Reality XP released the Sandel 3308 gauge competing with the one Eaglesoft was selling.There is a detailed chain of events from Eaglesoft's perspective that leads up to where we are now here:http://eaglesoftdg.com/forum/viewtopic.php?t=1127I don't blame the Eaglesoft folks for being upset with things if this is what happened. But what is really bothering me is thisfrom Eaglesoft: "In light of the dissolution of our partnership prior to the recent RXP release, Eaglesoft Development Group can no longer support panel integrations of RXP products into Eaglesoft Development Group aircraft. This includes support of RXP user built panel integration in Eaglesoft Development Group forums, and RXP users driving Eaglesoft Customers to RXP site/forums for RXP product integration into Eaglesoft Development Group products. This notice includes a request to remove all Eaglesoft Development Group references from RXP site along with any permission to integrate RXP products into Eaglesoft Development Group products."As I read it, no one is allowed to add Reality XP gauges to an Eaglesoft product. I can understand not them not wanting to support mention of Reality-XP on their forum, but to ban all use? Am I wrong at being upset with this? Am I reading into this more than I should? I enjoy products from both companies, and would like to use them together.There are a lot of good developers out there and we benefit when they all get along. Now the FSE and ASV guys are pointing fingers at each other over failure to move integration between the two products along. It

Uh...the way I read it, nothing's stopping you from using RXP avionics in Eaglesoft aircraft if you want, but don't expect help or support in your efforts to do so from either company.When I looked a couple days ago for unrelated reasons, the RXP site still had setups for their avionics posted for Eaglesoft aircraft. If you want 'em, better get 'em now and save yourself the trouble of getting a copy from somebody else or figuring out the setup by trial and error yourself later.

Tony, I couldn't agree more."This notice includes a request to remove all Eaglesoft Development Group references from RXP site along with any permission to integrate RXP products into Eaglesoft Development Group products."So they originally gave permission, but now they're taking it back? Lame. I feel as if I'm watching a bunch of kids fighting at the playground LOL. To be honest it makes me sick. Not only does this bother me, but all the bickering going on around here lately between the authors of the products you mentioned.

They are gone now. I never got around to downloading the CJ1 retrofit. In addition, the Reality XP forum was a good place for folks to post shots of retrofits they were doing, get feedback and help each other trouble shoot. I actually purchased the CJ1 partially based on the positve comments about it on the Reality XP forum. Based on my reading of Eaglsoft's post, we can't even talk about or post refits on public forums like Avsims. I don't have the talent and time to fully intergrate the into the VC like some of the others out there, and so I count on them.Tony

Dupe post.

I think I have the retrofit at home Tony..I'll send you a PM or email if I do have it.Eaglesoft just lost a customer today. Maybe it's a knee jerk reaction, but I'm sick of the "you slighted me, so now I'm gonna make all my customers pay for it" routine.I don't know what business school the Eaglesoft folks went to where they teach you to limit your customers ability to use your product, but they might want to get their money back.

I plan to maintain and integrate my RXP stuff into the Eaglesoft planes that I own. So there!:)Apparently the "gentlemen's" agreement was trumped by an under used word in the flight simulation business.... competition. Welcome to my world and tough.:) And a business strategy that could hurt a customer's product enjoyment is not well thought out IHMO. Bob....

Bob,Glad to see that you are willing to take the time and effort needed to integrate third party products into your aircraft:-)That is not only your right, but every other flightsimmers right to do so and we have never stated anything contrary to that. Note: Eaglesoft Development Group cannot, nor do we wish to prohibit private user built integrations into indidual or private aircraft. Although the recent flap re: Eaglesoft and RXP is old news and really is of little consequence to any flightsim enthusiast due to the fact that many have and will continue to integrate whatever they wish into whatever aircraft they wish, we will try to clear any confusion this may have caused. The unfortunate circumstances behind the recent flap between the companies are in our opinion "water under the bridge" and we have no malice toward RXP. We are simply in the undesirable position of being unable to offer support for integrations at this point in time. This is no more than a normal business "speedbump" to us and we assume the same goes for the other company involved. We see no need to make a "mountain out of a molehill" over this so we will attempt once again to clear the air as follows. This is an excerpt from our forum posted shortly after the recent flap which should be clear enough for any reader to see.:-)Note: Of course owners of Eaglesoft Development Group Aircraft are free to integrate whatever they wish into their own private aircraft but do so at their own risk and Eaglesoft Development Group has no responsibility as to product compatibility with any third party products.http://eaglesoftdg.com/forum/viewtopic.php?t=1132

Thanks for clearing that up Ron. I do have one issue remaining. Was it necessary to have RXP remove all the (Eaglesoft)user create mods off their site? As far as I know they were just providing space for people to upload their files so we didn't have to do the email/pm dance in order to use someone work. In fact, and I may be wrong here, but even RXP didn't support those files, they just provided the space.

>Thanks for clearing that up Ron.You are welcome Paul. Rereading our statement..."it should be obvious that this leaves Eaglesoft in the unenviable and unacceptable position of continuing to promote"..."by sanctioning integration".Unfortunate, but sometimes things happen in business. No need for it to become any more than what it is. As mentioned, no malice on our part towards other companies:-)

>Unfortunate, but sometimes things happen in business.>Sorry Ron, but I respectfully disagree with you. In making that statement you try to trivalize(sp?) something which is very important to some of your customers. If these things happen in business, then take care of it in some other creative way without impacting your fans. If you hadn't thrown a wet blanket over the whole thing and said, "sorry, just busines" - shrug, and tried to find another creative way to do 'business", then you would have made a positive impression on not only your current customers, but also potential new customers.

While it is your right to respectfully disagree, and we will no longer beat a dead horse, it should be noted that no company that we are aware of is obligated to support user integration of third party products into their own unless there is a partnership agreement.While we provided such support in the past we simply cannot at this point in time for reasons stated. No trivilizing here, just attempting to show that business realities sometimes have an unfortunate effect.We are aware of many user integration files which are already available and kindly suggest that those folks who are interested avail themselves of those files from other users.

The Microsoft School Of Business?Ever read the EULA of tiny print that comes with an MS product?

>>Unfortunate, but sometimes things happen in business.>>>Sorry Ron, but I respectfully disagree with you. In making>that statement you try to trivalize(sp?) something which is>very important to some of your customers. If these things>happen in business, then take care of it in some other>creative way without impacting your fans. If you hadn't thrown>a wet blanket over the whole thing and said, "sorry, just>busines" - shrug, and tried to find another creative way to do>'business", then you would have made a positive impression on>not only your current customers, but also potential new>customers.All you can do is vote with your feet/dollars/whathaveyou. In seeing both sides of the coin, I am sure the 3rd party add-on scene is tight. In my book, so long as the integration information is available elsewhere, not too big of a deal.I see Ron's point, but I, like you, don't really dig the extra hassle. I think margins are so slim and add-on development is still so ad-hoc and chaotic (voodoo black magic at times really), that many developers become cynical and jaded. Most of these guys have been through the wringer one too many times with the various foibles and pitfals of the "biz." On the other hand, our (we, the unclean masses) ability to get up close and and personal with developers from companies like Eaglesoft is an anomaly in the software biz. If you were constantly rubbed by the public you'd be callous too. A bigger shop/developer would actually have marketing/PR people who can deal with us consumers in scientifically proven methods. So, you take the good with the bad. The "I'm taking my toys home with me" vibe sucks for us, but most of the guys we interact with from these development teams are the developers themselves - too much pressure after awhile.

Sheesh, let it go guys:-) The user integration files are freely available from other users. A simple PM or email should get any integration that anyone wishes to have. Those of us who go back to the FS98 days well remember having to download and integrate any number of files from any number of places to put together what we wanted...surely anyone who wishes to integrate products together these days can email or PM the other interested parties for such files.:-)