FS9 support > Las Vegas FS9
GA Traffic at the gates?
FalconAF:
virtuali,
Like I said, I didn't mean any disrespect with my post. But the way this is going, it IS confusing. There are two versions of the KLAS scenery...FS9 and FSX. There are two separate Product Support forums for them. With the exception of one post in the FSX forum about parking codes only, the impression someone could easily get is that any current AFCAD endeavours are for the FS9 version only. Most posts relating to FSX AFCAD problems are in this FS9 support area. I (and probably many of your other customers) don't use FS9 anymore. If I am looking for support for your FSX product, I "normally" wouldn't be searching for it in the FS9 support forum.
And I'm sure Harpsi is well deserving of his hard (and much respected) work on creating better AFCADs for the FSDT sceneries. I certainly appreciate all he is doing for KLAS right now. But if I understand it correctly, those are being created using AFX...a payware program. And AFX DOES have compatability problems when creating AFCADs for "FSX-specific" sceneries. Many of your customers use ADE...the freeware program...which does not have these problems with FSX-specific AFCADs. It is very easy to "destroy" an AFX created AFCAD if it is opened in ADE (if the user isn't aware of how this can happen), so that it won't work in FSX anymore. Which can easily cause more "support" requests when incremental AFCAD updates users download for the FSX scenery versions quit working (if the end-user hosed it using ADE).
I'll crawl back in my cave now, and sit quietly awaiting an FSX AFCAD worthy of the outstanding FSX scenery developed for KLAS.
Rick
EDIT: Just to be sure that you know I honestly didn't mean any animosity with any of my posts here, the below is what caused all my confusion. It is a quote from you in a previous post in this thread.
"Simply because we do developement work in FSX only, so we prefer to use an FSX-native editor, and then derive the FS9 version by simply compiling the FSX source XML (removing the things FS9 doesn't support) with the FS9 SDK."
That led me to believe you develop the sceneries for FSX, THEN "do whatever is necessary" to make them work for FS9. That implied (to me) that any AFCAD discussion\rework here revolved around an FSX version of the scenery and AFCAD. But I just read your reply in Harpsi's newest post about a new KLAS AFCAD, and it says the AFCAD is for FS9 only right now. Your reply says that as soon as it is completed, it will be adapted to the FSX version of KLAS. You gotta admit...that doesn't quite agree with your quote above about the FSX version of the scenery being done first, followed by a "derival" of the FS9 version. That's what made this all so confusing.
Now that I understand what is actually going on...the development of a functional FS9 AFCAD FIRST...then a "dirivitive" of it for the FSX version...I'll just wait for the final FSX version.
Peace
virtuali:
--- Quote from: FalconAF on April 19, 2009, 06:26:11 pm ---Like I said, I didn't mean any disrespect with my post. But the way this is going, it IS confusing.
--- End quote ---
You are making this far more complex than it is.
As I've said already, you don't need to worry: as soon as we find the FS9 AFCAD has reached a satisfactory level, WE will take those addition and will integrate into the FSX version. You don't need to worry how we do it, we know what to do, we don't use any strange tool that would create problems, most of our editing is done directly at the source code level, and the final scenery is always compiled with the MS BGLCOMP coming from the official FSX SDK, I don't know where you get the idea we compile BGL with AFX, when we said, many times, we use FSX BGLCOMP, meaning, our files are 100% SDK compliant.
And, in any case, this shouldn't be your problem: you are not supposed to do the merging between the work Harpsi will do in FS9 into FSX. We are so, as long as we say (as we said, many times already by now) that once the FS9 file is finished, a similar FSX version WILL come, made by us, where, exactly, the issue is ?
FalconAF:
Our posts crossed. I added an edit to my last reply, and it looks like you didn't see it before you posted your above reply. It explains it. No problem anymore. I had assumed from your previous quoted reply the FIRST version of an updated AFCAD would be for the FSX version. When I downloaded Harpsi's first AFCAD in another thread, it didn't work in the FSX KLAS version. I didn't know it was designed for FS9 only. And based on some other posts from other FSX users in the forums, I think they probably didn't realize it either, especially if KLAS was their first FSDT purchase and they didn't have the previous experience of how the updated AFCADs are developed and released (the order they are done in).
See my post at the very top of Page 2 here. I actually thought maybe something like that was happening, and asked if Harpsi's AFCAD was for FS9 or FSX. I never got an answer to it, but THOUGHT it was for FSX. That resulted in my subsequent posts.
All is fine now. Just a mass miscommunication on both our parts.
Rick
Cereal Eater:
lol - quite litterally a "mass communication". :D
felixthreeone:
And that is all I am waiting for...Is a stable, well-assembled afcad (Harpsi you are the MAN)...and I will be purchasing this scenery. Thanks, Virtuali, for continuing FS9 support!!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version