2 hours ago, SteveW said:

Well, like I say, we have to get that system set-up all right first so we know its capacity.

i have such a system.

I never encountered that blurries (thank god) but i also did not set a lot of gates manually. But ive flown around with the default jetways did now at least 10 flights and (knock knock knock) dont have it. If i have to guess i set around 10 to 12 gates overall manually, so not much. Maybe it depends on this. Im with you there, often its the last added thing that overloads something so that looks like the reason. But even more often i see ppl fly around already with settings that give ppl 90% core usage and 99% gpu usage..... so i dont doubt an addon like this can break it completley. What doesnt mean that this addon is the reason.

And hopefully noone gets me wrong, i know theres a problem for many many ppl. I read the topic that hast like 16 pages now on the devs forum too. Absolutley not denying anything, i would rage same if it happened to me, im sure. I just want to give an example of a pc that seems to work. So no hard feelings pls, i only try to help ppl, even without having the problem so pls dont rage at me now. I see in our community very clearly that quite a few ppl have this and its bad. I hope the dev can improve it for the ppl having problems.

I dont have a very empty sim. Theres many orbx regions, hundreds of payware airports, activesky, rex hdairports worldwide, rex skyforce, reshade, tomatoshade with advanced reflections, smartcars, projectfly, utlive and probably 1 or 2 others i forgot now. Running in fullhd with around 80% of terrainsettings (included highres terain acticve), 2k textures, around 70% autogen settings, most shadows active but low effect settings and dyn reflections on low.

asus prime 270k

1070 msi aero itx

16 gb ballistrix sport ram

7700k

all standard core frews

win 10

NO HT MASK. But quite a few tweaks to reduce shadow sizes (like translucent_shadow and some others like these). Thats all the tweaks. Oh, wait, i set activesky etc, all the other apps around p3d, to not use first core (by simstarter). Thats all and my way of an AM.

I have the feeling the sim got a bit more microstutters though with GSXlv2, but thats so hard to tell....with different weather conditions and different regions etc...

Edited September 13, 20187 yr by SaenchaySor

3 hours ago, vgbaron said:

In all the years that I have been dealiig with computers and flight simulation I am always amazed at the number of people who continually blame a single program for their troubles based upon the "it worked before and it works after so it's the programs fault" theory.

Although there are a few occasions where this might be true, the majority of the time it is simply that the newest program revealed a deficiency in the system that wasn't apparent.

These problems are system specific - if that were not true then every user of the program would have the problem.

So, rather than blaming any one program I suggest delving into the systems of those who have the issues and find the OTHER common points that might give a clue to the real problem.

Does anyone here REALLY think that an experienced developer would release a complex add-on without testing?

Vic

Vic as a very experienced software/system engineer your arguments is one pitfall for many 😉
With complex software it can be a combination between different programs local even hardware which occur by only a part of your customers...
Of course this has been beta tested thoroughly, but always there will be bugs or unexpected events... Doesn't matter how good you are....
I have learned the hard way not to make statements written in black and white, it's more a grey area where you always have to be open minded.

For me personal it's always a warning flag when a program causes this kind of events in our virtual world environment.
It's not and attack or pointing fingers (to much respect for everybody contributing to our hobby) 
more sharing an experience which could be similar between fellow users and to help each other to solve the puzzle and enjoy our beloved hobby.

I agree that it could also be the tipping point in performance downgrade for some systems local...

Than again I did three airports with GSX2 SODE jetways (love this stuff) LSGG / LSZH / EHAM with a lot of gates...
Gone from a hefty 1.95gb texture size here local to 580mb (2K textures) Tested of course with both.
So today was the first day of testing between airports, so going in the upcoming days conduct
more tests with log tools to see what's going on in the background 😉

The support received from FSDT is great and they have to trigger the event local to solve it, (or it has nothing to do with GSX2 but more a conflict etc...)
So maybe we all can help each other in our quest for a smooth GSX2 experience.

However that's not the case here local 😉

Edited September 14, 20187 yr by awf

Andre - we are in agreement. I was intentionally vague because there are too many variables in a situation like this. My point is though - one cannot specifically point to a program like GSX and say the problem is it's fault. That is yet far from proven. It may well be the culprit but from what has been said it is just one of the possible causes.

I can guarantee that if there's something in GSX that triggers certain systems, Umberto will track it down. I just submit that it's easier to work with someone when you are not calling out his product.

Vic

 

3 hours ago, Bert Pieke said:

You are not being told that at all.. the discussion drifted off topic.

AM may help, but the underlying issue appears to be GSX.. and I would agree that that needs to cured if that is the actual problem.

If you are running a quad processor with HT on, start by trying an AM of 253.  11 11 11 01 and see if you feel better in the morning.

Thanks for the advice Bert. 253 and 84 produce the same blurries as no AM. I tested it with ATT disabled. 

50 minutes ago, duckbilled said:

Thanks for the advice Bert. 253 and 84 produce the same blurries as no AM. I tested it with ATT disabled. 

OK - back to the GSX topic 

 

ps. don't know what ATT stands for..

Edited September 14, 20187 yr by Bert Pieke

1 hour ago, Bert Pieke said:

I tested it with ATT disabled. 

I think it's his phone. 😁

6 hours ago, vgbaron said:

In all the years that I have been dealiig with computers and flight simulation I am always amazed at the number of people who continually blame a single program for their troubles based upon the "it worked before and it works after so it's the programs fault" theory.

Although there are a few occasions where this might be true, the majority of the time it is simply that the newest program revealed a deficiency in the system that wasn't apparent.

These problems are system specific - if that were not true then every user of the program would have the problem.

So, rather than blaming any one program I suggest delving into the systems of those who have the issues and find the OTHER common points that might give a clue to the real problem.

Does anyone here REALLY think that an experienced developer would release a complex add-on without testing?

Vic

Apparently the testing didn't reach an ideal sample of the community, otherwise it would have been caught before, during the beta test phase. See, there's not a handful of simmers having issues, there's an awful lot.

10 minutes ago, Wanthuyr Filho said:

Apparently the testing didn't reach an ideal sample of the community, otherwise it would have been caught before, during the beta test phase. See, there's not a handful of simmers having issues, there's an awful lot.

There's an "awful lot" of users who push their image quality settings too hard and eventually instigate issues.   LM doesn't test its sim with every possible combination of IQ settings and add-ons. Nor does LR test XP11 that way either.

I agree with Vic on this one.  But it wouldn't shock me to find that LM finds a way of further refining the rendering code in V4.4 such this "problem" is vastly reduced in scope.

I absolutely love GSX2.. Sooo good for commercial airline ops.. Gsx and sode are a marriage made in heaven.. But ever since I upgraded to gsx v2, I'm seeing more blurries, longer time for aircraft wing and body textures to load and also longer time for pmdg wing view sounds to load.. I've never had a situation where the sound needed time to catch up!  Also, a windows 10 update was forced on me around the same time.. Nvidia also prompted an update to driver, but didn't go for it.. Will do another test today and post some concrete data as simbol had requested.. 

6 minutes ago, jabloomf1230 said:

There's an "awful lot" of users who push their image quality settings too hard and eventually instigate issues.   LM doesn't test its sim with every possible combination of IQ settings and add-ons. Nor does LR test XP11 that way either.

I agree with Vic on this one.  But it wouldn't shock me to find that LM finds a way of further refining the rendering code in V4.4 such this "problem" is vastly reduced in scope.

That seems to be easy to check then. Get a P3D v4.3 installation empty of addons, just FSTD airports (mandatory) and GSXv2, and then put its graphic features to the minimum, so that it doesn't utilise much resources, and check whether or not the problem is there. Then go raising the number of addons and/or graphic features up to the maximum. IMO this is not the case, anyway, it seems to be such an "8 or 80" issue, very binary indeed.

2 hours ago, Wanthuyr Filho said:

Apparently the testing didn't reach an ideal sample of the community, otherwise it would have been caught before, during the beta test phase. See, there's not a handful of simmers having issues, there's an awful lot.

Don't  think  that's  the  issue  other  wise  it  would  have  been  caught   before it  was  released,  maybe  all the beta   testers  didn't  have  this  issue  and  there  are  many of  us  that  havnt  got  the  blurries

I have not used GSXv2 or intended to purchase at the moment but the addon updater kept tell me to update which I did when not running P3Dv4.3, now it seems I'm forced to have GSXv2 on my system as there's no GSXv1 anymore, the result is my FPS has dropped by 3-4 frames and the loading times have increased, and with 10 FSDT airports I'm faced with disabling GSX and possibly addon manager and loose my airports.         

5 hours ago, vin747 said:

a windows 10 update was forced on me around the same time

There indeed was a Windows update soon after GSXL2 was released.
I wonder if there is any relation between the update and the blurries people are experiencing.

The windows update only landed on my PC yesterday.

33 minutes ago, Rafal said:

There indeed was a Windows update soon after GSXL2 was released.
I wonder if there is any relation between the update and the blurries people are experiencing.

In my case no. I have Win 10 Pro, and have automatic updates turned off. The last update I did manually was in early August.

Ongoing research at the FSDT forums seems to show that the problem is most severe at airports with large numbers of replacement GSX-specific SODE jetways. Umberto has been working hard to try to resolve the issue for those who have it. A GSX live update was just released in the past day or so which downsized the textures on all the L2 replacement jetway objects, which seems to have made a substantial improvement for me. The only airport I have seen the blurries and high CPU load was on approach to default Detroit which has probably over 100 of the new GSX jetways.