I don't know what any of that means but it might be relevant to the devs.21:59:45.278 [debugTCP.disconnect]: No connection to debug console: "Connection to debug console failed: 'No connection could be made because the target machine actively refused it.
' (outStream status: 7, inStream status: 7)."
21:59:45.279 [debugTCP.send.warning]: Error sending packet header, retrying.
21:59:45.303 [debugTCP.send.error]: The following packet could not be sent: {"Oolite version" = 1.79; "packet type" = "Request Connection"; "protocol version" = 65792; }
21:59:45.339 [debugTCP.disconnect]: No connection to debug console: "Connection to debug console failed: 'bad stream.' (outStream status: 0, inStream status: 0)."
21:59:45.339 [debugTCP.connect.failed]: Failed to connect to debug console at address 127.0.0.1:8563.
21:59:49.155 [script.javaScript.exception.ooliteDefined]: ***** JavaScript exception (oolite-populator 1.79): Error: Ship.setCargoType: Invalid arguments ("SCARCE_GOODS") -- expected Can only be used on cargo pod carriers, not cargo pods.
21:59:49.562 [script.javaScript.exception.ooliteDefined]: ***** JavaScript exception (oolite-populator 1.79): Error: Ship.setCargoType: Invalid arguments ("SCARCE_GOODS") -- expected Can only be used on cargo pod carriers, not cargo pods.
21:59:50.305 [script.javaScript.exception.ooliteDefined]: ***** JavaScript exception (oolite-populator 1.79): Error: Ship.setCargoType: Invalid arguments ("PIRATE_GOODS") -- expected Can only be used on cargo pod carriers, not cargo pods.
21:59:51.145 [script.javaScript.exception.ooliteDefined]: ***** JavaScript exception (oolite-populator 1.79): Error: Ship.setCargoType: Invalid arguments ("SCARCE_GOODS") -- expected Can only be used on cargo pod carriers, not cargo pods.
21:59:51.146 [script.javaScript.exception.unexpectedType]: ***** JavaScript exception (oolite-populator 1.79): TypeError: this._addShips(role, 1, pos, 0) is null
21:59:51.356 [script.javaScript.exception.ooliteDefined]: ***** JavaScript exception (oolite-populator 1.79): Error: Ship.setCargoType: Invalid arguments ("PIRATE_GOODS") -- expected Can only be used on cargo pod carriers, not cargo pods.
21:59:51.662 [script.javaScript.exception.ooliteDefined]: ***** JavaScript exception (oolite-populator 1.79): Error: Ship.setCargoType: Invalid arguments ("SCARCE_GOODS") -- expected Can only be used on cargo pod carriers, not cargo pods.
A small report in oolite-trunk-1.79.0.e42842f-d
Moderators: winston, another_commander, Getafix
A small report in oolite-trunk-1.79.0.e42842f-d
During a Flushed load up ( Holding the shift key down while loading ) This
Flying Python Class Cruiser, Chapter & Verse IV
Re: A small report in oolite-trunk-1.79.0.e42842f-d
Those errors I think should be fixed in tomorrow's build. Thanks for reporting them.
Re: A small report in oolite-trunk-1.79.0.e42842f-d
Thank you cim,
I have now installed Oolite Trunk 1.79.0 Nightly build for Windows 64 bit OS - GIT revision 45289bb 12 November 2013 and the cargo issue is resolved.
The debug issue however remains but I suspect/would expect it will remain so until 1.79 goes live
Just one trifling observation, The Asteroids seem to have something of Red to Burnt Ochre appearance, If this is by design, no need to worry, I quiet like that it makes the Smaller Asteroids a harder target. That said, If you were not aware of it, It is then , worth a mention.
I have now installed Oolite Trunk 1.79.0 Nightly build for Windows 64 bit OS - GIT revision 45289bb 12 November 2013 and the cargo issue is resolved.
The debug issue however remains but I suspect/would expect it will remain so until 1.79 goes live
Thank you for the great work being undertaken in this respect by yourself and the other developers and contributors. I am enjoying very much the "busier" nature of the game and the improved appearance .14:31:10.082 [debugTCP.disconnect]: No connection to debug console: "Connection to debug console failed: 'No connection could be made because the target machine actively refused it.
' (outStream status: 7, inStream status: 7)."
14:31:10.083 [debugTCP.send.warning]: Error sending packet header, retrying.
14:31:10.108 [debugTCP.send.error]: The following packet could not be sent: {"Oolite version" = 1.79; "packet type" = "Request Connection"; "protocol version" = 65792; }
14:31:10.123 [debugTCP.disconnect]: No connection to debug console: "Connection to debug console failed: 'bad stream.' (outStream status: 0, inStream status: 0)."
14:31:10.123 [debugTCP.connect.failed]: Failed to connect to debug console at address 127.0.0.1:8563.
14:31:11.902 [startup.complete]: ========== Loading complete in 4.36 seconds.
Just one trifling observation, The Asteroids seem to have something of Red to Burnt Ochre appearance, If this is by design, no need to worry, I quiet like that it makes the Smaller Asteroids a harder target. That said, If you were not aware of it, It is then , worth a mention.
Last edited by Duggan on Tue Nov 12, 2013 2:49 pm, edited 2 times in total.
Flying Python Class Cruiser, Chapter & Verse IV
-
- Quite Grand Sub-Admiral
- Posts: 6682
- Joined: Wed Feb 28, 2007 7:54 am
Re: A small report in oolite-trunk-1.79.0.e42842f-d
Duggan: This is not a bug you are seeing there. It just means that Oolite tried to connect to the Debug Console and did not find it running. The messages shown are just the normal negotiation taking place: "- Hi, can I plz connect to debug console? - Nope, none running -Ah, alright then, kthxbye".
So if there are no other messages, it looks like we are pretty good thus far.
So if there are no other messages, it looks like we are pretty good thus far.
Re: A small report in oolite-trunk-1.79.0.e42842f-d
Thank you cim,
I'm not terribly techno savvy so it is good to read that this project is progressing as envisaged.
I'm not terribly techno savvy so it is good to read that this project is progressing as envisaged.
Flying Python Class Cruiser, Chapter & Verse IV