FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: peja1591 on September 08, 2018, 06:42:47 am
-
hello, once i bought and activated GSX level 2 i immediately had a problem with autogen loading. i tried to troubleshoot all possibilities but no luck... I did uninstall GSX level 2 and just went back to normal GSX and everything is perfect again. No problems. Has anyone else had this issue? What could be causing this?
-
I still have autogen but loading much slower than before
-
I don't have GSX Level 2 installed, but I did update to the latest GSX which provides level 2 services at FSDT airports. Since the update, if I load into an FSDT airport it loads like it used to before the update. If I then load into a different FSDT airport, the load time takes forever, sitting at 36% for a long time, the slowly counting up to 69%, where it stays for a long time, then slowly counting up, and then finally loads. I've taken a look at task manager when this is happening, and most of the time my CPU is idling at no more than about 15%, apparently doing almost nothing. In a couple of instances I've gotten a blue screen with a message that says "Preparing Security Options", which goes away after about 10 secs. and then back to the P3D load screen.
Unfortunately, I trashed my previous GSX installer, so I have no way of going back...but if I can't find a solution quickly, I'll have to uninstall GSX.
Kind Regards,
Steven Miller
-
Sorry, but it's impossible that installing GSX would make any difference to autogen, or even to the loading process of the simulator. When the simulator is loading, GSX is not doing *anything*, other than waiting for the sim to be ready.
It might be possible that, ON FSX, with an high passenger density and 4K textures enabled, the sim might crash when using it with a memory-hungry airplane and a complex airport, because you just exhausted the 4GB FSX can use at the most. And this should happen only AFTER deboarding started.
But on P3D4, sorry, whenever you are seeing, is NOT caused by GSX. Nothing has changed, other than the boarding process.
Blue screen CANNOT be caused by an user program like GSX. Only drivers can cause blue screen. So, you might be mislead thinking the problem is caused by GSX, but it might just be a problem of your video drivers. We use DX11 to create jetway numbers, so that might be somewhat related.
You can troubleshoot this. Disable the "Enable RTT" option in the Addon Manager settings, and restart the sim. If it works better, than you can SURE it's a driver problem. Or, possibly, a tweak gone wrong, or that is not right for your video card. In this case, removing all the tweaks and resetting the video card to all default settings might fix the issue.
-
Same here
-
I already listed some possible solutions.
-
...Disable the "Enable RTT" option in the Addon Manager settings...
The RTT option is not "Enable RTT", it is "Disable RTT"
In any case, I assume your suggestion is to make sure RTT is not being used - "Disable RTT" box checked. I did this, saved settings to P3Dv4.3, restarted the sim, and absolutely no change. First airport load is fine (loaded into default scenario/airport which is Eglin AFB), second airport load is a little slower, and 3rd airport load takes about 5 - 10 minutes.
Previous to disabling RTT, I had installed an earlier Nvidia driver for my GTX1070...was running 399.07, went back to 397.64 - still had the loading problem.
Umberto, have you actually TRIED the scenario I describe - load into P3D, then switch to a FSDT airport, then switch to a different FSDT airport...it's usually the 3rd change of airport that brings my comp to a standstill.
I uninstalled GSX - no change
I uninstalled all FSDT airports and Addon Manager - problem solved
I am going to try and install one FSDT airport at a time, and test to see if the problem returns, and if everything works okay with all FSDT airports, then I'll install GSX and test again.
-
Umberto, have you actually TRIED the scenario I describe - load into P3D, then switch to a FSDT airport, then switch to a different FSDT airport...it's usually the 3rd change of airport that brings my comp to a standstill.
Yes, and even made a video for you:
As you can see, I switched between 4 different FSDT airports in a row, all of them with SODE jetways, and there's no slow down, no autogen problem, no frame rate drop, nothing.
-
I installed FSDT KJFK2 and got this:
As instructed, I downloaded GSX and installed, and got this:
-
As instructed, I downloaded GSX and installed, and got this:
You failed to include the only useful information: the error log details the message asked you to open.
-
Where is the error log...I'd be happy to post it.
-
As instructed, I downloaded GSX and installed, and got this:
You failed to include the only useful information: the error log details the message asked you to open.
Umberto, I really appreciate all the hard work you put into your products, and the many hours to support them...but I have to say, a little different tone would go a long way to enlisting the support of your customers who have paid you money.
Here is a much better reply: "Please attach the error log, and I'll have a look."
Kind Regards,
Steven Miller
-
Where is the error log...I'd be happy to post it.
The screen shot you posted said "Do you want to open the error log ?". If you replied Yes, it would open the error log in Notepad for you.
-
Umberto,
If I had selected yes to open the error, do you really think we'd be having this back and forth...why the hell can't you make this easy and tell me where the error log is stored!?
Rather than argue with you, I just did a search for "Couatl" and found this:
couatl v3.2 (build 4032)
panic log started on Sat Sep 8 12:47:10 2018
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\common\dynamicShadows.py", line 131, in refreshObjects
File "couatl\JFK2\__init__.py", line 120, in seasonChange
File "couatl\JFK2\__init__.py", line 100, in patchSeason
RuntimeError: CreateFile failed: The system cannot find the path specified: "C:\ProgramData\virtuali/FSDT_KJFK/KJFK_sf01.mdl"
{'Airport': 'KJFK', 'User Pos': (40.628708464973016, -73.7733624481727, 5.7734 m, 1.8114 m, 301.0617069513269)}
-
If I had selected yes to open the error, do you really think we'd be having this back and forth...
Are you saying the error log showed once, and then never again ? Because, if it's still happening now, the only thing you had to do, was just start the sim again, to look at that screen. If the error, instead, is not happening anymore, then why bother posting about it ?
why the hell can't you make this easy and tell me where the error log is stored!?
For the obvious reason I assumed the error keep coming at each startup of the simulator so, it should have been obvious to you as well that it would havbe been enough to start the simulator again, and get another chance to say yes to that message.
RuntimeError: CreateFile failed: The system cannot find the path specified: "C:\ProgramData\virtuali/FSDT_KJFK/KJFK_sf01.mdl"
{'Airport': 'KJFK', 'User Pos': (40.628708464973016, -73.7733624481727, 5.7734 m, 1.8114 m, 301.0617069513269)}
That error indicates you haven't run the FSDT Live Update or, as usual, an antivirus/firewall might have prevented the Live Update to do its job or, you installed the OLD version of JFK2 OVER GSX Level 2, because that error clearly indicates you are running an old version of the JFK2 code, one that belongs to the previous version, and not the one which is currently online now on the Live Update server, which is not possible NOT to get it, unless something else is interfering.
So, again, running the FSDT Live Update now, will surely download the latest JFK2 code, because the old one you are running it's just not online anymore.
-
my problem is that at the scenario startup, the autogen is fine. One i start flying away from that airport area no autogen, and blurry textures everywhere with GSX 2 installed.
-
The order of my installs:
Step 1.) KJFK2, including allowing automatic Live update to complete. - after which the error indicating I needed the new GSX
Step 2.) GSX install )from newly downloaded installer from FSDT downloads), including allowing automatic Live update to complete. - which then gave the KFJK error above.
Is there a different set of directories/programs which need to be excluded from antivirus/firewall than what were required before the updates? I've been using FSDT products, including the Live Update, for quite some time without errors, it has only surfaced since the update.
If something is causing Live Update to not complete satisfactorily (such as antivirus/firewall block), doesn't it seem reasonable that it would help if an error log was created saying as much? Then we wouldn't be speculating that it MIGHT be related to AV/firewall block?
-
If something is causing Live Update to not complete satisfactorily (such as antivirus/firewall block), doesn't it seem reasonable that it would help if an error log was created saying as much? Then we wouldn't be speculating that it MIGHT be related to AV/firewall block?
Of course it's possible to create a log and, this is not even always required because, the latest Live Update (since GSX L2), as soon as it downloads a file, it will verify its hash and will compare it against the server, to be sure nothing is "blocking" the download. And will give you an alert about it.
OF COURSE, if your antivirus has even blocked the Live Update *itself*, such function wasn't available in the old Live Update.
But the issue is, if you installed the new JFK 2 and the new GSX, they already CONTAIN the new Live Update so, it's really not possible something like you are describing. The only possible (highly unlikely) chance for this to be happening, is that your local Cloudflare node, which caches all our Live Update files, still hasn't been updated with the new files we posted yesterday.
It's very unlikely, but it's theoretically possible, and it's the only explanation compatible with your report, also considering NOBODY else has posted the same error at JFK2 so, if we really had the old version online (we don't), every single JFK2 user would have seen the same error, not just you.
You might also try this, remove this folder:
%APPDATA%\Virtuali\UpdateCache
Then run Live Update again. That's another folder that a firewall/antivirus might mess up with.
-
my problem is that at the scenario startup, the autogen is fine. One i start flying away from that airport area no autogen, and blurry textures everywhere with GSX 2 installed.
Another video 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, no autogen loss.
-
I deleted %APPDATA%\Virtuali\UpdateCache, and ran Live Updater and was able to load KJFK without any errors, unfortunately I ended up with 2 overlapping jetways at most stands.
At this point does it make sense for me to download ALL airport installers, for airports I own, from the FSDT download page, uninstall all FSDT content, and start over with fresh installs and see what I get?
-
Hello, i uninstalled and reinstalled GSX 2 and everything is working fine now. Whatever the problem was, it is now gone and fixed.
-
unfortunately I ended up with 2 overlapping jetways at most stands.
This has been already discussed and answered here:
http://www.fsdreamteam.com/forum/index.php/topic,18503.msg128532.html#msg128532
Yes, there was a problem with the AFCAD which was online until now, but it's fixed. Run Live Update again to get it.
-
unfortunately I ended up with 2 overlapping jetways at most stands.
This has been already discussed and answered here:
http://www.fsdreamteam.com/forum/index.php/topic,18503.msg128532.html#msg128532
Yes, there was a problem with the AFCAD which was online until now, but it's fixed. Run Live Update again to get it.
Umberto,
Thanks, I'll run Live Update and check out the jetways at JFK. I assume it should be okay to install the other 9 of my FSDT airports?
-
I assume it should be okay to install the other 9 of my FSDT airports?
Yes, they should work.
-
my problem is that at the scenario startup, the autogen is fine. One i start flying away from that airport area no autogen, and blurry textures everywhere with GSX 2 installed.
I had the exact same thing as quoted above happen to me yesterday, I flew from FSDT KLAS to flightbeam KSFO and KSFO still was not fully loaded when I landed there.
-
flightbeam KSFO and KSFO still was not fully loaded when I landed there.
Flightbeam KSFO doesn't use our Addon Manager anymore so, the problem cannot possibly be caused by GSX or its possible interaction with another scenery that use the same engine.
-
well, I also noticed as I flew away from KLAS, the airport was just a big black square and took a really long time to reappear which is not normal for my system, usually it takes maybe a second or two. I'm about to do a flight back to KLAS and see how it goes. I've ran live update again and hopefully addressed the other problems I was having since installing GSX L2.
-
If KLAS takes too much time to load textures, while flying, the problem is clearly totally unrelated to GSX, which is not doing *anything* if you are flying, other than check your position and see if you are close to an airport.
All GSX vehicles and jetways, which might theoretically consume texture memory, will be destroyed once you fly away from the airport.
Of course, if your simulator is already overloaded with too high settings, too many addons, even the very act of the proper clean up of resources, which is correctly made by GSX to free up memory (not really by GSX, but the simulator itself, after GSX ask it to remove its objects), might take some time.
-
I assume it should be okay to install the other 9 of my FSDT airports?
Yes, they should work.
Umberto,
I installed KCLT, and I'm right back to where I started...loaded into Eglin (default scenario), then loaded KCLT - both loaded fine, but then I loaded KJFK and it took 10 minutes to load. Load progress for JFK got stuck at 37% for almost 5 minutes, then slowly progressed to a pause at 69%, and then very slowly loaded up to 100%.
I don't have a clue what to do now, as disabling RTT did nothing for me. I'll try uninstalling KCLT and see if I get back to everything loading okay again. If it does, I'll install a different airport and see if things load normally.
-
Well, so I uninstalled KCLT, and installed KSDF and it's the same problem...the 3rd FSDT airport load takes about 10 minutes. I loaded 10 different non-FSDT airports one after the other and had no problem, so all the evidence I have points to FSDT and something about the updated GSX that causes a problem that didn't exist until I updated.
I'm curious if the fact that I seem to be the only one reporting my specific symptom, if it's because I am not running GSX Level 2 (I didn't buy or install Level 2), and if it's not specific to an updated GSX without Level 2. I mean, how many people would have a reason to run Live Update to see that they need to download a new GSX full installer if they haven't changed anything related to FSDT on their system. And how many people have attempted to load several FSDT airports, one right after the other, after installing the updated GSX - only reason I did, was to see the new jetways, and see how they worked.
Umberto, I know you said you did a test load of several airports, but I suspect you have Level 2 installed. Have you tried it on a system with only updated GSX, without Level 2?
I'd really like to buy Level 2, but I won't even consider it until my problem is solved without it.
-
I'd really like to buy Level 2, but I won't even consider it until my problem is solved without it.
We cannot even start to think *how* to solve a problem that we cannot replicate in any way.
I'm quite sure of what will happen:
- You'll realize sooner or later your system had a problem, likely caused by other software, even non flightsim-related.
- You'll reformat your PC, which will run so much better and faster
- You'll reinstall the sim from scratch, and you'll finally be convinced the problem never had anything to do with our software to begin with
You might not do it today, but sooner or later you will, I'm sure of it. A system that requires 10 minutes to load an FSDT scenery that here takes a couple of seconds, has serious issues that should be attended to.
-
And back at you...
I can assure you it will be a cold day in hell when I reformat my pc to make YOUR software work, especially considering all of the other software I have from lesser vendors (you know, like Fly Tampa, Flightbeam, DD, and a whole host of aircraft and utility developers) works just fine. When added to the fact that all was good until I updated what WAS a perfectly working product...eh, think I'll just uninstall your stuff and live happily ever after.
And I'll let you practice your superior skills of diplomacy, and product support on other suckers.
Kind Regards
p.s. thanks for your offer to actually help in some way meaningful
-
I can assure you it will be a cold day in hell when I reformat my pc to make YOUR software work
You will, to make YOUR software work. What is not working is your simulator. But as I've said, you will do it, but I doubt you'll come here and saying "you were right".
-
I will certainly admit I was wrong about one thing: apparently it wasn't the updated GSX that caused my problem with loading of consecutive FSDT airports, I have the same symptom after restoring from a system image made the day prior to running the new GSX updater.
After loading P3D Eglin (default scenario airport) and then load FSDT airports, the 2nd one I try to load takes about 10 min. - same if I keep trying additional FSDT airports.
Yet I consecutively loaded P3D Eglin (default scenario airport), FB KBOS, Orbx KEGE, FT KTPA, Orbx KPSO, FB KSFO, DD KSEA, UK2000 EGLL, and none of them took longer than 30 sec. to load.
-
I will certainly admit I was wrong about one thing: apparently it wasn't the updated GSX that caused my problem with loading of consecutive FSDT airports, I have the same symptom after restoring from a system image made the day prior to running the new GSX updater.
That's already meaningful result. At least, you now know your problem doesn't have anything to do with some supposed "changes" in GSX Level 2 (of course I was quite sure of this), and it was already there in your previous install.
Nobody so far as ever reported 10 minutes to switch from an FSDT airport to another one. Not once, since FSDT exists...