I am perfectly aware of that, but what I asked is, do you have plans to make your C172 a full Prepar3D 2.x product, so that:

 

1. We don't have to paste dummies of fsx.exe in the Prepar3D folder?

2. All problems like the strobe light are fixed?

3. It takes advantage of the new Prepar3D 2.x features?

 

Because what you're saying is, the C172 is a product for FSX and Prepar3D 1.4, but you're letting us use it in Prepar3D 2.x because it works, albeit with a workaround to get it installed.

I agree and I am getting a bit frustrated so I will ask the question one more time.  Yes or no.

 

Will A2A have a P3D v2 installer RATHER that a work around?

Maybe in the future but we haven't decided anything as everyone is using her just fine as it is.

 

thanks,

Lewis

Maybe in the future but we haven't decided anything as everyone is using her just fine as it is.

 

thanks,

Lewis

 

In my opinion, terrible choice not to fully support a platform that has a future. Both FSX and Prepar3D 1.4 are locked platforms.

 

And not even a fix for that strobe light problem? Or do you still expect Lockheed Martin to fix that? What if another problem arises with Prepar3D 2.3?

In my opinion, terrible choice not to fully support a platform that has a future. Both FSX and Prepar3D 1.4 are locked platforms.

 

And not even a fix for that strobe light problem? Or do you still expect Lockheed Martin to fix that? What if another problem arises with Prepar3D 2.3?

 

The C172 was released pre P3D V2, hence the installer for the 172 being for P3D 1.4 and FSX. Also be careful about how you talk about locked platforms. If it wasn't for locked platforms I don't think you would be here, the market and avsim etc would no doubt have not been around if MSFS had not been locked platforms for third parties to work on development.

 

Looking forward and not backward however the next simulations from us are looking to be P3Dv2 compatible (AS NOTED THE C172 ALREADY IS) and even the updates as it is right now install into P3Dv2 with no issue.

 

I personally from my own simming point of view am viewing this period a little like the FS2004/FSX change over. I'm expecting mostly new products for P3D rather than any of my FSX add on's to be made to work with a whole new platform. Besides Lockheed have been clear in making sure that the platform retains FSX compatibility as noted by them in there marketing for P3D.

 

So once again to install the C172 into P3DV2 you need simply copy or create a single file and name it fsx.exe inside the P3DV2 root.

 

The light issue you note requires a reload of the aircraft and is a known P3D issue not loading all effects correctly upon first load.

 

thanks,

Lewis

I don't understand what you're saying about locked platforms. What I mean is that FSX and Prepar3D 1.4 will never be updated again. Prepar3D 2.2 is the only platform with a future.

 

Now you're becoming even more confusing. You're saying that your future products will be fully compatible with Prepar3D 2.2, which is great, but you also say that the C172 is too. This contradicts your previous statement that the C172 is a FSX/Prepar3D 1.4 product, which is why the installer does not have an option for Prepar3D 2.2. This means that the C172 is not fully compatible.

 

If you really wanted to provide full Prepar3D 2.2 compatibility, you would update the installer just like Orbx updated their 80+ installers. Not updating a single installer, which should be an easy task, either shows laziness from your part or unwillingness to make it fully compatible with Prepar3D 2.2. Looks like the latter to me.

 

Safe to say you've lost me as a customer. I really wanted to buy your C172, but provided it doesn't support the only ESP-based platform that has a future, I won't. I don't know who's to blame for the strobe light issue, but I do know that other developers like Orbx and FlyTampa are cooperating with Lockheed Martin to get issues with their products fixed, either through product patches or new Prepar3D versions. Is it guaranteed that the strobe light, or any other issue that arises in the future, will be fixed? Doesn't look like so.

Once again you are trying to put words in my mouth and seem to be either trying your hardest to troll me or using a whole lot of assumption and guess work in your posts?

 

Il'l just stop now. If you wish to clarify anything we have our forums at A2A which already has everything mentioned in these posts + a whole lot more already answered.

 

(Video thanks to RobA)

 

thanks,

Lewis

I never put any words in your mouth, I just pointed out the fact that you later statements contradicted your previous ones. And I'm not guessing anything; both the incompatible installer and the strobe light issue are facts. Instead, it looks like you are trying to trick me by saying the C172 is working "just fine as it is", because it clearly does not.

 

This video doesn't say anything to me. Plenty of add-ons that don't fully support Prepar3D 2.x can be installed via a dummy fsx.exe in the Prepar3D folder, or a manual install by moving the files, or a migration tool. Many will work just fine and others will have incompatibilities, just like the C172 has the strobe light issue. I'm sorry, but at the state it is right now, you cannot call your C172 fully compatible with Prepar3D 2.2. Not when there are other developers working really hard to ensure that their products are functioning perfectly in that platform, and you're just throwing at us a workaround.

 

I don't have anything else to say, and I don't think coming to the A2A forums will help one bit because I'll get the same responses.

Maybe in the future but we haven't decided anything as everyone is using her just fine as it is.

 

 

 

thanks,

 

Lewis

 

 

Too bad. I was really thinking about buying the C172. But a have an easy rule these days: I don't buy any products anymore which are not officially supporting P3D2. Because there is a difference between "it works in P3D2" and it is officially supported. The good thing is: We as customers can freely choose who get's our money. With this policy, you won't get mine...

What on earth is going on with P3D. I make a post and then I'm told i'm not officially supporting it, that I'm not working with P3D and all sorts of other utter Tosh of the highest order.

 

The C172 works in, is compatible with and is supported in P3D.

 

I'll be at Oshkosh this year feel free to come have a chat with us, vent and generally tell us your thoughts and feelings on how we can improve at our booth.

 

Alternatively visit and post on our forums right now. You will notice should you do that an air of anticipation for the next Accu-sim core update that will install into FSX, P3D's and update products and add all new features free of charge.

 

 

thanks,

Lewis

What on earth is going on with P3D. I make a post and then I'm told i'm not officially supporting it, that I'm not working with P3D and all sorts of other utter Tosh of the highest order.

 

The C172 works in, is compatible with and is supported in P3D.

 

I'll be at Oshkosh this year feel free to come have a chat with us, vent and generally tell us your thoughts and feelings on how we can improve at our booth.

 

We already told you what you're doing wrong (unless you think this is right) and how you can improve. The C172 in its current state doesn't fully support Prepar3D 2.x, and we've already said numerous times why. No need to repeat ourselves. If you're not willing to fully support Prepar3D 2.x, no money from us.

So you just want the installer changed?

So you just want the installer changed?

 

This isn't about fulfilling a desire of mine, this is about officially and fully supporting Prepar3D 2.x, which is something that many want. This means an installer that will easily install into Prepar3D 2.x (without the need of having FSX installed so you can place the dummy), and taking any necessary steps to solve incompatibilities.

 

If you're calling this Prepar3D 2.x support, then I don't dare to see how the PA28 or any of your future products will be. This is just crazy. Either do whatever you have to so that the C172 is fully Prepar3D 2.x compatible, or stop with the fake crap.

The C172 is compatible. A dummy fsx.exe file is needed that is all. Its a matter of right clicking in windows and creating a new notepad file. Name the file fsx.exe and you are done, no need to have FSX at all.

 

And as noted, we are looking forward so the next projects will come with the base installer for P3DV2.

 

If we don't officially support it for some existing simulations then why on earth am I telling people how to use it and not doing as other developers are and refusing outright or going as far as blocking its use? (Also have you even questioned why this is, do you even have an idea as to issues aircraft developers are potentially facing with P3D licensing?)

 

As one of the few developers supporting P3D the hostility from you guys leaves a damn sour taste in the mouth and makes one wonder indeed. I suggest you stop and think before posting, and also only use what you know, not what you think or assume is correct.

 

thanks,

Lewis

Wow, I had no idea it is so hard to update an installer and get in touch with Lockheed Martin to fix a simple issue after all. I'm sorry. Orbx probably have superhuman powers.

perhaps its value driven! You P3ders are getting as bad as the Xmen. I wants.