This text will be translated with translation as I only speak German.
I need help and hope that this thread is still active. I am not very pertinent in dealing with insert and co.
But I get the spaceship in the top right of the screen.
Do not understand where and how what is introduced to make it active. As far as everything from Xenon Ui and what is needed installed. Maybe someone can help me to make it active. I'm a beginner when it comes to that.
How do I get something here, and where must something go to be active?
If I understand correctly what you are asking, you want to see the player's ship rotating in the F5 status screen, right? To do this, you must edit the file .GNUstepDefaults (for the Windows version of the game, this is found inside oolite.app/GNUstep/Defaults) and you must add this line in it:
"show-ship-model-in-status-screen" = YES;
When you restart the game, you will have the Cobra Mk3 rotating on the status screen, same as you can see in the screenshot in the previous page.
If this is not what you were asking, please try to explain a bit more clearly what you need help with.
This text will be translated with translation as I only speak German.
Willkommen an Bord Commander,
sollte die Message von another_commander nicht die gewuenschte Loesung enthalten schreibe uns bitte in Deutsch wo Deine Probleme genau liegen. Sollte ich diese selbst nicht loesen koennen kann ich zumindest eine Uebersetzung weitergeben.
Translation for other readers:
Weclome on board commander,
incase that another_commander's message didn't include the desired solution please write us in German which problems exactly you are facing. If I can't solve it myself I will be happy to pass forward a translation.
Scars remind us where we've been. They don't have to dictate where we're going.
Warning (strict mode): reference to undefined property this.$IDsExt[id]
Active script: Lib_GUI 1.7.1
Lib_GUI.js, line 311:
ex = (this.$noEx.indexOf(id)===-1?this.$IDsExt[id]:null),
Warning (strict mode): reference to undefined property this.$IDsExt[id]
Active script: XenonUI 3.2
Lib_GUI.js, line 311:
ex = (this.$noEx.indexOf(id)===-1?this.$IDsExt[id]:null),
But I'm not sure what XenonUI is (unsuccessfully) trying to do with Library that's leading to this.
Well, at this point in proceedings XenonUI has handed off control of switching background images to Library GUI, so theoretically it's not doing anything.
What Library GUI is doing is looking for a potential match between the mission screen ID behing displayed and a background that may have been explicitly set for it. In this instance it doesn't find any, because XenonUI has requested that the default background be used in all mission screens.
In the Lib_GUI code, line 311 appears to allow for a null value to be used in the "ex" variable, so perhaps a better solution would be to make 311 be this:
Version 3.3 of Xenon UI and the Redux version have been released. This release fixes compatibility issues with the Ship's Library OXP, Sothis TC, New Cargoes and Iron Raven, where previously background images would not be shown.
Version 3.3 of Xenon UI and the Redux version have been released. This release fixes compatibility issues with the Ship's Library OXP, Sothis TC, New Cargoes and Iron Raven, where previously background images would not be shown.
Warnings:
* Description mismatch between OXP Manifest and Expansion Manager
* Version mismatch between OXP Manifest and Expansion Manager
* Tags mismatch between OXP Manifest and Expansion Manager
* Information URL mismatch between OXP Manifest and Expansion Manager
Version 3.3 of Xenon UI and the Redux version have been released. This release fixes compatibility issues with the Ship's Library OXP, Sothis TC, New Cargoes and Iron Raven, where previously background images would not be shown.
Warnings:
* Description mismatch between OXP Manifest and Expansion Manager
* Version mismatch between OXP Manifest and Expansion Manager
* Tags mismatch between OXP Manifest and Expansion Manager
* Information URL mismatch between OXP Manifest and Expansion Manager
....
.... and we really want to make it even more complicated than it already is? Don't get me wrong ... I'm a great admirer of Byzantine complexity, I consider it an unappreciated art-form, rather like Roccoco. But we are trying to get people who've spent their free time working on an OXP to put it up on the EM. Surely we should make be trying to make it easier...
Version mismatch between OXP Manifest and Expansion Manager
This one I don't get. The version number in the EM says "3.3". The version number in the OXZ file loaded to the wiki says version = "3.3";. If you're reading a discrepancy here, I'm not sure where it's coming from. Could it be a type thing? ie reading one value as a string, the other as a decimal?