Bug found

Attachments

  • BvxpQil.jpg
    BvxpQil.jpg
    90.4 KB · Views: 189
Numbers are notoriously difficult, you can add, subtract, multiply, divide, and do a bunch of other stuff with them, so naturally many have a struggle. Strangely enough, this is also the case with ED.
 
Probably something to do with rounding, doesnt matter much, safe to ignore.
I understand that a time synchronization of data and rounding. But I do not understand why in order for the program to show 12% in two different game menus - I still had to destroy additionally more than 10 pirate ships and at the same time earn about 2 million credits? This is clearly a bug in the program.
 
I am sorry to say this but my friend Bazmeson and who have both played elite since it very first started will no longerplay this wonderful game if this isn't fixed in June. We have talked at length about this and this our conclusion.

Regards,
Bigmaec
 
I understand that a time synchronization of data and rounding. But I do not understand why in order for the program to show 12% in two different game menus - I still had to destroy additionally more than 10 pirate ships and at the same time earn about 2 million credits? This is clearly a bug in the program.
Probably already a known but low priority bug - in one instance they are probably using floor() (or similar) and in the other they are probably using round() (or similar), it could also be an operation order thing.

I agree it is a bug BUT it is not one I would particularly worry about as an end customer/user, as a developer though I would certainly like to give the dev team a virtual clip round the ear for shoddy coding practices - things like that should be handled by a common method/macro/template/library. ;)
 
I understand that a time synchronization of data and rounding. But I do not understand why in order for the program to show 12% in two different game menus - I still had to destroy additionally more than 10 pirate ships and at the same time earn about 2 million credits? This is clearly a bug in the program.

a rounding difference in 2 integer expressions may be almost 1. eg 11.1 is 11 rounded down and 12 rounded up, it still will take 0.9 for them to appear equal. true, that extreme case is not really plausible since it would mean both displays would never match except when the original value is an integer (plus it would imply not only two completely different rounding methods, but quite bad ones at that!). but a 0.5% would be quite possible, and 10kills/2mill sounds plausible at some ranks for that too.
 
Yeah, the rounding is very inconsistent. Some will display 11.7% as 11%, others will round it up to 12%.

It's a bug, but I quite like it as it makes it easier to see where you are within the %.

Actually it's not inconsistent, it's a bug: they are using the wrong kind of rounding function sometimes.

There are more than one type of rounding functions (functions that convert floating point numbers into integers):

1. Round() - returns the nearest integer
2. Int() - simply returns the integer part of the number, so 1.897 becomes 1, for instance
3. Floor() - rounds always downwards (on positive numbers it works the same way as the Int() function, but on negative numbers it rounds "away from" zero)
4. Ceiling() - the opposite of the previous one, it always rounds upwards, e.g. 99.1 becomes 100 and 0.1 becomes 1.

Choosing the wrong rounding function is extremely annoying when the hull percentage of your opponent is being displayed, for instance. Currently the game is using a simple Round() function here, this is how they can become zombies flying around on 0% hull (actually it's something like 0.251). They should have used the Ceiling() function here.

And there is literally zero reason why they couldn't find some dev time to fix it in 5 years: it's a single line of code kind of thing which shouldn't have taken more that 1 minute to fix.
 
Last edited:
Yeah, the rounding is very inconsistent. [...]

It's a bug [...]
Actually it's not inconsistent, it's a bug: they are using the wrong kind of rounding function sometimes.
So actually it is inconsistent, then, as they use different rounding functions for the same value on different displays - for rank, for instance, Floor on the right panel and Round on the middle panel. And I already said it was a bug.

Ceiling() would also be wrong for hull strength, incidentally, since 99.1% would show as 100% which would also be undesirable. This one ideally needs a custom rounding function which behaves as Floor() except when 0% < hull <= 1%, when it returns 1%.

And there is literally zero reason why they couldn't find some dev time to fix it in 5 years
Has anyone actually reported it in those five years? I can't find any reference to any of the rounding issues in the bug tracker at all, and don't remember seeing anyone mention it in the old bug forums either. I know I've never cared about it enough to report it, and I've reported some pretty trivial bugs.
 
So actually it is inconsistent, then, as they use different rounding functions for the same value on different displays - for rank, for instance, Floor on the right panel and Round on the middle panel. And I already said it was a bug.

Ceiling() would also be wrong for hull strength, incidentally, since 99.1% would show as 100% which would also be undesirable. This one ideally needs a custom rounding function which behaves as Floor() except when 0% < hull <= 1%, when it returns 1%.


Has anyone actually reported it in those five years? I can't find any reference to any of the rounding issues in the bug tracker at all, and don't remember seeing anyone mention it in the old bug forums either. I know I've never cared about it enough to report it, and I've reported some pretty trivial bugs.

I didn't reply to your post to argue, it's not that I disagree with what you said. Yes it's inconsistent indeed, but the underlying reason is what you can call a bug or lazy programming at the very least.
 
Hi! I'm new here and my english is poor, soo please excuse me.
Yesterday while i bought a new boat the exact time the program froze. Since then I can't connect. It looks like this (I simplify it because of my bad english):
-launcher says server status ok
-program starts fine
-main menu - the server connection is shown below
-start the solo game
-charging screen (my new corvette siluette is spinning)
-after a while give an error message, "can't sonnect to server, orange sidewinder code"
-back to main menu
And it's been doing it since froze yesterday the exact time while buying a new ship (fed.corvette). I have good and stabile net connection, and the program connected to server in the main menu (I see the server adress below, and the galnet is online in the main menu)
I have no idea what can I do.
 
Back
Top Bottom