Trunk nightly

[another_commander]

Currently away from my dev computer, so I'll just mention this here and try to have a look at it when I get back, if it hasn't been fixed already by that time.

There is a small bug with trunk 1.81.0.6413-150325-9f6972a. The steps to reproduce are:
1. Start game, start new Jameson.
2. Set destination for hyperspace, then launch and start jump sequence.
3. Make sure you are switched to rear or side views (i.e. views without laser mounts) when countdown reaches 0.
4. On exit to destination system, front laser does not fire until any other view has been selected and returned back to forward.

[kanthoney]

Currently away from my dev computer, so I'll just mention this here and try to have a look at it when I get back, if it hasn't been fixed already by that time.

Works fine for me in both Linux and Windows.

[Cody]

Seems okay here too (Windows).

[another_commander]

OK, possibly a false alarm then, sorry!. I noticed this while test playing on an Internet Cafe Windows PC, so I'll have to blame the goblins in the machine for this one.. I'll double check it once I am back on my "proper" computers just to be sure,

[Cody]

... so I'll have to blame the goblins in the machine for this one.

<grins> A likely story!

[Cody]

I think I know what this one might be, having observed a bounty hunting party launching out of Onrira Torus.

I've been watching Quandixe Torus (awaiting a lift): a Python + Mamba escort launched, called the 'Jumping soon... ' message, and I followed it - out of the aegis, way out, in fact. Meanwhile, behind me a hunting party launched and happily jumped-out at about the right distance from the Torus. The Python though stubbornly refused to jump, and just kept heading out to nowhere (according to the ASC there was nothing along that heading). I tried nudging it and gently teasing it, but to no avail. Eventually, I had to leave it as I had parcels to deliver.

[another_commander]

... so I'll have to blame the goblins in the machine for this one.

<grins> A likely story!

Coming back to this one, I think I got the little detail that was missing before. Can you please repeat the steps outlined earlier (and reposted below for convenience), with the modification listed? For me this is totally reproducible.
1. Start game, start new Jameson.
2. Set destination for hyperspace, then launch.
3. Move a bit so that the buoy doesn't get hit and fire your front laser once. <-- This was missing in the steps earlier.
4. Start jump sequence.
5. Make sure you are switched to rear or side views (i.e. views without laser mounts) when countdown reaches 0.
6. On exit to destination system, front laser does not fire until any other view has been selected and returned back to forward.

[Cody]

Confirmed!

[kanthoney]

Also confirmed. It's got something to do with the weapon recharge rate - for some reason it goes from 0.5 second to 100 seconds, so if you hold the fire button down for 100 seconds you eventually get a shot out of it, at which point the recharge rate gets set back to normal.

You do find some interesting bugs!

[kanthoney]

Fixed! We were setting the weapon direction to forward after hyperspace, but not calling [self currentWeaponStats]; to update the recharge rate etc.

[spara]

Jump to interstellar space reveals a bug in the new chart gui feature. Maybe not drawing any lines is the way to go in interstellar space?

[Diziet Sma]

Maybe not drawing any lines is the way to go in interstellar space?

Perhaps.. but then it wouldn't really be clear which systems, if any, are still reachable. Not that the situation in the above pic is any better in that regard..

[spara]

Maybe not drawing any lines is the way to go in interstellar space?

Perhaps.. but then it wouldn't really be clear which systems, if any, are still reachable. Not that the situation in the above pic is any better in that regard..

The confusing part in the image is that the labels of reachable systems are correctly colored, but the lines go to systems that are unreachable or won't go to systems that are reachable. Riedquat and Tianve te be exact. The most natural solution would be drawing lines from the interstellar position to the reachable systems.

[Disembodied]

The most natural solution would be drawing lines from the interstellar position to the reachable systems.

Or, if that's not possible, reverting to the circle only in interstellar space. Inaccuracies are only to be expected in such a situation!

[another_commander]

Commit 83f170b introduced some bugs in the Expansion Manager. Building generates these warnings on Windows (and, from what I see in the Linux nightly status page, on Linux too):

Code: Select all

src/Core/OOOXZManager.m: In function '-[OOOXZManager showInstallOptions]':
src/Core/OOOXZManager.m:1718:5: warning: 'NSDateFormatter' may not respond to '-setDateFormat:' [enabled by default]
src/Core/OOOXZManager.m:1718:5: warning: (Messages without a matching method signature [enabled by default]
src/Core/OOOXZManager.m:1718:5: warning: will be assumed to return 'id' and accept [enabled by default]
src/Core/OOOXZManager.m:1718:5: warning: '...' as arguments.) [enabled by default]
src/Core/OOOXZManager.m:1719:5: warning: 'NSDateFormatter' may not respond to '-stringFromDate:' [enabled by default]

The result is that the navigation of the OXP lists in the manager is broken and the log records loads of this:

Code: Select all

13:35:19.670 [exception]: ***** Exception checking controls [pollDemoControls]: NSInvalidArgumentException : Can not determine type information for -[NSDateFormatter setDateFormat:]

The solution should be simply including NSDate.h in the manager class, but I can't test this while away from my main computer.