>
>Here is the bottom line.
>
>There are so many variatons of machines out there that while a
>procuct may work well on one machine it may perform dismally
>on another.
>
>If a person has a problem with a specific product whether it
>be payware or freeware on their machine it would seem to me
>that they
>first list the problem and second list their machine specs so
>that someone in either the forum or the seller or deveoper of
>the product can work on the "fix". There are simply to many
>variations of hardware to assume every product will work.
>
>So my point is: If you are having any problem with FSX then
>please
>list your specific machine components and there is a good
>chance
>someone will be able to help you.
>
>If you don't know what components are in your machine then
>don't don't waste time and expect any help.
>
>Ask for some help before badmyouthing a developer.
>
>If it's the deveopers fault then more that likley they use
>these forums to discover problems they may have not known they
>have.
>
>
>Craig
>

This post is directed at Craig (FTD1949)

Lets talk about the bottom line as you put it. There are many of us who DO NOT condone piracy based on the hard work that others like myself do.

I am addressing what you have hacked for your FS2004 KATL in this FSX forum because it directly relates to my FSX KATL here on AVSIM.

On the front page of your KATL you added a Product Update on

► 18 May 2008 RWY10/28 FMC fix for FSNAV/PMDG/LVL-D (among others) pilots

Regardless of wheather it was you, one of the staff, a person of interest, or someone that did it for you, my FSX KATL bgl was decompiled exposing both KATL and KLZU. Once that was done every single FSX line for line approach code that I spent months writing was extracted along with my KLZU ILS freq change and added to your update page. My KATL approach code is written for all the new Terminal Approach Procedures that are not part of FS9 or FSX based on the back timing. They tie directly into the ending of all new STAR arrivals since the release of FSX including

CANUK SEVEN (RNAV)
ERLIN FIVE (RNAV)
FLCON THREE (RNAV)
HERKO TWO (RNAV)
HONIE FIVE (RNAV)
LA GRANGE ONE
PECHY THREE (RNAV)
ROME THREE
SINCA FIVE
WHINZ ONE

So what is my enhanced FSX code doing in your FS2004 Airport.

The Product Update for your FS2004 KATL is not FS2004, it is not default FSX code but an entirly new approach code that I developed in Jan 2007 to bring FSX up to current Jeppesen charts that I subscribe to.

I fingerprint all my approach code for the simple reason to keep others from hacking my bgl's and placing it into PAYWARE /Freeware airport scenery. I also add statements to the master XML's that I write which will not show if decompiled with 3rd party utilities such as the following that is in my KATL bgl

</Airport>

<!--
<?xml version="1.0" encoding="ISO-8859-1"?>

Copywrite Active ILS Series of Airports
Jim Vile, uploaded to AVSIM on 01-01-2007
DO NOT EDIT or COPY to any other file.
DO NOT UPLOAD anywhere without my permission.
Do Not Decompile the companion bgl.

This file is exclusively for FSX KATL.
This XML contains new data compiled to a companion bgl file for ILS approaches.

This following copywrite statement is part of the compiled companion bgl but will not show
if decompiled.
-->
</FSData>

Whoever is responsible for hacking my approach code is not very knowledgeable. They did not even take the time to re-sort the Elements and Attributes and copied all the same new TERMINAL_WAYPOINTS that I placed for all the various Jeppesen 2008 Transition codes.

There is another small fingerprint I use which changes certain waypoints to a hex value if someone decompiles my approach code. Look at all your so called GPS receiver approach data and guess what, your lines are distorted or missing when you tried to compile my code back to a bgl. Hex code does not work very well as a waypoint name/uname tag. You would have been better off staying with the default FS2004 approach code and just stealing my RWY 10/28 ILS Transistion code instead of coping everything.

>
>Ask for some help before badmyouthing a developer.
>

I see no reason to ask for help when a developer pirates other designers work and then places their name on the bgl's that are in your Product Update.

I have written and updated many airports with correct approach code in both FS9 and FSX. Some of my code goes beyond FSX and only a real world pilot flying in out of KATL for many years would know how to write the exact correct Terminal Procedure Arrivals the way I have.

If you needed my code that bad then why didn't you just ask. That way I could have given you a FS2004 compatible code rather then you pirating my enhanced 2008 FSX code.

What happened? The thread has seemingly gone the way of the dodo bird.