10 hours ago, 0Artur0 said:

So, did Lockheed Martin respond to the issue?

They responded with their usual customer service robot response, then shut down the thread.

Made a small change to my AA settings with Inspector and even though I don't have an up to date system, I was content with the results:

 

Has anyone noticed this effect happens quite a lot with the Aerosoft Airbus Pro?

I am getting blurries after less than an hour of flight in cruise and this is with using FFTF dynamic.

I never got these with other complex add-ons...

I too have had terrible problems with the new AS Airbus. I think it's way more resource hungry than any other add-on in my hangar - and that includes all the full-blown PMDG aircraft (which work beautifully).

I found that I could successfully get rid of the blurries (using the info in this thread) but the Airbus autopilot often loses sync and the aircraft becomes unflyable. There are all sorts of theories and explanations (in other topics), but my own personal view is that the A318/319 is in dire need of some code optimisation.

Edited August 19, 20187 yr by Adamski_NZ

3 minutes ago, Adamski_NZ said:

I too have had terrible problems with the new AS Airbus. I think it's way more resource hungry than any other add-on in my hangar - and that includes all the full-blown PMDG aircraft (which work beautifully).

I found that I could successfully get rid of the blurries (using the info in this thread) but the Airbus autopilot often loses sync and the aircraft becomes unflyable. There are all sorts of theories and explanations (in other topics), but my own personal view is that the A318/319 is in dire need of some code optimisation.

In short what eliminated the blurries for you? It's a 30 page thread 😳

I get stutters as well. it's as if the performance get's worse with time during the flight.

1 hour ago, Shomron said:

In short what eliminated the blurries for you? It's a 30 page thread 😳

For me, I think the main thing was to change from an "Unlimited" TFR to 30 (a multiple of my 60Hz monitor), then enabling VSync and triple buffering. I left FFTF well alone (defaults to 0.33 I think).

5 minutes ago, Adamski_NZ said:

For me, I think the main thing was to change from an "Unlimited" TFR to 30 (a multiple of my 60Hz monitor), then enabling VSync and triple buffering. I left FFTF well alone (defaults to 0.33 I think).

I lock them to 30.5 in NVI, wonder if that does the same trick... thanks!

2 hours ago, Shomron said:

I lock them to 30.5 in NVI, wonder if that does the same trick... thanks!

I think the thread recommends locking the framerate and using vsnc via the P3D options menu.

Here I have always had a locked framerate without Vsync / TB with good results icw FFTF Dynamic.

Since I switched to SLI locked gives me a stutter every 1.5 seconds. Now Uimited + Vsync + monitors at 25 hertz give me the best result without stutters. And icw FFTF Dynamic.

 

vsnc on, 29fps locked, monitor 150Hz, FFTF .10, text exp 10, ASP4 5 layers 

600 MPH in F14 ...complete and unedited SFO to the roof top of Nvidia Hq (modeled). -stutter not representative of actual game play.

clip highlights:

I280 s.bound
01:42

Crystal Springs Bridge
02:53

Stanford University (back yard)
03:51

Apple HQ -new
03:53

Ca. 85 s.bound

Netflix
05:23

Western Digital -formally IBM Cottle Rd.
05:56

Reid Hillview airport
06:15

KSJC
07:02

Google Airport
08:12

Vertical climb over NVidia
08:29

 

https://vimeo.com/285859408

 

below is a clip from SFO to LAX .  everything captured during flight is in video ...no edits. meat and potatoes start at around the 6 min mark ....settings same as mentioned above.

https://vimeo.com/285635430

Edited August 20, 20187 yr by FunknNasty

My issue returned on my latest flight with QW787 over the east coast of North America, coastline all blurry and blotchy.

I have tested with the default flight P3D flight from the airbase near Gulf of Mexico in F22 flying due North for about 50 miles and it goes all blotchy.  I then removed all affinity's - both batch file way and the the job scheduler way - repeated the default flight and no blotches.  Seems like P3D 4.3 doesn't like AM.

Humph!  Was getting good results with Rob's and SteveW's help.

6 minutes ago, 9GTurn said:

I then removed all affinity's - both batch file way and the the job scheduler way - repeated the default flight and no blotches.  Seems like P3D 4.3 doesn't like AM.

I wish it were as simple as that! I've done the AM dance a few times  - and always ended up reverting back to *no AM*.

The impression I have from all my research and experimentation is that it's often more to do with whatever else you may be running at the same time as P3D (like ActiveSky, loading of scenery etc.). Throwing all the processing power at the main P3D application may cause bottlenecks with other processes (even disk access) which then impact P3D anyway.

IMHO, this explains why we have such a variation in results for what may appear to be at first sight just a "simple" tweak.

Adam.

Well I also may have an Orbx Global issue (missing files reported) - but I'm heading over to the Orbx forum to ask there.

4 hours ago, Adamski_NZ said:

I wish it were as simple as that! I've done the AM dance a few times  - and always ended up reverting back to *no AM*.

The impression I have from all my research and experimentation is that it's often more to do with whatever else you may be running at the same time as P3D (like ActiveSky, loading of scenery etc.). Throwing all the processing power at the main P3D application may cause bottlenecks with other processes (even disk access) which then impact P3D anyway.

IMHO, this explains why we have such a variation in results for what may appear to be at first sight just a "simple" tweak.

Adam.

The same, I tested a lot of settings on my i7 7700K but all are worse than „no AM” in cfg and they are case of stutters.

2 hours ago, YoYo said:

The same, I tested a lot of settings on my i7 7700K but all are worse than „no AM” in cfg and they are case of stutters.

Not much you can do with four cores to be fair.

Interesting fact: AM=15=1111=all four cores or is the same as leaving the AM out of the cfg completely.

With four cores and HT there's a little to be had there but only in terms of system resources like networking and P3D works on that irrespective of you having more than one node.

So you would naturally convert your 1111 into '01's like so = 01,01,01,01 - now with that AM the sim works exactly the same, even thinks there's only four cores available and is in fact running on all four cores.

If you see a drop in performance it's the other stuff taking advantage so adjusting the AM is fruitless in that regard. Even so I see folk attempting to get something out of an AM. What they are for is to stop something reducing the available throughput. That's usually caused by some software doubling up its task count when you don't want it.

That's why we start any exe apps that we run alongside the sim in a bat or with a specialist app so that they start in containment and can't spread out across those 'empty' Logical Processors - since they are not empty even when they say 0%.

It's a tricky subject and it's best to leave your AM out with few cores. Get something with a major core-count and you will need to consider it all very carefully.

 

All the best..