FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: AirBorne on September 09, 2018, 07:07:59 pm
-
Anyone else in here?
P3D v4.3 and the CPU started to go to 100% load.
-
Anyone else in here?
P3D v4.3 and the CPU started to go to 100% load.
Same problem here. Also posted a reply on AVSIM to someone experiencing this. The only change on my system was the GSX update (I did not install the new expansion pack). I have not experienced this problem prior to this. GeForce GTX 1080, Win 10 Pro, no new updates. Prepar3D V4.3.29.25520. I cleared the shader cache and will see if that helps. On Windows Control Panel, Programs and Features Applet, I noticed that the GSX update (version 2.5.0.5) installed the MS C++ Redist (32 bit) libs ver12.0.30501, and not sure if that's part of the issue.
Jeffrey S. Bryner
-
Yup same here, and we keep getting told “its not gsx” ..... if i start a flight and dont use GSX everything is fine, as soon as i start using anything from GSX, jetways, pushback etc, scenery goes blurry and no autogen loads anymore after i leave the airport area... i have an I7 7700K @4.6 ghz with GTX 1080 and i was using a default airport...
-
Yup same here, and we keep getting told “its not gsx” ..... if i start a flight and dont use GSX everything is fine, as soon as i start using anything from GSX, jetways, pushback etc, scenery goes blurry and no autogen loads anymore after i leave the airport area... i have an I7 7700K @4.6 ghz with GTX 1080 and i was using a default airport...
My issue is most notable after departure, cruise flight and then ground textures get blurry (not clouds though), but CPU pegs at 100% for the Prepar3d.exe process on all cores it is using. Can't say I've ever seen that before. So, that may be the problem and the symptom is the blurry textures. Once on the ground again, within about 5 minutes textures display again albeit rendering very slowly.
Jeffrey S. Bryner
-
Yes same here, except my textures and autgen never load again after departing the airport, everything is blurry ecept the clouds. So this obviously is a GSX 2 issue... i never had this problem before until GSX level 2.
-
Same here. I gave more detail in the AVSIM thread. 1st flight with GSXL2 installed was from FSDT SDF to SAN. Massive blurries after the clouds cleared. Very long load time when resetting the scenery.
-
hi all
Same here, after 2 flights with GSXL2
Cpu I7 8700k, gtx1080Ti
Cpu @100%
Gpu @25%
Close my traffic addon programms during flight, don't change cpu 100%
weather addon programs are on core 10 and 11, no problem
thanks
-
See this post here, starting from JFK2, in the most autogen-heavy area of the world, with the most autogen-unfriendly airplane possible, under the worse possible situation for blurries (flying at high speed)
No blurries, and no autogen loss.
http://www.fsdreamteam.com/forum/index.php/topic,18432.msg128490.html#msg128490
About CPU utilization, I just made another test here:
Showing first with the Addon Manager enabled and lots of replaced SODE jetways in view, CPU utilization averages around 27% and GPU around 63%. Then, I disabled the Addon Manager, which disables *all* our software at once, and restored the default jetways.
Yes, they are a *bit* better in fps, so much uglier to look at, and the CPU and GPU utilization are exactly the same as with GSX enabled! I couldn't be more proud of this result: being able to replace 12-years old jetways with much better looking model, without affecting the CPU/GPU consumption AT ALL, and with only a minimal impact on fps, it's really good.
Now, having proved the problem is not caused by GSX, by it's clearly related to system settings, it's likely that something that affect CPU utilization might have something to do with having played with the AffinityMask setting.
Have you changed this value ? I'm using default, which means no AffinityMask at all in the Prepar3D.cfg file, which is the setting that make more sense to me. I tried with other values, reading users report of "miracle" changes, but the only thing I could achieve, was a huge slowdown in loading textures so, I went back to default immediately.
And, of course, the usual common sense antivirus settings:
- Exclude the Addon Manager folder from the antivirus.
- Exclude the whole Prepar3D folder from the antivurs.
-
Same here. I just uninstalled and the problem does not go away. GSX2 was the only change I made. I wonder if the exclude files have anything to do with it.
Edit: I also noticed the aircraft nav lights and strobes would not show.
-
Same here. I just uninstalled and the problem does not go away.
Try to uninstall and reply YES to the question "Do you want to remove the Addon Manager ?". Doing so, will *totally* disable everything that came with GSX and our software.
-
Here's the video of the flight: Check at 57.17 in the video and 1:03 and 1:20. Not sure if this will help.
-
same here massive blurries since buying and installing gsx2
Darcy
-
hello , same here blurries and NAV , LANDING lights problem with GSX L2
and excuse me , posting video says that everything is fine not solving the problem that we are all about ;D
-
I think I already replied with:
- Two videos, one showing NO BLURRIES and another one showing NO higher CPU utilization and NO difference with/without GSX installed.
- Offering some suggestion on what you might have setup wrong in your system that might cause this.
-
Did you guys go to the time stamps I replied with? You can't see the issues??
-
nothing wrong sir , i simply install GSXL2 nothing else and the problem shows up
also simply try to uninstall GSX the problem gone and every thing back normal
so the problem with GSXL2 , and alot face this problem
-
Did you guys go to the time stamps I replied with? You can't see the issues??
do you mean the external lights problem ?
-
nothing wrong sir , i simply install GSXL2 nothing else and the problem shows up
lso simply try to uninstall GSX the problem gone and every thing back normal so the problem with GSXL2 , and alot face this problem
No, the problem is NOT GSX, of course.
The problem is some setting that on YOUR system (and possibly other users as well that might have used the same setting), is causing an issue to your simulator, that can only be noticed if you installed GSX, that doesn't mean GSX is the cause. It's the victim of your setting instead.
As I've said, I already proved the problem is not GSX, since it clearly doesn't do that, on a simulator properly installed and maintained.
-
:o
My oh my ... and here I am going through all dll.xml and exe.xml and prepar3d.cfg files trying to find out why I suddenly suffer massive blurries all over the place and then I saw this thread!
Also very LONG reloading of scenery when you hit [Refresh Scenery]
The videos don't really help if it is a default plane on default scenery ~°~ and ALL of us could not have something wrong on our setup.
#justsaying
-
ok sir tell me what is the wrong with the setting in my system so i can modify to be good with GSXL2 ?
i just want a solution for the problem, if you can help
-
ok sir tell me what is the wrong with the setting in my system so i can modify to be good with GSXL2 ? i just want a solution for the problem, if you can help
Have you read my post ? I already offered some suggestions about what might be.
-
ok sir tell me what is the wrong with the setting in my system so i can modify to be good with GSXL2 ? i just want a solution for the problem, if you can help
Have you read my post ? I already offered some suggestions about what might be.
ya sir i did , but first i never install antivirus so its not an antivirus problem. second the problem shows only with GSXL2 , GSX before the expansion was very good and no problems with THE SAME SYSTEM SETTING , that is why we suspect of GSXL 2 , that is all
-
The videos don't really help if it is a default plane on default scenery
What difference it makes ? If GSX really "caused" this, it would cause it with every situation. That was a perfect before/after test, the only difference was GSX enabled or disabled and, of course, it didn't make any difference.
Here's the PMDG 747 at JFK, which has 147 SODE jetways.
SAME CPU utilization as with a default airplane on a default scenery, and even LESS GPU utilization!
-
everything is fine without GSX level 2..... so it is GSX, just admit it.... Everyone obviously is having texture problems and slow running with GSX level 2!! why is it that everyting in P3D V4.3 is okay then without GSX level 2? can you explain that? or are you just going to sit here and give people the same answer over and over again and not coming up with a solution.
-
And before someone says "That's easy, try it with GSX doing something"
Here's with GSX loading cargo AND passengers at the same time, at JFK, with the PMDG 747. You can't go any heavier than that!
-
or are you just going to sit here and give people the same answer over and over again and not coming up with a solution.
I'm not giving the "same answer", I'm giving EVIDENCE the problem doesn't happen, on a system which is properly installed and maintained.
-
or are you just going to sit here and give people the same answer over and over again and not coming up with a solution.
I'm not giving the "same answer", I'm giving EVIDENCE the problem doesn't happen, on a system which is properly installed and maintained.
+1
Always keep tabs of what you use, where they are and if needed, how to uninstall/install them.
-
i just did a full windows reinstall last week, mine is properly maintained. So can you explain to me then why everything is fine without GSX 2? OBVIOUSLY it has to do with GSX 2.... there is nothing else. If you have 10 people telling you the same thing, then it is true.
-
You can also find 10 people from the other side who will tell you everything is fine, so.
-
i just did a full windows reinstall last week, mine is properly maintained. So can you explain to me then why everything is fine without GSX 2? OBVIOUSLY it has to do with GSX 2....
OBVIOUSLY not. It only shows you and very few people, might have the same problem, not the CAUSE is GSX. How do you explain it doesn't do any of that on my system ?
-
I just ran into the same problem. I just bought GSXL2 yesterday.
I have a saved flight from Baltimore (KBWI) to Boston (KBOS) that I fly all the time because it is relatively short. I flew it last week with no problems. I was using it to test my new GSXL2 install. Everything is fine until I get past NYC and am about to start my descent. Everything on the ground turns into a dull wash of green. I made it to final approach and the airport looked like it was built with shadows. FSX completely crashed. I shutdown the computer and left for a while. When I got back, I tried the flight again. At approximately the same point in the flight, everything started getting blurry again. I just uninstalled L2 and was going to try the flight again, but I'm getting an error starting FSX now that is telling me to run the stand alone add on manager install. I came on here to download it, and spotted this thread.
I'll keep testing and see if I can get screen captures that show it.
To be clear, the problem does not show up on the ground at the start of the flight. It happens gradually throughout the flight.
-
To be clear, the problem does not show up on the ground at the start of the flight. It happens gradually throughout the flight.
Here's a video made by another user on Avsim, showing a 2-hour flight from FSDT KSDF to Flightbeam KMSP: the scenery is still sharp at the end of the flight:
https://www.avsim.com/forums/topic/541722-blurries-out-of-nowhere/?do=findComment&comment=3894594
Quoting:
FPS did not take a hit with GSX2. Everything was fine I thought with GSX2.
-
Umberto, To insinuate that your system is maintained better than those of your customer's is somewhat out of touch. Many of your most loyal customers are tech savvy too. As I've said before, I support your innovation. However, I do have trouble reconciling your demeanor at times. I'm sure you mean well, but you quickly become defensive... We are looking for a solution, not to place blame. There appears to be a common denominator in GSX.
As mentioned by another, I don't have issues sitting at the airport, so the videos you posted really don't help much. Please take the PMDG 747 to KSDF or KMEM, load a flightplan and capture a video of the flight. If your flight doesn't produce what many of us are experiencing your argument will have much more merit. Wouldn't you agree?
-
To insinuate that your system is maintained better than those of your customer's is somewhat out of touch
I only showed how it works here, so prove GSX DOES work. That doesn't imply anything else.
Many of your most loyal customers are tech savvy too.
And if they are, they'll surely start looking into their system to understand what's wrong, thanks to the useful hint I just gave them about showing how GSX CAN work.
I'm sure you mean well, but you quickly become defensive... We are looking for a solution, not to place blame.
That's precisely why I haven't limited to arguing. I haven't argued AT ALL. What I did was
1) Reliving users reports, which means taking the time to try, record a video and post it. If I was "defensive", I wouldn't do that, and would rely on arguing.
AND
2) Offering some ideas about the AffinityMask, for example. This becase, of course, I BELIEVED user's report, which discussed about high CPU utilization.
There appears to be a common denominator in GSX.
The common denominator might as well be:
- Some other software they have, and I don't
- Some settings they have, and I don't
- Some other software, even non flight-sim related they have, and I don't.
[qutoe]As mentioned by another, I don't have issues sitting at the airport, so the videos you posted really don't help much.[/quote]
Since you said it happens only after a while, I posted a link to a 2 HOURS video made by another user on Avsim, showing a 2-hour flight from FSDT KSDF to Flightbeam KMSP: with the scenery still sharp, even at the end of the flight.
-
Do you have a test plan for the products that you release? I mean, are the products tested by beta testers that in fact *do use* other softwares? Because it looked like you don't, and to me this is a huge issue, considering that 99% of the flight simulation community do use other softwares from other developers other than FSDT.
And yes, I'm having severe blurry issues after having to install the GSX update (which I would not otherwise, I don't even plan on buying the extension) in a rig that was running perfectly balanced before that.
-
I don't want to put my oar in where it is not wanted but:
I don't think Umberto is being given everything he needs. Everyone is mentioning CPU speed/capacity and GPU percentages but haven't mentioned their base Memory capacity and speed and usage (or often which version of FSX or P3d) they are using. (along with the complex scenery package they are using along the way).
I notice that the videos provided, show Memory usage at the airport of 11 Gb.
Some questions, observations:
Some people with issues may not have that much base memory? Does FSX handle that much memory? Is it a greater usage amount at an airport with GSX installed than GSX2? Once airborne, does more of GSX2 remain in memory leaving less space for developing scenery? If there then is a shortage of memory and does the CPU and GPU speed up to transfer scenery in and out?
Personally, when I start noticing the scenery development is not catching up, (If I have been X2 speeding up or flying high speed, low, over a nice scenery package) I just pause the P3D v4.3 and watch. Everything catches up in about 15 seconds and I am on my way again. I recognise it is a limit of the combined system I have. My memory chips are DDR3 at 2200 so I assume it is they that are my limiting factor.
My 2 cents worth. Not meaning to create offence.
Aussie
-
Do you have a test plan for the products that you release? I mean, are the products tested by beta testers that in fact *do use* other softwares?
Obviously YES. Some of our testers are very well known reviewers, that have installed all sort of add-ons (which they usually get for free), some of them are renowned hardware experts AND testers for other developers products too, so they routinely install beta and potentially unstable software together with our stuff.
-
Having exactly the same problem here - completely blurry scenery after around 30 minutes, specifically an ORBX area (Germany South) - but in fact textures on all scenery incl. airports and autogen don't load at all any more. The aircraft texture also doesn't load correctly. It's definitely something that happened after GSX level 2 was installed as I never had this problem prior to this.
-
A simple thing to try:
All GSX jetway textures (which are NOT loaded when you are flying, of course), are 4K. Maybe, depending on how many other addons you have installed, how high your settings are and how MUCH VRAM you have, you might be close to VRAM exhaustion.
So, you might just want to try lowering the maximum texture size to 1024x1024 ( the 3rd to last notch in the Max Texture Size slider in FSX ), and see if it improves things.
-
I'll try this (reducing texture size to 1024) but, to be honest, I was on 2048 before and never a problem. But I'll try anything as it's really annoying.
-
I ran the stand alone add on manager and was able to start FSX. GSX was not shown in the menu, couatl was still present.
The flight completed as usual no texture or performance abnormalities whatsoever.
I will reinstall GSXL2 and try again....
-
I ran the stand alone add on manager and was able to start FSX. GSX was not shown in the menu, couatl was still present.
You mean you Uninstalled GSX and reinstalled only the Stand-Alone Addon Manager ?
The flight completed as usual no texture or performance abnormalities whatsoever.
That at least confirm it's NOT the software modules that cause the problem because, when you install the Stand-Alone Addon Manager, both the Addon Manager and Couatl are loaded and in memory.
-
reduced to 1024 and still got blurries. tried the solution on avsim and still getting blurries. I may have to delete gsx now so I can fly again.
too bad. It looked good.
Darcy
-
reducing to 1024 textures hasn't helped.
I've noticed a few other things:
- when I click "restart couatl", it disappears from the add-ons menu and a blank dialogue box appears with no text. In other words, it doesn't restart. After that, I can't use SODE anymore either.
- the problem with textures disappearing and/or loading extremely slowly seems to be MUCH worse at dusk or at night - in other words, whenever lighting is involved.
By the way, my problems all happen when using the FSL Airbus (so far, I've only been using this plane with GSX L2).
Can anyone replicate these things?
Chris
-
That's funny, I did at least 5 flights using GSX2 whitout any problems with blurries, but today I'm also getting this problem.. Yesterday I've flown PMDG 777 and 737, FSL A320 and Ifly 737. All went fine, but this morning I load up a flight with FSL A320 and I get massive blurries and my autogen doesn't work anymore.. The only thing that's changed today was that this time I've departed from a airport that I changed about 15 jetways and land on an airport that GSX changed the default jetways. On yesterday flights I used airports with default SODE or without jetways.
Also, my FSL A320 is not working properly with GSX2. I start my flights on GPU and Air, as soon as I operate the jetway the GSX2 unplug my GPU and Air and leave me in the dark.. Very annoing! And It also doen't let me usig external air and AC anymore when the Jetway is connected.
-
when I click "restart couatl", it disappears from the add-ons menu and a blank dialogue box appears with no text. In other words, it doesn't restart. After that, I can't use SODE anymore either.
We DID had a restart problem upon release, but it's fixed now. Are you sure you are running the latest Live Update ?
the problem with textures disappearing and/or loading extremely slowly seems to be MUCH worse at dusk or at night - in other words, whenever lighting is involved.
The only thing in GSX that uses DL are the ground vehicles headlights, which are turned off when then don't move, to save even up to the last resource. The vehicles are of course fully destroyed when you fly away from the airport.
By the way, my problems all happen when using the FSL Airbus (so far, I've only been using this plane with GSX L2).
Have you tried another airplane ?
-
As english is not my first language i ll try to explain what the différence between my 2 flights
From paris to lyon, no problem at all. Made a stop at lyon 1h without stopping p3d, i use jennasoft lfllX and i replace all their jetways by gsxl2, a long work but the result is very nice.
So before start i request pushback , in the mean time i realise i forgot to remove jetway, in the gsx menu i can t ask it because the process of the push is started.so i request abort push, addon manager crash, ask me if i want to restart coualt ...yes and request push. All went good until i pass fl100, i had a long frame time were p3d don t answer, and after 30 min of flight cpu go to 100% all the ground became blurry until approach lfpg 26L, i stop p3d because it was not possible to land due to blurry airport.
I use the exact same setting since a long time, i don t like play with that. I wish i can help you and you can help me.
-
That's funny, I did at least 5 flights using GSX2 whitout any problems with blurries, but today I'm also getting this problem..
GSX hasn't changed in the meantime. Well, we just added a new small stair for the Dash-8, but that's it.
The only thing that's changed today was that this time I've departed from a airport that I changed about 15 jetways and land on an airport that GSX changed the default jetways. On yesterday flights I used airports with default SODE or without jetways.
This might well be an issue. If the combination of your scenery+airport+airplane+jetway+your settings, has exceeded the capabilities of your card (either memory or shaders, etc.), it might be possible the end result is blurries.
But it's not "GSX fault". You added GSX now, so you might think GSX is the "cause" but, it would probably happen just the same if you had GSX with a default airplane, then bought a memory-hungry airplane and got blurries.
Is the airplane "fault", only because it's the last thing you installed ? Obviously not, it's the *combination* of everything.
Also, my FSL A320 is not working properly with GSX2. I start my flights on GPU and Air, as soon as I operate the jetway the GSX2 unplug my GPU and Air and leave me in the dark.. Very annoing! And It also doen't let me usig external air and AC anymore when the Jetway is connected.
This is a bug that FS Labs has confirmed is in the part of their code that interacts with GSX and they will fix it.
-
How do you get gsx to load cargo and the passengers at the same time? I want to turn this on as well.
That's how GSX always worked since it has been release. There's nothing special to do. Boarding/Deboarding is a single process, which loads Cargo and Passenger at the same time.
-
How do you get gsx to load cargo and the passengers at the same time? I want to turn this on as well.
That's how GSX always worked since it has been release. There's nothing special to do. Boarding/Deboarding is a single process, which loads Cargo and Passenger at the same time.
OO ok Its just that when the plane is boarding it loads passengers first (cargo truck sitting on other side of plane but takes off somewhere in the airport) then when passenger loading is finished the cargo tuck comes back and load the cargo on after that. Was think you could load the cargo and the people at the same time (or maybe the cargo truck is not ment to take off and leave the plane site and needs configured). Using q400 at nzns airport
-
OO ok Its just that when the plane is boarding it loads passengers first (cargo sitting on other side of plane but takes off somewhere in the airport) then when that is finished the cargo tuck comes back and load the cargo on after that. Was think you could load the cargo and the people at the same time.
As I've said, the cargo IS loaded together with passengers.
But in boarding, the carts are coming from far away and if the airport is not well designed and doesn't have vehicle parking spots close to the terminals or (even worse) lacks vehicle paths, the carts that are arriving might take longer than the passenger take to board, giving you the impression it's a sequential process, when it's not.
But now that we have passengers, which will usually take longer than the old simulated process, it less likely the cargo carts will arrive when boarding is already finished, so they will appear as running together.
-
Arr ok ill do some goggling and see how to edit the path's at the airport.
-
About blurries, I know it's a long shot but, could you please try this:
- Go to this place
"Documents\Prepar3d v4 Add-ons\Fsdreamteam Exclude"
And replace the add-on.xml there, with the one attached.
This file assume you installed GSX into the default folder C:\Program Files (x86)\Addon Manager. If not, please edit the <Path> line in this xml to show the correct path of our installation.
-
???
POSSIBLE SOLUTION
I've just done a flight from EHAM (FlyTampa) to EGCC (UK2000) and had no blurries.
What I've done is the following:
1. Delete all files in c:\ProgramData\Lockheed Martin\Prepar3D v4\SceneryIndexes_x64\ and let P3D write new ones
2. Delete shaders in \AppData\Local\Lockheed Martin\Prepar3D v4\Shaders\ and let P3D write new ones
My rig:
i7 7700 @4.2 with 32GB DDR4 and GTX1080Ti on Win10x64 and a 4K monitor
P3D4.3 with EZDOK, ASP4, ProATC, AivlaSoft EFBv2 and almost everything from ORBX
Reshade and TomatoShade+Reflections
The following tweaks are in prepar3d.cfg
[DISPLAY]
TEXTURE_BANDWIDTH_MULT=120
TextureMaxLoad=6
[SCENERY]
MaxRegionsPurgePerFrame=1
[MAIN]
FIBER_FRAME_TIME_FRACTION=0.11
[TERRAIN]
TEXTURE_SIZE_EXP=9
Forget the tweaks, and just try the first two suggestions and post your findings.
Maybe it helps for someone. Will fly again tomorrow and see what temperamental PeeThreeDee is coming up with because you never know.
Good luck
Terblanche
-
All I did was delete that folder SceneryIndexes_X64 and that did the trick. Everything else is not relevant. I wonder if that had something to do with the exclude file?
-
I deleted scenery 64 folder and still get blurries.
-
I don't want to put my oar in where it is not wanted but:
I don't think Umberto is being given everything he needs. Everyone is mentioning CPU speed/capacity and GPU percentages but haven't mentioned their base Memory capacity and speed and usage (or often which version of FSX or P3d) they are using. (along with the complex scenery package they are using along the way).
I notice that the videos provided, show Memory usage at the airport of 11 Gb.
Some questions, observations:
Some people with issues may not have that much base memory? Does FSX handle that much memory? Is it a greater usage amount at an airport with GSX installed than GSX2? Once airborne, does more of GSX2 remain in memory leaving less space for developing scenery? If there then is a shortage of memory and does the CPU and GPU speed up to transfer scenery in and out?
Personally, when I start noticing the scenery development is not catching up, (If I have been X2 speeding up or flying high speed, low, over a nice scenery package) I just pause the P3D v4.3 and watch. Everything catches up in about 15 seconds and I am on my way again. I recognise it is a limit of the combined system I have. My memory chips are DDR3 at 2200 so I assume it is they that are my limiting factor.
My 2 cents worth. Not meaning to create offence.
Aussie
Windows 10 Pro, Prepar3D V 4.3
ASUS X99-DELUXE II; Intel i7-6900K CPU @ 3.20GHz, 32GB Corsair DDR4-2133 RAM, NVIDIA GeForce GTX 1080, 2X LG Ultra HD (GSM5B09) 27" 4K Monitors
I still experience the problem.
-
Confirmed, same problem here with all my 8 cores to max
-
Like allways, like a just released product, there must be a bug around. I managed to get the 2 jetways that im installed in my Heavy Gate at my base Airport. Very eyecandy!!! Loved, but all cores went to 100%.
-
Like allways, like a just released product, there must be a bug around. I managed to get the 2 jetways that im installed in my Heavy Gate at my base Airport. Very eyecandy!!! Loved, but all cores went to 100%.
I did restarted Quatle and is fine now. Indeed is a bug, just a bit of revision still needed. Remember that every system is different even with same hardware. I have to for now, I will be following the thread, since when i fly i 95% of time i will use GSX while preparing the FMC and stuff ;)
-
About blurries, I know it's a long shot but, could you please try this:
- Go to this place
"Documents\Prepar3d v4 Add-ons\Fsdreamteam Exclude"
And replace the add-on.xml there, with the one attached.
This file assume you installed GSX into the default folder C:\Program Files (x86)\Addon Manager. If not, please edit the <Path> line in this xml to show the correct path of our installation.
I did and saw no different outcome. All cores of CPU hogged to their maximum capacity building up the blurries over a few minutes.
-
Might not be the same, I still post it here: I do not have increased amount of blurries, but when I first changed the first jetway in LSZH, my sim crashed suddenly without any error message. Since then, the texture loading is extremely reduced in performance. Means: while looking around or switching view points, it takes forever to load the textures correctly. Some AI planes and scenery buildings as well as the GSX vehicles remain black for several seconds. It was not like this before GSX Level 2. I could switch views and it took only 1-2 seconds for the textures to load, the GSX vehicles even loaded instantly.
It seems that GSX Level 2 somehow corrupted things. I will certainly try this shaders "trick", might also have an influence on my issues.
-
If I were the developer(s) I would take a look at the .DLLs and the likes. There must be a routine that is hogging the whole thing.
Anyone knows if there is a tool that shows the internal components of a running executable file? The idea is seeing the resources being consumed by the various linked components, such as Couatl, Bglmanx, Pmdghud, Trueglass, Reallight, Sode, etc, well, you know what I mean, right?
-
Please stop saying there's a bug in GSX, in Couatl, or something like that.
TWO users already reported the problem was fixed for them by refreshing the shader cache and the scenery indexes.
We don't modify any of them so, clearly, they were already messed up with something else, and installing GSX might just have made the problem (which they already had), just more obvious, but it wasn't the cause.
If GSX was the cause (it's not), it couldn't explain that:
1) I cannot replicate any blurries and any higher than normal CPU utilization, as seen in the various videos I posted, including one from another user on Avsim, arriving at destination after a 2 hour flight with no blurries at all.
AND
2) Some users reported the blurries were gone by refreshing the shader cache and the scenery indexes. If GSX were the cause, this wouldn't be possible.
The *simulator*, of course, will generate such files automatically, when new kind of objects are used for the first time, and when a new scenery is installed. The only scenery we install with GSX 2, is the empty Exclude folder, THAT'S why I suggested trying to use a different add-on.xml, but I don't really think this is the problem.
The simulator might have also added new shaders, when it found materials added by our newly installed Jetways. That's nothing we have any control over it, it's all done automatically but, sometimes the shader cache folder might end up corrupted, so it needs refreshing.
AND, if you have 3rd party shader utilities, like PTA or Tomato Shader, this will result in DIFFERENT shaders being created, because they modified the original shaders. The shaders in the ProgramData folder are binary representation of the source files under the Prepar3d\ShaderHLSL folder, and there might be MANY of them, since for each source, the simulator can create different variations depending how it's used in the various objects found in the sim.
I have 1703 shaders in my shader cache, but every use will have a different number, because it depends how many object you have seen in the simulator. Yes, when creating shaders, it's understandable the CPU utilization might be higher, and the scenery might look bad.
Maybe your shaders folder has grown up too large ? Maybe your hard drive is a bit slow in writing for some reason ? Maybe your ANTIVIRUS is slowing down reading/writing the shader cache ?
We had users reporting the GSX airport cache regeneration took "minutes" on their system, while it shouldn't take more than 10-20 seconds for a full regeneration, and 1-2 for a refresh after installing a single scenery. This WAS caused by Windows Defender, that tried to scan every single .BGL, just in case it might contain a virus, and excluding all the simulator folder from scanning resulted in a 10x decrease in time for these users. And of course, while doing this, the CPU utilization gets higher.
Could be the same is happening to your shader cache ? The simulator is doing its usual work of creating new shaders (because there are new objects installed by GSX), but is taking much longer than normal because of the antivirus (or because your shader folder has become too large), so you see high CPU utilization and blurries, and put the blame on GSX, when there's clearly nothing wrong with it ?
-
We DID had a restart problem upon release, but it's fixed now. Are you sure you are running the latest Live Update ?
Yes, all updated using Live Update.
The only thing in GSX that uses DL are the ground vehicles headlights, which are turned off when then don't move, to save even up to the last resource. The vehicles are of course fully destroyed when you fly away from the airport.
ok..
Have you tried another airplane ?
Not yet, but I will. Maybe it's something to do with the FSL (though I doubt everyone having this problem is using the FSL airbus). I also use Tomatoshade. Perhaps this is a factor.
-
Hi,
Exactly the same problem for me after 35 - 40 minutes after take-off blurry everywhere. Now I'm trying without L2 (desactivate and reinstalled) and jetway default to see if it works correctly.
Christian
-
Exactly the same problem for me after 35 - 40 minutes after take-off blurry everywhere.
This is when GSX is not doing anything, and has already removed all its created jetways and objects. It did about 3NM outside the departure airport.
Now I'm trying without L2 (desactivate and reinstalled) and jetway default to see if it works correctly.
Have you tried, instead, the solution suggested here, which fixed the problem for at least two users that did that ?
http://www.fsdreamteam.com/forum/index.php/topic,18564.msg129078.html#msg129078
-
Hi Virtuali,
Yes I did so I know it's not GSX but I want to fly and for me it's not compatible with my other product in some way so I turn back where all works perfectly all together.
Christian
-
Yes I did so I know it's not GSX but I want to fly and for me it's not compatible with my other product in some way so I turn back where all works perfectly all together.
If you still didn't had the "other product" (we don't know what it is in your case) which is causing this in combination with GSX, we can safely assume the problem didn't happen so, you would just bought GSX L2 without noticing anything.
Now, assume you buy/install this "other product" AFTER GSX. The problem starts to appear. Who's to blame then ?
This entire concept the last product installed is always the one that is at fault and must "fix" something, it's just wrong. What if there's just nothing we can do, if you run with too many addons, with some of them not compatible with each other ?
That's the nature of the flight simulation market, with hundreds/thousands of addon that no developer can even had any chance to test, in millions of different combinations if you also include hardware, software and OS combinations.
THAT'S why we offer a Trial version of everything since the beginning of time. Because there's no way we can guarantee with absolute certainty you will not have any problems, under any possible combination of addons and software/hardware combination.
Nobody better than you can test the product on your system before purchasing. There's no time limitation, you have all the time you want to be sure it works.
Offering a Trial version costs us money, both in bandwidth consumption and in maintaining an activation server and in offering unlimited downloads freely available with no registration and no time expiration. Use it to your own advantage, to be sure it works in your own unique installation.
-
Hi Virtuali,
No problem I understand. I just tested same flight without L2. No blurries after 35m so for me it's the solution for now.
I bought L2 and I assume no other product was installed in between...but I don't want testing anymore so maybe one day it will work all together for me too and at this moment I will reactivate L2 for now it's working perfectly with GSX without L2 and I don't blame you. It is just an observation and as I said I assume.
Regards,
Christian
-
So far, so good - did another flight from EGCC (UK2000) to LOWW (FlyTampa) and although there were no blurries, the autogen loads really, REALLY slow and it's only after descending through 7000" and getting airspeed to 200 ktns that the autogen started to pop up like a popcorn show. Now, I'm not saying it is GSX's 'fault' but it sure is GSX having an argument with something in P3D because ever since installing GSXv2 if you hit [Refresh Scenery] you can walk the dog, take a shower, prepare dinner and come back just in time to see it load through 80% ...
BUT as I said - after deleting the SceneryIndexes_x64 and Shaders [http://www.fsdreamteam.com/forum/index.php/topic,18564.msg129078.html#msg129078] it seems to have fix the ocean of blurries. Something, somewhere, somehow has a conflict with GSX and here is the point Umberto - you are correct to say that it's not the engine that makes a car drives off the road and the driver should check its wheels but if the engine delivers too much / too little torque then the driver will find it difficult to stay on the road - OR- if GSX remains active and priority in the background then P3D will first feed GSX's need before providing for the autogen's expectations. #justmytwosents
;)
-
if GSX remains active and priority in the background then P3D will first feed GSX's need before providing for the autogen's expectations.
GSX does NOT remain active in flight! With a recent update, it simply stop doing anything, even checking for nearby airports, if you are flying over 10K feet and/or faster than 250 kts.
The only thing it does, in that situation, is checking your altitude and speed, in case you go below 10K feet, so it's time to start checking nearby airports again. But I REFUSE to think asking for 2 variables each 4 seconds (that's the lowest priority you can ask to Simconnect) can cause issues to the simulator, when something like FSUIPC, for example, is asking for *hundreds* of variables at time!
-
Hi,
I'd like to uninstall GSX, try some of the solutions, test and reinstall. Do I uninstall GSX through the control panel or is there another method?
Also, should I uninstall the addon manager and if so, what is the process for that? FYI, I do have most of the FSDT airports and I don't really want to uninstall those. I just want to clean out GSX and reinstall it.
Thanks!
-
Hi,
I'd like to uninstall GSX, try some of the solutions, test and reinstall. Do I uninstall GSX through the control panel or is there another method?
Also, should I uninstall the addon manager and if so, what is the process for that? FYI, I do have most of the FSDT airports and I don't really want to uninstall those. I just want to clean out GSX and reinstall it.
Thanks!
Just disable the load of Couatl in the config file;-)
-
Hi,
Just for information I notice an error call: bglmanx64.dll when blurries occurs and I stop the flight and exit p3v4.
Maybe a clue.
Christian
-
Hi,
I'd like to uninstall GSX, try some of the solutions, test and reinstall. Do I uninstall GSX through the control panel or is there another method?
Also, should I uninstall the addon manager and if so, what is the process for that? FYI, I do have most of the FSDT airports and I don't really want to uninstall those. I just want to clean out GSX and reinstall it.
Thanks!
Me too. Steps please. Need to delete latest v2 and go back to working copy of GSX, so I can fly again.
Thanks
-
Just for information I notice an error call: bglmanx64.dll when blurries occurs and I stop the flight and exit p3v4.
Does the simulator continue to work, if you don't close it ?
-
Yes, I don't receive this error inside P3D but when I check in windows event log after I stop the flight and exit P3D:
Nom de l’application défaillante Prepar3D.exe, version : 4.3.29.25520, horodatage : 0x5b2c3263
Nom du module défaillant : bglmanx64.dll_unloaded, version : 4.5.0.6, horodatage : 0x5b8ebdee
Code d’exception : 0xc0000005
Décalage d’erreur : 0x000000000002d9f0
ID du processus défaillant : 0x1ec8
Heure de début de l’application défaillante : 0x01d44912392d8bc2
Chemin d’accès de l’application défaillante : D:\P3D\Prepar3D.exe
Chemin d’accès du module défaillant: bglmanx64.dll
ID de rapport : 6309f535-ab90-48f3-9860-a7fbf0ec183c
Nom complet du package défaillant :
ID de l’application relative au package défaillant :
Each time I get these blurries I get this error in windows log.
Christian
-
Yes, I don't receive this error inside P3D but when I check in windows event log after I stop the flight and exit P3D
Do you use Windows 7 perhaps ? If yes, try to check the "Disable RTT" option in the Addon Manager. You'll lose the Jetway numbers, but it might work better.
-
No windows last update : Windows 10 pro, version 1803
-
Try it anyway. We know there's something in Windows 7 DirectX that caused a crash on exit (only) but, perhaps it might happen in Windows 10, depending on driver settings. That option was added a while ago to side step this.
-
Hi,
Just for information I notice an error call: bglmanx64.dll when blurries occurs and I stop the flight and exit p3v4.
Maybe a clue.
Christian
Thanks. Which cfg file?
-
OK I will try again the flight with this option on and L2 and give you feedback.
-
Folks, it have nothing to do with GSX2, I got blurries before I have purchase GSX2. Something else is triggering this :-\ but what??
-
Yes, I don't receive this error inside P3D but when I check in windows event log after I stop the flight and exit P3D
Do you use Windows 7 perhaps ? If yes, try to check the "Disable RTT" option in the Addon Manager. You'll lose the Jetway numbers, but it might work better.
I often (but not always) get the silent bglmanx unloaded crash on exit, which only shows up in the event viewer. This predates GSX L2. It is most likely to happen if I have departed or landed at an FSDT airport, or have used GSX services at a non-FSDT airport at some point during a flight.
I can see it happen in real time if I monitor the shutdown of P3D and its child processes using MS Process explorer. Ordinarily I see couatl and SODE running under P3D.exe, along with the Active Sky sounds process.
On a normal shutdown, after exiting P3D, the main P3D desktop window disappears first, but its icon on the taskbar remains highlighted for a few seconds. Then both couatl and SODE shutdown at the same time, and the P3D taskbar icon becomes inactive at the same moment. The P3D process keeps running for about 10 to 15 seconds, then shuts down. The Active Sky process is always the last to end, and only after P3D has terminated.
The scenario when I have the bglmanx error is similar, except when P3D.exe terminates, there will be a WER Fault attached to the process as it exits, and I know that if I go to the event viewer later, I will see the bglmanx unloaded error with a C000005 fault.
I will definitely try disabling the RTT option on my next flight to see if it makes a difference. I had the bglmanx unloaded silent crash in Win 7, and still have it since upgrading to Win 10 Pro 1803
As far as “blurries”, I have seen none so far. I just completed a flight from KELM to FSDT KCLT with intense Active Sky cloud cover (in multiple layers) throughout the flight, and a low 500 foot ceiling on the ILS 36R approach at CLT. When I finally broke out of the overcast, the airport and surrounding terrain were fully rendered. I did have a few stutters in the last segment of the approach, but that is typical in my installation if I use the the HD landing lights on the CRJ with heavy cloud conditions near the ground.
I used full GSX services before departure as well.
-
Folks, it have nothing to do with GSX2, I got blurries before I have purchase GSX2. Something else is triggering this :-\ but what??
I'm afraid I can't agree in my case. The blurries (and complete lack of loading of entire scenery areas, such as Orbx Germany South) started immediately after I installed GSX2.
Someone in a Facebook group mentioned that it only happened to him using the FSL bus. When using other aircraft, he said the blurries didn't appear. I haven't got round to testing with another a/c yet but if that's the case, it's perhaps some kind of incompatibility with the FSL Airbus.
This is certainly a mysterious case...
-
Yup same here, and we keep getting told “its not gsx” ..... if i start a flight and dont use GSX everything is fine, as soon as i start using anything from GSX, jetways, pushback etc, scenery goes blurry and no autogen loads anymore after i leave the airport area... i have an I7 7700K @4.6 ghz with GTX 1080 and i was using a default airport...
My issue is most notable after departure, cruise flight and then ground textures get blurry (not clouds though), but CPU pegs at 100% for the Prepar3d.exe process on all cores it is using. Can't say I've ever seen that before. So, that may be the problem and the symptom is the blurry textures. Once on the ground again, within about 5 minutes textures display again albeit rendering very slowly.
Jeffrey S. Bryner
This PRECISELY describes my issue.
-
Try it anyway. We know there's something in Windows 7 DirectX that caused a crash on exit (only) but, perhaps it might happen in Windows 10, depending on driver settings. That option was added a while ago to side step this.
Feedback: option RTT is ON but I have the same problem - blurries after 40 minutes getting worse and worse so I stop the simulator and the error bglmanx64.dll is here again in the windows event log.
Christian
-
I ran the stand alone add on manager and was able to start FSX. GSX was not shown in the menu, couatl was still present.
You mean you Uninstalled GSX and reinstalled only the Stand-Alone Addon Manager ?
The flight completed as usual no texture or performance abnormalities whatsoever.
That at least confirm it's NOT the software modules that cause the problem because, when you install the Stand-Alone Addon Manager, both the Addon Manager and Couatl are loaded and in memory.
When I uninstalled GSXL2, I saw a message stating that all other products that used it would not function or something like that, so I chose the option to leave the addon manager installed. When I tried to run FSX, I got an error saying that there was something wrong with the addon manager and to run live update, which I did. FSX would then start. I agree that this means the SW modules are fine. They did not interfere with the flight.
Attached images: 20180909174832_1.jpg - mid flight GSXL2 not installed
20180909180916_1.jpg - KBOS 4L approach GSXL2 not installed
20180910130746_1.jpg - mid flight GSXL2 installed - NOTE: I snapped this one as the problem started. Note the clear line in the scenery when the blurries first start.
20180910132949_1.jpg - KBOS 4L approach GSXL2 installed
GSX should not be consuming many resources when I am in the air, but it appears as though it might be doing something at the airports I am flying by.
-
I concur, GSX Messed up something. It only occurs once on approach into an area around 25000 ft or so. Had my sim crash into Sydney and now also into HKG on the return leg...
Umberto, your stubborn animosity to our issues is a really bad response to an issue several customers are experiencing, I had none of these issues before and I think its related to the XML thing your GSX creates.
-
Win10 / P3Dv4.3 / GSX Level 2 / FSL A319
I have exactly the same issue, did LSZH-LEAM yesterday, about 1 hour into the flight i hear my AP disconnecting. FPS dropped down to single digits, my plane starts to behave like a drunken parrot and the scenery suddenly became blurry. The FPS issues went away eventually, but the blurries remained. Those werent the "standard blurries" that happen when P3D cant catch up with texture loading, as those blurries disappear after a while when pausing the sim. In this case the blurries remained and never got replaced by sharp textures. I had to restart my sim to get rid of the issue.
My system can handle P3D very well and i havent seen any blurries since its 64bit, and apart from buying and installing GSX L2, i didnt change anything on my sim recently.
-
Well I tried with the PMDG 737 and still get the issues so not just a FSL issue.
-
Yes sounds like my issue. That's exactly what I was thinking: it's not the normal blurriness that can occur when there's a lag in loading textures (although I never had this before installing GSX2). Even when pausing the sim, they don't load. There is definitely something fishy going on.
The common denominator here is GSX2 (or something the Live Update loads into the system).
-
EXACTLY! of course its GSX 2.... smh its nothing else on my sim, when i uninstall it, the sim is back to normal so how are they going to sit here and say its not GSX...
-
Hating to have to pile on here... I have powerful rig built for me by Jetline Systems to run Ifly 737 Cockpit Builders addition in P3d4.3 Have been getting superb performance out of this rig until I installed GSX 2. Massive blurries. Happened to me last night flying from KSDF to KDCA. Noticed the ground was washed out about half way thru flight. Arrived in DC to find a blacked outlined KDCA and washed out terrain. Tried the methods, mentioned by a couple other simmers, to fix, but no luck for me.
I installed a complete backed up copy of my computer system, to get rid of any GSX 2 and things for me are running normal again.
I hope this mystery is solved sooner rather than later.
Robert
-
Again, that is exactly what I have experienced.
I am sure the developer is trying to work out what the problem is. I guess we will have to be patient. It's frustrating, but it isn't the first time us flight simmers have had problems with add-ons I guess.
-
Can now confirm. I can fly with no blurries and cpu does not max out after deleting GSX 2. I would at least like to have the orginal GSX back so I can that working until someone comes up with a fix for this. Anyone know where I can get the GSX version prior to 2.5.0.5? I miss it already.
Thanks,
-
I have the same problem...
-
Today is a new day, so i will try and see whats going on :)
-
Tried to delete the shaders, tried the sceneries indexes.. Still get blurries at about 30 minutes in flight! I'm using FSL A320, now I'll try with another plane ans see what happens.
-
You do not need to uninstall or delete GSXL2.
Go into the add-on manager, highlight GSX Level 2, and then hit deactivate. This will put you back to using plain old GSX.
After I did this, I was able to fly that flight just fine. No blurries. Full "original" GSX functionality.
-
You do not need to uninstall or delete GSXL2.
Go into the add-on manager, highlight GSX Level 2, and then hit deactivate. This will put you back to using plain old GSX.
After I did this, I was able to fly that flight just fine. No blurries. Full "original" GSX functionality.
Will give this a try. reinstalling now :)
-
Sorry to say that I too just had this problem. I flew a flight earlier today to FSDT KCLT with no issues - there was heavy cloud cover the entire way, so I’m not sure if things went bad in terms of ground depiction or not, but when I broke out of the overcast on approach, the terrain and airport was fine. On that flight, I used full GSX services at departure and arrival.
However, I just flew a flight from KELM to KDTW and experienced exactly what everyone else has been describing. The only GSX service I used for this flight was pushback.
Here’s the thing: I have been a tester for the Aerosoft CRJ for quite some time, and I have flown this exact flight at LEAST 150 times over the past year while testing that aircraft.
It is my standard test scenario for any new aircraft I fly because it takes less than one hour to accomplish, and I know from experience it does not present a heavy graphics load that might skew test results. Much of the route is over water, traversing Lake Erie.
i know this flight like the back of my hand, and am very familiar with exactly how my system responds using a variety of complex add-on aircraft.
I have flown this same flight with default clear weather, and with r/w Active Sky weather ranging from fair skies to heavy storms. In all that time, I have never had any issue with graphics or frame rates.
I flew this exact flight 3 times last week with the MaddogX with no problems, prior to installing L2.
I have always had “original” GSX on this computer - using it mainly for the pushback function.
Today I flew the same flight plan as always: KELM HERBA YQO.SPICA2, FL 280, with a planned landing on runway 21L. No weather injection - just default clear skies.
During descent, I began to notice the terrain textures becoming increasingly blurry. By the time I crossed Lake St. Clair descending below 10,000 feet, the terrain tiles on both sides of the lake and the city of Detroit were just featureless green haze. I could see the (default) KDTW airport at about 11 o’clock, and it was a black square.
I have a liquid CPU cooling system, and heard the heat exchanger fans kick into high speed (which is unusual), and noted that all 4 cores were showing between 80 and 85C on my taskbar CPU temperature display.
In the 2 years I have owned this computer, I have NEVER had CPU temps that high! Not one single time. The warmest I have ever seen before was about 65C while flying the FSL A319 on an approach into Aerosoft EGLL, and that was on a hot day in July when the temperature in my computer room was about 30C.
I assume that all 4 cores were saturated at close to 100 percent load, though I did not check.
On final approach, the airport remained a black square, with only the runway VASI lights visible. At about 300 feet AGL, the airport graphics finally loaded, piece by piece -enough to land successfully.
As I taxied in to gate A61 at the terminal, the surrounding terrain resolution got better and better, and my CPU temps started to decrease back to a more normal range, but they were still on the warm side.
I have a well-optimized system, with 16GB system RAM, and a GT 1080 Ti GPU with 11GB VRAM. Running P3D 4.3 on Windows 10 Pro 1803.
I have added nothing new to this system recently. I run with antivirus disabled when flying. As a Windows 10 Pro user, I have disabled mandatory Windows updates.
I have ORBX Global Textures, NA Landclass and Vector, just as I have had with every flight I have made over the past year. I own multiple high-end airports by FSDT, PacSim, Fly Tampa and Flightbeam.
I have had no performance problems or graphics issues whatsoever, running the Aerosoft CRJ, Leonardo MaddogX, PMDG 737/747/777 and FSL A319 and A320. I almost always run with Active Sky weather, and typically fly 5 or 6 times per week.
The strange thing is that I have flown three previous flights (to KATL, KPHL and KCLT) since installing L2 with no issues, but things truly “went to hell” on this last flight, (between two default airports) with no weather injection — and the symptoms mirror exactly what multiple other users are reporting.
By the way, it has long been my practice to run the FSDT Updater, and to clear the scenery index folder before loading P3D to begin a flight, and I did so today before this latest one that went wrong.
I will clear the shader cache as well before my next flight.
-
Okay wierd, I reinstall and deactivated but going to CYEG I still get the SODE jetways and it is acting like I have the full version even though I deactivated GSX 2? Went to CYQR and still noticed the gate numbers and different jetways there as well. It says trial version but it is not supposed to work at these airports. I have not flown yet to see if I get the blurries but just wanted to note this.
-
Did another flight like yesterday lyon to paris with the new a321 aerosoft pro, same problem with blurry texture, yesterday it was the fsl a320. I had this problem the fps were at 60-100, i set in p3d fps to 60 instead unlimited. No difference.
-
deactivated GSX 2 and it still works like I have it activated. Tried at CYEG, CYQR, CYVR. Sode gateways and loading people.
I wonder if this has anything to do with the issue?
-
deactivated GSX 2 and it still works like I have it activated. Tried at CYEG, CYQR, CYVR. Sode gateways and loading people.
I wonder if this has anything to do with the issue?
Did you edit the exclude .bgl thing accordingly with FSDT GSX Control Panel?
-
deactivated GSX 2 and it still works like I have it activated. Tried at CYEG, CYQR, CYVR. Sode gateways and loading people.
I wonder if this has anything to do with the issue?
Did you edit the exclude .bgl thing accordingly with FSDT GSX Control Panel?
Not sure what you are talking about??
-
deactivated GSX 2 and it still works like I have it activated. Tried at CYEG, CYQR, CYVR. Sode gateways and loading people.
I wonder if this has anything to do with the issue?
Did you edit the exclude .bgl thing accordingly with FSDT GSX Control Panel?
Not sure what you are talking about??
My mistake. I apologise.
[/quote]
-
At this point, I think FSDT needs to provide detailed instructions on how to restore our systems to the exact state they were before we installed GSXL2. If it means I can't use GSX at all or it means that I can't use any of my FSDT airports, fine. I just want things back to where they were before I installed this. I'm not asking for a refund - I'm sure this will get worked out. I just want to be able to use my system while the smart people figure this out.
-
I wish they would have kept the GSX installers separate.
-
Today is a new day, so i will try and see whats going on :)
Like I said I made a flight.
Ifly 737-900 KLM from LOWI to LFKJ Ajaccio-Napoleón Bonaparte (In Corcega Island). After configuring GSX for the plane. Initiated all the GSX refuel, catering and boarding. It went 90% flawles, only for some moments it made the CPUS 100% an FPS went to 10, but it went away and got normal. Wondered why the vehicles came by the grass LOL!!!. ;D I hope Virtualli take time to check the program for those weird bugs.
I7 7700k 32GB Ram Nvidia 1080.
https://www.facebook.com/media/set/?set=a.10161000182735089&type=1&l=a6d6f2f471
-
Deactivating GSX v2 within the Addon Manager does not work, actually mine is not even activated, because I didn't buy it! So this is not an option.
What FSDT really has to do is implement a functionality to revert to GSX v1 for the ones who don't wish to upgrade, simple as that.
-
Sadly I too have the blurry issue/maxed CPU and it just started after installing Level 2. I would also be interested in knowing how to go back to the original version of GSX while Level 2 gets sorted out.
I will try the deleted shaders tomorrow and see what happens.
-
sorry for bad english
After I removed GSX Level 2 from the Addon manager, I activated the original GSX's .key file. the problem is resolved.
please find a solution to this GSX Level 2 problem
-
Well i dont have that issue. I use GSX2, also simmilar tweaks, PTA for shaders, and believe me, as max settings as i can force the system to...
I7 6700k GTX1070 32GB RAM, and all addons you can imagine...REX SKF, ASP4,(All from FSDT - OF-CO-UR-SE 8) ).... and no blurries issues...
If you use P3DV4, try clicking "Delete Generated Files" inside P3DV4 root folder, and restart. I would save everything in Program data(Scenery.CFG) and APP data folders before(Exe.xml, dll.xml)...
It is interesting that issue came after the product install though ??? ... Im scratching my head about how GSX could have interfere with blurries. Its a Dev-Coding thing may be? But if even unistalling is not returning to original state, well....
If doing this "Delete Generated Files" procedure solved your problem dont forget to share... ;)
-
Folks, it have nothing to do with GSX2, I got blurries before I have purchase GSX2. Something else is triggering this :-\ but what??
Exactly. Here's some threads on LM forum about "the Blurries", started months or even years ago, when nobody had GSX Level 2:
https://www.prepar3d.com/forum/viewtopic.php?f=6314&t=127074
https://www.prepar3d.com/forum/viewtopic.php?t=126401
https://www.prepar3d.com/forum/viewtopic.php?t=120394
http://www.prepar3d.com/forum/viewtopic.php?t=119640
https://www.prepar3d.com/forum/viewtopic.php?t=130169
http://www.prepar3d.com/forum/viewtopic.php?t=113284
http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=95338
I'm stopping here, since searching for "Blurries" on P3D forum, returns with more than 400 hits on Google...
-
Deleting the shaders did some good in my case, but I start to see what is going on here (in my case): I had a really fine tuned P3D before I installed GSX Level 2 and this addon now simply added exactly that amount of load that some issues appeared (returned?). The delayed texture loading is still more prominent that it was before, but come on, now I am at the Terminal A of LSZH with 16 SODE Gates instead of the 16 default gates, of course there is more load on my sim.
BTW: I did not delete the SceneryIndexes64 folder content, as inside this folder, only two files were changed on the day I installed GSX Level 2. Hardly possible that those two files did anything.
Regards
Chris
-
Umberto, your stubborn animosity to our issues is a really bad response to an issue several customers are experiencing, I had none of these issues before and I think its related to the XML thing your GSX creates.
How you can possibly use that derogatory "stubborn animosity" term, when I ALREADY suggested, several post ago, a solution to change the XML file, to see if THAT might be the problem ?
Have you tried it ?
And the result ?
Why you cannot understand the very simple fact that, unless I can reproduce it, and I can't, like several other users that ALSO posted here, I can only GUESS and have you affected TRY things that MIGHT help ?
Have you tried to check "Disable RTT" in the Addon Manager ? The Result ?
-
BTW: I did not delete the SceneryIndexes64 folder content, as inside this folder, only two files were changed on the day I installed GSX Level 2. Hardly possible that those two files did anything.
Another user posted this:
http://www.fsdreamteam.com/forum/index.php/topic,18564.msg129081.html#msg129081
All I did was delete that folder SceneryIndexes_X64 and that did the trick. Everything else is not relevant. I wonder if that had something to do with the exclude file?
-
And, it would be best if you tried the solution I suggested, which are the ONLY two things they might be somewhat different compared to the previous version of GSX. The new add-on.xml for the Exclude area, which might be changed like this:
http://www.fsdreamteam.com/forum/index.php/topic,18564.msg129077.html#msg129077
The "Disable RTT" texture option in the Addon Manager. This has something to do with rendering textures and, while we had this since several months, it was unused until Level 2, and it uses to draw jetway numbers in DirectX.
If you enable this (AND RESTART THE SIMULATOR), in addition to the XML change I suggested before, GSX will work *exactly* like before, with the only difference it's just drawing some new jetways, with bigger textures than default ones.
-
I had the issue with the 100% CPU load as well.
Reset all Gates to default and unload GSX 2
Run Live Update again, register GSX 2 again.
Issue gone.
-
I had the issue with the 100% CPU load as well.
Reset all Gates to default and unload GSX 2
Run Live Update again, register GSX 2 again.
Issue gone.
How do you reset the gates?
-
At the GSX control panel just reactivate default gates.
-
Reset all Gates to default and unload GSX 2
I would like to know if the issue can be fixed, instead, by checking the "Disable RTT" option, which will disable only the jetway number, but will keep the new jetways.
That would help understanding if your issues are "just" the new jetway texture which are too large for your combination of system/settings/other addons, or it's specific to the jetway number, which use a new (officially supported and fully documented) rendering method that we are probably the first one to use, so it's undergoing its first real world testing now.
-
ok but the jetway are default so no L2 active me too it works like this but L2 is not active.
-
Now massive blurries also
https://i.imgur.com/aN1Yakp.jpg (https://i.imgur.com/aN1Yakp.jpg)
-
No for me it doesn't work always same problem I post yesterday about this. There someting with the new jetway maybe priority one in the library of P3D is not good because GSX is off when we are in crz mode, it's a suggestion...
-
ok but the jetway are default so no L2 active me too it works like this but L2 is not active.
Plese re-read my reply. I asked to restore the GSX Level 2 jetways, and check Disable RTT in the Addon Manager (restart the sim after checking this), and see if the problem still happen.
-
There someting with the new jetway maybe priority one in the library of P3D is not good because GSX is off when we are in crz mode, it's a suggestion...
Have you changed the Exclude XML file as I suggested ? If you did, and you don't see any change, just DISABLE it and report back.
-
There someting with the new jetway maybe priority one in the library of P3D is not good because GSX is off when we are in crz mode, it's a suggestion...
Have you changed the Exclude XML file as I suggested ? If you did, and you don't see any change, just DISABLE it and report back.
how can i change the exclude XML file ?
-
How can i change the exclude XML file ?
As I explained several posts ago, in this very thread:
http://www.fsdreamteam.com/forum/index.php/topic,18564.msg129077.html#msg129077
Which I re-linked in another post in this same page:
http://www.fsdreamteam.com/forum/index.php/topic,18564.msg129423.html#msg129423
-
Have you changed the Exclude XML file as I suggested ? If you did, and you don't see any change, just DISABLE it and report back.
Can you briefly describe what to do I'm not sure what to do, I'm lost here.
-
rgr , will try that and report back , thank you
-
OK I change the file Addon, active RTT, and now I disable default Jetways and I test if it works like that.
Report back...
-
Delete shader, delete the scenery files and use the add-on.xml provided.
Still blurries.
-
Tested it's better but after 40 minutes blurries are here maybe less worse in the beginning than without these modification but there are here and start getting worse and worse after 54 minutes I stopped.
Just if someone want to test my flight it is LSGG-EIDW and blurries start after the aera of Paris I notice the airport of LFPG taking a lot of time to load from above I mean I see black runways and buildings like something block the load.
A clue here if your flight don't fly in a heavy aera in cruize or too short flights maybe there is no blurries until your destination so it's why some people have not this problem.
Ok now I go back to GSX without L2 til next suggestion.
Regards,
Christian
-
Tested it's better but after 40 minutes blurries are here maybe less worse in the beginning than without these modification but there are here and start getting worse and worse after 54 minutes I stopped.
Well, you saw some difference. How it was before ?
Just if someone want to test my flight it is LSGG-EIDW and blurries start after the aera of Paris I notice the airport of LFPG taking a lot of time to load from above I mean I see black runways and buildings like something block the load.
Do you use a custom AffinityMask ?
A clue here if your flight don't fly in a heavy aera in cruize or too short flights maybe there is no blurries until your destination so it's why some people have not this problem.
I already posted a 2 hours-long video from another user, flying from FSDT KSDF to Flightbeam KMSP, and the airport was perfectly fine on arrival.
-
Delete shader, delete the scenery files and use the add-on.xml provided.
Still blurries.
I my previous post, I said to ALSO try to check the "Disable_RTT" option in the Addon Manager, restart the sim, and report back if there's any difference.
-
Well, you saw some difference. How it was before ?
I mean blurries were less at the beginning but in the end it's the same.
Do you use a custom AffinityMask ?
No default no tweak.
I already posted a 2 hours-long video from another user, flying from FSDT KSDF to Flightbeam KMSP, and the airport was perfectly fine on arrival.
Ok but the world is big and you were maybe in a place where GsxL2 works without this issue. Try default airport.
-
Spent most of yesterday restarting/rebooting...lol Here is what I have tried individually and in various combinations with no change:
-p3d rebuild generated core files
-uninstall/reinstall GSX
-disable RTT
-del shaders and scene Indexes
-1024, 2048, 4096 in sim textures, which had no impact on timing or severity of blurries
-reset couatl on departure
-0% ai, 100% ai, various autogen draw distance/density settings
-affinity/no affinity in cfg
Sys resources stayed mostly consistent in all scenarios. GTX1080 45-65% load, 3-6Gb mem. cpu temps stayed in the 60-65c range, load never exceeded 90% on any core; devil's canyon. Process explorer working set 3-6Gb, virtual size 10Gb, system memory hovered at 50% physical usage.
-
Ok but the world is big and you were maybe in a place where GsxL2 works without this issue. Try default airport.
- I posted a video with no problems on a default airport on a default airplane, someone said "nobody flies like that, try an addon airplane on a big airport"
- I posted a video with no problems on JFK with the PMDG 747, someone said "try after a long flight"
- I posted a video of a long flight showing no problems, now the airports are not the right ones ?
Are you trying to suggest I'm supposed to try hours-long flight with EVERY airport, until I find the right one ??? Sorry, but this is impossible.
Do you have lots sceneries in your Scenery Library ? One test might be trying with everything disabled, and see if this depends by the number of sceneries installed. I know for sure P3D4 has a limit on the maximum number of textures (their size is not relevant) it can handle.
-
Spent most of yesterday restarting/rebooting...lol Here is what I have tried individually and in various combinations with no change
You haven't said if you tried with my alternative add-on.xml for the Fsdreamteam Exclude area, or if you tried by disabling it altogether.
-
@Umberto
I disabled the Addon manager and also the excluding file from Program Data/Lockhead Martin/Prepare3D v4 add-on.cfg
Same Airport as before LTFJ and absolutely no FPS drop.
Without the Addon manager I'm at the same stage as before your update.
-
I don't blame you...For me it doesn't work after trying all you told us so like I said I go back to GSX without L2 for now and maybe someone find something. I bought L2 but I assume.
-
Same Airport as before LTFJ and absolutely no FPS drop.
You must have confuse this with the other thread you already posted about your specific high fps drop, to which I already replied. Please stay in that thread, this one is about BLURRIES only.
-
same here massive blurries and optimum settings what should i "fix" now gsx? tell me, and also the procedure for a re fund as well
-
The whole thread is full of suggestions to try. Please read my posts.
-
You haven't said if you tried with my alternative add-on.xml for the Fsdreamteam Exclude area, or if you tried by disabling it altogether.
Sorry, yes replaced the xml file.
If by disable you mean GSX itself, yes. When it was off the system I departed kmem and never lost textures. Is that what you are asking?
-
If by disable you mean GSX itself, yes. When it was off the system I departed kmem and never lost textures. Is that what you are asking?
We are trying to FIX this problem and have GSX working with no blurries so, disabling is totally useless for the time being.
So, try all the many things I and others have suggested:
- The new add-on.xml and/or disabling ONLY the Fsdreamteam Exclude area
- Recreate your shader cache and sceneryindexes, which at least two user reported this fixed it for them
- Check the "Disable RTT" option in the Addon Manager and restart the sim (the option doesn't work without a restart)
AFTER you tried all of these, if you don't see ANY difference, we'll proceed with the next steps.
-
The whole thread is full of suggestions to try. Please read my posts.
now the blurries have decided to fix themselves mid flight, so i dont know what is going on here quite weird blurries were there for like 13 mins
-
and now p3d has decided to crash nice one, can I get a list of fixes in one page pls?
-
I already made a list of fixes to try in my previous post.
-
so i shall do all of those fixes at once or just ry one at a time, and how do i re generate scenery indexes and shader cache? hope it does not break my p3d and it's performance
-
You may have confused my post with another..., of course, I DID try all those items.
-
It’s better after follow your advised ... Change XML / Clear shader / Checked Disable RTT .... but it’s still blurie when fly below 6000ft at speed 180 Knots. very slow load autogen & texture.
Regards,
Dear
-
You may have confused my post with another..., of course, I DID try all those items.
You haven't said anything about this:
The new add-on.xml and/or disabling ONLY the Fsdreamteam Exclude area
that's why I asked, and I re-posted the whole list, so others can read it too
-
could it be because i did a long haul in the morning and it was completely fine, and then after i landed, i quite my sim and enabled some other airports via my scenery config as usual, and then did a flight from EDDT aerosoft to LIPZ RFSB no blurries, but when doing LIPZ to LICC other airport without restarting the sim after 120 nm got blurries and then the blurries fixed themselves following a sim crash, 16GB RAM , GTX1080, i7 7700k @4.4ghz, ( i did not restart my pc after the long haul.) P3D V4.3, latest GSX update downloaded today
-
If by disable you mean GSX itself, yes. When it was off the system I departed kmem and never lost textures. Is that what you are asking?
We are trying to FIX this problem and have GSX working with no blurries so, disabling is totally useless for the time being.
So, try all the many things I and others have suggested:
- The new add-on.xml and/or disabling ONLY the Fsdreamteam Exclude area
- Recreate your shader cache and sceneryindexes, which at least two user reported this fixed it for them
- Check the "Disable RTT" option in the Addon Manager and restart the sim (the option doesn't work without a restart)
I'll give a try again with all your suggestions.
Start a flight from LGSm - LIMC
Will let you know what happens
AFTER you tried all of these, if you don't see ANY difference, we'll proceed with the next steps.
-
after the addon xml thing after reseting position it says couatl engine stopped antivirus thing even though the entire folder is excluded from my antivirus
-
i did all the steps :
- i changed the Exclude XML file
- Recreate the shader cache and sceneryindexes,
- Check the "Disable RTT" option in the Addon Manager
and everything goes normal until the approach below 5000 ft approaching the the airport it happened ( blurie and slow loading autogen and textures gone )
i don't know but i think the problem begins when approaching the airport , maybe the process of loading the jetways in the airport causes the problem during approach
-
after the addon xml thing after reseting position it says couatl engine stopped antivirus thing even though the entire folder is excluded from my antivirus
this was fixed with the latest update as well even when not having the folders excluded in my anti virus..
-
i don't know but i think the problem begins when approaching the airport , maybe the process of loading the jetways in the airport causes the problem during approach
Was this airport using replaced jetways ? If it's a default one, it surely is so, could you please trying to JUST restore the default jetways from the GSX Control Panel, and see if it works differently with default jetways ?
-
i don't know but i think the problem begins when approaching the airport , maybe the process of loading the jetways in the airport causes the problem during approach
Was this airport using replaced jetways ? If it's a default one, it surely is so, could you please trying to JUST restore the default jetways from the GSX Control Panel, and see if it works differently with default jetways ?
ok , i will restore the default jetways and try
-
after the addon xml thing after reseting position it says couatl engine stopped antivirus thing even though the entire folder is excluded from my antivirus
Are U running ESET? There has recently a lot changed so you have also to exclude the runtime files... The folder isn't enough...
-
after the addon xml thing after reseting position it says couatl engine stopped antivirus thing even though the entire folder is excluded from my antivirus
Are U running ESET? There has recently a lot changed so you have also to exclude the runtime files... The folder isn't enough...
Mcafee Livesafe
-
You may have confused my post with another..., of course, I DID try all those items.
You haven't said anything about this:
The new add-on.xml and/or disabling ONLY the Fsdreamteam Exclude area
that's why I asked, and I re-posted the whole list, so others can read it too
I mentioned in a previous post that I did replace the addon.xml. Disabling the exclude had no impact.
-
I mentioned in a previous post that I did replace the addon.xml. Disabling the exclude had no impact.
I find quite difficult to memorize the post history of everybody so, I referred to your latest post only.
Now, could you please try what I suggested to another user, restore the default jetways from the GSX Control Panel, and see if it works differently with default jetways ? You would have to try a default airport, to see default jetways.
-
Also have this so its definitely not one user..... GSX Level 2 is causing major issues on my system.
Please sort it.
-
Also have this so its definitely not one user..... GSX Level 2 is causing major issues on my system.
If you followed this thread, you'll know we are trying every possible kind of test, to understand what's causing it and why it affects only some users.
-
Hi umberto sorry for bad english.
I Disabled RTT, changed the addon.xml but blur still continues
First I got 300 passengers from LTBA without jetway, there was no blur.
Then I removed the .bgl jetway from gate 108 and created a new jetway., Passengers boarded the plane. the problem continued.
-
well I will add my name to the list of users experiencing massive blurries. Prior installing GSX level2, I have never experienced blurries whatsoever, I have a GTX1080 ti and i7K running @ 4.6GHz.
-
Well...then I guess I should hold off my credit card for a while. Too sad as I've been eagerly waiting for the L2.
-
So after the flight from LGSm to LIMC the blurries are still there.
I arrived LIMC aprox. 1 min before my autogen arrived it.
All steps mentioned here in the posts are done.
Last but not least Umberto you'll have a lot of work.
I didn't have this issue before and my system was running like a charm doesn't matter I use FSLabs PMDG or QW.
Also doesn't matter which airport or region I'm in.
I'll disable the lvl2 for now and wait until a reasonable solution was found.
My time is to valuable to give the beta tester here.
-
Well, not 100% sure yet but the steps sugested by Umberto worked for me on my flight today.. Lets test further before give 100% sure..
-
Never had blurries, but replacing the add-on.xml definitively restored my texture loading back to normal. Thanks for this.
-
problem solved for me , everything back to normal with GSXL2 after the following steps :
- i changed the Exclude XML file
- Recreate the shader cache and sceneryindexes,
- Check the "Disable RTT" option in the Addon Manager
- restore the default jetways via GSX control panel
but i liked the idea of disable default jetways cuz it adds jetways for all default airports that has not jetways by default , i hope that there is no problem of disable default jetways
-
We are trying to FIX this problem and have GSX working with no blurries so, disabling is totally useless for the time being.
So, try all the many things I and others have suggested:
- The new add-on.xml and/or disabling ONLY the Fsdreamteam Exclude area
- Recreate your shader cache and sceneryindexes, which at least two user reported this fixed it for them
- Check the "Disable RTT" option in the Addon Manager and restart the sim (the option doesn't work without a restart)
AFTER you tried all of these, if you don't see ANY difference, we'll proceed with the next steps.
I've tried, still having trouble
https://ibb.co/diNpAU
https://i.hizliresim.com/g6M9E2.jpg
-
Well, looks like if I depart from an airport that I've changed the jetways using GSX I still get blurries. If I depart from other airport with sode jetways but not the GSX ones, I'm getting no blurries at all. Landing in any airport doesn't give me blurries... The problem seems to be depart from an GSX SODE airport. If I do that, at about 30 min flight I start to get very blurried textures.
-
problem solved for me , everything back to normal with GSXL2 after the following steps :
- i changed the Exclude XML file
- Recreate the shader cache and sceneryindexes,
- Check the "Disable RTT" option in the Addon Manager
- restore the default jetways via GSX control panel
but i liked the idea of disable default jetways cuz it adds jetways for all default airports that has not jetways by default , i hope that there is no problem of disable default jetways
I followed each of these steps - testing after each one - and found that the problem of blurry textures *appears* to have been fixed after the final step (restoring the default jetways).
This seems to suggest the problem was with the jetways (and/or their textures) that had replaced the default jetways...
What does this mean in practice? We can't use SODE jetways at airports that didn't previously have SODE?
Chris
-
Well, looks like if I depart from an airport that I've changed the jetways using GSX I still get blurries. If I depart from other airport with sode jetways but not the GSX ones, I'm getting no blurries at all. Landing in any airport doesn't give me blurries... The problem seems to be depart from an GSX SODE airport. If I do that, at about 30 min flight I start to get very blurried textures.
That's an interesting comment.. I tested the steps that a member suggested above and it seemed to have solved my blurry texture problem - but I departed from EDDM, an airport at which I hadn't changed the jetways. I'll have to test from LSZH, where I had installed a config file.. thx
-
Interesting findings (which should have been accomplished during beta testing which in turn makes me think beta testing here was not well performed).
I also noted that depending on the departing (and overflown maybe?) airport the issue does not arise, so apparently the routine that hogs the system is never launched.
I'm also having some .DLL errors during the shutdown of P3D (BGLMAN*.*), within the session the textures (aircraft, jetways, service vehicles, etc) are not loaded correctly and when they do, they take a lot of time.
Also bear in mind that I did NOT buy the Level 2, so deactivation is nonsense in this case as it's not even enabled. I'm not sure in this case whether or not deactivating SODE/Original jetways is something possible, but I will take a look.
-
problem solved for me , everything back to normal with GSXL2 after the following steps :
- i changed the Exclude XML file
- Recreate the shader cache and sceneryindexes,
- Check the "Disable RTT" option in the Addon Manager
- restore the default jetways via GSX control panel
but i liked the idea of disable default jetways cuz it adds jetways for all default airports that has not jetways by default , i hope that there is no problem of disable default jetways
I followed each of these steps - testing after each one - and found that the problem of blurry textures *appears* to have been fixed after the final step (restoring the default jetways).
This seems to suggest the problem was with the jetways (and/or their textures) that had replaced the default jetways...
What does this mean in practice? We can't use SODE jetways at airports that didn't previously have SODE?
Chris
This might explain why I developed massive blurring on my 4th flight since installing L2, but not the first three.
The first flight was to ImagineSim KATL, which has native SODE jetways, but not GSX versions.
The second flight was to Sunskyjet KPHL, which has static jetways that were not automatically replaced by GSX SODE versions.
The third flight was to FSDT KCLT, which has very nice moving jetways that can be controlled by GSX, but which are not GSX SODE replacement jetways.
The fourth flight, (where major blurries occurred), was to KDTW, a P3D default airport with CTRL-J jetways, ALL of which were replaced by GSX SODE. Between the McNamara and North terminals, there are probably over 100 individual jetways there.
The only strange part to my mind is that the blurries began when I was a good 20 miles from the airport, well before any detailed rendering of the airport environment (and terminal jetways) would have begun.
I have now disabled the RTT option in the add-on manager. I will try another flight into Detroit tomorrow (Wednesday) to see if it helped the situation.
-
Well, looks like if I depart from an airport that I've changed the jetways using GSX I still get blurries. If I depart from other airport with sode jetways but not the GSX ones, I'm getting no blurries at all. Landing in any airport doesn't give me blurries... The problem seems to be depart from an GSX SODE airport. If I do that, at about 30 min flight I start to get very blurried textures.
i can confirm the same thing
-
We just posted a new Live Update now. It has many other fixes, but there's a small change that *might* affect this, considering your reports of the problem being fixed by restoring the default jetways.
The Render To Texture feature (RTT), is used to draw the Jetway numbers so, if you disabled it, you would see a black texture instead of the number. With this version, the entire object is not drawn (the box that contains the number). I'm not sure if it makes any difference, but it's worth trying.
You must disable the default jetways with the GSX Control Panel, for test being meaningful.
-
Just did a test with the update. I still got the blurries about 30 minutes into flight. Back to default jetways for now. Thanks for effort.
Darcy
-
i just tried with the liveupdate and RTT disabled. no autogen loading and blurries still. Back to regular GSX for now...
-
I tried the live update there is no blur with the default jetway. I see blurries when I created new jetway.
-
I tried with:
1) No Exclude (deleted all references & traces)
2) RTT disabled
3) Default jetways selected
Departed from KMEM and had the blurries a few minutes later while flying, i.e., it's not solved yet.
I also noticed that KMEM has absolutely no jetways moving this way, no SODE, no CTRL+J, nothing. Is this correct?
-
I tried with:Departed from KMEM and had the blurries a few minutes later while flying, i.e., it's not solved yet.
Nobody ever said this is solved.
Assuming you ran the latest Live Update, the Disable RTT option has been changed only to be sure that nothing of the new things we are doing for this version, which is the Rendering To Texture using DirectX 11, might have some problem, possibly a P3D4 bug because, as far as I know, we are the first with a relased product using this feature.
With the previous version, even disabling RTT still called the object that was supposed to contain the rendered texture, which is the jetway number. Now, the whole object is not even created.
Which seems to confirm two things:
- The problem never was with any of the new things we do in our software, which were the ONLY ones we had some control over it (not entirely, because we still call officially documented functions provided by the simulator), because now when you disable them, there are not even there.
- Since many seem to confirm the problem disappears when reverting to default jetways, since they are totally standard objects with nothing special, other than having fairly large 4K textures, that goes back to square one, which is your system simply reached ITS OWN breaking point, which you were already close before installing GSX, which was just the proverbial "last straw that broke the camel's back".
We'll try to create a 2K or even 1K version of the texture. Maybe the simulator is using memory nevertheless, even you set a texture size lower that 4K so, reducing the size from the option might not be useful, and we *must* resize the texture themselves.
-
I tried with:Departed from KMEM and had the blurries a few minutes later while flying, i.e., it's not solved yet.
Nobody ever said this is solved.
Assuming you ran the latest Live Update, the Disable RTT option has been changed only to be sure that nothing of the new things we are doing for this version, which is the Rendering To Texture using DirectX 11, might have some problem, possibly a P3D4 bug because, as far as I know, we are the first with a relased product using this feature.
With the previous version, even disabling RTT still called the object that was supposed to contain the rendered texture, which is the jetway number. Now, the whole object is not even created.
Which seems to confirm two things:
- The problem never was with any of the new things we do in our software, which were the ONLY ones we had some control over it (not entirely, because we still call officially documented functions provided by the simulator), because now when you disable them, there are not even there.
- Since many seem to confirm the problem disappears when reverting to default jetways, since they are totally standard objects with nothing special, other than having fairly large 4K textures, that goes back to square one, which is your system simply reached ITS OWN breaking point, which you were already close before installing GSX, which was just the proverbial "last straw that broke the camel's back".
We'll try to create a 2K or even 1K version of the texture. Maybe the simulator is using memory nevertheless, even you set a texture size lower that 4K so, reducing the size from the option might not be useful, and we *must* resize the texture themselves.
Reducing the texture size of the jetways might indeed be worth a shot Umberto. The problem crops up, as you say, at airports which utilise GSX and the SODE jetways associated with it.
For example, having restored default jetways, disabled RTT, deleted the sceneryindexes_x64 and shaders directories, yesterday I flew from EDDM (Taxi2Gate's version, with SODE) to LSZH (Aerosoft's version, with GSX2 SODE jetways). Departure from Munich was fine, no blurry textures on the way either, but framerates dived on arrival into Zurich and textures loaded slowly. So I can only assume from this that there are indeed problems associated with airports which have got the replacement GSX2 SODE jetways.
Anyhow, I'll try anything :) I'm quite eager (as I'm sure you are too) to get this working properly.
Thanks,
Chris
-
Blurries now gone.
What I've done: Simply uninstalled the whole GSX and AddonManager.
Delete all related files and folder. Clean up the registry and reinstall GSX fresh download from the website.
Flight from LFRS to EDDS with no blurries anymore. So far GSX base is running fine now.
Will test tomorrow with LvL2 and report again.
P.S. as in the other thread, I've still massive FPS droppes using GSX (bording and cargo loading)
-
when i restore default jetways in GSX L2 the process of boarding passengers is acting like GSX version one , this means that there is no animated passengers visible via the gateway! , and the gateway is visible by the way , is this means to see animated passengers via the gateway i should disable the default gatways ?!
-
Couldn't care less about 4k textures.. I'm using a 22'' monitor and even if I pay atention I coudn't notice any difference. To be honest, almost all add-ons out there let you choose the quality of your textures, GSX should had it by default. I hope this solve the issue, as of now I'm saving all my "GSX jetways airports departure" flights when reaching cruise level and closing P3D to load the flight again without blurries. Even trying to refresh the scenery doesn't work in a long term, the textures goes back to normal but start to get blurries again. its like something is sucking all resourses from my PC. The only way is to shut the P3D down and reload the save scenario.
-
~°~
After a few days of flying and trying different scenarios, I can concur that the 'blurries' have something to do if you fly from an airport that was edited with GSXv2 ... but even if I don't the main thing now is the disappearance of autogen around airport and from altitude there is simply NO autogen. If you hit [REFRESH SCENERY] it takes up to 8 and more minutes to reload everything while the CPU rocks through the roof. As you come in to land the autogen starts popping up like a popcorn show and by the looks of it in a 10-15nm radius around the aircraft. It doesn't matter what your LEVEL OF RADIUS is in P3D settings, the issue is the same.
All the suggestions have been followed and applied after every flight:
- Recreate shader cache and sceneryindexes
- New add-on.xml installed
- "Disable RTT" applied
- Latest LIVE UPDATE applied
- Only airport of departure and airport of destination enabled
The conclusion: My FPS (i.e performance) are rock solid and no dip in FPS because of GSXv2; when I fly from an airports that I've edited then the blurries are back regardless, notwithstanding, in spite of above mentioned suggestions (proposed fixes); the lost of autogen suggests that something in the background is taking up a lot of CPU power and therefore P3D quits releasing breathing space for autogen except when you fly low and slow then the popups appear.
With all the experience and knowledge I have with FSX/P3D I'm not pointing fingers at GSX, I'm just trying to 'understand' and to make a meaningful contribution to solve this and to be able to fly effortlessly without have to fiddle and change setups all the time.
Hopefully the holy grail, or silver bullet will be found soon that is causing this anomaly.
Until then, you'll find me in GA hanger doing low & slow from small airfields.
-
~°~
After a few days of flying and trying different scenarios, I can concur that the 'blurries' have something to do if you fly from an airport that was edited with GSXv2 ... but even if I don't the main thing now is the disappearance of autogen around airport and from altitude there is simply NO autogen. If you hit [REFRESH SCENERY] it takes up to 8 and more minutes to reload everything while the CPU rocks through the roof. As you come in to land the autogen starts popping up like a popcorn show and by the looks of it in a 10-15nm radius around the aircraft. It doesn't matter what your LEVEL OF RADIUS is in P3D settings, the issue is the same.
All the suggestions have been followed and applied after every flight:
- Recreate shader cache and sceneryindexes
- New add-on.xml installed
- "Disable RTT" applied
- Latest LIVE UPDATE applied
- Only airport of departure and airport of destination enabled
The conclusion: My FPS (i.e performance) are rock solid and no dip in FPS because of GSXv2; when I fly from an airports that I've edited then the blurries are back regardless, notwithstanding, in spite of above mentioned suggestions (proposed fixes); the lost of autogen suggests that something in the background is taking up a lot of CPU power and therefore P3D quits releasing breathing space for autogen except when you fly low and slow then the popups appear.
With all the experience and knowledge I have with FSX/P3D I'm not pointing fingers at GSX, I'm just trying to 'understand' and to make a meaningful contribution to solve this and to be able to fly effortlessly without have to fiddle and change setups all the time.
Hopefully the holy grail, or silver bullet will be found soon that is causing this anomaly.
Until then, you'll find me in GA hanger doing low & slow from small airfields.
That's definitely a helpful contribution actually. I hope it helps FSDT to get to the bottom of it. Perhaps lower resolution textures will help, let's see. Fingers crossed :)
-
Same blurries?
-
Done my first flight after setting up everything, huge blurries :'( :'(
-
Hello,
How to return to the basic version ?
Thank you for your help.
Jean Marc
-
Sorry virtuali, but if multiple users are reporting blurries after instantiation of Level 2, there is a problem somewhere even if it's not obvious.
As always great products have issues ;D
-Ollie
-
Hello,
How to return to the basic version ?
Thank you for your help.
Jean Marc
And same as this guy, til issue is sorted ;)
-
Hello,
How to return to the basic version ?
Thank you for your help.
Jean Marc
And same as this guy, til issue is sorted ;)
Thank you, nothing understood ??? ;D :D
-
Hello,
How to return to the basic version ?
Thank you for your help.
Jean Marc
And same as this guy, til issue is sorted ;)
Thank you, nothing understood ??? ;D :D
What do you mean nothing understood???
-
Umberto,
The blur problem occurs because of jetway of the GSX L2, I tried the other Sode Jetway (JustSim Antalya LTAI) Passengers boarded to airplane through the jetway and there wasn't any blurries.
-
Can I just throw something into the mix.
I remember reading once that scenery developers only made a few gates at airports SODE because of the animation of the bridges. As I remember as your scenery loads, any gate with an aircraft at I gets served by a bridge ( animated ). Im just wondering if as you fly over airports, all these sode bridges are trying to dock at once dragging the FPS and CPU down.
What about someone who is having this problem reducing their air traffic settings to zero so no aircraft are parked on the ground and get animated gates. Maybe this is the reason some people are not experiencing this problem ie they already have their traffic at zero.
I myself are awaiting the cure before I upgrade.
Just a thought
Graham
-
Our jetways are static with no kind of animation whatsoever, and they are replaced by an animated jetway only when GSX operates them on ground so not, this cannot be the issue.
Please allow us some time to investigate this. Fact you almost confirmed the blurries are gone by returning to the default jetways, is already a big help. In the meantime, you can continue to use GSX with default jetways.
-
Our jetways are static with no kind of animation whatsoever, and they are replaced by an animated jetway only when GSX operates them on ground so not, this cannot be the issue.
Please allow us some time to investigate this. Fact you almost confirmed the blurries are gone by returning to the default jetways, is already a big help. In the meantime, you can continue to use GSX with default jetways.
Virtuali I have a contribution converted to 2K (dds dxt5) and folder size gone from 1.94GB to 580MB the difference is huge ;-)
Happy to upload in zip files if needed?
-
Our jetways are static with no kind of animation whatsoever, and they are replaced by an animated jetway only when GSX operates them on ground so not, this cannot be the issue.
Please allow us some time to investigate this. Fact you almost confirmed the blurries are gone by returning to the default jetways, is already a big help. In the meantime, you can continue to use GSX with default jetways.
Virtuali I have a contribution converted to 2K (dds dxt5) and folder size gone from 1.94GB to 580MB the difference is huge ;-)
Happy to upload in zip files if needed?
"the difference is huge" do you mean blurries by this?
-Ollie
-
Our jetways are static with no kind of animation whatsoever, and they are replaced by an animated jetway only when GSX operates them on ground so not, this cannot be the issue.
Please allow us some time to investigate this. Fact you almost confirmed the blurries are gone by returning to the default jetways, is already a big help. In the meantime, you can continue to use GSX with default jetways.
Thank you for listening :D :D
-
Have you tried them ? Saw any difference ?
-
just a shot in the dark but has anyone tried updating their GPU drivers? There was a recent driver update for the NVIDIA 1080
-
just a shot in the dark but has anyone tried updating their GPU drivers? There was a recent driver update for the NVIDIA 1080
Yes, no difference.
-
Had a crash going into CYYZ the other day around FL250 - 100% CPU usage with 5 cores around 40% kernel (not user) time. I suspect it had something to do with the problems here.
Today, updated GSX2, used P3D 4.3 and TFDI 717 from FlyTampa CYYZ to ImagineSim KATL. No issues whatsoever. Previously, deleted shadercache and scenery indexes. I'll fly more this weekend to test.
Cheers!
Luke
-
I can confirm the temp fix as suggested: disable RTT, jetways to default, sim runs as it did before the addition of Level 2. The CPU no longer max's all cores and no blurries.
-
Yes Disable RTT fixes issue completely!!!!
;D ;D ;D ;D
-
I can confirm the temp fix as suggested: disable RTT, jetways to default, sim runs as it did before the addition of Level 2. The CPU no longer max's all cores and no blurries.
Thank you
-
Disabling RTT doesn't do it for me. While it does seem to improve the blur, I still get 100% CPU usage and terrible performance. Yesterday I tested it. I was flying the NGX over western Kansas with no cloud cover - near 100% CPU usage. If I disable GSX, it drops down to the 60's. Re-enable - back up to 100%
had a great flight from LGA-RDU last night - GSX disabled, of course.
-
Disabling RTT doesn't do it for me. While it does seem to improve the blur, I still get 100% CPU usage and terrible performance. Yesterday I tested it. I was flying the NGX over western Kansas with no cloud cover - near 100% CPU usage. If I disable GSX, it drops down to the 60's. Re-enable - back up to 100%
Do you know whether that's kernel or user time? When I saw it, it was an abnormally high percentage of kernel time which suggested that it was doing something related to the O/S - file I/O or something like that.
Cheers!
Luke
-
@virtuali have you got any closer to a solution? (not being pushy just wondering :D)
-
Disabling RTT doesn't do it for me. While it does seem to improve the blur, I still get 100% CPU usage and terrible performance. Yesterday I tested it. I was flying the NGX over western Kansas with no cloud cover - near 100% CPU usage. If I disable GSX, it drops down to the 60's. Re-enable - back up to 100%
Do you know whether that's kernel or user time? When I saw it, it was an abnormally high percentage of kernel time which suggested that it was doing something related to the O/S - file I/O or something like that.
Cheers!
Luke
Not sure. Tell me what to look for and I'll retest. Right now I'm just looking at resource monitor.
-
When I select Disable RTT in the manager and click exit, restart sim, the check is no longer selected in the RTT box. Does this mean the deactivation of RTT did not happen? Thanks!
-
Well, looks like if I depart from an airport that I've changed the jetways using GSX I still get blurries. If I depart from other airport with sode jetways but not the GSX ones, I'm getting no blurries at all. Landing in any airport doesn't give me blurries... The problem seems to be depart from an GSX SODE airport. If I do that, at about 30 min flight I start to get very blurried textures.
After 4 hours of testing it seems that this also solved my issue. I manually deleted the changes I made after I bought the Level 2 Expansion from the files in %appdata%\Virtuali\GSX.
I tried the other ideas first (Exclude, shader cache, SceneryIndexes, RTT) but without success. I will now enable these things again.
-
I have not changed any jetways.
-
By the way... same Problem here. Bluries after boarding with GSX V2 after 30 minutes of flight. I did the fixes and it worked for me. But it would be great to have the enhanced Jetways.
-
I have not changed any jetways.
The sceneries I made changes to are EDDK and EDDL which have static jetways. I couldn't even disable them. I placed SODE jetways at one gate in EDDL and at one gate in EDDK to check how it works.
So it might be that the problem is indeed in the SODE jetways or at least something happens that causes the blurries.
-
Was busy with adding gates so time to test FSDT LSGG > FT EHAM both with GSX2 SODE jetways 2k textures departing LSGG
wend fine however at FL110 above the Netherlands had massive blurriness...
Noted that the GPU was at 32% and the CPU around 84% with the FSLABS bus A319.
Something is taking all the time from simconnect or background because when changing something via the P3D menu it takes ages....
Never experienced this kind of blurriness always great performance and sharp textures...
RTT disabled plus done all the steps before testing...
-
Was busy with adding gates so time to test FSDT LSGG > FT EHAM both with GSX2 SODE jetways 2k textures departing LSGG
wend fine however at FL110 above the Netherlands had massive blurriness...
Noted that the GPU was at 32% and the CPU around 84% with the FSLABS bus A319.
Something is taking all the time from simconnect or background because when changing something via the P3D menu it takes ages....
Never experienced this kind of blurriness always great performance and sharp textures...
RTT disabled plus done all the steps before testing...
Ok was disabling GSX 2 custom stuff and loaded FT EHAM and noticed double gates (via control panel enabled default jetways)
So GSX is still loading the static jetways as soon as I stop GSX2 the jeways are removed and the original jetways are in place...
Maybe the issue?
To add I notice the problem is the GSX ini file in the Virtuali directory which isn't restored to it's previous state without the FSDT static jetways entries...
So renaming the exclude add-on xml file isn't enough to revert back to scenery without FSDT jetways...
-
Restore default jetways only restore default jetways. It won't automatically destroy (that would be *very* wrong) all the work you made to add customized jetways.
-
So you can add me to the list of people facing blurries and 100% CPU utilization on all cores because of GSX since updating to Level 2. I tried all the solutions posted and spent two days troubleshooting.
- No Exclude (deleted all references & traces)
- Recreate the shader cache and sceneryindexes,
- Check the "Disable RTT" option in the Addon Manager
- Default jetways selected
- Latest LIVE UPDATE applied
I still have blurries out of KLAS and 100% CPU utilization. Plus P3D will not close properly and crashes out on exit every time. The only thing has solved the blurries and returned my sim back to normal is uninstalling GSX. I also had to uninstall KLAS because it DOES NOT WORK without GSX, which is completely ridiculous. GSX is broken, Couatl is broken, your company is broken.
Why are you still in Flight Sim development game? WHY? Seriously just get out. The only reason I ever bought anything from you is because of KLAS. Now none if it works and was a complete waste of money. If FSDT had any respect left, they would start offering refunds to everyone who got conned into upgrading to GSXL2. You can keep my money for KLAS. It was nice while it lasted. But I'm waiting in great anticipation for Flytampa KLAS which should be out very soon. Done with FSDT products, and I'll make sure everyone knows about it.
-
So you can add me to the list of people facing blurries and 100% CPU utilization on all cores because of GSX since updating to Level 2. I tried all the solutions posted and spent two days troubleshooting.
- No Exclude (deleted all references & traces)
- Recreate the shader cache and sceneryindexes,
- Check the "Disable RTT" option in the Addon Manager
- Default jetways selected
- Latest LIVE UPDATE applied
I still have blurries out of KLAS and 100% CPU utilization. Plus P3D will not close properly and crashes out on exit every time. The only thing has solved the blurries and returned my sim back to normal is uninstalling GSX. I also had to uninstall KLAS because it DOES NOT WORK without GSX, which is completely ridiculous. GSX is broken, Couatl is broken, your company is broken.
Why are you still in Flight Sim development game? WHY? Seriously just get out. The only reason I ever bought anything from you is because of KLAS. Now none if it works and was a complete waste of money. If FSDT had any respect left, they would start offering refunds to everyone who got conned into upgrading to GSXL2. You can keep my money for KLAS. It was nice while it lasted. But I'm waiting in great anticipation for Flytampa KLAS which should be out very soon. Done with FSDT products, and I'll make sure everyone knows about it.
Jesus it's not like he scammed you, it's just a bug. He will fix it!
-
So you can add me to the list of people facing blurries and 100% CPU utilization on all cores because of GSX since updating to Level 2. I tried all the solutions posted and spent two days troubleshooting.
- No Exclude (deleted all references & traces)
- Recreate the shader cache and sceneryindexes,
- Check the "Disable RTT" option in the Addon Manager
- Default jetways selected
- Latest LIVE UPDATE applied
I still have blurries out of KLAS and 100% CPU utilization. Plus P3D will not close properly and crashes out on exit every time. The only thing has solved the blurries and returned my sim back to normal is uninstalling GSX. I also had to uninstall KLAS because it DOES NOT WORK without GSX, which is completely ridiculous. GSX is broken, Couatl is broken, your company is broken.
Why are you still in Flight Sim development game? WHY? Seriously just get out. The only reason I ever bought anything from you is because of KLAS. Now none if it works and was a complete waste of money. If FSDT had any respect left, they would start offering refunds to everyone who got conned into upgrading to GSXL2. You can keep my money for KLAS. It was nice while it lasted. But I'm waiting in great anticipation for Flytampa KLAS which should be out very soon. Done with FSDT products, and I'll make sure everyone knows about it.
great post you have got, 1 post and a rant like this goodbye thx for the 1 post laugh made my day, maybe you should troll some where else like in avsim forum see how far you get there
-
This post is indeed a disgrace. FSDT has provided to our leisure great products and will still do. Their airports are among the best. KLAX, KDFW, KIAH and many other airports are just fantastic for those who know them.
Dom Mason
-
@SolRayz u got reported
-
So you can add me to the list of people facing blurries and 100% CPU utilization on all cores because of GSX since updating to Level 2. I tried all the solutions posted and spent two days troubleshooting.
- No Exclude (deleted all references & traces)
- Recreate the shader cache and sceneryindexes,
- Check the "Disable RTT" option in the Addon Manager
- Default jetways selected
- Latest LIVE UPDATE applied
I still have blurries out of KLAS and 100% CPU utilization. Plus P3D will not close properly and crashes out on exit every time. The only thing has solved the blurries and returned my sim back to normal is uninstalling GSX. I also had to uninstall KLAS because it DOES NOT WORK without GSX, which is completely ridiculous. GSX is broken, Couatl is broken, your company is broken.
Why are you still in Flight Sim development game? WHY? Seriously just get out. The only reason I ever bought anything from you is because of KLAS. Now none if it works and was a complete waste of money. If FSDT had any respect left, they would start offering refunds to everyone who got conned into upgrading to GSXL2. You can keep my money for KLAS. It was nice while it lasted. But I'm waiting in great anticipation for Flytampa KLAS which should be out very soon. Done with FSDT products, and I'll make sure everyone knows about it.
We take all the criticism into consideration but you must know, based on the real numbers of our GSX level 2 customers, that your opinion represents 0.02% of our customers, having said that, surely your problems will be resolved promptly.
And welcome to our forum :), considering that you are writing your first post. ;)
-
So you can add me to the list of people facing blurries and 100% CPU utilization on all cores because of GSX since updating to Level 2. I tried all the solutions posted and spent two days troubleshooting.
- No Exclude (deleted all references & traces)
- Recreate the shader cache and sceneryindexes,
- Check the "Disable RTT" option in the Addon Manager
- Default jetways selected
- Latest LIVE UPDATE applied
I still have blurries out of KLAS and 100% CPU utilization. Plus P3D will not close properly and crashes out on exit every time. The only thing has solved the blurries and returned my sim back to normal is uninstalling GSX. I also had to uninstall KLAS because it DOES NOT WORK without GSX, which is completely ridiculous. GSX is broken, Couatl is broken, your company is broken.
Why are you still in Flight Sim development game? WHY? Seriously just get out. The only reason I ever bought anything from you is because of KLAS. Now none if it works and was a complete waste of money. If FSDT had any respect left, they would start offering refunds to everyone who got conned into upgrading to GSXL2. You can keep my money for KLAS. It was nice while it lasted. But I'm waiting in great anticipation for Flytampa KLAS which should be out very soon. Done with FSDT products, and I'll make sure everyone knows about it.
SHAME ON YOU! FSDT/Virtuali doesn´t deserve such cheap and stupid statement like you wrote here.
Can YOU do it better, can you provide some solutions to these issues, can YOU develop a better Addon?
I have with every software-addon used for P3Dv4 or FSX some issues or problems somewhen, somehow, no one delivered a 100% "issue free" product up to now: too differents and unpredictable computer system combinations are being used all over the world. No one can predicts how a new software will behaviour when installed in one of million possible configurations!!!
Please go anywhere else to write your useless and offending comments.
-
So you can add me to the list of people facing blurries and 100% CPU utilization on all cores because of GSX since updating to Level 2. I tried all the solutions posted and spent two days troubleshooting.
- No Exclude (deleted all references & traces)
- Recreate the shader cache and sceneryindexes,
- Check the "Disable RTT" option in the Addon Manager
- Default jetways selected
- Latest LIVE UPDATE applied
I still have blurries out of KLAS and 100% CPU utilization. Plus P3D will not close properly and crashes out on exit every time. The only thing has solved the blurries and returned my sim back to normal is uninstalling GSX. I also had to uninstall KLAS because it DOES NOT WORK without GSX, which is completely ridiculous. GSX is broken, Couatl is broken, your company is broken.
Why are you still in Flight Sim development game? WHY? Seriously just get out. The only reason I ever bought anything from you is because of KLAS. Now none if it works and was a complete waste of money. If FSDT had any respect left, they would start offering refunds to everyone who got conned into upgrading to GSXL2. You can keep my money for KLAS. It was nice while it lasted. But I'm waiting in great anticipation for Flytampa KLAS which should be out very soon. Done with FSDT products, and I'll make sure everyone knows about it.
SHAME ON YOU! FSDT/Virtuali doesn´t deserve such cheap and stupid statement like you wrote here.
Can YOU do it better, can you provide some solutions to these issues, can YOU develop a better Addon?
I have with every software-addon used for P3Dv4 or FSX some issues or problems somewhen, somehow, no one delivered a 100% "issue free" product up to now: too differents and unpredictable computer system combinations are being used all over the world. No one can predicts how a new software will behaviour when installed in one of million possible configurations!!!
Please go anywhere else to write your useless and offending comments.
I suggest we just ignore offensive comments and get back to the important issue of fixing the problems we are having. Is there any progress on this yet? Specifically, have lower resolution textures been made for the jetways? Thanks!
-
I suggest we just ignore offensive comments and get back to the important issue of fixing the problems we are having. Is there any progress on this yet? Specifically, have lower resolution textures been made for the jetways? Thanks!
I'm waiting some feedback about this test. Maybe you can try that too:
Go into the Addon Manager\Couatl folder, and remove (or maybe MOVE it to a different place, so you can restore them easily ) the following folders:
KCLT
KIAH
KLAS
KMEM
KSDF
Of course, move only those you have. Yes, this will disable these sceneries, but we are doing a test so, don't panic. Then, try to do the same flight you did last time, and see if there's any difference.
Pay attention not to run the Live Update during this test, because it will restore these folders, making the test useless.
-
I'll continue testing in a few hours. I will try to restore my airport changes (stop position, guidance/parking system, jetway) and see at which time the problem reappears. Just as a reminder, the airports I tested it so far have a static jetway, so I added a SODE jetway with GSX and changed a few other things. After removing the changes manually from the airport config file, the issue was gone.
I'll then try to depart a FSDT scenery. When the problem occurs, I'll try what Umberto just suggested.
I'm just remembering one test where I did not request pushback. So I placed myself at EDDK at the gate I changed and departed without pushback. Of course the jetway and parking system were visible. But I did not get blurries. At this point it seems I only get blurries when I request a GSX service (like pushback).
-
I suggest we just ignore offensive comments and get back to the important issue of fixing the problems we are having. Is there any progress on this yet? Specifically, have lower resolution textures been made for the jetways? Thanks!
I'm waiting some feedback about this test. Maybe you can try that too:
Go into the Addon Manager\Couatl folder, and remove (or maybe MOVE it to a different place, so you can restore them easily ) the following folders:
KCLT
KIAH
KLAS
KMEM
KSDF
Of course, move only those you have. Yes, this will disable these sceneries, but we are doing a test so, don't panic. Then, try to do the same flight you did last time, and see if there's any difference.
Pay attention not to run the Live Update during this test, because it will restore these folders, making the test useless.
Thanks Umberto, I'll try this when I get home and report back.
-
I suggest we just ignore offensive comments and get back to the important issue of fixing the problems we are having. Is there any progress on this yet? Specifically, have lower resolution textures been made for the jetways? Thanks!
I'm waiting some feedback about this test. Maybe you can try that too:
Go into the Addon Manager\Couatl folder, and remove (or maybe MOVE it to a different place, so you can restore them easily ) the following folders:
KCLT
KIAH
KLAS
KMEM
KSDF
Of course, move only those you have. Yes, this will disable these sceneries, but we are doing a test so, don't panic. Then, try to do the same flight you did last time, and see if there's any difference.
Pay attention not to run the Live Update during this test, because it will restore these folders, making the test useless.
what will happen if none of these scenery? there is only KLAX
-
I suggest we just ignore offensive comments and get back to the important issue of fixing the problems we are having. Is there any progress on this yet? Specifically, have lower resolution textures been made for the jetways? Thanks!
I'm waiting some feedback about this test. Maybe you can try that too:
Go into the Addon Manager\Couatl folder, and remove (or maybe MOVE it to a different place, so you can restore them easily ) the following folders:
KCLT
KIAH
KLAS
KMEM
KSDF
Of course, move only those you have. Yes, this will disable these sceneries, but we are doing a test so, don't panic. Then, try to do the same flight you did last time, and see if there's any difference.
Pay attention not to run the Live Update during this test, because it will restore these folders, making the test useless.
Well Umberto I did already a test without them KCLT/KIAH/KMEM however I'm flying in europe and tested between FSDT LSGG and FT EHAM with GSX2 SODE jetways...
Tested with 4k and 2K textures
-
Restore default jetways only restore default jetways. It won't automatically destroy (that would be *very* wrong) all the work you made to add customized jetways.
That's why I have a backup of that particular folder maybe an option in the control panel
to temporary disable those and revert back to original (the ini file installed before editing the airport)
Similar to the bgl enable > disable routine (jetways)?
-
Well Umberto I did already a test without them KCLT/KIAH/KMEM however I'm flying in europe and tested between FSDT LSGG and FT EHAM with GSX2 SODE jetways... Tested with 4k and 2K textures
And the result is ?
Be sure to do the test *exactly* as I've indicated. Don't uninstall any scenery, don't deactivate anything and keep default jetways disabled. JUST remove the folders (the ones you have) I indicated.
-
Hi
I too after installing level 2 noticed blurred textures and that my computer while cruising at 38000 ft paused a few times for about 10 secs flying near large airports and that fps periodically would go to a crawl while flying from miami to toronto. I disabled RTT as recommended and there no are no pauses and fps frame rates are constant as before while flying from toronto to orlando. Kind of seems like the sode jetways at default airports were being loaded even thou I was at 38000 ft. Disabling rtt is all that I did and I still have sode jetways installed at default airports.
Hope the above is helpfull in finding the solution for the problem
Don
-
Hi
I too am getting massive blurries, but for some reason this only seems to happen after using SODE jetways, does not happen at all when no jetways used. Also occasionally after using SODE jetways aircraft texture and virtual cockpit and spot views take ages to load. Also flight frequently crashes after use of SODE jetways. ( does not happen if jetways not used). I have not made any other changes except latest GSX and level 2 expansion downloads. Finding this very frustrating. Hope it is sorted out soon. This new addition was not cheap.
-
We you keep posting about you too having blurries ?
We are far that stage at this time. We are to the point I asked to do some things, so I expect the next post from now should just report any results of the test I asked. I'll link again to my previous post of the previous page:
http://www.fsdreamteam.com/forum/index.php/topic,18564.msg130312.html#msg130312
-
where are these folders ? Addon Manager\Couatl folder \ then where ?
-
where are these folders ? Addon Manager\Couatl folder \ then where ?
Where ? THERE! ( I'm sounding like Igor in "Young Frankestein", now...). I listed the names of the folders so, if you go in Addon Manager\Couatl, you surely can see them, IF you have installed any of these sceneries from FSDT, of course.
You might see less of them, or even none, if you don't have any of these sceneries.
-
I'm doing the test just now, give me 10 minutes and you'll have an answer :-)
-
where are these folders ? Addon Manager\Couatl folder \ then where ?
Where ? THERE! ( I'm sounding like Igor in "Young Frankestein", now...). I listed the names of the folders so, if you go in Addon Manager\Couatl, you surely can see them, IF you have installed any of these sceneries from FSDT, of course.
You might see less of them, or even none, if you don't have any of these sceneries.
;D ;D i don't have these sceneries from FSDT , excuse me i got you wrong , my bad
so there is an update , when i opend p3d GSX asks me to update , should i update now or wait ?
-
so there is an update , when i opend p3d GSX asks me to update , should i update now or wait ?
Yes, always update when prompted. Then, you can try the test but, if I understood correctly, you have *none* of these folders already, correct ?
That's not what I wanted to hear because, I suspected they might be what causing GSX to load jetways and airports even above 10K feet (that's what they do, in fact) so, I hoped that, by removing those files, with GSX surely not loading any airports or jetways when cruising, the blurriness and the high-cpu load would go away.
-
so there is an update , when i opend p3d GSX asks me to update , should i update now or wait ?
Yes, always update when prompted. Then, you can try the test but, if I understood correctly, you have *none* of these folders already, correct ?
That's not what I wanted to hear because, I suspected they might be what causing GSX to load jetways and airports even above 10K feet (that's what they do, in fact) so, I hoped that, by removing those files, with GSX surely not loading any airports or jetways when cruising, the blurriness and the high-cpu load would go away.
ya correct i don't have any of these folders , so i will update anyway and wait for others to test
-
NO blurries for me now. Tested at KIAH. First test with KIAH I had blurries. Then I moved KCLT, KIAH, KLAS and KMEM (don't have KSDF) and blurries are gone now.
Will do the entire test again to confirm.
-
If you said the problem of the blurried textures is after GSX2, then i would say it was since the installation of GSX because i used to have blurried textures long time ago since GSX...
And i HAD the barcelona scenery from ORBX completely blurred even without the GSX. I did a complete reinstall and i installed ONLY ORBX GLOBAL AND VECTORS AND BARCELONA and i had a completely mess blurried textured. After changing my processor for a I7 8770K last i had a better chance in BARCELONA BUT the blurs still occurs.
Yesterday i had a MASSIVE BLUR even with the FLY TAMPA - TAMPA. i landed in a black hole.
I had the video to prove it. What can happen is GSX2 intense the blurred textures but believe me - the blurred happened before...
here follow the video. Check out the landing with PERFORMACE INDICATOR ON SCREEN and NOT at 100%:
&feature=share
-
I dont know if my answer was posted. but here again:
I think the blurried textures are a problem that happened before GSX 2!
I bought Barcelona from ORBX and i coudnt simply use it... I made a CLEAN install with ONLY P3D Free of addons (NO ONE) and ORBX GLOBAL + VECTORS and Barcelona City. Was UNFLYIABLE!!! I changed my processor to I7 8770K and it helped but yesterday i had a MASSIVE BLUR and problem with the FLYTAMPA airport TAMPA... Check it out:
&feature=share
-
I have none of those folders but I do have cyvr and KLAX. I get the blurries.
-
I have none of those folders but I do have cyvr and KLAX. I get the blurries.
So, let's sum up the last 3 posts:
Post #252
http://www.fsdreamteam.com/forum/index.php/topic,18564.msg130438.html#msg130438
NO blurries for me now. Tested at KIAH. First test with KIAH I had blurries. Then I moved KCLT, KIAH, KLAS and KMEM (don't have KSDF) and blurries are gone now.
Will do the entire test again to confirm.
Post #254
http://www.fsdreamteam.com/forum/index.php/topic,18564.msg130442.html#msg130442
I made a CLEAN install with ONLY P3D Free of addons (NO ONE) and ORBX GLOBAL + VECTORS and Barcelona City. Was UNFLYIABLE!!! I changed my processor to I7 8770K and it helped but yesterday i had a MASSIVE BLUR and problem with the FLYTAMPA airport TAMPA...
Post #255 (your post)
http://www.fsdreamteam.com/forum/index.php/topic,18564.msg130442.html#msg130442
I have none of those folders but I do have cyvr and KLAX. I get the blurries.
So, what you or anybody suggest we should do now ? I'm trying to proceed by exclusion to remove everything that *might* be different with GSX L2 but, there's not much else we can do, if you are in a situation as in Post #254.
-
So, what you or anybody suggest we should do now ? I'm trying to proceed by exclusion to remove everything that *might* be different with GSX L2 but, there's not much else we can do, if you are in a situation as in Post #254.
I meanwhile did the test again and I can confirm, when I delete/move the 4 folders (I don't have KSDF) the blurries are gone.
Earlier today I continued my tests at EDDK (static jetways of the scenery, I added a SODE jetway with GSX to test the latest GSX version (including Level 2 Expansion)) and I found out that I don't get blurries anymore when I remove the jetway_pos line from the config file.
-
Well Umberto I did already a test without them KCLT/KIAH/KMEM however I'm flying in europe and tested between FSDT LSGG and FT EHAM with GSX2 SODE jetways... Tested with 4k and 2K textures
And the result is ?
Be sure to do the test *exactly* as I've indicated. Don't uninstall any scenery, don't deactivate anything and keep default jetways disabled. JUST remove the folders (the ones you have) I indicated.
I apologize was with the same negative result.
-
I have only the KLAS folder and after remove it I still getting blurries if I depart from an airport with GSX sode jetways. My sim is just fine if I depart from ANY other aiport. But I must say that without the KLAS folder I get les blurries.
-
I'm trying to test with the latest instructions of removing selected FSDT airports. Problem is SDF is where my test flight originated. I'm trying to find another origin where the problem exists. I did a flight from MSP to STL - that went fine. I'm trying LGA to MSP right now, but I need to get into the flight a bit to see if I get the blurries. So far, textures appeared to load normally at LGA.
-
So, what you or anybody suggest we should do now ? I'm trying to proceed by exclusion to remove everything that *might* be different with GSX L2 but, there's not much else we can do, if you are in a situation as in Post #254.
The real important information is that blurries only occur when I used a Jetway befor a flight. When I have used an remote stand without a jetway my flight was perfect without any blurries. So it might have something to do with the moving of a jetway ?!
At the moment / since 7 days I was not realy able to perform a flight, because I got blurries at every top of climb and my P3D v4 stopped working. I tried every possible solution from this thread but nothing worked. This is an unacceptable situation for me because I paid 30 dollar and can't use my simulator anymore. As mentioned before it only happens when using a GSX lvl2 jetway prior a flight so you can't tell me it is not caused by GSX. You have to find a solution for this problem!
-
Hello,
I have the same... CPU goes up and my fans are behaving like turbines.
Also blurries.
I hope you will find a fix quickly.
In our Forum, we have other users with the same problem.
I will de-install and wait.
:(
-
Maybe to clarify my findings: When I confirmed, deleting those folders solved my issue, I was testing at KIAH. So in fact I did not see the KIAH scenery during the test, but I could push back normally.
When I went back to EDDK (with the folders still deleted) the issue appeared.
The real important information is that blurries only occur when I used a Jetway befor a flight. When I have used an remote stand without a jetway my flight was perfect without any blurries. So it might have something to do with the moving of a jetway ?!
I think this is exactly the point. And you have to use GSX service at this parking spot. Not using the jetway (I did not use the jetway on all my tests) but a pushback is enough. When I do tests without pushback (just loading at the gate, waiting a few minutes and then depart) the issue does not occur. So I have to request GSX service at a gate with a SODE jetway (only pushback for me). My tests where I deleted the jetway_pos line of the airport config confirms this in my view. I don't know what GSX does internally but everything points to jetways in my view.
-
I have set out people to test that, but it sounds logical, since:
1. This behavior started with installing of the Updated version & GSX V2
2. The main new feature is the Jetway....
I truly hoop for a fix. Else than that I love the product!
But at the moment its useless.
-
Not sure. It looks like I can't reproduce the problem if I start from an airport other than SDF. I have disable att checked, I have default jetways enabled in the control panel and I did the live update that came out yesterday. I have done 3 test flights today. All were with the NGX, ProATCx, ASP4 (RW weather) and UTL. GSX was used for jetway docking and for pushback only.
MSP (Flightbeam) to STL (T2G). This flight went fine
SDF (FSDT) to KSAN (LantinVFR). Terrible. Slow loading textures and blurries with about 30 mins. I didn't complete it.
LGA (IS) to MSP (Flightbeam). In the air right now over Ontario and things look good.
So, I'm not sure what to do next. I really need to be able to repeat the issue to know if the removal of those airports works. Still, something seems to be up with SDF.
-
I think this is exactly the point. And you have to use GSX service at this parking spot.
I have tested at SDF without using services and I still had the issue. Keep in mind that this was pre-live update and before I restored default jetways in the control panel.
-
One thing I'm curious about is which logical processors are getting maxxed out when these blurries present themselves.
A user on AVSIM presented a situation where if you load an FSDT scenery, then move to another FSDT scenery, then do it once again, the sim hangs during loading and the CPU load goes sky high for as much as 10 minutes during the loading of the third or subsequent FSDT scenery. It's consistently reproducible--I start with the PMDG 737 at KLAS gate A12, then move to KMEM gate B12, then move to KJFK gate 803. What I saw when I reproduced that sequence was relatively normal load times for the first two, then at KJFK, a stall at about 36% during the terrain loading phase and 100% load on all of the logical CPUs that handle terrain and texture loading (in my case logical CPUs 4-7 on an HT-enabled quad-core i7). Changing the order of the airports didn't seem to make a difference, either. This, BTW, is with GSX v1 without ever having upgraded to v2. Killing the couatl, UTLive, and SimobjectDisplayEngine processes had no effect once the hang occured. RAM usage was normal (~7.4GB) and VRAM usage was also not problematic (~3.8GB on a pair of 11GB 1080Ti GPUs).
I'm not certain if it's relevant to the blurry issue, but the apparent similarities between the two--the presence of a large, long-duration and unexplained load on the logical CPUs that handle terrain and texture loading is suspicious. It may be demonstrative that GSX and/or FSDT sceneries are coming up against some kind of internal limitation not previously encountered in P3Dv4.
Regards
Bob Scott
-
I'm not certain if it's relevant to the blurry issue, but the presence of a large, long-duration and unexplained load on the CPUs is suspicious. It may be demonstrative that GSX and/or FSDT sceneries are coming up against some kind of internal limitation not previously encountered in P3Dv4.
I think those are connected because when I first experienced the blurries, I went to Scenery Library and just clicked OK which forces a reload. After 3 minutes I considered P3D as crashed but I got/get the same CPU load. It appears to me like something is taking up a lot of CPU usage and causes P3D to stop loading new stuff.
-
One more question for those having the problem--are you over or near another airport when this problem first occurs? Is the airport default or an add-on, and does it have jetways? If so, what kind?
A good number of the people reporting the problem seem to encounter it after some time in flight. I wonder if it is something creeping up over time due to the CPUs being too heavily-loaded to keep up, or is it triggered by something around you in the scenery environment? Reports of people hearing the CPU fans spin up at problem onset suggests to me it's being triggered by something in the nearby scenery.
Test flights with an eye on CPU load (or temp as a surrogate) might tell a story here.
Regards
Bob Scott
-
Actually I realised this evening I don't have any of these sceneries installed. So, for me at least, they aren't the cause of the problems.
-
1. This behavior started with installing of the Updated version & GSX V2
2. The main new feature is the Jetway....
How do you explain Post #254 then ? I'll copy it again the relevant bit:
http://www.fsdreamteam.com/forum/index.php/topic,18564.msg130442.html#msg130442
I made a CLEAN install with ONLY P3D Free of addons (NO ONE) and ORBX GLOBAL + VECTORS and Barcelona City. Was UNFLYIABLE!!! I changed my processor to I7 8770K and it helped but yesterday i had a MASSIVE BLUR and problem with the FLYTAMPA airport TAMPA...
-
Very simple: Blurries are not a cause but a symptom of a much deeper issue. Blurries are also not a new thing, I've heard of them already 10 years ago but I never experienced them till now. Also the blurries can be different. Slow loading of textures or not loading new elements at all.
-
Regarding CPU load: I have 4 cores and I can see core 0 at 90-100% which is normal. Cores 1-3 are at 100% (straight line) after around 10 minutes.
-
A user on AVSIM presented a situation where if you load an FSDT scenery, then move to another FSDT scenery, then do it once again, the sim hangs during loading and the CPU load goes sky high for as much as 10 minutes during the loading of the third or subsequent FSDT scenery.
Tried that, doesn't happen here.
I'm loading the following sceneries, one after the other. This is how much time took to load each one, from pressing OK after selecting the ICAO, two the end of the entire loading process, when airport loaded completely:
KJFK
KLAS - 28s
KSDF - 40s
KMEM - 60s
KLAX - 34s
LSGG - 39s
LSZH - 38s
CPU at 100% happened only once, and lasted only 1 second.
-
Very simple: Blurries are not a cause but a symptom of a much deeper issue. Blurries are also not a new thing, I've heard of them already 10 years ago but I never experienced them till now.
That's what I tried to explain since this thread started but, but soon enough started all posts saying "I never had blurries before, then I installed GSX L2, and so they started, I uninstalled GSX L2, they disappeared, it *must* be GSX L2"
Which I do believe, but with all the evidence we are gathering, it seems the way they happen seems different for everybody.
I fear we are running into some kind of limitation, after that the sim starts to display blurries. I'll try to make a simple as possible example, to explain why this can be easily connected to GSX L2, without this being a problem or something wrong we are doing.
- Suppose you are already 95% close to your own blurrines limit. If replaced SODE jetways are impacting for more than 5%, you'll pass this threshold, and get the blurries. You uninstall GSX L2 or stop it from replacing jetways, you are back at 95%, you are fully convinced "it was GSX's fault", but this will last only until you install the NEXT addon, at least one that would cause a similar effect of a least 5%.
- If you are only 80% close to your own blurrines limit. You will not see any blurries.
- If you start from a clean P3D install, install some addons and/or raise settings too much, you can eventually reach your own blurrines threshold, even without installing GSX L2. This is what might have happened in Post #254
- You were at 95%, and crossed over 100% (thus getting the blurries) after installing GSX L2 but, after my suggestion of removing those folders related to some FSDT sceneries in the Addon Manager\Couatl folder, you reduced GSX L2 impact from, let's say, 8% to 3%, so you are now back under 100%, so this fix worked for you.
I'm trying to offer an explanation that is compatible with ALL your reports:
- Those that don't have blurries
- Those that have them after installing GSX L2 and fix them by uninstalling it or disabling the replaced jetways
- Those that fixed the blurries use GSX + replacement jetways by doing the removals I suggested.
-
So what I get you saying then. We are out of luck and should not use GSX 2 then if it is pushing us over the threshold (for me using default gateway stops the blurries). I bought this for the gateways and not the people. I know you could not predict this happening, although I am surprised with so many reporting it that a beta tester never experienced it. I guess a refund for my $40.00 is out the question. Oh well maybe down the road someone will find a solution.
Thanks,
-
although I am surprised with so many reporting it that a beta tester never experienced it.
That alone should indicate is not happening to everyone in the same way.
I guess a refund for my $40.00 is out the question. Oh well maybe down the road someone will find a solution
Don't think for a moment we are done investigating.
I'm just trying to make it clear to everyone the conditions under we are working right now, with multiple conflicting reports, both about the very existence of the problem, but also how different for everybody our various proposed solutions are.
Someone reported this happens ONLY (on his system), if jetways starts to move. That's the only part which is done entirely outside our software. We create the jetways as static, when you press the GSX menu to "Operate" them, we replace the static jetway with the dynamic version, but we still don't move it. Then, we pass control to SODE, which will do the *actual* animation of the jetway.
Others reported it was enough to overfly an airport with replaced jetways (which are all static at that point). This conflicts (or debunk, your choice), the above theory of a supposed problem related to animating jetways.
Some reported my proposed fix or removing the various files under the Fsdreamteam\Couatl folder fixed the issue for them. This seems to confirms the previous theory of the jetways themselves being a problem, even if they are just created because, without going in too long explanations, removing those files has *ENSURED* NO jetways are ever created when flying over 10K feet.
But then, somebody else said this fix didn't do anything for him, conflicting with this last theory as well.
-
Just did a flight from EKCH with GSX2 jetways (ini file) and got severe blurries after about 10 minutes, CPU at 99-100 % (pics attached)! Eventually the aircraft textures load up but the ground never loads. If I uninstall GSX2, everything is fine. No blurries, no stutters.
-
Just did a flight from EKCH with GSX2 jetways (ini file) and got severe blurries after about 10 minutes, CPU at 99-100 % (pics attached)! Eventually the aircraft textures load up but the ground never loads. If I uninstall GSX2, everything is fine. No blurries, no stutters.
So, your are possibly in this camp:
Suppose you are already 95% close to your own blurrines limit. If replaced SODE jetways are impacting for more than 5%, you'll pass this threshold, and get the blurries. You uninstall GSX L2 or stop it from replacing jetways, you are back at 95%, you are fully convinced "it was GSX's fault", but this will last only until you install the NEXT addon, at least one that would cause a similar effect of a least 5%.
-
Perhaps, but I have never experienced blurry textures before.. with all the add-ons I have installed! But I honestly have to say I am not an expert and can only report what I see..
Without GSX L2, my CPU is mostly around 40-50 percent in cruise flight...so....
-
well virtuali , what the specification of your machine where you test the GSX L2 and everything gone ok unlike us ?
to compare with mine , so your theory should be correct
-
Perhaps, but I have never experienced blurry textures before.. with all the add-ons I have installed!
That's perfectly compatible with my previous explanation.
Without GSX L2, my CPU is mostly around 40-50 percent in cruise flight...so....
Mine it's about 27% WITH GSX L2, on an FSDT airport with the PMDG 747-400. I already posted a video about this. Another user (See Post #254), posted a video of blurries happening WITHOUT GSX installed, after a clean install.
-
Point taken. Then there must be something specific to my (and other people's) setup that is conflicting. Finding out what this conflict is, is probably like looking for the proverbial needle in a haystack..
Incidentally, when I try to shut down P3D at this stage (with blurries, as in the pics I posted) it just hangs and I have to forcibly close it.
-
In doing some testing today, I find that, on my system at least, I don't get any blurries at all if I don't use the GSX jetway or pushback. Once I connect and retract the jetway, OR use the GSX pushback, I get blurries on that flight every single time.
I get similar results to the video you just posted, Umberto, until I operate a GSX installed jetway. I notice in the video you don't operate any jetways. Once I do that, loading becomes very very slow. Do you see results similar to the video once you have operated a GSX2 jetway, or done a pushback?
-
Where is the 2k, 1k jetways? I would like to test it. My blurries are very selective, they only appear with GSX jetways.. I can take off from any airport such as LFPG with like 50 sode jetways but I can't do the same in SBSP wich I put only 1 GSX sode jetway.. How is that possible? It has to be a reason..
-
I just started with GSX2. Like many I also have the blurry problem in P3Dv4.3 and FSX (I tested to see if there was a difference). I have no FSDT airport.
-What I have noted in various tests is blurries only occur when I used a Jetway before a flight.
-If I don't use jetways the flight happens without blurries.
-I did the tests with the same KPDX/KGEG flight plan.
-ORBX Global, Open LC NA, Open LC Europe, Vector, Ezca2, AS for P3Dv4/AS16, Little Navmap, FSUIPC 5.14 (bought), Open Hardware Monitor. Config in my signature.
Thank you and Regards,
Richard
-
Where is the 2k, 1k jetways? I would like to test it. My blurries are very selective, they only appear with GSX jetways.. I can take off from any airport such as LFPG with like 50 sode jetways but I can't do the same in SBSP wich I put only 1 GSX sode jetway.. How is that possible? It has to be a reason..
Yeah, if I restore default jetways or fly from an airport without GSX jetways, everything is fine again. Perfectly crisp textures.
-
You have to consider that things are more complicated than that. There's no guarantee that every test performed by the users are standardized: what if the ones who reported not having the issue (or not anymore) made the right test? What if the've flown a city-pair that's not affected by the bug?
Also, I'd like to understand what is the point of removing those FSTD airports, if I fly another city-pair away from them, how could they be the cause of the issue if you told that when one is far away from the airports/objects they're not loaded into memory whatsoever?
-
Unfortunately this users test with stuff that has already issues with blurriness ;-) ORBX Barcelona ;-)
Ok tested again today from a fresh downloaded FSDT LSGG and FT EHAM and now with EZDOK instead of chaseplane...
Start of the flight including GSX 2 stuff wend fine, however approaching EHAM I had one blurry mesh not the normal blurriness but just the whole sim timed out...
Stutters when overflying airports with default jetways huh, never had this before it seems there is some sort of memory leak here at play...
Maybe the combo FSLABS A319 and GSX... Going to test tomorrow with another aircraft same flight...
-
In doing some testing today, I find that, on my system at least, I don't get any blurries at all if I don't use the GSX jetway or pushback. Once I connect and retract the jetway, OR use the GSX pushback, I get blurries on that flight every single time.
This is what I have noticed when I tested all afternoon. No matter what steps I've tried that I've found in this thread, nothing seemed to solve it, and in each case, I was always pushing back from gate 36 at JFK Terminal 4 via GSX. By 30 minutes into the flight, there was no hope for the textures, it was just completely blurry. Only when I started the flight from runway 4L and took off straight away did I manage to fly without having issues with the texture being blurry.
-
Sadly today I got the blurries problem.... even after the update. Still works to be done :) :) :)
-
Tried that, doesn't happen here.
I'm loading the following sceneries, one after the other. This is how much time took to load each one, from pressing OK after selecting the ICAO, two the end of the entire loading process, when airport loaded completely:
Oddly, I was able to recreate the same sequence you show in the video without issue. But then if I go to KJFK, spot 803, after LSZH, I still get the same lockup at 36% on the loading progress with 5 of the 8 LPs (the main thread on LP0 and all four of the texture/terrain LPs 4-7) at 100%. I never see the entire CPU at 100%, but watching the LPs rather than the overall CPU load yields some interesting additional detail.
Regards
Bob Scott
-
Flew from MSP to SDF in the PMDG 747 at sunset after GSX loaded the cargo. Had a short stutter session as I flew near Chicago, but they were brief and insignificant. Landed with no blurries, simply experienced some SDF loading stutters on approach.
Rebooted the system.
Loaded AS319 pro at a generic airport that had 4 GSX replaced jetways. Chose a location in the middle of desert essentially. Started on the runway, flew straight out, FL300. Blurries not long after reaching cruise. GSX 2 loading the SODE jetways not generic.
Used GSX CP to load default jetways. Started the same flight. Blurries occurred with the same timing and intensity.
Will try same flight tomorrow with addition of RTT disabled.
-
Got this problem too for all flights after updating to Level 2
Tried the solution provided, clearing the shaders cache, disable RTT, restore to default jetways, lowering texture quality. Nothing worked...
Tried a flight today at RJAA using PMDG 777-300ER, CPU usage was fine at around 20-30%. Didn't even tried to board passengers using GSX. After requesting push back, CPU usage ran off the roof. All cores at 100%. Airport texture became black, couldn't load aircraft texture. Tried refreshing Scenery Library, the game stuck at loading.
CPU: i7-4790 3.6GHz
Display Card: NVIDIA GeForce GTX 1060 3GB
*Same setting in the sim worked perfectly before Level 2.
**Tbh, I'm very disappointed, I can't even do any flights after Level 2
-
So my issue with high CPU load at KJFK appears to be the result of the P3D Content or Scenery installer re-installing the TrafficAircraft.bgl file into \scenery\world\scenery.
It had been disabled (renamed to .off) when UtLive was first installed (on P3D v4.1, IIRC). Strangely, even though all of the traffic sliders in P3D were at zero, having this traffic bgl active together with UtLive and GSX (v1) brought the CPU to it's knees when reloading at JFK. After removing it, the CPU only loads up for a few seconds at the 36% point and then progresses.
No idea if this could be "a" culprit, or "the" culprit behind the blurry issues, but it might be worth checking even if you're not seeing the problem...I'll bet other folks have done module upgrades and missed that file getting reactivated. I think users of MyTraffic also disable that bgl.
Regards
Bob Scott
-
So my issue with high CPU load at KJFK appears to be the result of the P3D Content or Scenery installer re-installing the TrafficAircraft.bgl file into \scenery\world\scenery.
It had been disabled (renamed to .off) when UtLive was first installed (on P3D v4.1, IIRC). Strangely, even though all of the traffic sliders in P3D were at zero, having this traffic bgl active together with UtLive and GSX (v1) brought the CPU to it's knees when reloading at JFK. After removing it, the CPU only loads up for a few seconds at the 36% point and then progresses.
No idea if this could be "a" culprit, or "the" culprit behind the blurry issues, but it might be worth checking even if you're not seeing the problem...I'll bet other folks have done module upgrades and missed that file getting reactivated. I think users of MyTraffic also disable that bgl.
This does not appear to have solved it in my case.
-
Tried the solution provided, clearing the shaders cache, disable RTT, restore to default jetways, lowering texture quality. Nothing worked...
Please try the last solution I posted here about removing some files in the Fsreamteam\Couatl folder, if you have them:
http://www.fsdreamteam.com/forum/index.php/topic,18564.msg130312.html#msg130312
-
Used GSX CP to load default jetways. Started the same flight. Blurries occurred with the same timing and intensity. Will try same flight tomorrow with addition of RTT disabled.
I don't think it would make any difference. RTT only does Jetwaynumbers on replaced SODE jetways so, if you are flying with default jetways, they are not even there, unless you are flying only through airports you replaced all jetways manually.
-
hello,
Here are my findings after trying at several airports (with 1 to more than 10 jetways) with several aircrafts
A. generic aiports
disabling GSX jetways: no blurries at all
enabling GSXjetways:
1. using jetways or pushback at parking spot with jetways: just after starting these actions, texture loading of AI aircracft very slow, micro stutters, few minutes after take-off blurries appear
2. starting on the runway : no blurries
3.using parking spot with no jetway, loading passengers, pushback: no problem with texture load GSX, AI aircraft, no blurries
B:third party addons airport with sode jetways : no blurries at all
-> seems that only the parking spot with GSX jetways are causing troubles. otherwise product is great. hope you will find solution
regards
Xavier
-
disabling GSX jetways: no blurries at all
Another two conflicting reports, see here post #294 from Ken:
http://www.fsdreamteam.com/forum/index.php/topic,18564.msg130551.html#msg130551
Tried the solution provided, clearing the shaders cache, disable RTT, restore to default jetways, lowering texture quality. Nothing worked...
Which is highly frustrating. The more reports we are getting, the more it seems that for SOME users like you, replacement jetways might be the problem, but in Ken's case, it might be something else entirely.
-
Which is highly frustrating. The more reports we are getting, the more it seems that for SOME users like you, replacement jetways might be the problem, but in Ken's case, it might be something else entirely.
Frustrating indeed, but this is definitely the trigger for blurries in my case
-
Where is the 2k, 1k jetways? I would like to test it. My blurries are very selective, they only appear with GSX jetways.. I can take off from any airport such as LFPG with like 50 sode jetways but I can't do the same in SBSP wich I put only 1 GSX sode jetway.. How is that possible? It has to be a reason...
If texture size are the issue, fact an airport has 50 jetways (which are likely using the same textures) won't be a problem if they are small. A couple of users tried reducing the texture size themselves, and reported no change.
However, if you want to try, here's two sets of textures at 1K and 2K for the default replacement jetway, and all the Thyssen-Krupp Steel family:
2K
https://www.dropbox.com/s/l7w5e34pm2684qr/jetways_TB_2k.zip?dl=0 (https://www.dropbox.com/s/l7w5e34pm2684qr/jetways_TB_2k.zip?dl=0)
1K
https://www.dropbox.com/s/xkhh6tadkstvqdf/Jetways_TB_1K.zip?dl=0 (https://www.dropbox.com/s/xkhh6tadkstvqdf/Jetways_TB_1K.zip?dl=0)
Place either set into this folder:
Addon Manager\Simobjects\Misc\FSDT_SODE_Jetway_static\TEXTURE
-
When I "restore default Jetways" my blurries go away.
-
When I "restore default Jetways" my blurries go away.
That's precisely my point, it's clearly different for everybody, see last post here:
http://www.fsdreamteam.com/forum/index.php/topic,18564.msg130575.html#msg130575
-
Ok i will try 1k texture
-
Hi Umberto
This is my test
Airport ZWWW (Default) Gate 9 PMDG737-800
T / O Rwy07 imm right hdg 180 then VOR 115.70 R160 outbound FL150
After 25-30 minutes:
1) Jetway GSX2 activated and used (At least hook and release) blurries
2) Jetway GSX2 activated and NOT used NO blurries
3) Jetway default NO blurries
Cache shader and scenery index clean
RTT disabled
Greetings
Luigi - PVI Italy
-
Just to clarify it again: When I reported deleting the folders solved my issue, I was testing at KIAH. When I tested it at EDDK with the folders removed, the issue occurred. So basically that trick did not resolve the blurries.
It seems to me to be related to the jetways at the departure airport (as many people including myself already reported).
enabling GSXjetways:
1. using jetways or pushback at parking spot with jetways: just after starting these actions, texture loading of AI aircracft very slow, micro stutters, few minutes after take-off blurries appear
That is quite interesting because we may can narrow down the moment it happens (hence the things in the code which happen). I also had the idea that the cause of the issue starts earlier, just because it has the area around the airport already loaded, we only see it later when P3D wants to load something new (like sharper textures, autogen, other sceneries).
disabling GSX jetways: no blurries at all
Another two conflicting reports, see here post #294 from Ken:
http://www.fsdreamteam.com/forum/index.php/topic,18564.msg130551.html#msg130551
Tried the solution provided, clearing the shaders cache, disable RTT, restore to default jetways, lowering texture quality. Nothing worked...
Which is highly frustrating. The more reports we are getting, the more it seems that for SOME users like you, replacement jetways might be the problem, but in Ken's case, it might be something else entirely.
I'm commercial software developer, too, and I experienced a lot of very weird things in my career. In my view we should follow the people who can narrow it down to a certain moment. At least for those people we have precise clues of the moment it is happening. Maybe the other users have a totally different cause, maybe it's the same cause, just do to different systems specs it appears differently. There are a lot of things in the background that can go wrong in many different ways.
-
2) Jetway GSX2 activated and NOT used NO blurries
Did you do a pushback with GSX or did you depart without any GSX request/service?
-
Hi,
Without push back and no any GSX request except Operate Jetway to speed up the test
Greetings
Luigi - PVI Italy
-
You do not get blurries if you have GSX installed +level 2 and don't use it, but if you use GSX you get blurries
-
First of all Ciao to everybody,
I am on FSX-Stem under win10 and GSX L2 intalled. Unfortunatly I am experienced massive blurries and FSX freezes.
I have done 3) test flights to undestand if the blurr was due to my fsx setup, of course i deleted from couatl KFLL and KDFW(demo) as requested.
I disableed all non stardard airport and everything not related to Europe (I use Simstarter) to avoid any OOM and to be lite on scenery complexity.
I install only 1 GSX L2 jetway at EIDW gate 302, PMDG 737 was the airplaner used.
Take off from 28 then 360° turn to be able to reach the famous 10000 feet still in the airport range to check for blurr with all the airport texture still loaded, then heading east vs Wales over 60 miles of water to provide same relief to the system in terms of loading textures.
1) Start at Gate 302 (the one with the GSX L2 jetway) didn't use any GSX facility and didn't dock the jetway.
No Blurries everything fine, stop the test when reaching France.
2) Start at Gate 301 (No jetway) used GSX boarding and Pushback (used only 20 passenger but was nice watching them going from the bus to the aiplane)
No Blurries everything fine, stop the test when reaching France.
3) Start at Gate 302 used GSX only to dock and undock the GSX L2 jetway, no memory of fps impact.
Blurries starts around 10000 feet but I was still in the airport range. Then I was over the water toward Wales. I was monitor the VAS and all memory allocated to the airport was correctly realeased at this point Couatl should have been already disconnected GSX. When I reach Wales cost the first terrain texture were fine but after a few seconds every starts the blurries ... massive blurries and FSX start to get mad!!!
What to says?!
For me the GSX L2 docking system has problem, same how keeps loading the CPU in such a way that the CPU cannot fullfile the usual tasks.
I have a question.... sorry for say that Virtuali... but ... are you sure that you have not adopted some software protection to avoid people to steal GSX L2 sode parameters and it keeps running overloading our CPUs?
Regards, Roberto
-
Just a quick question, do you have the whole simulator folder excluded from the antivirus, in addition to the Addon Manager folder ?
And, if you have other sceneries installed outside the simulator, for example in a big separate drive, have you disabled these folders from antivirus scanning as well ?
That's how I always run my sim and, some users a while ago reported extremely slow loading time of our files (the airport cache regeneration taking several minutes instead of seconds).
It might be worth checking.
-
I have a separate FS computer without any antivirus.
-
Same the antivirus has Nothing to do with the issue, i think this guy is right:
What do you guys think?
-
Same the antivirus has Nothing to do with the issue, i think this guy is right: What do you guys think?
That's the reason for my antivirus question, because it *can* affect this. But yes, he gave me an useful hint, I'll try to prepare something new to test.
-
Just a quick question, do you have the whole simulator folder excluded from the antivirus, in addition to the Addon Manager folder ?
And, if you have other sceneries installed outside the simulator, for example in a big separate drive, have you disabled these folders from antivirus scanning as well ?
That's how I always run my sim and, some users a while ago reported extremely slow loading time of our files (the airport cache regeneration taking several minutes instead of seconds).
It might be worth checking.
everything excluded - FS main folder, sceneries on separate drive, addon manager.. the lot
-
Used GSX CP to load default jetways. Started the same flight. Blurries occurred with the same timing and intensity. Will try same flight tomorrow with addition of RTT disabled.
I don't think it would make any difference. RTT only does Jetwaynumbers on replaced SODE jetways so, if you are flying with default jetways, they are not even there, unless you are flying only through airports you replaced all jetways manually.
I understand. I'm just trying anything/everything to see if anything/something has an affect.
For me, it doesn't appear like a typical resource blurry at all. Once the textures, autogen and terrain stop loading they don't come back like normal. I've paused the sim and walked away for 45 minutes and come back to marginally better terrain tiles, but still blurries and no autogen.
This is beyond a head scratcher...
-
"I understand. I'm just trying anything/everything to see if anything/something has an affect.
For me, it doesn't appear like a typical resource blurry at all. Once the textures, autogen and terrain stop loading they don't come back like normal. I've paused the sim and walked away for 45 minutes and come back to marginally better terrain tiles, but still blurries and no autogen.
This is beyond a head scratcher..."
Yes, the auto gen cannot load at all as the CPU is stuck on 100% loading something or processing something, but what?!?!
-
right, same experience here, it's a very strange problem. Has anyone tried the 1K or 2K textures that Umberto provided links to on the previous page? I'm just about the try them..
-
"I understand. I'm just trying anything/everything to see if anything/something has an affect.
For me, it doesn't appear like a typical resource blurry at all. Once the textures, autogen and terrain stop loading they don't come back like normal. I've paused the sim and walked away for 45 minutes and come back to marginally better terrain tiles, but still blurries and no autogen.
This is beyond a head scratcher..."
Yes, the auto gen cannot load at all as the CPU is stuck on 100% loading something or processing something, but what?!?!
Can I just say: although this problem is deeply frustrating for all of us affected by it, I do appreciate the effort that the developer is obviously going to in trying to solve it. And it's wonderful that we can all exchange experiences on this forum in a civilised manner (mostly). Just wanna say...
Hope the root of this can be found soon. It would be an awful shame if not, because otherwise GSX Level 2 is amazing. It has endless potential.
-
a heads-up:
Someone just posted over on Avsim:
https://www.avsim.com/forums/topic/541722-blurries-out-of-nowhere/?do=findComment&comment=3896653
Anyone tried this? I'm actually not quite sure what he means..
-
I've made another small tweak to the Addon Manager .dll I posted earlier, adding a new optimization. Like before, place it in the Addon Manager root, to overwrite the existing file:
64 bit
http://update.fsdreamteam.com.s3.amazonaws.com/setup/fsdtroot/bglmanx64.dll
32 bit
http://update.fsdreamteam.com.s3.amazonaws.com/setup/fsdtroot/bglmanx.dll
-
Ok lemme try
-
Which bit do i use for FSX?
-
Unfortunately no change :(
-
Which bit do i use for FSX?
32bit
-
Unfortunately no change :(
We are starting to exhaust all the options related to our software. Is it fixed if you restore default jetways ?
-
No, unfortunately this didn't make any difference. And I also tried with 1K jetways + the new bglmanx64.dll...
Do you think it could be related to the boarding passengers? Perhaps the CPU power required to calculate this causes the problem. I find that when the passengers start boarding, there are regular freezes for a second or two at a time, which last for about a minute, until around 40 or so passengers have boarded. After that, the textures go blurry and the autogen doesn't load (I can just test this by jumping to an AI aircraft near the airport - with default jetways enabled, everything loads quickly).
-
Do you think it could be related to the boarding passengers?
That would be easy to try: just dock/undock a jetway, without calling boarding/deboarding.
I based this change on a recent report that it was enough to operate jetways to trigger the blurries and, in fact, found a place where I could optimize this. But, apparently, that's not the issue. I'll await further reports though.
-
Loaded up MEM with the new dll, major stutters on take off, nothing loaded outside of the initial airport surrounding load. No new autogen, textures etc...
-
Hi,
Big problem for me too. P3dv4 unplayable since I installed GSXLEV2.
many textures take a lot of time to load. including that of my plane.
this while the frame rate is good (around 50 FPS)
when I change the view, the previous textures disappear and then put 40s to reload.
is it possible to find gsx just before level 2? because p3d has become unusable since gsxl2...
Try this: bglmanx64.dll
Not work
I decrease the graphical parameters
not work
1k texture... not work...
-
unfortunately did not change. still blurries :-\
-
Loaded up MEM with the new dll, major stutters on take off, nothing loaded outside of the initial airport surrounding load. No new autogen, textures etc...
Tried that too and, I don't see any problems whatsoever taking off from KMEM with the PMDG 747. Sorry for my crappy hand-flying:
I take all your reports seriously, which is why I'm constantly trying to new things. If only I was able to reproduce it...
-
unfortunately did not change. still blurries
Ok, let's try another route:
Start the SODE Platform Manager when the sim is not running, and select "Unregister", to temporary disable it. Jetways won't move, but everything else will be the same.
-
is it possible to find gsx just before level 2? because p3d has become unusable since gsxl2...
Please read the previous posts. If you restore default jetways, GSX will work as it was before.
-
Do you think it could be related to the boarding passengers?
That would be easy to try: just dock/undock a jetway, without calling boarding/deboarding.
I based this change on a recent report that it was enough to operate jetways to trigger the blurries and, in fact, found a place where I could optimize this. But, apparently, that's not the issue. I'll await further reports though.
OK - so I did this test: I parked at a remote stand at EKCH (FlyTampa), GSX jetways active, new bglmanx64.dll, 1K jetway textures. During boarding, there is some stuttering. If I jump to an AI aircraft while the passengers are boarding, the textures take a while to reload (that's understandable really). The main point is that the textures - both autogen and ground - DO reload eventually. And I get crisp ground textures, no blurries.
Can someone else test this? Remote stand, board passengers using bus with GSX L2.
Chris
EDIT: I tried this again - all textures load perfectly. No blurries. So - for me - it is most definitely a question of actually USING the jetways. They can be active, but mustn't be actually extended. Perhaps it has something to do with boarding the passengers through the jetways. I will try just moving the jetways but not boarding passengers. Maybe something else can also try this.
EDIT#2: I was wrong.. about 15 minutes into the flight, the textures stop loading and it gets blurry. ORBX textures (Germany North) don't load at all (pic attached). Damn it !!! And this is without using the jetways! OMG...
-
unfortunately did not change. still blurries
Ok, let's try another route:
Start the SODE Platform Manager when the sim is not running, and select "Unregister", to temporary disable it. Jetways won't move, but everything else will be the same.
I've tried. unfortunately unchanged
-
They can be active, but mustn't be actually extended. Perhaps it has something to do with boarding the passengers through the jetways. I will try just moving the jetways but not boarding passengers.
Yes, that might be useful to try, and I think I suggested this too: just operate jetways (dock/undock), without boarding/deboarding.
-
They can be active, but mustn't be actually extended. Perhaps it has something to do with boarding the passengers through the jetways. I will try just moving the jetways but not boarding passengers.
Yes, that might be useful to try, and I think I suggested this too: just operate jetways (dock/undock), without boarding/deboarding.
Will try this: see my last post (EDIT#2) for more info on the question of jetways...
-
Ok, here something different.
I had massive problems with NVIDIA,
De installing 399.24 and goeing back to 382.05 seems to help for others.
Since I am not at my PC, but working at Europes friendliest Airline at the moment, can somebody try this?
The driver was updated around the release of GSX V2.... ;)
-
Ok, here something different.
I had massive problems with NVIDIA,
De installing 399.24 and goeing back to 382.05 seems to help for others.
Since I am not at my PC, but working at Europes friendliest Airline at the moment, can somebody try this?
The driver was updated around the release of GSX V2.... ;)
Not for me running stable for a long time 388.59 8)
I'm thinking more and more that it has something to do with the jetway system either GSX2 or SODE...
-
unfortunately did not change. still blurries
Ok, let's try another route:
Start the SODE Platform Manager when the sim is not running, and select "Unregister", to temporary disable it. Jetways won't move, but everything else will be the same.
Didn't help, still blurries. I'll update my Nvidia driver now, I'm on an "old" version as last year there was a memory leak which affected my PC.
-
Didn't help, still blurries. I'll update my Nvidia driver now, I'm on an "old" version as last year there was a memory leak which affected my PC.
No change with the latest Nvidia driver :(
-
One thing we haven't seen much of in this discussion is the configuration and operating conditions of regular folks that are using GSX v2 without problems. Umberto's system is going to be devoid of most of the other commonly-used programs we all use, which makes sense for a test environment, but it doesn't have a good probability of reproducing a problem arising from an unhappy interaction because of its relative sterility.
Regards
Bob Scott
-
Having the same issues from my end here.
GTX 1080 TI
i7-8700K
Any aircraft, anywhere I fly -10-15 min after departure blurries all over the place.
-
Yes, all my tests have been done with the whole simulator folder and the Addon Manager excluded from the antivirus.
Roberto
-
+1
i7-8700k + GTX 1080ti
-
Maybe we should look in the direction of memory.
I red somewhere that the fellow having no problems have 32gb ram. I've only 16.....
And if the cpu turns up and we gt blurs it can be some memory issue.
-
I don't think so. FSX is a 32bit application and can only address up to 4MB . When the Blurries appears I still have more then 1GB of spare memory and let me say it' a lot of memory.
Roberto
-
I have 32GB of memory.
I am flying RJAA to KDEN at the moment.
P3D is running at about 20-25% memory.
My CPU has been constantly at 100% during 9hrs of flight until this moment.
-
I am one that have not being seeing any of these anomalies yet and i have almost every FSDT airport and all FTX ORBX regions etc.
I will not claim i have tested anything or everywhere but at Memphis (which is an amazing airport btw on a GTX1080TI in 4K with all shadows to the right) with PMDG747 and B717-200 by TFDI i have no issues . Stayed at the airport for almost 3 hour with high /ultra settings.
Nvidia driver is 399.07
Thanks
Michael Moe
-
Can someone do a test: dock your plane at a GSX2 jetway, extend the jetway, BUT DON'T BOARD ANY PASSENGERS. Retract jetway, push back and start the flight. Do you get blurry textures etc. in this situation? I can't test right now, since I'm working, but I will do later.
Chris
-
I red somewhere that the fellow having no problems have 32gb ram. I've only 16.....
I do have 32GB. With P3D4, the more, the better.
-
32 GB RAM with P3D v3. VAS usage is at 2.2 GB.
-
Do you think it could be related to the boarding passengers?
I've had the issue without even touching the jetways. All I used was the GSX pushback, and that was enough to have problems.
-
32 GB RAM with P3D v3. VAS usage is at 2.2 GB.
32 GB with P3D (32 bit) is completely useless.
-
Not really, there's a nice thing called RAM Disk - Way faster than a SSD.
-
I've made another small tweak to the Addon Manager .dll I posted earlier, adding a new optimization. Like before, place it in the Addon Manager root, to overwrite the existing file:
64 bit
http://update.fsdreamteam.com.s3.amazonaws.com/setup/fsdtroot/bglmanx64.dll
32 bit
http://update.fsdreamteam.com.s3.amazonaws.com/setup/fsdtroot/bglmanx.dll
-
Not really, there's a nice thing called RAM Disk - Way faster than a SSD.
Still way slower than the application being able to access RAM directly, instead through all the overhead of the Windows filesystem.
-
Do you know what a RAM Disk is? You use a certain part on your RAM as a hard drive. Access times are way shorter than a SSD, you typically use this for your most often used sceneries. The only drawback is, a script needs to copy sceneries to the drive each time after startup, because of course the RAM gets lost after shutdown. I made tests, loading times of sceneries are around 4 times shorter than with my SSD.
Before you ask: I tested it also without RAM Disk, it doesn't affect the blurries issue.
-
Do you know what a RAM Disk is? You use a certain part on your RAM as a hard drive. Access times are way shorter than a SSD
I know very well what a RAM disk is, using them since the 80s when you use to configure RAMDRIVE.SYS in your CONFIG.SYS file.
However, while a RAM disk is faster than an SSD, that's besides the point. You implied with a RAM drive you could make use of all your memory with a 32 bit application, as if it were real memory. It's not: because, as you said yourself, is like an "hard-drive", so each since file access will have to go through the normal Windows NTFS fileystem, with the same overhead of directory access, opening/closing files, etc. Real memory, only possible with 64 bit apps, it's another thing entirely.
So yes, maybe 32 GB on a 32 bit app is not *entirely* useless, but it's still a waste, and not a replacement for a 32 bit apps. And a ram disk won't save you from OOMs, of course.
But this is really off topic. Please stay on the thread subject.
-
I think you didn't get what I meant initially. You are 100% right, I never said it has something to do with the RAM the application can use. You said 32 GB are useless on a 32 bit application. Well that's true regarding the RAM itself (the space the app gets) but not concerning the RAM Disk. RAM got so cheap, so why buying 16 GB when you get 32 GB for 20 more bucks?
So I simply assigned 16 GB as a RAM Disk where I put my most often used sceneries on. The "only" advantage is that the sceneries are loading way faster (the ones on the RAM Disk) because P3D can access the files faster. I never said I don't get OOMs (I got OOMs last year with that Nvidia driver memory leak) and I never said P3D gets more than those magic 3.x GB of VAS. My point was just that 32 GB are not useless ;-)
-
I have not seen a change.
-
I have not seen a change.
Nothing, as in ZERO difference ? That's odd. The only possible explanation of not seeing any difference, is that code was already very well optimized, that optimizing it further results in improvements that cannot be appreciated.
-
Hi,
I have disabled all FSDT sceneries via addon manager in P3D
I did a flight this afternoon LFPG (Taxi2gate), just using jetwasys, but no assenger loading to KIAD. My route arrived over USA over JFK. Dpetarture from LFPG and flight over south of UK without any problem.
Just when I arrived over JFK, P3D stuck for about 7 minutes, with CPU usage about 100%, goeing down to 85, then up to 100. After this, no blurries.
About 60 miles after JFK, just before my TOD, second stop of P3D, very less CPU usage (about 60 to 65%), and after this stop, blurries....
Memory usage 8 to 10Go (I have 32Go)
I also think there is a problem of memory, because the blurries appear exactly as they appered in the 32bits version of P3D.
Next test : I went to the scenery library, unchked a scenery, far away from KIAD, and Oh surprise, got a perfect scenery after that... Just on fianl at this time.
Yves from ELLX
-
I have disabled all FSDT sceneries via addon manager in P3D
Nobody suggested to do this. I've posted many suggestions, but not this one. The thing that *seems* to be common about this problem, is having used SODE jetways. Do you see any difference if you restore default jetways with the GSX Control Panel ?
Have you tried the updated .DLLs I posted earlier ?
-
Just unisntalled GSX completely and the blurries still occur...
-
I only used the sode jetways provided on LFPG. No others.
I run a live update at noon, just before begining my flight.
Correction : after landing, pour textures, black IA planes and black GSX trucks...
-
I have disabled all FSDT sceneries via addon manager in P3D
The thing that *seems* to be common about this problem, is having used SODE jetways.
Not necessarily. My issues are related to airports that GSX has been used to modify in some way or are fsdt produced, even if the default jetways are restored and even if i don't trigger anything GSX related at all.
Trying the new dll.
-
Just unisntalled GSX completely and the blurries still occur...
Have you also replied YES to the question "Do you want to remove the Addon Manager ?" That would remove our software entirely from the system.
-
Just updated : dll for today 14:57 and 15:20
I will reactivate fsdt sceneries
Will try a night flight..
-
Have you also replied YES to the question "Do you want to remove the Addon Manager ?" That would remove our software entirely from the system.
I relpied "No" Because I have other FSDT products installed. Do you suggest uninstalling everything including the addon manager?
I tried the new .dll file but no success.
-
Sorry, new .dll looks like this
-
I relpied "No" Because I have other FSDT products installed. Do you suggest uninstalling everything including the addon manager?
Just disable it from the Options->Add-on menu.
-
Can someone do a test: dock your plane at a GSX2 jetway, extend the jetway, BUT DON'T BOARD ANY PASSENGERS. Retract jetway, push back and start the flight. Do you get blurry textures etc. in this situation? I can't test right now, since I'm working, but I will do later.
Chris
I have done that quite a few times.
At IAH, I get slow loading textures but no blurries
At SDF, I always get slow loading textures, studders and eventual blurries. If I take off and turn back to the airport, the airport is black. When I load SDF, the whole airport is missing. Eventually, the buildings and runway lights load and then the runway textures appear to load on top of the runway lights.
At MEM, I get slow loading textures. I have not tested a flight out of MEM yet.
I did take off from JFK with the QW 787 and flew towards Manhattan. Aside from reduced FPS, no issues. I even tried this with the F22 at high speed just above the ground. Everything was cool.
These test have been done with default jetways restored and disable RTT checked.
I have also done flights starting on the runway (no services and ones were I started at the gate but did not use any services - all at SDF
Windows7, 4790k@4.4, 1080TI, 16GB RAM, P3DV4
-
ok.. I guess that rules out that one then. Sounds to me like a problem with the actual module (couatl). Or something else. Who knows! Umberto must be really frustrated, poor man... I'll patiently wait for a fix, although it's a little disappointing not to be able to use the full functionality of this new version.
-
I have to add my name to the list has well. Only thing I did was update add-on manager.
1. GSX casche takes forever to load.
2. Upon takeooff, I have blurry textures for scenery and aircraft. (similiar to a memory loss)
Michael Thomas
-
Hello,
Count me in, it has to be 100% related to GSX. I was perfectly fine with GSX (updated but without expansion activated), got a a message today to update to new couatl version. I ignored it for the first two flights and after that shutted down the sim to install it.
After installing it I have had several issues which I did not have before.
- AI airplanes and other airport trucks appear black at first and take several seconds to be "normal". When switching views I have to wait again.
- Texture of my aircraft doesn't appear sharp until a few seconds have passed, that is every time I switch views.
- When I get to destination airport I always upload the autogen by changing the slider from high to very high, this normally takes 30s max. After the update it takes some 3 or 4 times more + the new loaded autogen appears with very blurry textures beneath it.
I tried restarting couatl and restarting sim + pc several times with no luck.
Please Umberto do something to fix this or allow to go back to previous version. It really ruins the whole experience.
Thanks
P3D v4
-
is it possible to find gsx just before level 2? because p3d has become unusable since gsxl2...
Please read the previous posts. If you restore default jetways, GSX will work as it was before.
I still see all the symptoms, even disabling the jetways, which render my FSDT airports with totally static jetways. That's why I would like to have GSX v1 back to my system.
-
Please run the FSDT Live Update now. I'm confident it should work much better now.
-
Please run the FSDT Live Update now. I'm confident it should work much better now.
Umberto,
Are you saying we can now disable default jetways again?
-
Yes, go back to normal, with everything.
-
Just did an opcheck and looks like things are normal. Going to do a test flight now. Thank you!
-
Please run the FSDT Live Update now. I'm confident it should work much better now.
Did you find something that might be causing the problems? I uninstalled gsx completely and problems were gone.
I'm going to install again now and run the update, I'll let you know how it works.
-
Did you find something that might be causing the problems?
Yes, I managed to connect to one of our testers that has everything from OrbX installed, made several tests, and we were finally able to see the blurries! They couldn't possibly appear with the default scenery but, with the added load caused by the ginormous number of files added by OrbX, allowed to see the problem.
And yes, it was entirely MY fault: when porting the Addon Manager code from FSX to P3D4, the most difficult part wasn't porting to 64 bit, that was easy, but rewriting lots of code to support Unicode. A single function wasn't converted correctly, and that slowed down the file access, but it could be noticed only if the simulator was already overloaded by other addons.
And no, Couatl and GSX didn't had anything to do with it...it was just a single line of code in the Addon Manager which I overlooked.
-
Please run the FSDT Live Update now. I'm confident it should work much better now.
Looks ok on my side. Thank you! :) :-*
-
Fantastic, thank you very much Umberto!
Installed again and everyting looks good as before the troubles.
I'm glad you could find the cause. Good night.
-
Great Job Umberto..! highly appreciate it.!! :D
-
Congratulations!.... Premiun support! 8)
-
Please run the FSDT Live Update now. I'm confident it should work much better now.
Just tested and indeed, you fixed it. Get some rest. Thank you for all the help. I owe your a beer.
-
Thanks a lot Umberto!!!
Richard
-
Thanks very much for the fix Umberto, I was only having slow texture loading not blurriness but the latest update works great. I think it also reduced the CPU load if I compare it to GSX v1.
-
Yes indeed. Looking good now. P3d even loads a tad quicker. :D
Thanks for your tireless Herculean support.
Clayton
-
Yep, all good here too. Great job Umberto..
-
Brilliant Umberto, well done! I had a feeling you would find it. Thank you!
-
It seems ok
Thanks Umberto
Luigi PVI Italy
-
;D I am crying all my tears of joy reading that you fixed it Umberto (with the help of everybody).
This new GSX feature is so great. :D
Thanks a lot
Dom
-
I knew you could solve this problem
Thanks for your great efforts.
-
Unfortunately I still get blurries on P3D v3 (32 Bit)...
-
Great Job! THX Umberto!!! ;)
-
Thanks very much for the fix Umberto, I was only having slow texture loading not blurriness but the latest update works great. I think it also reduced the CPU load if I compare it to GSX v1.
Yes, it's a bug we had since the first 64 version. But you needed jetways to notice it, because they are created everywhere, not just on an FSDT airport.
-
Yes, it's a bug we had since the first 64 version. But you needed jetways to notice it, because they are created everywhere, not just on an FSDT airport.
Any idea why I still get the problem with P3D v3?
-
Will the update fix FSX?
-
is 4.5.0.6. the latest version?
-
The latest update unfortunatly doesn't work on FSX , still Blurries :'( :'(
Roberto
-
The latest update unfortunatly doesn't work on FSX , still Blurries :'( :'(
Roberto
That's good news for me, that means I'm not alone with my blurries of P3D v3 (32 bit). It seems to have solved the problem for the guys with 64 bit P3D v4 though.
-
Still blurries for fsx :-\
-
i hope us last fsx users don't have to suffer (going to p3d v4 soon so it's not that bad!)
-
You would be surprised to see how many people still cling onto FS2004, let alone FSX.
-
You would be surprised to see how many people still cling onto FS2004, let alone FSX.
Yes.. if it's a question of $$$, I can understand them. Otherwise there is absolutely no reason to stick to FSX anymore.
-
Did you find something that might be causing the problems?
Yes, I managed to connect to one of our testers that has everything from OrbX installed, made several tests, and we were finally able to see the blurries! They couldn't possibly appear with the default scenery but, with the added load caused by the ginormous number of files added by OrbX, allowed to see the problem.
And yes, it was entirely MY fault: when porting the Addon Manager code from FSX to P3D4, the most difficult part wasn't porting to 64 bit, that was easy, but rewriting lots of code to support Unicode. A single function wasn't converted correctly, and that slowed down the file access, but it could be noticed only if the simulator was already overloaded by other addons.
And no, Couatl and GSX didn't had anything to do with it...it was just a single line of code in the Addon Manager which I overlooked.
Excellent news! I have P3D 4.3, and do indeed have Orbx Global textures, NA Landclass and Vector. The global textures probably don’t add any additional load, but I’m sure that Landclass and Vector do.
I just re-flew the flight to KDTW that was causing major performance problems, and it worked perfectly with the new Addon Manager. Thank you for your diligent efforts to get to the bottom of this problem.
-
Can the team fix the issue with fsx? :P
-
Did you find something that might be causing the problems?
Yes, I managed to connect to one of our testers that has everything from OrbX installed, made several tests, and we were finally able to see the blurries! They couldn't possibly appear with the default scenery but, with the added load caused by the ginormous number of files added by OrbX, allowed to see the problem.
And yes, it was entirely MY fault: when porting the Addon Manager code from FSX to P3D4, the most difficult part wasn't porting to 64 bit, that was easy, but rewriting lots of code to support Unicode. A single function wasn't converted correctly, and that slowed down the file access, but it could be noticed only if the simulator was already overloaded by other addons.
And no, Couatl and GSX didn't had anything to do with it...it was just a single line of code in the Addon Manager which I overlooked.
it isn't over yet... still doesn't work for FSX
Excellent news! I have P3D 4.3, and do indeed have Orbx Global textures, NA Landclass and Vector. The global textures probably don’t add any additional load, but I’m sure that Landclass and Vector do.
I just re-flew the flight to KDTW that was causing major performance problems, and it worked perfectly with the new Addon Manager. Thank you for your diligent efforts to get to the bottom of this problem.
-
Please run the FSDT Live Update now. I'm confident it should work much better now.
Looks ok on my side. Thank you! :) :-*
WHAO! wHaO ... good work and well done!
Do we need to reinstall or just run LIVE UPDATE ...?
-
Please run the FSDT Live Update now. I'm confident it should work much better now.
Looks ok on my side. Thank you! :) :-*
WHAO! wHaO ... good work and well done!
Do we need to reinstall or just run LIVE UPDATE ...?
I just ran Live Update, and it worked!
-
???
-
If it's still an issue for fsx, maybe it should have been been called "p3d v4" only
-
i wanna fly :(
-
i wanna fly 😞
ols500
You made like 8 postings in the last two hours. I think they get the message. Even FSDT needs to sleep seeing they were up pretty late from the earlier post working and fixing the problem. The update came out around midnight EST in the US so I know for FSDT in Europe it was extremely late for them.
Sent from my iPhone using Tapatalk
-
Thank you so much for the fix! So this issue was only related to the GSX Level 2 release, correct? Or could have this caused blurries since P3D 64bit?
-
It would appear that it would have been related to the Add-on Manager, so nothing to do with GSX, though running GSX may have exacerbated the problem.
-
Thank you for the great support
Problem solved
Regards
Xavier
-
Right, so could it have caused blurries since the beginning of the 64-bit upgrade of the Add-on Manager?
-
Thank you so much for the fix! So this issue was only related to the GSX Level 2 release, correct? Or could have this caused blurries since P3D 64bit?
you do realise that blurries was around way before gsxv2 even came out, this was a different kind
-
Yes I do. Just making I understand.
-
Thank's al lot. All is OK.
Now, i am tryig a flight throu the Labrador zone. Perhaps, and I hope so, your correction will also correct the CTD problem in this zone.
I tell you when I'll landed at CYYZ.
Yves
-
Perhaps, and I hope so, your correction will also correct the CTD problem in this zone.
You still get that issue? Because I also still get it even after the GSX disabled above 250 kts / 10000 ft fix.
-
it's sad the only fix was for p3d and as soon as p3d players got the fix they stopped getting rage, but then they rage at fsx players to shut up and deal with it
-
it's sad the only fix was for p3d and as soon as p3d players got the fix they stopped getting rage, but then they rage at fsx players to shut up and deal with it
I'm on P3D v3, I think it was only a fix for the 64 bit version (P3D v4).
-
it's sad the only fix was for p3d and as soon as p3d players got the fix they stopped getting rage, but then they rage at fsx players to shut up and deal with it
I'm on P3D v3, I think it was only a fix for the 64 bit version (P3D v4).
I mean V4 ;)
-
Please run the FSDT Live Update now. I'm confident it should work much better now.
Since I did not get the live update message from within the sim, do I need to run the FSDT Live Update from outside P3Dv4.3?. It's updated even if I'm not yet using GSX 2?.
Cheers, Ed
-
Please run the FSDT Live Update now. I'm confident it should work much better now.
Since I did not get the live update message from within the sim, do I need to run the FSDT Live Update from outside P3Dv4.3?. It's updated even if I'm not yet using GSX 2?.
Cheers, Ed
Wouldn't hurt to do it.
-
As a FSX userI think this expansion should be a 64bit only. Too many limitations even with the best effort by Umberto to help and solve the problems
Sent from my iPhone using Tapatalk
-
HI
I am running FSX and experienced the performance problems others have already reported after installing gsx level2. I uninstalled same as well as all of my fsdt airports.
I also cleaned up my fsx config file removing the entry for add on manager. My sim was now running perfectly with tex-max-load of 4096. I then reinstalled fsdt airports and consequently add on manager but did not install GSX. When I checked my fsx config file however I noticed that my Tex-max-load was 1024. I manually changed the value back to 4096. Can you tell me why installing these airports would change my fsx config file this way?. So far with just the airports installed performance is ok but not as good . the fact that most of the airports require gsx installed to run properly is also a problem. Im not installing GSX again until there is a fix for FSX.
Hope the fix comes soon since it appears the culprit has been identified.
Thanks for all your efforts.
Don
-
As a FSX userI think this expansion should be a 64bit only. Too many limitations even with the best effort by Umberto to help and solve the problems
Sent from my iPhone using Tapatalk
If Umberto agrees, i think fsx users should be entitled to a full refund, cbut hopefully not, i'm sure he will fix us fsx'ers!!
-
Hi,
CTD between URTAK and ALSOP...
Yves
-
Simply - the upgrade in my view has not been rolled out in an appropriate manner. Existing users are being forced to take an update which clearly has caused problems with their performance using flight simulator. I am one of those users and I am an experienced flight sim user and also a real world IT technician and data analyst before the FSDreamTeam staff try and insult my intelligence as they have done to other loyal customers raising concerns.
I personally feel that the upgrade cost to add passengers walking around is unfair, targeted at loyal existing customers who play a vital role in the long term development of this software add on, though I appreciate the jetway improvement is part of it. My view is that the SODE jetways should have been the separate add-on.
With regards to the upgrade - as soon as I have upgraded add-on manager and as part of that the GSX part 2 supporting version of GSX, my Flight Sim is stuttering every 60-90 seconds and at least 10-20fps reduction whilst running GSX.
This is simply not good enough and the responses we receive on these forums by staff are quite harsh and abrupt - remember, we are paying customers.
May I suggest there is simply a rollback function to return GSX or add-on manager temporarily to the pre-update format to keep customers satisfied, rather than forcing a partial upgrade/update on customers who are now suffering?
Craig
-
Agree I think we (FSX users) should be entitled to roll back to pre level 2 expansion
Sent from my iPhone using Tapatalk
-
I did a flight today in the morning, and had no blurries, just disabled GSX jetways before knowing that there is a fix now, i will try another one later and will keep inform :) :D
-
Latest update seemed to have fixed my issues in P3D V4.
-
Tommow Umberto should reply as Sundays are his day off👌
-
The recently-implemented update has not only fixed the “extreme blurries” problem on my P3D 4.3 installation, I am also no longer getting a bglmanx64.dll_unloaded silent crash on exiting P3D. That problem has been going on for quite some time (since well before L2) on my system.
-
Thanks for the fix. All good here now.
Darcy
-
Thanks very much for the fix Umberto, I was only having slow texture loading not blurriness but the latest update works great. I think it also reduced the CPU load if I compare it to GSX v1.
Yes, it's a bug we had since the first 64 version. But you needed jetways to notice it, because they are created everywhere, not just on an FSDT airport.
Great work thanks for the fix 8)
-
Umberto:
You are the mannnnnnn - just finished a flight from KMIA - KLGA - P3DV4.3 - 64bit win10 - FSLabsA320X - Orbx - Active Sky - REX Sky Force - Pretty much everything max out except auto gen to normal - AA16x - SS2x - my CPU is at 85-90% & GPU 90-95% no stutters, no blurries - everything is beautiful. The only thing I noticed was the jetway alarm sound when moving into position or away from L1door - their was no alarm sound. But heck we are back to normal . Thank You for all of your efforts and everyone in the Forum community who ran exhaustive test since Sunday 9/9/2018 - I was reading up each day on the results and trying out all the test and was getting the same results as everyone else and now we are back. Thanks again to everyone. ;D
-
it's sad the only fix was for p3d and as soon as p3d players got the fix they stopped getting rage, but then they rage at fsx players to shut up and deal with it
No one is raging against you or FSX users but 8 posting in less than two hours is ridiculous. Your point was made on the first posting. Also, your already asking for a refund before Umberto even has time to address it. Let the man get some sleep seeing he was up very late. Then he can address your concern. Stop blaming P3D users and being so impatient. It hasn’t even been 24 hours since the update.
Sent from my iPhone using Tapatalk
-
The fix didnt help for me. My cpu still hits 70 to 99% while using P3D v4. My computer never hits more than 50% using P3D and my FSGlobal textures are suffering as well. I'm getting day and night textures at night and water mixed into ground textures. I uninstalled after the blurry textures and once I reinstalled after the update it went from blurry to broken, spotted textures. Is there a way to completely get rid of the passengers (trail mode) so I can enjoy my sim again.
-
it's sad the only fix was for p3d and as soon as p3d players got the fix they stopped getting rage, but then they rage at fsx players to shut up and deal with it
No one is raging against you or FSX users but 8 posting in less than two hours is ridiculous. Your point was made on the first posting. Also, your already asking for a refund before Umberto even has time to address it. Let the man get some sleep seeing he was up very late. Then he can address your concern. Stop blaming P3D users and being so impatient. It hasn’t even been 24 hours since the update.
Sent from my iPhone using Tapatalk
Ok yes, sorry i was annoyed everyone was getting happy accept from me
-
I got to say I’ve been pulling my hair out with blurries since even before GSX lvl 2 but now after this update it seems it was the silver bullet. I wonder if the Manager was the culprit I never guessed in a million years it was GSX before level 2. Anyways thank you so much.
-
As I never suffered from blurries but from other signs putatively telling me that I was running my sim close to the edge of overloading it, I really wonder what else was related to this bug obviously present since the switch to 64bit. In my case, I had issues with texture loading and autogen. Both are now gone, most surprisingly also the autogen loading late and in patches bug. At least on my flight from LEPA to LSZH yesterday, I had all autogen fully loaded when approaching LSZH with a setting that resultet in no or patchy loading autogen some weeks ago. Overall, I never had such a smooth experience when approaching LSZH, it seems that this little fix really changed a lot. Thanks for this!
Regards
Chris
-
Any idea why I still get the problem with P3D v3?
Because your blurries were caused by something else. The bug was present only in the 64 bit version of the Addon Manager.
-
Will the update fix FSX?
32 bit version of the program didn't had this bug. If you have blurries in FSX, it's something else.
-
Any idea why I still get the problem with P3D v3?
Because your blurries were caused by something else. The bug was present only in the 64 bit version of the Addon Manager.
I'm sorry but they were introduced in our sims with the GSX Level 2 Expansion. So it's time to look for another bug in the code ;)
-
Right, so could it have caused blurries since the beginning of the 64-bit upgrade of the Add-on Manager?
Only at our airports that used SODE jetways. But, since they were entirely discarded when you flew away from them, it wasn't possible to notice it. But now, since we are placing jetways everywhere, it finally came out.
-
The fix didnt help for me. My cpu still hits 70 to 99% while using P3D v4. My computer never hits more than 50% using P3D and my FSGlobal textures are suffering as well. I'm getting day and night textures at night and water mixed into ground textures. I uninstalled after the blurry textures and once I reinstalled after the update it went from blurry to broken, spotted textures. Is there a way to completely get rid of the passengers (trail mode) so I can enjoy my sim again.
This fix obviously fixed ONLY the problem which was caused by the Addon Manager bug. It cannot magically fix blurries caused by something else and, *everybody* knows blurries were ALREADY a problem, way before the GSX L2 release.
Your problems now are something else entirely.
-
Your problems now are something else entirely.
You said the same before more and more people were complaining and at some point you were able to reproduce them.
So when we are 20 people here (more on other forums) that say that our blurries started when we installed the latest GSX (we all had no blurries before), then GSX *must* have something to do with it, or another thing like Couatl or Addon Manager.
-
I got to say I’ve been pulling my hair out with blurries since even before GSX lvl 2 but now after this update it seems it was the silver bullet. I wonder if the Manager was the culprit I never guessed in a million years it was GSX before level 2.
No need to wonder. We confirmed the problem WAS an Addon Manager bug, which is now fixed. We ALWAYS admit when a problem is in our software and, more importantly, we always fix it, and very fast.
It's just this one required to fill the simulator to its max capacity before it could be noticed. It couldn't possibly happen with the default scenery because, when the simulator runs at 30% CPU utilization, and only on the 1st core (typical for a default install), if something takes more processing power than it should, you won't noticed it when you have some much spare power from the unused cores.
But if the sim is already closer to full utilization, which happens if you install ten of thousands of files of complex autogen/vector/lc addons, you don't have any headroom for mistakes, so everything else must be as optimized as possible.
-
The thing is none of the folks I saw mentioned anything about the $. Their argument was that they did not want to leave FS2004/FSX because it was a "stable" platform. Hence why I don't understand. P3D is as stable as a sim can possibly be.
-
I'm sorry but they were introduced in our sims with the GSX Level 2 Expansion. So it's time to look for another bug in the code ;)
No, they weren't. The 32 bit version never had this problem to begin with. We recompiled it and put it online anyway, just to be sure, so it's 100% aligned to the 64 bit versions but sorry, this is not open to discussion.
If you still have blurries with FSX, and you think they were caused by installing GSX Level 2, I thing the problem is more trivial: your FSX has reached the limit of its capabilities (I hope you didn't assume they were "infinite"), and JUST adding replacement jetways moved it over its breaking point.
You still have the option to restore default jetways, of course. Passengers will still be there on open parkings, and if you customize a single 3rd airport, it shouldn't affect your flying elsewhere.
-
I'm on P3D v3 and if you follow the thread, I tried my best to help you narrow down the problem as I'm a commercial software developer, too. None of the fixes helped, the only way to avoid the problem is by not using any GSX service at all (also no pushback). The only thing I can do now is to offer my system as a test bed to find the problem.
-
The thing is none of the folks I saw mentioned anything about the $. Their argument was that they did not want to leave FS2004/FSX because it was a "stable" platform. Hence why I don't understand. P3D is as stable as a sim can possibly be.
Well the same problem happens on P3D v3. I don't know many people that are on v4 yet, it's also a matter of time. No "real" simmer has only 5 addons installed.
-
I'm on P3D v3
Doesn't make any difference, it's exactly the same as FSX regarding this matter.
[I tried my best to help you narrow down the problem as I'm a commercial software developer, too. None of the fixes helped, the only way to avoid the problem is by not using any GSX service at all (also no pushback). The only thing I can do now is to offer my system as a test bed to find the problem.
There's nothing to test. The 32 bit version of the software wasn't affected by this bug so, again, your problem it's just that, adding GSX L2 to your already overstuffed installation, has reached the limit of what a 32 bit simulator can do.
As I've said, you still have the option to restore default jetways, of course. Passengers will still be there on open parkings, and if you customize a single 3rd airport, it shouldn't affect your flying elsewhere.
You can try using the 1K/2K replacement jetway textures too so, it's not is that you don't have options.
-
There's nothing to test. The 32 bit version of the software wasn't affected by this bug so, again, your problem it's just that, adding GSX L2 to your already overstuffed installation, has reached the limit of what a 32 bit simulator can do.
If I said that to my customers, I would lose all my customers in the next hours...
As I've said, you still have the option to restore default jetways, of course. Passengers will still be there on open parkings, and if you customize a single 3rd airport, it shouldn't affect your flying elsewhere.
That means I can't use any FSDT airport at all?
-
P3D is a software under continuous developpement. A new v4.X version comes almost every few months. Devs. prefer keeping up with the software and enjoy the benefits each new version brings. It's up to the customer to follow.
-
I never criticized your attitude towards customers and said good about fixing problems very fast, but at this point your attitude is very unfair.
I think you should have made this expansion P3Dv4 ONLY rather than imposing everyone through the live updates. It’s simply not for FSX and I guess no one in this forum would have doubt choosing btw : GSX Level 2 with massive bluerries and unflyable or GSX Level 1 flyable.
Sent from my iPhone using Tapatalk
-
P3D is a software under continuous developpement. A new v4.X version comes almost every few months. Devs. prefer keeping up with the software and enjoy the benefits each new version brings. It's up to the customer to follow.
This is the usual sentence I read but you missed one point: People are asking either to fix the problem OR be rolled back to Pre Level 2 Expansion.
If he said GSXL2 is P3Dv4 only this would be perfect. We were imposed an update which is not possible for FSX. That’s it.
Sent from my iPhone using Tapatalk
-
If I said that to my customers, I would lose all my customers in the next hours...
What is "that" ? I said your 32 bit application has reach its limit, how this, exactly, is something you can't say to your customers ?
I'll make an analogy:
YOU: "dear Adobe support, I have this picture taken with my new 50M/Pixel camera, and I would like to edit it but, the problem is, I'm still running 32 bit Photoshop, and it crashes when I opened it. Could you make it fit in the 32 bit Photoshop ?"
ADOBE: "Do you have a 64 bit CPU and you run a 64 OS ?"
YOU: "Sure, I have a shiny new i7 and I use Windows 64 bit"
ADOBE: "Well, you can just download the 64 bit version of Photoshop. You know it's free for all our customers ?"
YOU: "No, I can't switch to 64 bit Photoshop. I have a scanner which I bought during the Reagan administration, that only has 32 bit drivers, they made new scanners but, they cost too much to upgrade. I also bought a plugin from this developer, which has now retired, so he won't upgrade it to 64 bit. I'm stuck with 32 bit"
ADOBE: "I'm sorry but, your Photoshop installation has reached the limit of what a 32 bit application can do."
YOU: "If I said that to my customers, I would lose all my customers in the next hours...I DEMAND you can make Photoshop 32 bit to perform just like the 64 bit version."
That means I can't use any FSDT airport at all?
Obviously not. Restoring default jetways will restore *only* default jetways. We don't use them...
-
This is the usual sentence I read but you missed one point: People are asking either to fix the problem OR be rolled back to Pre Level 2 Expansion. If he said GSXL2 is P3Dv4 only this would be perfect. We were imposed an update which is not possible for FSX. That’s it.
If you restore default jetways from the GSX Control Panel, GSX L2 is in fact working like basic GSX.
-
If you restore default jetways from the GSX Control Panel, GSX L2 is in fact working like basic GSX.
As people said: It does not fix the problem. We don't say it related to Level 2 but to the GSX update.
-
As people said: It does not fix the problem. We don't say it related to Level 2 but to the GSX update.
Of course it doesn't fix the problem if it was caused by something else. If you remove this folder too:
Addon Manager\Couatl\GSX\DLC.Jetways
The WHOLE code that creates jetways and passengers will be gone, entirely.
-
If it's not gsxs fault and you said it worked for FSX but then we uninstall gsx and get no blurries its clearly gsxs fault not fsx and i understand it cannot be solved so shouldn't any fsx user that thought they could use the product be entitled to a refund or the old gsx? I am going to p3d v4 thankfully but im just thinking for the other fsx users
-
I think I understand what's happening with 32 bit: I said I recompiled the 32 bit version too, but I didn't changed the version so, it seems is not being updated by Live Update, because nothing else was different, not even the version, so it skipped the update.
I raised the version just to be sure it will be installed, try Live Update now. The version of the Addon Manager .dll must be 4.5.0.9 after the update. If you have it, you should all set.
-
I have just run the update only DLL 64bit is 4.5.0.9 the DLL 32bit is still 4.5.0.8
Roberto
-
I have just run the update only DLL 64bit is 4.5.0.9 the DLL 32bit is still 4.5.0.8
Try again later. We don't have much control over *when* your local Cloudflare server will get the updated file. Well, this is the direct link, bypassing Cloudflare, if you don't want to wait...
http://update.fsdreamteam.com.s3.amazonaws.com/setup/fsdtroot/bglmanx.dll
-
It seems to be fixed :-) I'm 10 minutes into flight and usually I could see many blurries by now. Sharp as it should!
In fact before the update both DLLs were at 4.5.0.8. Does that mean I didn't even receive the 64 bit update because my server wasn't up to date when you released that fix?
-
Got it now 4.5.0.9
I will test soon.
I have a question: when couatl get disconnected from FSX ? passing 10000ft + 250 speed?
Thanks
Roberto
-
In fact before the update both DLLs were at 4.5.0.8. Does that mean I didn't even receive the 64 bit update because my server wasn't up to date when you released that fix?
No, the 4.5.0.8 was already good for 64 bit, it's just that I had to change the version in the 32 version to be sure it won't be skipped by the updater so now, I just changed both to be 4.5.0.9, to reduce confusion.
-
How do i check the dll version? is it gonna be in addon manager folder?
-
I'm on P3Dv4.3, run the FSDT Live Update yesterday and my blgmanx.dll is still 4.5.0.8 (dated Sept. 13, 2018). Could I safely download the new version from the link above, or it's just for FSX users?.
-
Alright I tested it a second time including jetway operation and NO blurries :D
I hope that other 32 bit users can confirm the resolving of this issue.
Thanks!!!
-
i think it's solved the issue, i'll do a test flight :-* :-*
-
I'm on P3Dv4.3, run the FSDT Live Update yesterday and my blgmanx.dll is still 4.5.0.8 (dated Sept. 13, 2018). Could I safely download the new version from the link above, or it's just for FSX users?.
Sorry, I mis-typed the version in my previous reply, I fixed it now:
No, the 4.5.0.8 was already good for 64 bit, it's just that I had to change the version in the 32 version to be sure it won't be skipped by the updater so now, I just changed both to be 4.5.0.9, to reduce confusion.
-
solved! ::) ::) ::) ;D ;D ;D thanks so much
-
FSX-Steam (DLL 4.5.0.9) same flight test from EIDW as I have done yesterday.
I can say the blurries problem is solved at least for me.
I just left Wales and I am flying over U.K. and the ground texture are perfect.
I have also noted that both GPU and CPU temperature are running cooler than yesterday.
Thank you very much.
Roberto
-
I’m trying right now with the new update. Crossing fingers, the problem seems solved :). Thanks Umberto
Sent from my iPhone using Tapatalk
-
looks like everyone is happy, i think virtuali should call this is ***solved*** ;)
-
looks like everyone is happy, i think virtuali should call this is ***solved*** ;)
I think so. We can publish it as an official Live Update with the notification too.
-
HI
I am using fsx and after updating the bglmanx.dll file with new version and using the default jetways it appears the blurries have gone and cpu is running normally. It seems the file was affecting 32 bit as well. I will make the switch to sode jetways for default and will report back.
Don
-
My problem is not something else I can assure you. I deactivated GSX Level 2 and I dont have a single blurry and distorted texture. Im simply reporting a bug that arose after I bought and installed your product. I have not had a single blurry texture before this. Dont talk down to me like I dont fly my sim everyday. Im not the only person to face blurrys and a cpu that reaches 100% after purchasing GSX L2.
-
The update fixed the problem (in FSX:SE) for me !!!
Thank you, Umberto! 8)
-
Yup same here, and we keep getting told “its not gsx” ..... if i start a flight and dont use GSX everything is fine, as soon as i start using anything from GSX, jetways, pushback etc, scenery goes blurry and no autogen loads anymore after i leave the airport area... i have an I7 7700K @4.6 ghz with GTX 1080 and i was using a default airport...
I tried what Peja has done in doing a flight without using anything in GSX, I got his same result in completion of a complete flight without any texture Blurring at all which is thus confirming that the issue of blurring is definitely related to new GSX, even after running the latest installer on 20 September 2018, this has not fixed anything
-
My problem is not something else I can assure you. I deactivated GSX Level 2 and I dont have a single blurry and distorted texture. Im simply reporting a bug that arose after I bought and installed your product. I have not had a single blurry texture before this. Dont talk down to me like I dont fly my sim everyday. Im not the only person to face blurrys and a cpu that reaches 100% after purchasing GSX L2.
If your still have the problem, the only possible explanation is you haven't run the FSDT Live Update, or something in your system like an antivirus or firewall might have prevented the Live Update to download the fixed .DLL that, as confirmed by everybody else that has participated in this thread, is FIXED, but in P3D and FSX.
I've posted a direct link to the fixed file in an earlier post, in case something in your system is preventing Live Update to do its job, try that.
-
Yes, the problem of Blurring texture is now SOLVED completely after manually updating GSX-Level2 , and working well and perfectly with FSX. The file that FSDREAMTEAM has provided to me and found in the forum and I used it is working very well. May be some users are running live update and still found the problem , this may be that the file is not actually updated as happened to me. Thanks a lot to Umberto who helps me a lot and providing the file that I added it manually and fixed my problem. Really working well and fully compatible 100% with FSX. I tested and working well.
-
Hello Umberto
I also do suffer from the massive blurry and I realized my CPU load is up very high between 95 - 100% with GSX2. Without it, it sits nicely around 25 to 35%. I did run the latest Live Update but the problems still Comes up.
Any ideas?
-
I did run the latest Live Update but the problems still Comes up.
Haven't you read the post just before yours ? The direct download was on this same thread, in the previous page, and will surely fix the problem when you have some kind of external software (antivirus or firewall), which is blocking the Live Update.
-
Hello again
I will try to manual download again tonight, once back from work. Is there any way to check before if the Live Update was successful? I assumed it was fine, since it fixed the Geneva problem before without any problem. There was also not an error message during the install. My AVG anti-Virus usually opens a windows and states that something has been blocked and my fsdreamteams folder is anyway excluded from the anti-virus.
-
Is there any way to check before if the Live Update was successful? I assumed it was fine, since it fixed the Geneva problem before without any problem.
The Geneva update didn't require a new executable, the blurries fix did so, it's possible your antivirus has blocked the updated .DLL, but let pass the updated scenery files.
My AVG anti-Virus usually opens a windows and states that something has been blocked and my fsdreamteams folder is anyway excluded from the anti-virus
I learned to never trust antivirus in nothing they do. I personally witnessed on an user's system the antivirus still blocking the executable *SILENTLY*, without any warnings AND with the Addon Manager disabled and even with the antivirus *itself* disabled but, apparently, "disabled" from the antivirus user interface doesn't really mean "disabled", because the antivirus was still running its low-level Windows service and was still mistakenly blocking things without even telling.
You might also try to remove this folder:
%APPDATA%\Virtuali\Updatecache
Because, we check for every file to be successfully downloaded and to be the same version as the online one but, if the firewall/antivirus is blocking the list of files on the server, it won't work. Removing that folder should fix this problem.
-
Hello Umberto
I replaced the dll in the FSDreamteam/Addon Manager folder and redone parts of my yesterdays flight, the very bad blurry is gone, but I can still see some textures further away are blurred but start to load once I get closer. However CPU load is still a lot higher than normal. I am averiging 85% on all cores. This is way above what I usually expierence. So there still something giving a high load on the CPU. And this was in dayload without any weather. I am afraid that it the average load will be even worse in weather.
So for me the problem is not 100% solved. What do you suggest? Should I go ahead and remove the Appdata/UpdateCache folder as well? Can i just delete it or should I run Live Update again after that?
Dani
-
However CPU load is still a lot higher than normal. I am averiging 85% on all cores.
I bet you use OrbX Vector. If yes, it's normal.
The main reason why we couldn't initially replicate the blurries, is because with the default scenery, the CPU load is about 30% average, with the 1st core used at 100% and the rest very low. Thanks to a tester that lend his system fully stuffed with OrbX, we finally were able to replicate it, because there was no way for it to show up, if the system wasn't already under high stress.
Even with NO FSDT software installed, the average CPU utilization went from 30% to 80-85%, just after enabling OrbX. This is entirely normal: the vastly improved vector detail (roads, rivers, coastlines, lakes, etc.) DOES have a cost in performance, because the simulator must create way more *different* textures compared to the monotonous default scenery.
Vector data is not separated from textures, it's "baked in" by projecting all the vector polygons over the base landclass textures to create new combined textures on the fly. The more detailed the vector data is, the higher the cost on CPU. HOWEVER, this is one of the FEW things the simulator does in true multi-threading, that's why you see more core utilization and, as long you don't exceed 100% in total, it's a GOOD thing: it means the simulator is making good usage of all the cores. It's only if you go *over* 100%, that blurries might start and/or fps might go down.
So for me the problem is not 100% solved.
Yes, the part of the problem which was *caused* by our software IS fixed, and you confirmed it yourself. We cannot obviously fix EVERY other problem related to blurries (which were a problem very well known for *years*), or any other problem of high CPU utilization.
-
Hello Umberto
You are right, I am using a few ORBX products and as well Vector. I will do further tests and will disable Vector to see if that has really such an high impact on my system. A friend of mine runs his similar system with Vector at around 65% core load.
Thank you for your help so far.
-
put this string in the Terrain Part of your P3D.cfg and the blurries with ORBX will gone.
TEXTURE_SIZE_EXP=9
-
Hi Artox
Back from holiday I tried your settings and changed from 10 down to 9. And this actually brings the blurry back for me. With 10 I seem to be fine, but not with 9.
-
Putting that line in the cfg will force the sim to use high-resolution terrain textures even if they are selected “off” in the main P3D graphics settings. IF the blurries are being caused by CPU overloading, it will only make the problem worse.
-
HI JRBarrett
I had this line in anway, but with a setting of 10 and this seems to be fine for my sim without any blurries.
That's probably an ORBX setting I guess?
-
The standard setting without TEXTURE_SIZE_EXP=9 is TEXTURE_SIZE_EXP=8
using TEXTURE_SIZE_EXP=10 is just possible if you have a graphic card with at least 11GB otherwise your memory load e.g. at EDDT EDDF is aprox. 7GB and with this nearly full or overloaded.
Depending on the memory you have on the Graka.
-
That is strange to me... i am fine with Setting 10, but when I put it to 9, then I get blurries again.
If I understand you correctly, 9 should cause less load then 10 right?
-
That is strange to me... i am fine with Setting 10, but when I put it to 9, then I get blurries again.
That's because going down from 10 to 9 ALSO lowers the texture resolution so, it's normal those textures will be less sharp than the ones at 10.
But that's a kind of "blurries" that doesn't have anything to do with this thread, which discussed a problem which was a bug in our software that could only be noticed when the system was already overloaded, but this has been long fixed.
-
Hallo Umberto
Not agreeing with you on this point. When I go down to 9 the "original blurry" as discussed here before comes back to me. It's not just a bit less sharp, it's really one big super blurred texture.
I agree with you however that with setting 10 and i am not having problems anymore :-) and that's the main point.
-
Not agreeing with you on this point. When I go down to 9 the "original blurry" as discussed here before comes back to me. It's not just a bit less sharp, it's really one big super blurred texture.
Which is clearly not be caused by the (now SOLVED) GSX bug because, if it were (only possible with an outdated software), it should have been much worse at 10, with the system more loaded.
I agree with you however that with setting 10 and i am not having problems anymore :-) and that's the main point.
Which simply confirms you are seeing an entirely new phenomenon now, possibly a bug in the sim, but not what is being discussed here.