21 replies to this topic

[Jackal Noble]

asking the real questions because.....wot is dis
1st image - the heat management in the floating all stat window says 1.5, whilst the general stat says 1.45.





Also - cannot unsee this. That's the franken camo (this looks like a 10% improvement on what we already have with the cryengine and surprisingly similar to MWO) and that laser is acting funny (hit-detection).


^ that is mostly just a sigh at the fact that there hasn't been any actual material other than the AMA where the mechlab was discussed in obtuse detail.

Edited by Jackal Noble, 05 September 2019 - 05:09 PM.

[Bombast]

That's a Cauldron-Born, otherwise known as the "Ugo-Bushwacker."

[Jackal Noble]

Bombast, on 05 September 2019 - 05:10 PM, said:

That's a Cauldron-Born, otherwise known as the "Ugo-Bushwacker."

Hey man, that was my baby for the longest time. Used to imagine what it would be like cruising in one at around in one at 87 (54 mph) while driving on the highway.

[Y E O N N E]

I bet the pop-up just rounds to the nearest ten.

[Jackal Noble]

Y E O N N E, on 05 September 2019 - 05:33 PM, said:

I bet the pop-up just rounds to the nearest ten.

Ya that I guess that makes sense, but just add one more character to the table.

[Bombast]

Jackal Noble, on 05 September 2019 - 05:34 PM, said:

Ya that I guess that makes sense, but just add one more character to the table.

Adding decimal points is a slippery slope. Once you get two points, why not go to three? And once you're at three, why not four? Soon we'll be having to read stats down to the quintillionth.

[dario03]

Bombast, on 05 September 2019 - 05:56 PM, said:

Adding decimal points is a slippery slope. Once you get two points, why not go to three? And once you're at three, why not four? Soon we'll be having to read stats down to the quintillionth.

Why stop at just a quintillionth???

[evilauthor]

dario03, on 06 September 2019 - 07:16 AM, said:

Why stop at just a quintillionth???

You've probably run out of screen space by then.

[dario03]

evilauthor, on 06 September 2019 - 08:31 AM, said:

You've probably run out of screen space by then.

Get an Ultrawide?

[VonBruinwald]

Bombast, on 05 September 2019 - 05:56 PM, said:

Adding decimal points is a slippery slope. Once you get two points, why not go to three? And once you're at three, why not four? Soon we'll be having to read stats down to the quintillionth.

Is it too much to ask for consistency? Rounding everything to 1dp should have been a design decision made at the start for the purpose of consistency across the UI.

[LordNothing]

rounding. lol.

always believe the number with the most decimal places. ui is doing some unwanted formatting for you.

Edited by LordNothing, 06 September 2019 - 11:53 PM.

[Feral Clown]

Jack you've been around this long and you're bringing this up now? What you want attention or something....

[LordNothing]

Y E O N N E, on 05 September 2019 - 05:33 PM, said:

I bet the pop-up just rounds to the nearest ten.

you mean nearest tenths right? because if you rounded to the nearest ten it would be zero.

[LordNothing]

Bombast, on 05 September 2019 - 05:56 PM, said:

Adding decimal points is a slippery slope. Once you get two points, why not go to three? And once you're at three, why not four? Soon we'll be having to read stats down to the quintillionth.

my rule of thumb

if its going to be looked at by stupid people zero or one place.
if it has anything to do with money 2 places.
electrical engineering 3 or 4 places.
kerbal space program 5 places.
real rocket science 6-9 places.
single precision float 7 places
particle physics 10+ places.
double precision float (the default on 64 bit machines, at least that's what sizeof(float) returns) 15 places.

Edited by LordNothing, 07 September 2019 - 03:09 AM.

[Jackal Noble]

Feral Clown, on 07 September 2019 - 02:39 AM, said:

Jack you've been around this long and you're bringing this up now? What you want attention or something....

maayyybe

[Bombast]

LordNothing, on 07 September 2019 - 02:52 AM, said:

you mean nearest tenths right? because if you rounded to the nearest ten it would be zero.

Look out, we have a master of mathology over here.

[Jackal Noble]

Ok fine..... here's one. Is it 63.4 or is it 63.5? because that's really going to make or break this mech for me. That .1 is all the nascar difference I need.

[Jackal Noble]

it's like 63.484

[LordNothing]

Bombast, on 07 September 2019 - 04:44 AM, said:

Look out, we have a master of mathology over here.

nah jut an understanding of fp maths. i write code where i need to make the fpu do things it really doesn't know how to do or even want to do. you can get 15 places but what if you need 20. the x87 instruction set used to have support for an 80-bit float but idk if thats still supported on 64bit machines (it would require a doubling up of registering operations as you need to load the extra 16 bits into a register). quadruple precision was supported on a lot of 70s/80s minicomputers, like the vax mainframe i used in highschool cs class (it was slow and your time was shared with other users).

but i guess this kind of stuff was deemed unnecessary for consumer hardware (its really only useful for the science and engineering sector). a lot of gpus still only support single precision or have reduced capabilities when using doubles, workstation gpus have the extra precision though, which is why they cost more. dp isnt needed for rendering though and is more of a hinderance, but if you want to do accurate photogrammetry operations on your gpu you might be better off with the more expensive card. though im not sure if they support quad out of the box (i doubt it). you can always gain extra precision in software though, even if you have to break out the large fixed point, and that usually comes with some performance penalties.

and really if i was that smart id be able to do these kind of maths in a way that requires less precision from the hardware.

Edited by LordNothing, 07 September 2019 - 01:35 PM.

[Bombast]

LordNothing, on 07 September 2019 - 01:16 PM, said:

nah

Spoiler

jut an understanding of fp maths. i write code where i need to make the fpu do things it really doesn't know how to do or even want to do. you can get 15 places but what if you need 20. the x87 instruction set used to have support for an 80-bit float but idk if thats still supported on 64bit machines (it would require a doubling up of registering operations as you need to load the extra 16 bits into a register). quadruple precision was supported on a lot of 70s/80s minicomputers, like the vax mainframe i used in highschool cs class (it was slow and your time was shared with other users).

but i guess this kind of stuff was deemed unnecessary for consumer hardware (its really only useful for the science and engineering sector). a lot of gpus still only support single precision or have reduced capabilities when using doubles, workstation gpus have the extra precision though, which is why they cost more. dp isnt needed for rendering though and is more of a hinderance, but if you want to do accurate photogrammetry operations on your gpu you might be better off with the more expensive card. though im not sure if they support quad out of the box (i doubt it). you can always gain extra precision in software though, even if you have to break out the large fixed point, and that usually comes with some performance penalties.

and really if i was that smart id be able to do these kind of maths in a way that requires less precision from the hardware.