• There seems to be an up tick in Political commentary in recent months. Those of us who are long time members of the site we know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religiours commentary out of the fourms.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politicion will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment amoung members. It is a poison to the community. We apprciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

New U.K Scenery, Coming Soon

Status
Not open for further replies.
Hmm yes, I suppose it can be seen as personnal opinion. And my personnal opinion is still in the "looks like" area, which means it's not final, just first impressions.
Having seen the french autogen projects growth, I realized the amount of work that was involved, both from payware (FranceVFR) and freeware (Vogel, Gropied and other members).

You're saying that taking all the autogen definitions they created, which meant a lot of time and efforts, to include it in your own file without asking authorization is not piracy ? You think it's all cool and FranceVFR and other french forums members should apology for complaining about it ?
Seriously....
 
Hmm yes, I suppose it can be seen as personnal opinion. And my personnal opinion is still in the "looks like" area, which means it's not final, just first impressions.
Having seen the french autogen projects growth, I realized the amount of work that was involved, both from payware (FranceVFR) and freeware (Vogel, Gropied and other members).

You're saying that taking all the autogen definitions they created, which meant a lot of time and efforts, to include it in your own file without asking authorization is not piracy ? You think it's all cool and FranceVFR and other french forums members should apology for complaining about it ?
Seriously....

I'm not asking for "FranceVFR and other french forums members" to apologise for anything; I'm suggesting that as you made what appears to be a completely unfounded allegation of piracy on SOH it might be appropriate for you to admit you made an error. But even though Darren has explained what the issue is, you are still accusing them of taking others files without authorization? Ah well, looks as though manners has taken a back seat at SOH, maybe it's time for me to move on for good.
 
Hi Daube

Any information that ES has added to the Autogen files has been sent to us from an ES customer who's ES scenery has been broken by another add-on. Whenever this occurs we merge the customers files so that they are again able to use their ES scenery (and their new add-on at the same time). As long as the customers problems are resolved we'll then include the definitions in the compatibility set we have on our helpdesk to prevent a repetition, so we can more easily resolve the issue for other customers who might get the same combination of scenery going forwards.
I've personally never seen a copy of this AGX file swapper program, and you'll see that there are plenty of other sceneries ( each with the potential to break ES scenery) that are included in our compatibility files, but none of those appear in the AGX lists. ( Orbx, RevX, Sim720 etc ) As I understand it, we sent out our newsletter the day before AGX was available, and I can promise you that I did not catch a ferry to France and then break in to France VFR's offices in order to get my hands on his definitions. :running: The purpose of the newsletter was to inform customers of our current work and some Reviews & awards we'd just received. The mention of compatibility files was a small paragraph 3/4 of the way down the e-mail.

Helping your customers should be the only objective of any developer, which we have always tried our best to do. This is not about scoring points. If that were the case why is it we only tell ES customers about the availability of compatibility files? Ok.. so I'll tell you why, it's because those are the people we have a duty to help.
 
you made what appears to be a completely unfounded allegation of piracy on SOH it might be appropriate for you to admit you made an error.

Completely unfounded ? What exactely allows you to say that ?
Darren provided his explanations, and that's nice.
The French guys, both from the payware and the freeware sides, provided their explanations, which is nice as well.
Both explanations are saying oposite things.
So who should I believe ?
 
Completely unfounded ? What exactely allows you to say that ?
Darren provided his explanations, and that's nice.
The French guys, both from the payware and the freeware sides, provided their explanations, which is nice as well.
Both explanations are saying oposite things.
So who should I believe ?

Well, you appear to have accepted what is being said on the France VFR forums, so I guess that is who you believe. But that's your call I guess and, as the Mods appear to be happy about you making accusations of piracy, not something I will comment on any further .... in fact I won't be commenting at SOH full stop.
 
Hi Daube

Well...imagine taking this to a court of Law.

The complainant ( France VFR ) case is that there is copyright infringement on files. The files he's talking about and claims ownership of are the Microsoft system files within FSX. Which are clearly copyrighted and owned by Microsoft. Is he do you think going to win his case?

The moral question is do I have a right to serve my customers interests, when another company breaks our product. I wholeheartedly believe that I do. Especially when item 3 of my reply above remains the case.

3: ES have been providing compatibility files for a long time, we have always had them discretely placed on our helpdesk for the benefit of ES customers who run into difficulties after their ES scenery is broken following the installation of another add-on. Ironically, and for all it's misgivings, Our ESI installer is the ONLY installation program that integrates the required changes into the autogen files, whereas all the others will replace them. So if all developers installers were doing things the same way as ours does, there actually wouldn't be any need for the compatibility files at all. :rolleyes: . This can be demonstrated easily enough. Install a France VFR scenery & then install an ES scenery. Result = Everything co-exists. On the other hand, if you install an ES scenery first, followed by a France VFR scenery. Result = Your ES scenery is broken...And who is it that picks up all the support for this eventuality? ..yep ..We do.
 
Status
Not open for further replies.
Back
Top