Has anyone installed the Mustang and gotten it to run using FSX Service Pack 1? SP1 is my version of choice for FS-X, as I get the best results when Tileproxy is running.Thanks and Regards,John

Has anyone installed the Mustang and gotten it to run using FSX Service Pack 1? SP1 is my version of choice for FS-X, as I get the best results when Tileproxy is running.Thanks and Regards,John

Can anyone answer?

Can anyone answer?

SP2 is required.

SP2 is required.

I know the docs say that, I would like to know if anyone has tried it with SP1 unless you can identify a feature in SP2 that is required which SP1 doesn't offer.Regards,John

I know the docs say that, I would like to know if anyone has tried it with SP1 unless you can identify a feature in SP2 that is required which SP1 doesn't offer.Regards,John

John,You just got your answer from the developer of the Mustang. What more do you want?

John,You just got your answer from the developer of the Mustang. What more do you want?

Can the snide answers. I am a developer as well, and we release baseline support requirements to our clients. That doesn't mean a product won't run if someone deviates from that baseline, it just means we won't support it if issues arise--we can't lab a million different system configurations in our shop.Jim said SP 2 but he didn't give a reason why. Is that all they will support? I have no problem with that if someone has used the package with service pack 1. I don't call or email add-on vendors every five minutes with an odd question or support issues. Flight 1 products have been excellent on my system and if there's one I can't install, I don't have a problem with that. But if someone out there has installed it, I'd be happy to still buy the Mustang absent of support.

Why not just try to run it with your installation, no hurt in that

Why not just try to run it with your installation, no hurt in that

I'm considering it but if there's a compelling reason not to, I'd rather not waste Flight One's time asking for a refund if things go awry. There may be something unique to SP 2 that the Mustang requires. I just installed the Duke recently and the Carenado 172 prior to that and both worked very well, but neither would be using the systems the Mustang would be trying to emulate.Regards,John

Why not just try to run it with your installation, no hurt in that

Because that would cost us time and money processing a refund when I can tell you that it will not work properly in SP1.I believe MS did a great disservice by not removing SP1 when SP2 was released. Just one more level of confusion.Regards,Jim

Because that would cost us time and money processing a refund when I can tell you that it will not work properly in SP1.I believe MS did a great disservice by not removing SP1 when SP2 was released. Just one more level of confusion.Regards,Jim

Thanks Jim, Problem with service pack 2 is when autogen is off, buildings have a habit of disappearing when the angle of view shifts--I've had airport buildings vanish then reappear on final, which is quite distracting. Since ACES is no more, chances of this issue ever getting addressed seem to be zero. Since Autogen is not supported under Tileproxy (nor would it look right), the issue is quite obvious. If SP 1 weren't available, I wouldn't be flying FS-X. The disservice Microsoft has done is in ceasing support for this great franchise. Regards,John

I have issues with SP2 as well, mostly performance. I know SP2 is suppose to perform better, but I'm getting sharp decrease in FPS when I pan around in the virtual cockpit, that doesn't happen with SP1. I know this is probably due to upgrading to my current install, and a fresh install will probably fix the issue. I have too much installed to start from scratch, so unless I have to reinstall I'm happy with what I got. To answer John's question, I have the Mustang and it will not work with SP1. I do have it running on my acceleration installation on my Vista boot disk and it works great, but I do most of my flying on my XP installation in SP1, so I don't get to fly it that often.

Thanks Jim, Problem with service pack 2 is when autogen is off, buildings have a habit of disappearing when the angle of view shifts--I've had airport buildings vanish then reappear on final, which is quite distracting. Since ACES is no more, chances of this issue ever getting addressed seem to be zero. Since Autogen is not supported under Tileproxy (nor would it look right), the issue is quite obvious. If SP 1 weren't available, I wouldn't be flying FS-X. The disservice Microsoft has done is in ceasing support for this great franchise. Regards,John

You use the addon Tileproxy, you have the FSX autogen turned off and using SP2 buildings dissappear, so you use SP1, and this is a fault with SP2, so you blame Aces because your FSX doesnt work correctly with an addon? Do I have that right? If so have you considered removing Tileproxy? I have a 3 year old system and SP2 runs perfectly here.

You use the addon Tileproxy, you have the FSX autogen turned off and using SP2 buildings dissappear, so you use SP1, and this is a fault with SP2, so you blame Aces because your FSX doesnt work correctly with an addon? Do I have that right? If so have you considered removing Tileproxy? I have a 3 year old system and SP2 runs perfectly here.

No he's saying scenery objects disappear with autogen turned off. Since he uses Tileproxy he doesn't use autogen. This is the problem I warned about when SP2 changed the rules of the game midstream in regards to backward compatibility. You now have addons that worked fine in SP1 that doesn't work in SP2 (at least without modification) and worse now you have addons built for SP2 that isn't compatible with SP1. I thought FSX was FSX SDK compliant? Compatibility changes should only be made on a major release, else you end up splitting the community.

No he's saying scenery objects disappear with autogen turned off. Since he uses Tileproxy he doesn't use autogen. This is the problem I warned about when SP2 changed the rules of the game midstream in regards to backward compatibility. You now have addons that worked fine in SP1 that doesn't work in SP2 (at least without modification) and worse now you have addons built for SP2 that isn't compatible with SP1. I thought FSX was FSX SDK compliant? Compatibility changes should only be made on a major release, else you end up splitting the community.

I've never tried turning off autogen but now that my curosity is peaked, I'll give it a try next time I fly. I'm aware of the problem with some planes and the different SP's, one of my favorites was the PMDG 1900 but after SP2 the props are hosed, so now it's a hanger queen.

You use the addon Tileproxy, you have the FSX autogen turned off and using SP2 buildings dissappear, so you use SP1, and this is a fault with SP2, so you blame Aces because your FSX doesnt work correctly with an addon? Do I have that right? If so have you considered removing Tileproxy? I have a 3 year old system and SP2 runs perfectly here.

Even without tileproxy, if Autogen is turned off when SP2 is installed, buildings can disappear and reappear during a flight. A good example of this is flying out of Tahoe Valley towards Stateline, NV. As you fly closer, with autogen off, the casinos will vanish or reappear depending on your POV. So I do blame ACES for this--not everyone flies with Autogen on. It does not always realistically depict the real world, whether one uses Tileproxy or not. The option of having it off while flying should have been considered.