So, it DOES work and work well. 

 

 

That's been my experience also. And the best news is that the joystick loss issue under Win 8 appears to be fixed. I run unlimited, no NI meddling and with an explicit full AM (4095, for 12 physical cores).

 

The reason that I mention NI is that LM recently posted that they are waiting for nVidia to provide a new 3D profile for P3d 2.1. The key sticking point is the AA bits setting, which users like us can only fool around with by trial and error. For FSX/DX10, people have concluded that "0x80000F71 (BioShock, BioShock 2)" works best, but there's no reason that it should also work best for P3d 2.0/DX11. That's not to say that the BioShock bit setting doesn't work at all (it does get SGSAA to do something), rather that nVidia may have a better idea of what the setting should be. In the mean time, I'll wait for the driver with the new 3D profile for P3d 2.1.

......

We still have a long way to go. One thing I do know, though: unlike the last few years I will be spending more time playing other games. I've been disappointed with flightsimming too often by now and I sometimes don't feel like flying at all anymore. But of course that also might have happened if I had stuck with FSX... ^_^

Think positive Jeroen, all the lamenting doesn't help you to come further one inch.

Spirit

 

 

quite frankly this is really a horror tale in the making.

 

I think that description is a bit over the top. For many (if not most) v2.1 is an improvement, if you take all the posts herein on balance. To me, it sounds like most issues are from 3rd party add-ons and systems tweaked for FSX that have had P3D thrown on top of it. If you have the equipment, make a system image and try 2.1. Seems unfair to make lengthy conclusions without trying it.

this is really a horror tale in the making.

 

Oh the drama...

 

It is frustrating, but it is certainly no horror.  The accident at the corner of my road two nights ago where a little girl was killed.  That's a horror.

OK, that's too bad but thanks for forwarding the info!

 

Edited to add that I think it's a pitty QW look at the issue that way because now with lots of people wanting to have a good a/c in P3Dv2.1 QW could sell lots of extra copies of their BAe 146. Oh well...

Agreed, I've considered buying the QW146 but I'm not buying anything now unless there's at least a commitment to get it working in P3D2.x

K

I found a screen from v2.0 of Brisbane and tried to match it to see if the Autogen cone has changed. Unfortunately its a little difficult to tell, as I fly low and the screen was zoomed out, but if you squint  :Hypnotized:  you can see the edge of the agn radius.

 

Maybe 2.1 is slightly closer, or the cut-off tighter, but from this flight and screen, there is not much in it... its does need a better comparison to be sure.... not that its likely LM will change things back if the cone is smaller.

 

One weird thing here... I have lost the pilot from the Tiger Moth external view with 2.1 - any ideas as to why? I have tried reinstalling it, so maybe 2.1 breaks it [i know its not a P3D model, but it was working 100% before]

 

2.0

 

 

 

2.1

 

 

After doing a number of flights, I've come to the conclusion that there's something definitely wrong with v.2.1.  While it does fix many of the issues of v.2.0, it also appears to add a few new ones.  This was to be expected to some degree, but there are a few things that stand out.

 

1.) Why does v.2.1 break the compatibility of so many 3rd party addons, that worked fine in v.2.0?

2.) We were told the that pre-release patch was sent to 3rd party developers. If so, how did all these incompatibilities go unnoticed?

3.) Why hasn't LM acknowledged some of the issues that so many users are reporting on their site?

 

Here's just one example: A2A's C172 ran fine in v.2 (as long as you had mipmapped VC disabled), but in v.2.1, I've been noticing all sorts of issues lately (most of which I initially missed). After completing a successful short flight, where the aircraft was in 'excellent' condition; the next time that I fire up P3D and load the C172, it will sometimes be in much worse condition (once the prop was damaged, once the engine needed a complete overhaul).  Sometimes its beacon works ... sometimes it doesn't (and it is the times when it doesn't work that I find that damage has mysteriously occurred, while my C172 was parked). I've also noticed that when the beacon doesn't work, that my Saitek X52 is not longer listed as my controller ... AND then I get stutters (the ONLY time I have experienced any stutters with v.2.1 is when my A2A's C172's beacon is not working).

 

Also A2A's Piper Cub no longer has any prop animation with v.2.1 (and it worked perfectly with v.2.0.  When I reported these issues to A2A, I was told that it was P3D's problem, and to report them to LM. When I reported these issues to LM, they have so far been totally ignored. 

When I reported these issues to A2A, I was told that it was P3D's problem, and to report them to LM. When I reported these issues to LM, they have so far been totally ignored. 

 

The XML parsing engine in 2.1 is tighter, and as a result, less tolerant of syntax errors. Carenado are releasing patches for all their aircraft to fix the broken GNS 430/530 and G1000, but since A2A don't support Prepar3D, you'll have to live with those issues until they change their mind.

One weird thing here... I have lost the pilot from the Tiger Moth external view with 2.1 - any ideas as to why? I have tried reinstalling it, so maybe 2.1 breaks it [i know its not a P3D model, but it was working 100% before]

 

I think the pilot figure visibility is controlled by the load setting, so perhaps you have an empty load by default whereas it was full before?

Thinking to myself...

 

Boy do I love having a huge backup disk in my system and built-in tools in Windows 7 such as Robocopy and WBAdmin...30 minutes and not a single trace left of P3D on my system except for the setup files...

 

Now I'm off doing some FSX DX10 flying rather than P3D troubleshooting :wink:

 

Have a great weekend everyone however you choose to spend it!

I think the pilot figure visibility is controlled by the load setting, so perhaps you have an empty load by default whereas it was full before?

 

Thank you for the suggestion... I have pilot and passenger in the payload, but neither display. Maybe a compatability issue; not the end of the world but spoils any screenshots using this ac, which I do a lot... can't expect a fix, as its a freebe.

 

 

 

 

 

Have a great weekend everyone however you choose to spend it!

 

This....

 

 

2.1 in its glory.

 

 

 

 

 

 

For FSX/DX10, people have concluded that "0x80000F71 (BioShock, BioShock 2)" works best, but there's no reason that it should also work best for P3d 2.0/DX11.

 

Works great here for 2.0.  I use it w/ SUPERCVAA_64_12x4 w/ SGSS 4x or plain supersample 4x.  Takes care of runway lines & thresholds, plane exteriors great, etc.  Water looks as good as it can as well.  On my system I DO NOT have performance issues w/ this approach--it was a miraculous finding ;o)

I know that it "works", but when you look at how diverse that bit setting is for the spectrum of 3D apps, there must be some fine tuning that nVidia does. I can't imagine that the bit setting is just a bunch of random numbers.

 

I will try your suggestion, though, but I have 2.1 working really well, so I'm leery about messing with NI too much.

 

 

I will try your suggestion, though, but I have 2.1 working really well, so I'm leery about messing with NI too much.

 

You can always reset everything in NI and stop using it. Everything you do with NI is reversible so nothing will be lost by simply giving it a try.

After doing a number of flights, I've come to the conclusion that there's something definitely wrong with v.2.1.

 

 

I fly the A2A 172 a lot also and you are correct, the beacon no longer works. As to the condition of the aircraft changing from the end of flight to the beginning of the next flight, I haven't seen that yet, but it is easy to work around the problem by heading to the hangar and doing a complete overhaul. That destroys some of the realism, but the only other option is to delete the 172's history DAT file, which sometimes gets corrupted even with FSX. Here's a thread with some good ideas on how to revert to backup DAT files (where the plane's history is stored):

 

http://a2asimulations.com/forum/viewtopic.php?f=107&t=36871

 

A2A has clearly stated that they don't support P3d2 (which only means don't ask them for help), but they have also stated that they "are working to support all platforms in the future."