Anyone having SODE issues (red crosses) after W10 updates ?

[GSalden 4,656]

Since 2 days I am getting Red Crosses at SODE gates. Two days ago on both view pc’s U did all updates that W10 advised + optional ones.

At Marseille I noticed it first. An uninstall of SODE 1.63 and install of SODE 1.65 solved the issue

Todat with the new Faro the same thing. So I uninstalled and reinstalled SODE 1.65. It worked right away.

However, when shutting down both pc’s and rebooting them a couple of hours later the same issue appears 

Any ideas ?

[Toktok 156]

The red X is a separate model from the base SODE install. Nothing to do with Win10 updates.

It is an indicator of missing or misnamed model files. If you reference a model by its "SimTitle" in the xml and the MDL file is missing on the harddisk, then SODE will just place the red X. This is also the case if the "SimTitle" in the xml is spelled incorrectly. In both cases the SODE.log file will reveal the underlying problem with an error message. It could also be duplicate SODE jetways or the fact that SODE models from previous install not removed before installing v1.6.5 

I suggest you get in touch with the scenery developers and advise them of this issue which they should fix.

Edited November 3, 2019 by Toktok

[GSalden 4,656]

The red crosses appeared after 2 larger W10 updates.

And like I wrote : when reinstalling SODE it is working o'nce. So if there is something missing it wouldnt be there at all. Not it is there with a clean reinstall of SODE and the next time it is not there.

Just tested it again. It seems that SODE gets Unregistered. So if I re-regsiter it all works again. Till a reboot of the pc's...

This is with SODE 1.65.

 

Edited November 3, 2019 by GSalden

[Toktok 156]

I had major Win10 updates lately also. Removed SODE 1.6.4 and updated to 1.6.5 just this week when Jeffrey (SODE developer) came out with his new VDGS, so again, it has nothing to do with Win10 updates. Win10 does not alter SODE XML files as SODE is a stand-alone module. SODE red Xs are indication of missing or duplicate XML names, etc. My recent RKSI release had duplicate names/files (red Xs) and had to go back into the placement XML for each gate and fixed the offending files. The red Xs are SODE-related errors. Go into your C:ProgramData\12bpilot\SODE\Log and send the log to the scenery developers to ID the offending XML files, etc.

[GSalden 4,656]

Did you read what I wrote...?

When reinstalling SODE it is working at that moment ..   

Someone else a suggestion ?

 

Edited November 3, 2019 by GSalden

[mpo910 2,112]

1 hour ago, GSalden said:

Since 2 days I am getting Red Crosses at SODE gates. Two days ago on both view pc’s U did all updates that W10 advised + optional ones.

At Marseille I noticed it first. An uninstall of SODE 1.63 and install of SODE 1.65 solved the issue

Todat with the new Faro the same thing. So I uninstalled and reinstalled SODE 1.65. It worked right away.

However, when shutting down both pc’s and rebooting them a couple of hours later the same issue appears 

Any ideas ?

Hi Gerard. Are there any permssion problems maybe? What about ADMIN rights for your APPS like P3D or Sode....? After I updated windows I had to set them again. Regards Marcus

[Toktok 156]

I did. Your topic refers: "...SODE issues (red crosses) after W10 updates ?" so I explained to you that red Xs has nothing to do with Win10 updates. I further gave you the example that updating from 1.6.4 to 1.6.5 in my case did not alter my XML files at all. So the possible issue that is causing the red Xs to show - even after you reinstalled 1.6.5 and the red Xs disappeared for a moment - is related to SODE placement XML files specific to the airports you are seeing the red Xs. Write to the SODE developer and he will tell you the same thing.

OK, someone else help this guy with a better explanation. 

[GSalden 4,656]

12 minutes ago, Toktok said:

I did. Your topic refers: "...SODE issues (red crosses) after W10 updates ?" so I explained to you that red Xs has nothing to do with Win10 updates. I further gave you the example that updating from 1.6.4 to 1.6.5 in my case did not alter my XML files at all. So the possible issue that is causing the red Xs to show - even after you reinstalled 1.6.5 and the red Xs disappeared for a moment - is related to SODE placement XML files specific to the airports you are seeing the red Xs. Write to the SODE developer and he will tell you the same thing.

OK, someone else help this guy with a better explanation. 

Please stop replying with the wrong answer.

[Toktok 156]

I am assuming now that you found a fix?

[GSalden 4,656]

14 minutes ago, mpo910 said:

Hi Gerard. Are there any permssion problems maybe? What about ADMIN rights for your APPS like P3D or Sode....? After I updated windows I had to set them again. Regards Marcus

Hi Marcus,

Thanks for thinking with me. Imho the permissions are correct.

Airport model files that aren’t there do not suddenly exist after a reinstall of SODE. Something is not correct and it started after the W10 updates. 
Also 1 Prosim pc had issues but I was able to solve it quickly .

regards, Gerard

[mpo910 2,112]

2 minutes ago, Toktok said:

I am assuming now that you found a fix?

What is this? This kind of reply isnt helping anyone. I read what Gerard wrote AND understood what is finding is. He clearly wrote that everything worked fine untill he did some windows updates. His message is very clear. So maybe stop this irritating statements. 

[mpo910 2,112]

Did you try uninstalling the addon manager also and install this again?

[Toktok 156]

This is an open forum so I jumped in with my response from experience with the same issue to see if that may help. If my responses are irritating from your perspective, then my sincere apologies. No big deal.

[GSalden 4,656]

12 minutes ago, mpo910 said:

Did you try uninstalling the addon manager also and install this again?

No, just in-and reinstalled SODE as the developer from Marseille advised me to do so. It worked before. And indeed it worked after a SODE reinstall. The scenery nor Airport SODE files did not change..

A SODE repair also does the trick ; I then also choose to Register/activate SODE again.

 

[GSalden 4,656]

Finally found out what triggered the issue.

I Always use AO from Lorby-Si to actovate/deactivate/install my scenery. On closing then it asks if the scenery indexes need to be cleared. I Always choose Yes. And that caues SODE to be unabled to read the airport files now. Reinstalling/repairing SODE solves it till I clear the scenery indexes again.

Not clearing them and SODE keeps working. Also after a reboot. Before those W10 updates I always was able to clear the scenery indexes after making changes in the library and never had an issue afterwards.