FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Martyjr on December 09, 2018, 08:58:08 pm
-
SODE stopped when exiting P3Dv4.4
I was at KLAX gate 105
All GSX and SODE (v163) jetway was operating.
I attached /detached jetway ok.
Exited P3D.
Got a SODE Stopped working mesaage box "close the program"
I got the COUatl log and the P3D content log for reference.
-
Your content error log shows so many errors in your addon, some caused by missing files in the PMDG airplanes, some caused by mistakes in a 3rd party scenery, and some by errors caused by an unknown addon which is causing problems with variables, most likely an airplane gauge.
And, since many lines of the log are in Chinese, I cannot say more about.
The only thing sure, it's that nothing in your log shows any errors with GSX, KLAX or SODE so, most likely, SODE crash as a result of those other problems.
-
Thanks for the reply.
I contacted PMDG (forum) about the fx errors. Their response was:
"Ignore it. "
Could taxi path errors have to do with OrBx products and not FSDT KLAXv2 ?
[error.25]
error=Taxiway path with 0 width
[error.26]
error=Taxiway path with 0 width
I will do a couple more tests with different aircraft and other (SODE in use) airports.
The log I sent has no Chinese in it (sample what I see in my file):
*******************************************************************
[error.0]
error=Failed to load visual effect "fx_PMDG_NGX_navwhih"
[error.1]
error=Failed to load visual effect "fx_PMDG_NGX_navwhih"
etc;
[error.19]
error=Gauge/Script Error
Type: Unknown
Name: Unknown
Error: PANELS lookup_var : SimVarGet Failed - Module_Var ID: "692".
[error.20]
error=Gauge/Script Error
Type: Unknown
Name: Unknown
Error: PANELS lookup_var : SimVarGet Failed - Module_Var ID: "674".
[error.25]
error=Taxiway path with 0 width
[error.26]
error=Taxiway path with 0 width
[error.27]
error=Taxiway path with 0 width
[error.28]
error=Taxiway path with 0 width
[error.29]
error=Taxiway path with 0 width
[error.30]
error=Taxiway path with 0 width
-
I am doing new tests now.
Test 1
This is the Context error log for:
P3Dv4.4
Default F22 jet
FSDT KLAXv2
Gate B48
SODE v163 active
GSX Purchased
GSX v2 demo (not purchased) active.
Jetway was not used
When I exited P3D I did not get a SODE "stopped working" error. Maybe it will come up in my next test.
Could you comment on errors 0 and 77?
[error.0]
error=Taxiway path with 0 width
more of same to next error until # 76
[error.76]
error=Taxiway path with 0 width
then
[error.77]
error=Invalid Texture name "DDS" specified for model "Win_Adt_Male_008_ArcWalk1_PF1".
This last error a known P3D error:
[error.78]
error=Payload station indexes should be between 1 - 1
-
None of the errors in your log are caused by any of our products.
The taxiway with 0 width is coming from another scenery that was loaded in that session, not necessarily in that area, but the simulator will report it as long it was loaded during that session.
The Win_Adt_Male_008_ArcWalk1_PF1 error is not an object that comes with any of our products
And you have two errors, 19 and 20, which seems to be caused by an airplane gauge, in addition to the two errors in the PMDG Effects.
I can safely assure you that, installing GSX and KLAX on a clean install of the simulator won't result in any errors logged.
-
Thanks for the follow up information on the Context errors. I will try to track them down.
The reason I posted the logs was to give the only technical data I had that maybe pointed to a possible SODE or FSDT problem.
Did a few more tests.
My test 3 setup (below) gave the SODE error when I exited P3Dv4.4
My test 4
(KPHX)
did not give a SODE error after closing P3Dv4.4
nor the Invalid Texture name "DDS" specified for model "Win_Adt_Male_008_ArcWalk1_PF1 error
Test 2
******
This is the Context error log for:
P3Dv4.4
Default PMDG777
FSDT KLAXv2
Gate B48
SODE v163 active
GSX Purchased
GSX v2 demo (not purchased) active.
PMDG777 I attached External power cart and external air
PMDG777 I selected Ext power Avail to ON
PMDG shut down engines
Jetway was not used
When I exited P3D I did not get a SODE "stopped working" error. Maybe it will come up in my next test.
Test 3
******
This is the Context error log for:
P3Dv4.4
Default PMDG777
FSDT KLAXv2
Gate B48
SODE v163 active
GSX Purchased
GSX v2 demo (not purchased) active.
PMDG777 I attached External power cart and external air
PMDG777 I selected Ext power Avail to ON
PMDG shut down engines
Jetway was docked/undocked
When I exited P3D I got SODE "stopped working" error.
Context error: error=Invalid Texture name "DDS" specified for model "Win_Adt_Male_008_ArcWalk1_PF1".
Test 4
same as previous setups
I used a different airport with SODE: KPHX
terminal 3 gate 5
Jetway was docked/undocked
No SODE error exiting P3Dv4.4
No context error: Invalid Texture name "DDS" specified for model "Win_Adt_Male_008_ArcWalk1_PF1".
Edit, I sen this to Orbx forum:
I was at KLAX (KLAXv2 by FSDT) and I noticed a P3Dv4.4 Context error log entry:
[error.93]
error=Invalid Texture name "DDS" specified for model "Win_Adt_Male_008_ArcWalk1_PF1".
I asked FSDT and they said it was not their's
So, I did some searching and found some similar textures names here:
C:\Lockheed Martin\Prepar3D v4\ORBX\FTX_AU\FTXAA_ORBXLIBS\Texture
-
The reason I posted the logs was to give the only technical data I had that maybe pointed to a possible SODE or FSDT problem.
It's surely not an FSDT problem, since nothing in your report or in your log ever indicates a problem with any files belonging to FSDT.
But, since you had several content errors related to files belonging to other products, it's *possible* they might causing issues TO SODE, with the one related to the Gauge being the most likely.
So, I would try to get rid of ALL errors first, and see if you still have problems with SODE.
-
I am working on the errors by contacting product developers.
The error=Invalid Texture name "DDS" specified for model "Win_Adt_Male_008_ArcWalk1_PF1". was Orbx, they will fix it.
For the gauge errors I will try another aircraft (not PMDG) today.
So far, as mentioned in my last post, the SODE problem (after exiting P3D) only is at FSDT airports and only if I dock and undock the jetway.
No SODE problem at KPHX (with PMDG aircraft).
-
So far, as mentioned in my last post, the SODE problem (after exiting P3D) only is at FSDT airports and only if I dock and undock the jetway.
But since nobody has ever reported it, it's surely something specific in your configuration, that's why I said to get rid of the error first, and then we can look at it, if it's still there.
Fact it only happens at FSDT airports, it's just because SODE works a bit differently there, but that doesn't automatically mean there is a problem with the airports, otherwise it would happen to everybody.
-
Just did another test.
Went to KJFKv2 gate 840
Used iFly737
docked/undocked jetway
exited p3dv4.4
got the SODE stopped working message
The Content log no gauge errors but did have taxi path errors logged:
[error.0]
error=Texture I737_WING_L_L.DDS failed to load (FE_REQUEST_STATUS==13)
[error.1]
error=Texture I737_WING_R_L.DDS failed to load (FE_REQUEST_STATUS==13)
[error.2]
error=Taxiway path with 0 width
many more taxi errors then
[error.111]
error=Texture I737_WING_R_L.DDS failed to load (FE_REQUEST_STATUS==13)
[error.112]
error=Texture I737_WING_L_L.DDS failed to load (FE_REQUEST_STATUS==13)
[error.113]
error=Payload station indexes should be between 1 - 8
the end the log
-
The Content log no gauge errors but did have taxi path errors logged:
And again, none of these errors have anything to do with FSDT or SODE but, as I've said, get rid of ALL the errors first, and then we might proceed.
-
Did another test, P3Dv4.4:
GSX disabled
Reboot PC
iFly737 , KPHX, normal SODE jetway operation, no SODE error after exiting P3D
Reboot PC
iFly737
KJFKv2 FSDT
Gate 840
SODE not available (normal, with GSX disabled)
No SODE error after exiting P3Dv4.4
-
GSX disabled
As I've said in my last post, SODE works a bit differently when used with GSX, but that doesn't mean the problem is *caused* by GSX because, of course, if it was, everybody would have it just the same, not just you.
Have you managed to exit from the sim with NO ERRORS in the content report .txt file ? As I've said, several times already, until you remove all the errors in the sim, it's useless keep pointing at GSX, which is clear not the problem.
Of course, I already tried KFJK Gate 840, operating jetways with GSX, and I have no errors of any kind, not on exit and not in the content.
-
"SODE works a bit differently when used with GSX"
Good to know.
I thought SODE was the same at all airports.
"Have you managed to exit from the sim with NO ERRORS in the content report .txt file ?"
Basicall, yes.
I tested the P3Dv4.4 default F22 at default airport (KVPS).
Got one error in content log. This error, per posts on P3D forum, has to do with FSUIPC.
[error.0]
error=Payload station indexes should be between 1 - 1
No errors exiting P3Dv4.4 (as expected).
So, my Content error log errors and errors exiting P3Dv4.4 are from 3rd party products.
Still working on getting rid of all the Content errors at payware airports / payware aircraft.
I am going to do a few tests at other FSDT airports.
Maybe time to for me reinstall GSX / SODE and FSDT airports (one at a time).
I did another test.
I wanted to see the Content log from KPHX, PMDG777 and SODE dock/undock jetway.
There are errors in the log (see 4 typical errors below).
So, as far as I can tell KPHX has the same type of Content errors as FSDT airports.
Got many repeat errors of these four but no SODE error exiting P3D:
[error.0]
error=Gauge/Script Error
Type: Unknown
Name: Unknown
Error: PANELS lookup_var : SimVarGet Failed - Module_Var ID: "673".
[error.7]
error=Taxiway path with 0 width
[error.28]
error=Gauge/Script Error
Type: Unknown
Name: Unknown
Error: PANELS lookup_var : SimVarGet Failed - Module_Var ID: "280".
[error.655]
error=Gauge/Script Error
Type: Unknown
Name: Unknown
Error: PANELS lookup_var : SimVarGet Failed - Module_Var ID: "280".
Edit:
I found out just now what is causing the (many) taxi path errors by reading here:
Taxi path error explained here in post by Gerard (GAAB) an IT guy :
https://www.avsim.com/forums/topic/546614-flysimwware-updates-for-p3dv44/?tab=comments#comment-3940668
-
The taxiways with 0 width shouldn't be a problem. The Gauge script error might be more serious and possibly affect SODE.
And, another thing you should try, is to disable *EVERY* Addon module (yes, including FSUIPC, with "every", I really mean "every"), and leave ONLY the Addon Manager and SODE, and nothing else, and see if you still get the crash on exit.
-
Just for follow up.
Did a quick test :
FSDT KORD
Gates B17 and C20
PMDG777
GSX Level2 Demo Jetways OK
No error exiting P3Dv4.4
Many P3Dv4.4 Content errors like this:
[error.0]
error=Gauge/Script Error
Type: Unknown
Name: Unknown
Error: PANELS lookup_var : SimVarGet Failed - Module_Var ID: "673".
[error.1]
error=Gauge/Script Error
Type: Unknown
Name: Unknown
Error: PANELS lookup_var : SimVarGet Failed - Module_Var ID: "692".
-
FSDT KORD
GSX Level2 Demo Jetways OK
No error exiting P3Dv4.4
With "GSX Level 2 Demo jetways", you mean you replaced all jetways at FSDT KORD with GSX ? That would the only way you could see GSX Level 2 jetways at FSDT KORD, since any airport with default jetways with a *custom* model, and FSDT KORD is like that, requires to exclude jetways first, and replace them with GSX. It's not done automatically.
Being at an FSDT airport, will just mean you are free to do it, even without purchasing GSX Level 2.
So, if you haven't done this, you are not looking at GSX jetways, but just at custom default jetways, which is what FSDT KORD comes with it.
Many P3Dv4.4 Content errors like this:
As I've said, unless you can fix all the errors, you cannot do a meaningful test, and these Gauge errors CAN possibly affect SODE.
Fact you were able to exit without a SODE error at FSDT KORD, doesn't mean they are not harmful to SODE because, as explained above, unless you manually replaced all jetways at FSDT KORD, they are not SODE by default and they are not automatically replaced.
-
"So, if you haven't done this, you are not looking at GSX jetways, but just at custom default jetways, which is what FSDT KORD comes with it."
Using FSDT KORD.
PMDG aircraft.
FSDT custom default jetways at KORD.
Exiting P3D generates a Content error log with the same gauge errors listed as another FSDT airport with SODE jetways.
But there are no errors after exiting P3D.
So, FSDT custom default jetways work with no errors after exiting P3D.
I was just point out the results of my last test.
Edit:
Actually I thought all FSDT airports were supposed to have SODE jetways now using GSXv2 demo e.g., just like KJFK/KLAX.
I just checked my purchase records.
I got the upgraded KLAS and KORD when on sale June 2017.
It looks like KLAS has FSDT/SODE jetways and KORD has FSDT/custom default jetways (not SODE).
Edit:
For your tests where you did not get any P3D Content errors logged.
Where you docking SODE jetway to PMDG 777 or iFly 737 aircraft (which I used in my testing)?
-
FSDT custom default jetways at KORD.
As I've said in my previous message, unless you haven't replaced them yourself, there are NO SODE jetways at FSDT KORD.
For your tests where you did not get any P3D Content errors logged.
As I've said:
"I already tried KFJK Gate 840, operating jetways with GSX, and I have no errors of any kind, not on exit and not in the content."
Where you docking SODE jetway to PMDG 777 or iFly 737 aircraft (which I used in my testing)?
I used a default airplane, since that would be the only sure way to be sure I'm testing GSX, SODE, the FSDT scenery, and nothing else.
-
"I used a default airplane, since that would be the only sure way to be sure I'm testing GSX, SODE, the FSDT scenery, and nothing else."
If I had previously known that I could have tested the same way you did.
I would like to use the same plane you used in my testing today.
Which default plane did you use to dock/undock SODE jetways in your test?
-
Which default plane did you use to dock/undock SODE jetways in your test that did not generate errors in the P3D Content Log?
It will be good to use a standard P3D aircraft to check out problems like the gauge (PMDG) and other errors in the P3D Content Log.