JFI, as someone pointed out elsewhere, if you read the Learning Centre ( Lockheed Martin/ Prepar3D v2/Learning Centre from Start Menu), under Prepar3d Product you will find Tuning Guide - General Performance Tuning which gives 4 other tweaks to the .cfg apart from the affinity mask.  Would be interest if the others make a difference too.

HIH

I am sure they are very interested and they already looked at how for instance the C172 works in P3D 2.0 but they haven't officially announced anything yet. I just asked about this on the A2A forum so we'll see!

I installed the A2A 172 today using the faux FSX.exe file as per Jeroen's method. Works perfectly.

I have an Intel i7-2600K Sandy Bridge CPU @3.4GHZ O/[email protected]. According to CPU-Z I have 4 cores 8 Threads. Not sure how to access my BIOS to check if I have HT on/off? What would be my Affinity Mask Setting?

Well put J!   Don't see why LM has any "strong reason / need" for compatibility (in the future).  Pretty scenery has little to do with flight sim and training - and if an add-on a/c is not supported (and doesn't fit P3D core training needs anyway)  d***ed if I see why LM should dumb down future P3D - an evolving product after all - for developments made for a near 8 year old platform. As for "the FSX community getting led into another platform" . . . pfui Teufel!.  half my FSX stuff isn't compatible with FS9 let alone 2002 and earlier.  Why isn't  A2A compatible with my old original (Apple) flight simulator?.

I should respectfully point out to some people - we are lucky!.  Lockheed Martin is sure not going to crash and burn because they don't kowtow to some developers - but said developers will, if they try to force loyal customers into continuing with a creaking platform.  what happens when it finally (hopefully) goes 64bit. - will these developers insist we continue to buy unsupported old copies of FSX?  or will "the community" refuse to be bullied?

Kind of disappointing. Sounds like they want Lockheed Martin to do the work for them when an incompatibility is found, but if they try too much to keep backwards compatibility with FSX add-ons, then the application cannot move forward that much (because as few things as possible will have to be broken). What would A2A do if Prepar3D 2.0 was 64-bit?

I have an Intel i7-2600K Sandy Bridge CPU @3.4GHZ O/[email protected]. According to CPU-Z I have 4 cores 8 Threads. Not sure how to access my BIOS to check if I have HT on/off? What would be my Affinity Mask Setting?

You should read my post a little bit up in this thread. There you'll see what AFM you need.

Spirit

You should read my post a little bit up in this thread. There you'll see what AFM you need.

Spirit

Pretty sure its AFM=14 for me but not sure how to check if HT on/off? How can i access BIOS to check status of HT?

Hi,

 

Been using A/M since day one, For those of you struggling with A/M and what to select. Here is an A/M (with and without H/T) calculator.

 

http://www.gatwick-fsg.org.uk/affinitymask.aspx?SubMenuItem=hardware

 

 

Hi,

 

Depends on your motherboard, for me I just press DEL during bootup, on another computer I have to press Esc, on my Laptop I have to press F12, that brings me to CMOS.

 

---------------------

For your system

---------------------

[JOBSCHEDULER]
AffinityMask=14

 

or With H/T ON

 

[JOBSCHEDULER]
AffinityMask=84

 

 

Pretty sure its AFM=14 for me but not sure how to check if HT on/off? How can i access BIOS to check status of HT?

I'm still getting blurries no matter what

I'm still getting blurries no matter what

 

Well, I suppose you simply have your settings too high then...

Pretty sure its AFM=14 for me but not sure how to check if HT on/off? How can i access BIOS to check status of HT?

 

 Quick way is to open Task Manager/Performance and see how many cores are shown. If 4, then HT is off, 8 would mean HT is on.

 

If HT is not on, you would still have to go to the BIOS to change it. ( or tun it off)

 

Hope this helps.

 

Lyn

Task Manager shows 8 cores which means HT is on. I will set AFM=84 and see how it goes. Thanks folks!

A2A doesn't seem to have realised that Prepare3D v2.0 isn't FSX - in fact it even v1.x wasn't. It was ESP.

 

Lockheed Martin have little interest in maintaining backwards compatibility. All it actual said on this matter was that Prepa3D v1.x and FSX add-ons should work with v2.0. It's the responsibility of add-on developers to make their products compatible with v.2.0, not the other way round. Regardless of what A2A may think Lockheed Martin has no reason / need to continue to keep 100% compatibility.
 

A2A's response is slightly surprising. If LM are fundamentally changing parts of the core sim to move the whole platform forward, it doesn't seem reasonable that they also need to provide fixes for every developer's product that falls over in P3D. It would seem as though some developers are not willing to invest time in P3D yet unless the economics makes it viable - which on the flip side is also reasonable. Seems like the migration to P3D might be as slow as it was to FSX from FS9.

A2A's response is slightly surprising.

 

 

Eh, not really. A2A is not a giant corporation and they probably can't afford to support multiple platforms. Here's the hierarchy from the easiest to accommodate to the more difficult.

 

1. FSX Acceleration/Gold Edition DX9 only

2. FSX ,but also DX10 compatible (look how much resistance there was even to this minor change)

3. FSX and P3d 1.4 (initially most vendors ignored P3d like it was the return of the Black Plague)

4. FSX and P3d2 (probably the main target platforms for the next year or so).

5. FSX, P3d 1.4 and P3d2 (why bother with P3d 1.4 at this point?)

6. FSX, P3d 1.4, P3d2 and XP10. (any 3rd party vendor has my best wishes for being so committed to flight simulation)

 

Besides,A2A will come around to your way of thinking eventually as they are a progressive bunch. I remember when a number of 3rd party vendors said that they would NEVER support the use of their products in P3d. Look where that kind of thinking ended up.