Page 1 of 2
Two Questions
Posted: Sun Mar 04, 2018 10:17 am
by Nite Owl
First - before I go through the long process of moving files around to find the culprit does anyone recognize which .oxp(z) the following comes from?
Code: Select all
[shipData.load.error]: ***** ERROR: the shipdata.plist entry "IR-GSE-ad" specifies non-existent model "IR-gse-ad.dat".
Second - what does this mean?
Code: Select all
[WARNING]: Warning! Global namespace polluted by:
[WARNING]: ["MC_clockStringToMinutes","MC_randomElement","MC_randomExponential","MC_randomNormals","MC_ceilScale","MC_floorScale","MC_logistic","MC_uniform","buoy","TRAPS","ECMJammer_ecmShips","key","c"]
Neither one of these seems to have any effect on my game play but they are a pain to constantly see popping up in my Latest Log. Thank You - We now return you to your regularly scheduled forum.
Re: Two Questions
Posted: Sun Mar 04, 2018 10:29 am
by Cody
Iron Raven; it means nothing (Library).
Re: Two Questions
Posted: Sun Mar 04, 2018 11:02 am
by Nite Owl
Tweaking and fixing stuff is getting easier once you know where and what to look for. It is also getting scary. Time for milk and cookies.
Re: Two Questions
Posted: Sun Mar 04, 2018 11:21 am
by Cody
Nite Owl wrote: ↑Sun Mar 04, 2018 11:02 amTime for milk and cookies.
Time for coffee! <worships at the shrine of the caffeine goddess>
Re: Two Questions
Posted: Sun Mar 04, 2018 4:17 pm
by Svengali
The shipdata error is likely to be a missing is_external_dependency key.
The Library warning about global namespace is a problem, because global namespace shouldn't be used and is likely to clash with other AddOns which are using it. And if this kind of clash happens then it will be pretty difficult to find the reason. And to complete it - it is easy to use the scripts namespace / scope instead.
Re: Two Questions
Posted: Sun Mar 04, 2018 6:16 pm
by Nite Owl
The first one was an easy fix once one is told where to look. The coded reference was to "IR-gse-ad.dat" when it should have been referenced as "IR-GSE-ad.dat". Capitalization matters in such things apparently.
The second one is way beyond my current ability to fix so it will be lived with for now.
Working my way to a Latest Log with no error messages and a game that suits my play style despite 300+ Oxz(p)'s. These were the very last of the errors that could not be figured out until now. More errors will probably pop up later as things get added, updated, and tweaked. Are we having fun - YES - there is a "not in game but benefits the game" challenge to it that is quite enjoyable.
Re: Two Questions
Posted: Sun Mar 04, 2018 6:20 pm
by Mauiby de Fug
Nite Owl wrote: ↑Sun Mar 04, 2018 6:16 pm
Working my way to a Latest Log with no error messages and a game that suits my play style despite 300+ Oxz(p)'s.
...
Are we having fun - YES - there is a "not in game but benefits the game" challenge to it that is quite enjoyable.
This is pretty much my default way of playing Oolite at the moment - not actually playing at all!
Re: Two Questions
Posted: Tue Dec 12, 2023 10:41 pm
by Cholmondely
Nite Owl wrote: ↑Sun Mar 04, 2018 10:17 am
Second - what does this mean?
Code: Select all
[WARNING]: Warning! Global namespace polluted by:
[WARNING]: ["MC_clockStringToMinutes","MC_randomElement","MC_randomExponential","MC_randomNormals","MC_ceilScale","MC_floorScale","MC_logistic","MC_uniform","buoy","TRAPS","ECMJammer_ecmShips","key","c"]
Might this be the Mining Contracts oxp?
Re: Two Questions
Posted: Tue Dec 12, 2023 11:18 pm
by Nite Owl
The [WARNING]: Warning! Global namespace polluted by: stuff has continuously popped up in my Latest.log since forever. It comes in many variations and does not always have the same references nor does it seem to have any relationship to any previous time it has appeared. The best advice received was to just ignore it.
Re: Two Questions
Posted: Tue Dec 12, 2023 11:27 pm
by phkb
The message comes from Library, and it means that some OXP has done something in the "global" namespace that it shouldn't really be doing. With my current OXP load, all I get is:
Code: Select all
18:05:56.431 [WARNING]: Warning! Global namespace polluted by:
18:05:56.431 [WARNING]: ["postFX","prop","key","c"]
The only way to narrow down which OXP is responsible is to remove some and then see if the items go away.
Re: Two Questions
Posted: Wed Dec 13, 2023 12:05 am
by Nite Owl
The [WARNING]: Warning! Global namespace polluted by: entry in my Latest.log has gotten much shorter then it was back in 2018. This is likely due to updated OXZ releases squashing the bugs that caused the warnings in the first place. Some of the warnings might have also been squashed due to a better understanding on my part of how Oolite works. Back in 2018 nothing was known. Today a smidgen more is understood. Going through an extensive Binary Search of over 300 OXZs to narrow down the few remaining entries is something best left for "another day". Game play does not seem to be influenced in any way so we shall see what we shall see.
Re: Two Questions
Posted: Wed Dec 13, 2023 12:26 am
by Cholmondely
Just for completeness, my most recent latest.log has this:
Code: Select all
23:03:14.525 [WARNING] GlobalLog (OOJSGlobal.m:266): Warning! Global namespace polluted by:
23:03:14.525 [WARNING] GlobalLog (OOJSGlobal.m:266): ["MC_clockStringToMinutes","MC_randomElement","MC_randomExponential","MC_randomNormals","MC_ceilScale","MC_floorScale","MC_logistic","MC_uniform","buoy","TRAPS","pow","LITF_placeLabel","LITF_reLabel","FuncGalaxyCheck","FuncMarkGal_0","FuncMarkGal_1","FuncMarkGal_2","FuncMarkGal_3","FuncMarkGal_4","FuncMarkGal_5","FuncMarkGal_6","FuncMarkGal_7","FuncUnMarkAll","key","c"]
Re: Two Questions
Posted: Wed Dec 13, 2023 1:18 am
by phkb
Hmm.
Cholmondely wrote: ↑Wed Dec 13, 2023 12:26 am
Code: Select all
"MC_clockStringToMinutes","MC_randomElement","MC_randomExponential","MC_randomNormals","MC_ceilScale","MC_floorScale","MC_logistic","MC_uniform"
Oh, look! I actually fixed Mining Contracts for my own build back in 2018...
Maybe I should upload this version. I don't think Diagoras is coming back.
Edit: and done. v1.13 should be available in the DM shortly.
Re: Two Questions
Posted: Wed Dec 13, 2023 2:54 am
by phkb
Cholmondely wrote: ↑Wed Dec 13, 2023 12:26 am
Just for completeness, my most recent latest.log has this:
Cholmondely, can I get you to replace your current SecComFinder4GalNavy OXP with this one:
SecComFinder4GalacticNavy_0.6.2.oxz and see if more of the reports have been cleaned up. If it still works OK (I don't run with GalNavy and I'm not in the mood to try atm) I'll publish this to the DM.
Re: Two Questions
Posted: Wed Dec 13, 2023 5:51 pm
by Cholmondely
phkb wrote: ↑Wed Dec 13, 2023 2:54 am
Cholmondely, can I get you to replace your current SecComFinder4GalNavy OXP with this one:
SecComFinder4GalacticNavy_0.6.2.oxz and see if more of the reports have been cleaned up. If it still works OK (I don't run with GalNavy and I'm not in the mood to try atm) I'll publish this to the DM.
Done!
Result from replacing SecComFinder4GalacticNavy (I had to tweak the manifest.plist) & Mining Contracts with your cleaner versions:
Code: Select all
17:08:55.551 [WARNING] GlobalLog (OOJSGlobal.m:266): Warning! Global namespace polluted by:
17:08:55.551 [WARNING] GlobalLog (OOJSGlobal.m:266): ["buoy","TRAPS","pow","LITF_placeLabel","LITF_reLabel","key","c"]
The LitF is the unfinished version which MassivelyLocked was working on.