FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: DVA12924 on October 03, 2018, 11:27:14 am
-
Every time I make any edits with the editor from GSX L2 it causes P3Dv4.3 to become unresponsive. I have to force close the sim (ctrl+alt+delete) and restart where I find that none of the changes I was attempting to make have even been executed or saved. Attempting to redo the edit again causes the sim to become unresponsive. It is not the sim itself as I can leave the sim going for hours not touching GSX editor with no freezes or errors of any kind but as soon as I open the editor and attempt to apply a change, the sim becomes unresponsive. :-\ :-[ :'(
I've done a full Repair install of P3D, a full uninstall and reinstall of GSX/L2, and full revert to an old display driver and update to newest driver again. Folders, paths, links all have been verified and are working for all other programs. I am extremely confident in saying that this is not a system issue on my end. GSXL2 works great for its actual animations now with the 1st 2 problems I reported as resolved, but without the ability to update a single gate without causing a freeze where changes are not even applied has thrown yet another wrench into the gears of progress.
I also was never able to solve the issue with the black gate numbers http://www.fsdreamteam.com/forum/index.php/topic,19175.0.html following your instructions and even despite a FULL uninstall including add-on manager and reinstall for GSX/GSXL2. Immediately on reinstall, the same gates that had black numbers before still had them so this leads me to believe that somewhere rooted in the installation are files that do not get uninstalled and have become corrupted causing these gates to remain with black gate numbers and also causing editor to cause P3D to become unresponsive. The black gate numbers I could have dealt with and continued to finish this project while we troubleshoot the issue so I could actually fly for the first time in 2 week, but with the issue of editor causing the sim to freeze now, I am once again grounded until this problem can be resolved, or I will have to not use GSX (half of my heavy gates at ZBAA have been replaced with 2 jetways but the 2nd jetway not positioned yet so I have jetways laying around everywhere in the incorrect locations. I cant change that because Editor keeps freezing P3d every time I click apply) thereby rendering the program useless.
Umberto, I am trying my best to remain calm and civil but please understand that just because you open your sim and don't see the same issue doesn't mean it doesn't exist. Everyone has a completely different set up with hardware and folder paths and add-ons. I understand that there is no way to predict and avoid every possible combination of issues that could arise. At this point, I just want to get these problems resolved so I can go back to enjoying my flight simulator. I can do my best to walk you thru all the steps I've taken to get to this point if needed in case it it something that may have become corrupted on my system, or whatever the case may be. I want to work with you to get this problem fixed.
-
Closed and reopened P3D but this time it didn't show the rebuild database message and no gates showed up. Only add-on manager was showing in the addon drop down menu from FSDT and it doesn't even show GSX or GSXL2 registered on the system now and has them in trial mode but it is still installed. There's for sure something going on here that shouldn't be.
Re inserting the serial numbers I have in email confirmations are not doing anything. GSX is now stuck in trial mode on my system.
-
I completely uninstalled and reinstalled GSX/L2 again, this time being sure that all files GSX installed were uninstalled/deleted. The reinstall allowed GSX to see the product as active again but was still freezing P3D when "Apply" was clicked from the editor. I deleted the INI file from appdata folder and I could then send the command to change "all gates w /J" to be changed to a different gate model. I could see the change taking effect, but even after almost 10 minutes of waiting without seeing more changes, some jetways still showed the GSX default model. When I tried to edit a parking position where one of the jetways were still GSX default, the sim froze again.
This leads me to believe that the editor is creating corrupt INI files that is causing the sim to freeze and prevent the proper models from loading. The only resolution I have to prevent the sim from freezing is to allow GSX to just replace the jetways with the GSX default model and leave everything else alone. This basically means that I have no customization available for anything within GSX or the sim will freeze. I have nothing else running with the sim aside from GSX and ChasePlane when this happens (and I've had the same results with chaseplane not running).
-
Closed and reopened P3D but this time it didn't show the rebuild database message and no gates showed up. Only add-on manager was showing in the addon drop down menu
This was simply because Couatl didn't start because you opened / closed the sim too quickly between sessions. I think I already explained this to you:
Have you noticed how much time it takes AFTER the simulator icon has disappeared, for the "Compile" button in the GSX Control Panel to become active ? This is the same time when is REALLY safe to start the sim again after closing it once, because the GSX Control Panel ASKS Windows when Prepar3d.exe has closed, and this can (and it DOES) happen several seconds *after* you see its icon disappear, so you might be tempted to just starting it again.
-
I wait a minimum of 5 minutes between each restart of P3D, as I also already explained to you. This in no way has any change on the editor causing the sim to become unresponsive whenever "apply" is clicked in the gate editor, which is the topic of this title and the issue needing attention.
-
This leads me to believe that the editor is creating corrupt INI files that is causing the sim to freeze and prevent the proper models from loading. The only resolution I have to prevent the sim from freezing is to allow GSX to just replace the jetways with the GSX default model and leave everything else alone.
The editor surely doesn't create corrupt INI files. An INI file cannot cause the sim too freeze. Not just that, the whole GSX/Couatl programs, by themselves, CANNOT cause the sim to freeze, no matter how hard they try, because they are separate .EXE programs so, by definition, cannot crash the sim.
What CAN crash the sim, instead, are the models themselves. Not because the models are wrong, of course, but because there might be some kind of problem in your video driver settings/tweaks which is causing what is an otherwise 100% perfectly compatible model, not not work on your system.
When you customize a single jetway, the one in the parking spot you are editing will momentarily switch from static to dynamic, in the same way when you USE the jetways in normal use with SODE.
Are you able to customize the automatically-replaced default jetways ( move, rotate ), as they are, without changing their model ?
-
I wait a minimum of 5 minutes between each restart of P3D, as I also already explained to you. This in no way has any change on the editor causing the sim to become unresponsive whenever "apply" is clicked in the gate editor, which is the topic of this title and the issue needing attention.
I was ONLY replying to your specific report of "this time it didn't show the rebuild database message and no gates showed up". That's why a made a separate post only for THIS issue, and a separate post for the "sim to become unresponsive whenever "apply" is clicked.
Ok, so you waited but, instead of waiting 5 minutes, which is surely not required, next time it happens, check if Couatl.exe is still running in the Task Manager. Maybe it has been unable to close for some reason, and the most likely reason for this is the simulator not closing cleanly, so Couatl couldn't receive the order of quitting from the sim.
-
I will have to test default models tomorrow.
It may be the graphics card driver, but I have an Nvidia 1080 card with the latest driver. This thing can run the Space Shuttle if it wanted to (meaning it has WAY more power than my system or the sim build could need (Windows shows CPU usage at 24-40%, RAM usage at 40-50%, and GPU usage at 25-30% with sim running along with ProATC X, GSX, Virtual Airline ACARS system, Active Sky, REX, and chaseplane all running along with it)).
I'll try changing the default jetways (since all airports have been reverted back to fresh GSX install anyway) and if that doesn't work, I'll revert to an older graphics driver and see if that works. Issue with it may be the graphics driver is the last driver was installed on 9/28/18 but the issue of P3D freezing didn't start until 1 or 2 days ago.
And just to clarify, the ONLY time P3D freezes at all, ever, is when I click the "apply" button on the gate editor. If you will recall my videos from prior issues, this was not an issue then because I could click the apply button and make adjustments, but has since become oan issue and no new graphics drivers or graphic settings were changed between then and now.
-
It may be the graphics card driver, but I have an Nvidia 1080 card with the latest driver. This thing can run the Space Shuttle if it wanted to
You are now confusing the "power" of your system, with what a single obscure tweak might possibly cause. So not, it's not as simple as just changing driver, it might be a setting/tweak problem instead.
I always use the latest drivers, and I never had any of such issues with any version of them. But each time nVidia release a new driver, I always choose a custom install, with the option to do a "clean" installation.
sim running along with ProATC X, GSX, Virtual Airline ACARS system, Active Sky, REX, and chaseplane all running along with it)).
Have you tried disabling all this stuff, at least while editing (just AS A TEST), to see if some of these could cause a problem ?
-
When I am editing GSX, it is only GSX and P3D running. All the other add-ons are launched only when an actual flight is about to take place.
I reinstalled the graphics driver in hopes that would fix the black box gate numbers yesterday but did not do a custom clean install, I'll give that a go tomorrow also.
With GSX reverted back to a clean installation, I had a chance to throw in the long haul flight I've been putting off. I would love to test now while we are both awake, but currently I am over southwest Alaska enroute to Beijing with about 10 hours of flying left.
I'll take this chance to reread the GSX documentation with the chance I've overlooked something.
-
I have done the following:
Reinstalled latest Nvidia graphics driver using a custom clean install
Restarted computer
Deleted P3D Shaders and P3d.cfg (recommended by many users on another forum)
Restarted computer
Ran P3D using default airplane at default location and did a quick test flight to ensure P3D recreated the shaders and P3D.CFG files - No issues found and sim worked wonderfuly
Closed P3D
Waited 30 minutes (got lunch)
Ran FSDT Live Update
Restarted computer
Opened P3D, running alone with no other add-ons
Loaded PMDG 747 to ZBAA gate 403
Allowed GSX to finish starting and PMDG to load aircraft
Changed panel state to cold and dark so i could edit freely and allowed PMDG to load the panel state (it at this point has been about 3 minutes since the flight had been "launched" from P3D main menu)
Opened GSX menu with Ctrl+F9 (key command I set for GSX as to not interfere with UTLive key commands)
At this point, GSX has fully loaded along with P3D and GSX has imported/replaced all standard FSX gates with default GSX SODE gates, however some are still showing black gate numbers)
Selected "Customize this parking location" from the GSX menu
Selected all gates with /J using the button at the top left of the gate editor screen and selected to change them all to a different type of gate with bridge and gate numbers
Clicked Apply
GSX started replacing gates, but even after a 5 minute wait, some gates did not change from default GSX SODE gates to the newly selected ones and still some had black gate numbers
P3D had not froze at that point so I tried to enter the customize mode by selecting the gate I was loaded into (403) and clicked "Customize Parking" from the editor screen, where GSX loaded the customization mode placing the sim into SLEW mode, as it should.
Noticed the jetway at the spot I was editing disconnected from the jetway additional options (AC unit, elec plug, etc) and the gate was then rotated facing away from the aircraft (90 degrees from the location it should have been with head facing opposite direction) but the ground markings and jetway additions were still where they should have been.
I moved the parking position back slightly to test if controls were still working, and the parking spot moved. Moving the Jetway moved the unit, marking, and addons but while still 90 degrees misaligned.
I pushed "Y" to exit SLEW/Edit mode and P3D immediately became unresponsive and was forced to shut down. The GSX gate editor screen remained open and functional between P3D freezing and when I shut it down using ctrl+alt+delete (verified while in there that no other programs were running other than those listed with the 4th screenshot. Couatl.exe*32 was showing as running in the "Processes" tab, but not using any CPU at that time, however after P3D was forced shut down, Couatl.exe*32 began using CPU without GSX or P3D running, using about 20-25% of the CPU usage (out of 28-30% usage for the entire computer usage)
Below are the screenshots:
https://prnt.sc/l2aylo - in Edit mode with jetway disconnected from the ground makings, additions, and rotated 90 degrees and facing away from aircraft
https://prnt.sc/l2aywl - GSX gate edit screen showing gate Number is still not generating correctly, and jetway /jetway options selected for all gates with /J.
https://prnt.sc/l2az3f - Top title bar of P3D now shows as "Not Responding" immediately after exiting Edit/SLEW mode
https://prnt.sc/l2aza1 - showing P3D not responding, no other programs running with P3D aside from GSX gate editor and GSX Control Panel (Firefox opened to post the thread and see screenshots). Also, notice in the upper right corner of this image that the gate did not change from the GSX default SODE jetway.
2 things tested but faild to yield results: Graphics Driver reinstalled using Custom Clean install and ability to edit parking position/jetway positions with no other addons running.
Windows Event Viewer did not generate a critical error, but did see it as an "Application hang" ... here is the report from Event Viewer:
The program Prepar3D.exe version 4.1.7.22841 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: e70
Start Time: 01d45c29e32d6874
Termination Time: 380
Application Path: C:\Users\Steven\Desktop\P3Dv4\Prepar3D.exe
Report Id: 1c582dbd-c81f-11e8-9952-d43d7e4c88bd
What's interesting in this report, it that it sees P3D as version 4.1.7.22841, where as the windows control panel of installed programs shows P3D installed as 4.3.29.25520
Perhaps this has something to do with the issues?
screenshot attached - From within P3D Help/About menu showing P3D V 4.1 installed
http://prntscr.com/l2bf02 - Windows control panel showing P3D V4.3 installed
Since all of my addons are stored outside P3D main folder, I will try to uninstall P3D and reinstall and then verify addons working including GSX. It seems to me that there is something that didn't happen correctly with the P3D update to 4.3 (I knew I should have stayed with 4.1( :-\ :'( ). I'll see if that fixes anything and if P3d shows that it is actually 4.3 now. Also, notice in the last screenshot that Simconnect is still reading as 4.1, but P3D 4.2 installed simconnect 4.2 as I've seen from other users. I'm leaning more toward this is an issue/conflict with P3D update and simconnect rather than a GSX issue.
-
Did a full reinstall of P3D, and it is now showing version v4.3 in help/about in the sim.
I launched the default scenario and GSX loaded fine.
Opened the GSX menu and the correct options displayed.
Changed aircraft to PMDG 747 and moved to ZBAA gate 403.
Noticed that the same jetways with black numbers as before the reinstall are still showing black.
Noticed that all jetways were GSX default SODE gates overlayed onto FSX default jetways.
Exited P3D and opened GSX Control Panel and selected "Disable default jetways"
Reloaded P3D with PMDG 747 at ZBAA gate 403
Allowed aircraft, sim, and GSX time to load up.
Opened GSX gate editor from GSX menu
Selected "all gates with /J" from upper left corner
Changed all gates to a different model with bridge, ground markings, jetway additions, and gate number.
Clicked "Apply" and watched the changes take place. Waited about 3 minutes to be sure GSX editor had enough time to complete the changes.
Noticed that 2 Jetways in the view did not change to the ones I had selected in Editor, but instead remained GSX default SODE jetways.
Exited from Editor
Reloaded airport database within Couatl menu
Noticed the Jetways that had not changed were removed when Couatl shutdown to begin restart and rebuild, so they are imported and managed by GSX
Once reloaded, opened the editor and selected "Customize Parking"
Waited for the load to complete and then moved the parking back a forth a bit to test functioning. parking position did in fact move with the commands and Jetways appeared normal.
Exited from parking customization mode
Selected all gates with /J and again switched to a different Jetway type model with the same features as the prior (ground markings, no logo, jetway additions, etc.)
Clicked "Apply"
P3D froze and became unresponsive.
After 4 hours of downloading files and uninstalling/reinstalling, I managed to get GSX to work for all of 5 minutes
I'll try with a different aircraft at a different airport, just to rule those 2 out
-
Closing sim and reloading into a default P3D aircraft (non-addon) the C-130, called up GSX to have a follow me car dispatched to take me to the gates (testing functionality). When I arrived at the gates, the 3 Jetways were replaced with GSX default SODE as they should be. I shut the engines off and called up the gate editor. From there, I selected all 3 gates and changed them to a new jetway model with personal options for ground markings and jetway additions and clicked "apply". All 3 gates changed to the ones I had selected from Gate Editor. I selected "customize parking" for the gate I was at and moved the parking spot back and forth to test functionality - no issues. I exited parking customization and no sim freeze. I selected the individual gate I was parked at and again changed the jetway and clicked "apply and the jetway displayed properly, without sim freeze.
This leads me to one or more the the three as the issue:
1)PMDG 747 aircraft
2) AFCAD I am using for ZBAA - I download AFCAD files from AVSIM for FSX and update them to P3D using ADE 1.76 with the following method:
-Add any Object Files that the selected airport will use and ensure they are in the library (use ModelConverterX to open any object models within the downloaded AFCAD and eport to desktop with a new name _OBJ.bgl which is then moved to P3D Scenery/Global/Scenery)
-ensure all aprons, taxi, runway, paths, parking are set to "Draw Surface" = Yes "Draw Detail" = Yes
-customize runways and taxi/path/parking lighting to my personal preference (all taxiways/paths/parking have center line and center line lights)
-Run Fault Finder and fix any faults found
-Create new CVX file to go with AFCAD by drawing a polygon around the airport following the boundary fence selecting "Flatten Mask Class ExcludeAutoGen" for the polygon type tag (this makes sure that P3D, ORBX, or anything else places any trees or other unwanted objects/buildings on the airport).
-Run Fault Finder again to verify no faults found
-Compile to add on AFCAD folder which is kept outside of P3D main folder
-This method has worked many many times and is the approved method for updating FSX AFCAD files to P3Dv4 compatible. GSX does read these AFCAD files correctly as the push back and follow me vehicles have always followed the paths 100% accurately).
3)GSX does not like at all when you try to edit 126 gates at once - The default airport and all airports I have edited with GSX up to ZBAA have had a maximum of 18 gates within a terminal and I would update 1 terminal at a time. This ZBAA AFCAD however has no terminals, but just lists all the gate numbers in order using 101 102 103 for "terminal 1" 201 202 203 for "terminal 2" and so on. This means that when I go to change the default GSX jetways, GSX is trying to change 126 selected gates and edit them at the same time. It could be that trying to edit that much at once is overloading the system with information and causing the freeze.
I'm going to perform more tests, breaking down all 3 of the above and testing.
PS- sorry if anyone feels this is off topic or whatever, but I assure you, all of the information I have posted in this thread is related to P3D freezing when using GSX gate editor so it is on topic, and Umberto said himself elsewhere that the reason GSX support is on a forum is so that anyone can see the resolutions to the the reported problems and be able to fix them themselves in the future if the user runs into the same problem. Whatever the issue may be, knowing the steps taken and the testing done to get to the resolution is just as important as having a resolution if another user is to benefit from it. So I apologize for the massive amount of information, but simply remaining quiet until I come back and only say "fixed it!" and nothing more will help no one.
-
I renumbered every parking spot in the AFCAD and reopened P3D and GSX. As you can see in the video, all worked well until I tried to customize a gate where the gate number is showing as a black box, then trying to edit that gate caused P3D to become unresponsive.
Whatever is causing these gates to show black gate numbers is also what is freezing P3D. I tried it again using the default P3D C-130 and the same issue happens when trying to edit a gate with a black gate number. Windows Event Viewer did populate an Error for P3D once it was closed:
The program Prepar3D.exe version 4.3.29.25520 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 1ae0
Start Time: 01d45c7e6913aacc
Termination Time: 449
Application Path: C:\Users\Steven\Desktop\P3Dv4\Prepar3D.exe
Report Id: 214f7be8-c873-11e8-bbf1-d43d7e4c88bd
You can also see in the video that Couatl is not using CPU until P3D is closed and then uses the majority of CPU being used system wide. But because all running applications aside from P3D show as responding and P3D.exe is what is freezing, then GSX error logs will not show anything wrong because those programs, per windows, are working still.
So I can say for sure that it is not the AFCAD, the large amount of edits at once, or the aircraft. I'm stumped as to why GSX is acting this way.
Edit - the simulator was closed for the entire length of time it took to type the above. I reopened the simulator and loaded P3D default C-130 to a heavy gate at ZBAA (D1 now) and nothing in GSX loaded and the GSX menu was missing from the addon menu in P3D, but Addon manager was still there. I opened Addon Manager, and it shows GSX and GSX Level 2 both in trial mode. This is the same as what happened before. When it happened last time, I uninstalled GSX and GSX L2 and when making sure all was removed, I found the registry keys in one of the remaining GSX folders (intentional?), this time I can't find it in a folder. I did notice while looking for it that the INI file for ZBAA did not change the gate numbering I did in AFCAD, so GSX was still reading the old INI file but putting the correct data on most spots.
When I uploaded the video to YouTube, I noticed it cut off right before I went to edit that gate next to mine with the black gate number which is when P3D froze ::) >:( ... I'll try to make a new video showing the entire process.
-
I get this error when trying to restart computer after P3D freezes - http://prntscr.com/l2g697
There is something somewhere that is causing Couatl to cause at least my setup of P3D to freeze and the Couatl program does not terminate, remaining running in the background even though GSX sees the simulator as closed.
-
As I've said in many of my replies, what is causing the sim to freeze is likely a video driver or video setting problem, which makes your installation not fully compatible with the Render To Texture feature required by GSX to create jetway numbers.
Try to check the "Disable RTT" option in the Addon Manager, restart the sim, and see if you can edit jetways without freezing the sim.
-
I'll try your method, but I can assure you I am not the only GSX owner with this graphics driver installed, so how is it I am the only impacted user if this in fact a graphics driver issue? Shouldn't it be impacting everyone with GSX and the latest Nvidia graphics driver for a 1080 card? Just trying to understand why you are certain it is a driver issue and not something else. GSX is the only program or add on to P3D or my computer and other games installed that is causing any errors at all.
I recall once before I did disable RTT, closed the sim, restarted the computer, and launched the sim again and still had the same issues. I'll try it again if it will appease you.
-
I'll try your method, but I can assure you I am not the only GSX owner with this graphics driver installed, so how is it I am the only impacted user if this in fact a graphics driver issue?
I believe I tried to explain this to you several times.
The issue might not be the driver *itself* because, as you said yourself, it would affect thousands of users, not just you. The issue might be, instead, some kind of obscure tweak or setting that you might have applied long ago and forgot about it, which is still there in the registry, affecting something.
That's why I told you, to try a custom install with the option to do a clean install, which *might* remove your tweak.
-
And I did that, many times already, as I've stated more than once throughout this thread. Nothing changed. I don't make tweaks or adjustments with graphics settings from Nvidia. I make graphics changes in P3D to match my hardware and visual requirements
-
I have done the following:
Reinstalled latest Nvidia graphics driver using a custom clean install
If you'll notice further in the same post and further in the thread, the same issues with P3D freezing and now 2 times GSX doesn't even show itself active have happened since the graphics drive was installed last, as a custom clean install. No tweaks, no changes, no modifications. Uninstalled, reinstalled driver, restarted computer, and continued with the rest of the flow I mentioned in the same post as the quote above.
So again, I am not sure why you are saying this is a driver issue on my part due to tweaks and or changes when clearly there have been none.
in the same post as the quotes above, just after custom clean install of graphics drive (notice the flow in the original post, no changes were made to ANY grpahics settings, in Nvidia nor in P3D:
https://prnt.sc/l2aylo - in Edit mode with jetway disconnected from the ground makings, additions, and rotated 90 degrees and facing away from aircraft
https://prnt.sc/l2aywl - GSX gate edit screen showing gate Number is still not generating correctly, and jetway /jetway options selected for all gates with /J.
https://prnt.sc/l2az3f - Top title bar of P3D now shows as "Not Responding" immediately after exiting Edit/SLEW mode
https://prnt.sc/l2aza1 - showing P3D not responding, no other programs running with P3D aside from GSX gate editor and GSX Control Panel (Firefox opened to post the thread and see screenshots). Also, notice in the upper right corner of this image that the gate did not change from the GSX default SODE jetway.
It seems the problems are getting worse, not better. We started off with a disappearing jetway that was fixed by waiting for server to update. Then we moved on to jetways not resolving to the aircraft. From there, we got a bit better with the only issue being the black gate numbers, but then that turned into P3D freezing 90% of the time I click "Apply" in the editor.
I feel if this truly was a graphics driver issue, it would be impacting the same thing at a regular, consistent, repeatable event and wouldn't be escalating into much more. The only thins that has been consistent is that P3D will freeze when I click "Apply" ... it hasn't been impacting the same things. I've had now more than 5 issues with GSX since L2 was installed on my computer. I didn't change any graphics settings before, and I din't this time.
A graphics driver issue wouldn't explain why I can restart the sim and GSX shows as "In TRIAL Mode" from the addon manager, which is the only FSDT menu option for any program in the sim. GSX completely looses its own registry path and won't show as active again until after I restart the entire computer. That doesn't seem like a graphics driver issue to me. So forgive me as to me being interested as to why you feel this is a graphics driver issue and trying to understand why you feel that way.
-
A graphics driver issue wouldn't explain why I can restart the sim and GSX shows as "In TRIAL Mode" from the addon manager, which is the only FSDT menu option for any program in the sim. GSX completely looses its own registry path and won't show as active again until after I restart the entire computer. That doesn't seem like a graphics driver issue to me. So forgive me as to me being interested as to why you feel this is a graphics driver issue and trying to understand why you feel that way.
I never said a graphic driver issue would cause GSX reverting to Trial. I said:
what is causing the sim to freeze is likely a video driver or video setting problem
So, I was replying ONLY to THIS issue. It's clear you don't have a "GSX issue". You have MULTIPLE issues in your system. Something which is causing the sim to freeze, and something ELSE, which is causing GSX going back to Trial.
A wrong compatibility mode for the simulator might cause this. Setting a Compatibility mode will force video drivers to go into a lesser performance mode (called WDDM 1.0, as opposed to the more correct and recent WDDM 1.1 and above) AND will re-route ALL registry calls made by all applications, including the Esellerate library, which will in turn force our software to assume GSX is in Trial.
That's something which is compatible with your report. First, check you don't have any Compatibility settings for Prepar3d.exe in the Compatibility tab. NOTHING should be checked there, which is how the simulator runs by default, and how it's supposed to run.
And, it's possible that other addons which runs together with it, might cause the simulator to behave as if a Compatibility setting was enabled for itself. So, be sure you don't have any of such Compatibility settings for any of the addons that run together with the simulator and be sure you are not starting the sim from one of them. As an alternative, DISABLE ALL ADDONS, just to be sure none of them is causing this.
In addition to that, Windows sometimes sets some wrong Compatibility settings in the registry, automatically, without your knowing and with no way to change them other than editing the registry manually. Check BOTH the following keys:
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
And be sure Prepar3d.exe is NOT listed on the right side of the window. If it is, REMOVE IT!
-
The only compatibility option that I changed or set was to "Run as Administrator" which is a very strongly recommended selection for windows 7, from both Microsoft and from Lockheed Martin, despite if the program is installed into the default installation folder, or in my case, installed into a new folder on the desktop. Every program and add-on I have installed on this system is set to run as administrator. I don't play around with compatibility settings like running any program as compatible with an older version of windows. If it is not made for, designed for, and fully functions with P3Dv4 then it does not go on my computer.
Prepar3D.exe is only listed in the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers registry, but its data value shows "RUNASADMIN" and there are no other references to Prepar3D.exe in either of the registry locations you mentioned.
At this point, to rule out this being my system, I'm 100% uninstalling P3d and all add ons and then reinstalling P3D using the download links directly from Prepar3D, making sure P3d opens and operates correctly, and then only installing GSX/GSX L2 and will again test. This will 100% rule out any conflicts, improper system setup, or bad RegKeys on my end.
As I have stated, graphics driver has been uninstalled and reinstalled as a custom clean install, more than once; P3D had been opened and tested with only GSX running (but other addons still installed but not running); I have tried the "repair" function of the P3D installer; I have made sure P3D is fully updated to v4.3; I have tested with the aircraft I usually fly and with P3D default aircraft; I have tested at a large airport and a small airport; I have made sure Windows Update is fully updated; I have made sure all hardware and software on my system is 100% updated; I have tried all the suggestions you have mentioned in the thread; I have tried at a default unmodified airport and at airports which I have an AFCAD for; and no matter what test I perform or what function I do, I always end with the same failing result of P3D becoming unresponsive the exact time I click "Apply" in the Gate Editor (If I am able to click "Apply" at all, not all the gates or all the options I selected are performed/applied, like some jetways wont change from default or some will change to new jetway selected but will not have ground markings or will still have the logo board on the jetway. And If I try to edit again, 100% of the time at that point when I click "Apply" P3D will become unresponsive).
The only other test I can think to do is start from scratch testing only P3D running with GSXL2 alone. GSXL2 is the only program/feature/addon that is not 100% working on my system and this computer was professionally built and used ONLY for P3D usage and scenery building/editing and aircraft modeling/texturing. I'm reluctant to blame my system set up only due to the fact that P3D and all other addons worked 100% perfectly, including GSX L1, up until the point I installed GSX L2 and that is when these problems started. If I uninstall GSX/L2 from my computer and run P3D as I did before L2 was installed, I can fly for hours upon hours without even so much as a minor stutter from P3D. And that test was done while the other testing was on going in the past few days when I hadn't changed anything else other than removing GSX installation from the computer. So yes, I am very reluctant to point blame at my system when no less than 11 other addons all running along side of P3D have and continue to function perfectly without GSXL2 installed.
I'll need a few hours to uninstall P3D and all the addons 100% and then reinstall P3D and GSX/L2 but I'll report my findings when I'm done with it.
-
(Umberto please read the ENTIRE message so we are both on the same page)
Testing is not done, yet. but I have managed to get most of it done. Please note, not only was antivirus not activated at the time of the steps below, but I even uninstalled it and disabled Windows Defender so there would be no chance of any antivirus interference. Antivirus is at this point still not reinstalled, so all testing done without antivirus.
Steps take so far in the order taken:
1. P3D and ALL addons uninstalled via Windows Control Panel
2. C drive checked manually in ALL folders and sub-folders for for remains of ANY P3D addon and deleted, including the RegEdit utility
3. Restarted Computer
4. Disk Cleanup performed
5. Disk Defragment checked - found 1% fragmented
6. Defragmented C drive
7. Computer restarted
8. ALL graphics drivers uninstalled and any remains deleted from system (graphics auto reverted to version 398.?? which came installed with graphics card out of the box)
9. Current version of Nvidia graphics driver downloaded directly from Nvidia and installed using custom clean install (absolutely not 1 single setting/feature/modification made to default settings with fresh install)
10. Computer restarted
11. P3Dv4.3 downloaded directly from Lockheed Martin and installed running installer as administrator and installing to a new P3Dv43 folder created on desktop
12. P3Dv4.3 SDK downloaded from Lockheed Martin and installed to a sub-folder created in the P3Dv43 folder created on step 11
13. Computer restarted
14. P3Dv4.3 launched directly from install folder, registered and tested - PASSED (absolutely not 1 single setting or option changed from P3D default with clean install)
15. GSX/L2 downloaded directly from FSDT and installed into a GSXL2 folder created inside the P3Dv43 folder created in step 11
16. Ran FSDT Live Update
17. Computer Restarted
18. Verified default jetways disabled in GSX Control Panel
19. Disk defragment checked - 1% fragmented, defragmented C drive
20. Computer restarted
21. P3D launched directly from installed location with GSX installed and running (please note, at this time there are no other addons reinstalled yet, not even FSUIPC, NOTHING only P3D and GSX/L2)
22. GSX functions tested: GSX rebuild database upon P3D open at default airport - PASS; Addon Manager showing in Add On menu in P3D - PASS; GSX Menu showing with default Crtl+F12 keypress - PASS; Follow-me car requested and arrives, follow to gate where verified P3D default gates were replaced by GSX SODE gates and ground service vehicles/marshal appear and are active - PASS (dedpite having deleted any trace of GSX I could find anywhere on the computer, Addon Manager showed GSX and GSXL2 as activated the 1st time I ran P3D with GSX reinstalled)
23. After engine shutdown, opened GSX menu and selected Customize this parking. Changed jetway type and textures only and applied - PASS
24. Selected Customize Parking from parking editor menu and observed for proper functions - PARTIAL PASS
25. Selected all 3 gates at default airport and edited jetway texture and additional options and applied - PARTIAL PASS
26. Reset airport to default in parking editor and observed proper changes - PARTIAL PASS
Notice steps 24, 25, and 26 are only PARTIAL passes. Here is what I found (keep in mind what I'm about to say was reported before with different settings and did eventually lead to the major issue of P3D becoming unresponsive when clicking "apply")
In step 24, when entering into SLEW mode to customize parking position and item locations, the jetway was rotated 90 degrees with head pointing opposite direction while jetway additional features such as logo, AC Unit, and Power unit remained in correct position - https://prnt.sc/l3temb and also noticed that the gate number was now a black box again - https://prnt.sc/l3tf7s but otherwise all commands were correct with texture color and model type change
In step 25, when all 3 gates were modified at once, noticed that all 3 gates now have black box for gate number however, texture color and model changes were correct - https://prnt.sc/l3tfyn https://prnt.sc/l3tg4r
In step 26, after resetting airport to default in parking editor, noticed that all 3 gates now had Logos that went thru instead of along the jetway and still all 3 gates had black boxes for gate numbers - https://prnt.sc/l3tgzk
As evidence that ONLY GSX has been reinstalled, here is my add on menu from P3D - https://prnt.sc/l3tgca
What I also noticed, is that for each of these partial pass tests, P3D was auto-pausing due to the parking editor window opening. Once the sim was unpaused in P3D, ALL features corrected themselves (jetway returned to normal position from step 24, Logo corrected position from step 26, all gate numbers showed correctly in all 3 steps). Here is the ONLY change that was different between this testing and the testing performed prior to a full uninstall and reinstall: I had the "Pause on task" switch turned OFF prior to uninstall in P3D.. I retested again with the "Pause on task" switch OFF and all changes were made to all 3 steps above without issue.
I still need to go back and reinstall the addons I had before, and also want to test steps 24, 25, and 26 again at ZBAA (both default and modified AFCAD) before I reinstall addons. At this point, it would seem the issues (perhaps all of them) I was having were caused by a conflict with P3Dv4.3 and GSXL2 perhaps having something to do with the sim not being paused when edits were made (just a guess from the testing and results thus far)? Umberto, anyway this could have been the issue? Especially at large airports when making a massive amount of changes to each parking position? Perhaps while customizing both GSX positions and parking positions in AFCAD at the same time (of course unable to compile changes in AFCAD while sim is running in that region) so a lot of going back and forth between screens?
So far that is the only explanation I can think of given that the testing in a fresh install of only P3D and GSXL2 showed very similar errors while the sim was automatically placing itself in pause while edits are made (in pause with edits being made, errors show. Unpause sim and errors correct themselves). I'm thinking that someway created a conflict between the old install of GSX and P3D which lead to P3D becoming unresponsive. Umberto, please feel free to correct me or offer your insight. Id like to know what exactly caused the errors I had so I can prevent them from happening again. I have not at all enjoyed not being able to use my simulator for the past 3 weeks, and I did not enjoy having to uninstall everything and reinstall. How exactly are we supposed to be making edits using the parking editor? Sim paused and then unpause after GSX had time to make changes and verify all changes made? Is it OK to have the "Pause on task" switch OFF when making changes with parking editor? What's the correct method? It looks to me like either P3D or GSX thought the old install of P3D was in pause which would lead to me seeing the same errors already reported but the sim not being in pause and when that conflicting information was recieved by the P3D program (thought it should be in pause but wasn't) then that could have created the reason the sim went unresponsive. I know you get on late (my time) so I'll keep testing until all addons are reinstalled one by one and retested after each reinstall but I am eager to hear your thoughts about this.
-
I read the whole message but, basically, the main thing you said is:
- Everything works correctly if the "Pause on Task switch" option is disabled.
I'll look into it but, there's just nothing we can do about it, if the simulator doesn't call our software when it's paused, maybe it's something new in the PDK (which is a new SDK not many developers use).
-
Well, for one, I haven't finished testing, so marking this as solved is premature in my opinion. Secondly, the issues that I posted in the screenshots on the last post were the exact same issues I was getting just prior to P3D becoming unresponsive (black gate numbers, jetway models disconnecting from jetway addons when in edit mode), as they were reported just days prior, so it IS still possible once I have reinstalled everything, the same issue could arise again. If you recall, both of those issues were reported and while attempting to troubleshoot them is when the issue of P3d becoming unresponsive when clicking apply came up. Please allow me time to complete testing before marking the issue as solved. There are still MANY addons to be reinstalled and tested and any one of them could have created the conflict. I'll have most if not all the addons reinstalled in the next few hours but will then need to do some editing within some of those addons to get the sim back to where it was prior to the uninstall.
It is factual that this this exact moment with absolutely nothing installed except P3D and GSXL2, the default airport and the default P3D planes are not causing the sim to become unresponsive at this time, but there there is still much work to be done and any number of variables could arise again causing the same issue. It's your forum and do as you wish, but until I have all addons reinstalled and tested, I don't see the problem as solved.
-
There are still MANY addons to be reinstalled and tested and any one of them could have created the conflict.
Of course some other addon was likely the cause. I was quite sure of this.
It is factual that this this exact moment with absolutely nothing installed except P3D and GSXL2, the default airport and the default P3D planes are not causing the sim to become unresponsive at this
That's precisely my point.
but there there is still much work to be done and any number of variables could arise again causing the same issue. It's your forum and do as you wish, but until I have all addons reinstalled and tested
When you'll find the conflicting addon, you should report it to its developer, perhaps with a quick update here too.
-
It was most likely NOT another addon, since I previously stated that by uninstalling ONLY GSXL2 the sim and all other addons ran 100% perfectly fine without so much as even a stutter. Even GSX L1 ran great. I had not 1 single problem or error with any addons since buying P3D and add-ons as they came out before installing GSXL2. So the chances of another addon failing at the exact time I installed your addon is about 0%.
There may some conflicts between your addon and their addon, but they will most likely not make changes to their product if it was not the faulting product, as yours was. You wouldn't care if I came to you and said that GSX works perfectly, however when ran at the same time as, lets say, Ultimate Traffic Live, it causes the sim to crash. That's not your issue because its not your faulting program. Their products ran great with no issues. It was your product that has now cost me over a years works of updates needing to be replaced and over 3 weeks of frustrating troubleshooting leading nowhere that resulted in me having to completely uninstall and remove all traces of P3D and all addons just so I could say that at its very basic (no weather, no traffic, no addons, no textures, no enhancements what-so-ever that 98% of the flight sim world installs), very basic, your product is working, at this time.
Is the problem resolved? No. I haven't finished testing it.
Have we found the issue so others can fix without all the stress I've been thru if they run into the same problem? No
All you've done is the same as you have since the beginning: Find 1 sentence that looks like what you want and just focus on that while blaming everyone else and their products for causing errors that did not exist before your product was installed. This issue is not solved until I am done testing and confirm it is. If this is how you work with your BETA team, no wonder L2 has had so many issues. They would tell you they have 1 thing working and you'd release the entire project to the public and take their money for it. There are GSX L2 issues listed all over flight sim forums, for a product that has only been out less than a month! AFTER I have finished testing, I will confirm if this issues is solved or not. The I.T. team I have been working with trying to get your product to work has a few ideas at what may/might have been the issue, but we will not know until testing is done.
Clearly there is still some underlying issues with GSXL2 which surfaced just prior to crashing my sim. Just look at the screenshots! That's not normal! That's not a functioning bug free program!
No one wants to spend $69USD if it means that they will have to uninstall all their other addons just to get yours to work correctly. I'd rather just not have L2 if that is the case.
I'll update once testing is done with the findings.
-
There may some conflicts between your addon and their addon, but they will most likely not make changes to their product if it was not the faulting product, as yours was.
AFTER we'll find if there are conflict, you might start to speculate which one is the "faulting" product. You are making a judgement before getting all the facts. Right now, the only fact you have, is that GSX works fine with a clean installation.
It was your product that has now cost me over a years works of updates needing to be replaced and over 3 weeks of frustrating troubleshooting leading nowhere that resulted in me having to completely uninstall and remove all traces of P3D and all addons just so I could say that at its very basic (no weather, no traffic, no addons, no textures, no enhancements what-so-ever that 98% of the flight sim world installs), very basic, your product is working, at this time.
Every other developer will probably tell exactly the same: until you try a clean reinstall, you cannot possibly prove who's the faulting product.
Is the problem resolved? No. I haven't finished testing it. Have we found the issue so others can fix without all the stress I've been thru if they run into the same problem? No
You are making my point, again. You might have not found the faulting product yet, you only found that GSX now works fine on a clean install.
If this is how you work with your BETA team, no wonder L2 has had so many issues. They would tell you they have 1 thing working and you'd release the entire project to the public and take their money for it. There are GSX L2 issues listed all over flight sim forums, for a product that has only been out less than a month!
You could say the same for just every other product released recently. If you "read the forums", you might assume NO FLIGHT SIM PRODUCT basically works when it's released. That's not true, of course, but on support forum, you'll ONLY find post of users asking for SUPPORT, that's why they are called "support forums".
Clearly there is still some underlying issues with GSXL2 which surfaced just prior to crashing my sim. Just look at the screenshots! That's not normal! That's not a functioning bug free program!
All your screenshots were made when you had problems. You now say that, with "Pause on Task switch" disable, it works normally. Is this still true ?
No one wants to spend $69USD if it means that they will have to uninstall all their other addons just to get yours to work correctly. I'd rather just not have L2 if that is the case.
You can probably say the same of the yet-unknown-addon who's causing the conflict.
Don't worry, if you IDENTITY the conflict, we WILL have a look at it and, eventually, work with the developer.
The issue is, lots of times when users report a "sure" conflict, we usually contact the developers, exchange a free copy of our addons (we developers DO NOT use all the stuff you users use, we wouldn't have any time to do, you know, *development* if we also had to install other's guys stuff), and we almost invariably find ourselves not able to replicate the issue.
It recently happened with Ezdok Camera, Active Sky VRS Tac pack, and A2A accu-feel. In ALL cases, duly following users reports of conflicts between these and our software, we sent GSX to them, they sent their product to us, and NEITHER us or them were able to find ANY problems.
That's just to clarify what we do. We'll do it in your case too, don't worry.
-
Not ignoring the above, taking it into consideration as testing continues, however, I am about to test on a modified AFCAD file (enhancement for FSX default airport downloaded from AVSIM, modified and updated by myself to work with P3Dv4), but a thought crossed my mind and only you know the answer:
ADE1.75 (probably previous versions also) complies into a .bgl file which GSX reads for gate and item placement per the editor. However, ADE also has the ability to make the same .bgl with an xml copy (stored wherever user would like). Since P3Dv4 is heavy with xml usage, does GSX L2 look at all for AFCAD modifications in xml format? I haven't been saving any xml files with the bgl files for airport AFCAD modifications to save space.
Simply put: does GSX L2 want the AFCAD in bgl, xml, or both?
-
took modified AFCAD and saved the BGL file to P3Dv4. NO OTHER ADDONS YET REINSTALLED, so this is still only P3Dv4.3 and GSX ONLY along with the AFCAD file (attached). No settings have been changed except turning off the "pause on task" (which I will reactivate and try testing the same AFCAD again. I will also try placing the modified AFCAD directly into the main P3D install folder instead of the external folder Lockheed Martin stated must be done prior to 4.3 update).
when 1st loaded, noticed the gate I was at had a black gate number, but others around showed fine - https://prnt.sc/l3wphj
launched gate editor window using Ctrl+F12 and selected all parking with /J and changed gate model type, texture color, added ground markings, removed logo, and left show gate number checked as it is by default and applied changes. After a few moments all visible gates in any view had been changed to the new settings applied, with the exception of still a black gate number at the spot I was parked in. Selected that spot and clicked to customize jetway and P3Dv4.3 became unresponsive immediately upon clicking apply - https://prnt.sc/l3wrf4 (top left corner shows "(not responding)"
The AFCAD file is the only addition I have made to P3Dv4.3 since previous testing, so we could say it is the AFCAD, but if so, why before the uninstall of P3D did all the other 186 modified AFCAD files not have the same issue of causing P3D to become unresponsive prior to this one? I haven't done anything different with the AFCAD than I do with any others.
The original FSX AFCAD by Ray Smith can be found on AVSIM searching file: fsx_zbaa_rs.zip
Changes I make to update AFCAD:
1. Ensure all building and object models will show by opening the AFCAD in ModelConverterX and exporting the models as a P3Dv4 .bgl file and placing that file into P3D main install folder ... Scenery/Global/Scenery
2. Add bgl file from step 1 into ADE1.75 Library Object Manager
3. Open original AFCAD file
4. Select all aprons and change "Draw Surface" and "Draw Detail" to Yes (required by P3Dv4 for the surface type to show in the sim)
5. Open the list of Taxi Links
6. Select all (this will select all Taxiways, Parkings, Paths, Runways, vehicle roads, closed taxiways)
7. click Edit
8. change "Draw Surface" and "Draw Detail" to Yes (required by P3Dv4 for the surface type to show in the sim)
9. Draw Polygon around airport following the boundary fence to flatten the entire airport to 1 elevation (the reported elevation of the airport), exclude AutoGen (no trees on the runway or taxiway etc)
10. Compile and save
i'm not making any changes that would cause the AFCAD to have any issues. And all 186 AFCADs worked perfectly without GSX, and also worked with GSX L1.
Further testing:
Removed AFCAD from the standard AFCAD addon folder I created and made a new ZBAA folder with scenery and texture folder. Deleted old scenery from P3D and add the new one. Closed P3D and reopened (ensure both P3D and GSX read new scenery) - used the EXACT same AFCAD that I was using when freeze happened but just in a different location and folder structure. Used default plane and moved to the same gate I was at above (233 in the attached AFCAD) at ZBAA. This time, gate 233 gate number was working, but the one to my left which was working before is now not working. So we at least still have the issue of random gates getting black gate numbers. I opened parking editor and it is referencing the new and correct scenery folder and AFCAD. Made some jetway texture and model changes and applied, but no sim freeze this time. Waited a few moments for changes to apply. Turned back on "Pause on task" switch and reopened parking editor and made some addition changes in texture colors and models and applied, again no freeze but also not all gate numbers showing. Waited a few minutes for all gates to update the applied settings. So at this point with only P3Dv4.3 installed, GSX/GSXL2 installed, and 1 AFCAD scenery installed I am still have ALL the issues I reported before - jetway modeling issues, black gate numbers, and P3D becoming unresponsive when clicking Apply from the GSX editor (may be random with having to create a new scenery folder for every AFCAD file because with all AFCAD files in 1 addon folder, GSX would cause P3D to become unresponsive 100% of the time, but seem to act SLIGHTLY better with each AFCAD having its own scenery folder and added by itself into P3D addons).
So I'm wondering whom should I be contacting about a faulty product now? Lockheed Martin whos simulator platform has worked fine for years? Scruffy Duck who designed the AFCAD Editor (ADE) when FSX was new and keeps it updated including for P3Dv4 and has had no issues? Ray Smith who added parking and a few pieces of static eye-candy vehicles to the FSX default airport and uploaded it to AVSIM almost 1 year ago and whom I've been in contact with and he has reported no issues on FSX or P3Dv4.3 with the AFCAD on his system, nor anyone contacting him reporting issues with it from their systems? Or you, Umberto, whos product at this point at best has random jetway issues including but not limited to: black gate numbers at random stops and will change to different spots if you change the scenery location AFCAD (but you blame the use "moving too fast", modeling issues when sim is paused (but you blame the user "didn't allow all the files to download from the server), people have been reporting jetways on roofs of buildings (not an Issue I have) (but you blame the user for having a faulty AFCAD despite there are a handful of these reports), Editor causing sim to randomly become unresponsive and forced to shut down (but you blame the other addons which aren't even installed at this point, antivirus which isnt even installed at this point, system problems despite that removing GSX results in 0 issues outside of having GSXL2 installed), other issues located here in this forum AND on AVSIM forum, P3D forum, FlightSim Forum (at least 4 forums with issues relating to your product). You have so far blamed everyone but never accepted the facts that there is SOMETHING that is not right with this program. So who should I be contacting? Seems to me this is 300% a GSXL2 issue and blame cannot, at this point, be placed anywhere else. I have a group of developers and I.T.Professionals who agree with me! This is a 100% clean install of P3dv4.3, no antivirus software even installed on my computer right now to conflict with files, Clean GSX install, no addons running or installed, no settings changed, every trace of P3D and ALL the addons and folders were deleted from the system including ANY mention of any of the programs in the RegEdit. There's no one else to blame here. This is a GSX issue plain and simple. You can see the screenshots, and I've given step by step every single action performed since before I uninstalled anything up to this point. Can you please just accept the facts and find a solution? I can't program your software myself, that's something you will have to do.
You have not ever told me once that you have presented ANY of the many issues I've had with L2 to the team to be investigated and see if there is a bug somewhere. Instead, you point the blame at everyone else and cause us to do your work for WEEKS until you finally decide, "yeah, he did a clean install and is still having the exact same issues. Maybe this really is a GSX issue and we should do something about it." I'm beyond frustrated and annoyed with L2 at this point. I have not been able to do 1 single flight with it since installed. I can uninstall it and fly for years to come without any more issues, but then I would have wasted my money and you don't do refunds as you stated in a message despite the fact that a search on the forums shows results where refunds had been given in the past. I have been sold a faulty product advertised as working despite evidence that it is NOT working, the developer refuses to resolve the issues, and refuses to offer a refund ...
-
Further information regarding the issues: As I stated in the past, I felt these issues were connected. If I attempt to edit a gate where the gate number shows correctly, I have no issues at all other than other random gates not showing gate numbers correctly. HOWEVER, when I try to edit a gate position whos gate number is a black box, THAT is what is causing P3D to become unresponsive. I'll try to find a recording software online and upload a video and attach the GSX log file to this message when they are ready. I will walk you thru every step I'm taking and I guarantee you 100% I can reproduce the error 100% of the time.
-
I have no issues at all other than other random gates not showing gate numbers correctly. HOWEVER, when I try to edit a gate position whos gate number is a black box, THAT is what is causing P3D to become unresponsive
That's what I always said, right from the start: there must be something wrong with your video card drivers/settings, because that's the only thing that can freeze the sim, and it's the same which is causing the black numbers.
So I'm wondering whom should I be contacting about a faulty product now? Lockheed Martin whos simulator platform has worked fine for years
I tried to explain this to you several times, but it seems to keep ignoring it, or decided not to hear it, because you didn't like the answer.
What creates the black numbers is a relatively NEW feature, called "Render To Texture", which has been introduced sometime in P3D 2.5, but nobody used it. It was updated many times, usually following OUR feedback, because it had issue in P3D3, and it was updated again, many times, with P3D4.
Again, please note, GSX Level 2 is probably the first released addon which use this feature so, we are the first putting this feature to the test, in the real world.
It's highly interactive with video drivers, so it's potentially exposed to issue with them, or their settings. So, it's very much possible that, under certain conditions, it might fail, and maybe you are just discovering an unknown bug in the simulator that, if you could just STOP blaming GSX for this, it might be useful for everybody (even other developer) to report it to LM, assuming it CAN be reproduced ( I can't, for example ).
WHICH IS WHY, I believe I asked you to DISABLE it, to see if this is in fact what causing your problems. The "Disable RTT" option in the Addon Manager does just that: it turns off a feature that, since it's brand new and not much tested, might cause problems with some configurations.
Have you tried doing what I already suggested, to turn it off, and see if the sim doesn't freeze anymore ? Note that, you *must* restart the simulator after you turn it off. OF COURSE, you will not seeJetway Numbers anymore: that's precisely what the option does.
-
Which video driver do you use and I'll custom clean install that one? If we are using the same drivers and I can still reproduce the problem, then we can rule-out a driver conflict. I am running the latest from Nvidia (custom clean install after deleting and uninstalling all NVIDIA components all the way back to how it came out of the box. the current version is 411.70 and out of the box was 398.?? (I didn't catch the last 2 numbers).
Here are the videos showing the errors in real time. The recording software has a 5 minute limit so It's 2 videos. It took me 2 times to get gate 222 to cause the sim to stop responding, but it did happen. I'll test again a few times with spots where the gate number works, test functions at P3Dv4.3 default KATL (I don't have a AFCAD for this airport anymore, but its big enough default to test for errors without AFCAD addon), and I'll test with RTT on and off. Those Videos will be posted as they are completed.
For the record tho, seeing jetway numbers is a feature that required me to have to pay real money to use, so IF disabling RTT fixes the issue, I'm still not getting what I paid for because I have to disable the paid feature to get a working product which I could have gotten from GSX L1. Yes, there are other features to L2 that I look forward to eventually being able to use, but the product is still not complete as paid for.
Video 1 -
Video 2 -
The FS Labs folder is in place, but I have not downloaded and reinstalled the FSLabs A320 yet. The other addons in the addon folder is where all addons are kept. Aside from the ZBAA, all other files are only being read by ADE at this time, not P3D or GSX.
And as promised, attached is the log from the testing done with the videos listed here. I did not see anything unusual in the log, except that it was looking for scenery that isn't installed ... not sure if it is just searching for FSDT scenery or if it thinks there should be scenery somewhere when it was deleted prior to reinstalling P3D.
-
Which video driver do you use and I'll custom clean install that one? If we are using the same drivers and I can still reproduce the problem, then we can rule-out a driver conflict. I am running the latest from Nvidia (custom clean install after deleting and uninstalling all NVIDIA components all the way back to how it came out of the box. the current version is 411.70 and out of the box was 398.?? (I didn't catch the last 2 numbers).
As I've said, several times by now, it might not just be a "driver" problem, but simply a driver tweak or setting. I couldn't see black numbers with ANY driver but, FYI, I'm using 416.11 right now, which is the current version, according to the GeForce Experience software.
and I'll test with RTT on and off. Those Videos will be posted as they are completed.
Testing by disabling RTT is likely the most meaningful test you can do now.
For the record tho, seeing jetway numbers is a feature that required me to have to pay real money to use, so IF disabling RTT fixes the issue, I'm still not getting what I paid for because I have to disable the paid feature to get a working product which I could have gotten from GSX L1. Yes, there are other features to L2 that I look forward to eventually being able to use, but the product is still not complete as paid for.
RTT is a FEATURE OF THE SIM. So, whatever money you paid to get this feature, you paid it to LM so, if this feature has a problem ( on YOUR system ), it should be your own interest, as a LM customer, to report it. If we find problem, we'll report it too, of course.
You might have had a point if we FORCED you to use it, and crashing your sim because of it but, if the feature is bugged in the sim, the most we can do is to ALLOW you to disable it, which is what we do.
-
And as promised, attached is the log from the testing done with the videos listed here. I did not see anything unusual in the log, except that it was looking for scenery that isn't installed ... not sure if it is just searching for FSDT scenery or if it thinks there should be scenery somewhere when it was deleted prior to reinstalling P3D.
Your log doesn't show any errors (those that looks like "errors" about the not installed sceneries are not errors, they are normal), other than a minor issue of not being able to find a deicer for the airplane you are using, which I don't think it's a problem, however, I always customize an airport with a fully supported default airplane.
Other than that, the log simply shows GSX didn't cause any errors, and it correctly detected the sim has crashed on its own.
-
I didn't see your post about the testing with RTT disabled until after uninstall took place. I tested with RTT disabled using the modified AFCAD at different gates just now, using different textures and models and more than 1 jetway at a gate and I couldn't get the sim to become unresponsive.
This seems it is an RTT issue. A clean install wasn't a bad idea anyway, ruled out other issues and made things more organized. So now that we know what is causing the issue, the question is how does it get fixed and how does it get prevented from happening the next time Nvidia releases a new driver (every month of so it seems). or better yet, which driver was this tested with and I can just install that driver and update later. Nvidia loves to release drivers that are more toward VR which I don't have, and for games I don't play. I can do without having the latest driver, but which driver version do I need?
I will take a moment and apologize for being frustrated. I purchased L2 and had high hopes of being able to quickly customize airports and enjoy the product, but was severely let down and frustrated when the errors began and would not stop. I'm sure you and the team will come to a solution and in the mean time, I'll have to leave RTT disabled to use the product.
Does having RTT disabled remove any other features?
-
Does having RTT disabled remove any other features?
For the time being, the jetway numbers and the display on the battery charger in the power unity.
-
I'm running Windows 7 64-bit and newest driver I can get is 411.70 ... so maybe this is a driver version limited by windows issue? If you are able to get a higher driver than I can, it can only be because of the windows version, and if your driver is working and mine is not, then it may a limitation with windows 7 and Nvidia?
Here is what nvidia website shows me for latest available driver:
GeForce Game Ready Driver
Version: 411.70 WHQL
Release Date: 2018.9.27
Operating System: Windows 7 64-bit, Windows 8.1 64-bit, Windows 8 64-bit
Language: English (US)
File Size: 469.19 MB
download
Release Highlights
Supported products
Additional information
Game Ready Drivers provide the best possible gaming experience for all major new releases, including Virtual Reality games. Prior to a new title launching, our driver team is working up until the last minute to ensure every performance tweak and bug fix is included for the best gameplay on day-1.
Game Ready
Provides the optimal gaming experience for Assassin’s Creed Odyssey, Forza Horizon 4, and FIFA 19
Gaming Technology
Includes support for NVIDIA GeForce RTX 2080 and RTX 2080 Ti graphics cards
-
Good news, I downloaded the AFCAD you posted earlier, and I think I found the issue. Yes, I think we can fix it, I'll keep you updated.
-
awesome! thanks! Was it the AFCAD? I tried 2 different AFCADs for ZBAA and before disabling RTT both would freeze the sim. I also recall starting to have the issue of black gate numbers prior to uninstall when I was working with either KSNA or KSEA, both had AFCADs downloaded from AVSIM and modified as stated above.
I was just reading the P3D forum posts about RTT issues with Windows 7, going back to July this year. I guess it would have helped you to know I was on windows 7 when the issues first came up so you would have probably at that moment known it was for sure RTT conflict with windows. But I also don't see LM looking to fix that bridge.
it's almost 6AM here and I've been awake for 24 hours at work followed by finishing reinstalling P3D and GSX and testing since. I'll look for a reply when i wake up.
Oh, BTW, the AFCAD I uploaded, has library objects that if you do not also have, will display black boxes in ADE. I have all the library objects and can send them to you if needed. I think they were compiled into the original AFCAD (link somewhere above) but I extract them and make a new bgl file for just the models and place it in the main install folders under Scenery/Global/Scenery ... that way if another airport AFCAD I download wants to use them, they are there. Ray Smith makes a lot of AFCAD files that are easy to convert to P3D4 usable but he also loves to reuse a lot of static objects in them. So the uploaded AFCAD I don't think has the objects compiled into it. I wish there was a way to keep them intact, but once an original AFCAD is decompiled, which it must be to apply changes so P3D4 will read it properly, there is no way to recompile with the objects still intact except for extracting the objects to their own bgl file. So each AFCAD would have 3 files once completed: XXXX_ADE4_SD.BGL (main airport) XXXX_ADE4_SD.CVX (ground poly to flatten and exclude autogen) and XXXX_ADE4_SD_OBJ.BGL (kept in the main P3D install folder and contains only the object models from the original AFCAD. The other 2 files are USUALLY kept in a folder outside the main P3D install folder in a folder only for AFCAD addon which has the Scenery folder for all the AFCAD and the texture folder for any textures that may need to go there, then the Addon AFCAD folder is activated in P3D as addon scenery). This method has worked true for me, up until RTT came about, if it is in fact what is causing the break.