Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

FJsonObject::GetIntegerField() loses precision


Stumbled upon this today as I was reading Unix timestamps from a json input.

FJsonObject::GetIntegerField() invokes FMath::TruncToInt( float ) with an argument of type 'double'. The implicit double -> float conversion silently loses precision and screws up reading perfect int32 values.

Having FMath::TruncToInt( double ) would fix that. It's absence might actually have negative implications outside FJsonObject as well.

Product Version: UE 4.12
more ▼

asked Jul 29 '16 at 09:47 AM in Bug Reports

avatar image

129 2 13 12

avatar image Tim C ♦♦ STAFF Aug 03 '16 at 05:47 PM

Hi bstone,

I can see a potential issue with regards to what you are doing, but it is more related to limitations of the Float data type than the implicit Double-to-Float conversion. What are the results that you are seeing? Knowing what you are seeing will help me determine if my initial suspicion is correct.


avatar image bstone Aug 03 '16 at 07:40 PM

Hello Tim,

Thanks for looking into that.

What I do is parsing a Json payload. Some fields contain integer numbers. I use FJsonObject::GetIntegerField() to retrieve those values. But instead of the values specified in the Json representation I get slightly other values, i.e. GetIntegerField() returns wrong results. For example if I have:

{ value: 1470252657 }

FJsonObject::GetIntegerField() for 'value' would return 1470252544, not the expected 1470252657.

As you can see I'm only dealing with integer values and don't even access Float data or use it anywhere in that process.

Anyway, what I was pointing to is that not having FMath::TruncToInt( double ) is dangerous because "int32" values have 31 bit precision while "float" values have only 24 bit precision. Routing double values through FMath::TruncToInt( float ), which now happens silently without any warnings, loses 7 bits of precision for nothing. And FJsonObject::GetIntegerField() is a good example of why it is dangerous.

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

1 answer: sort voted first

Hi bstone,

What you described is what I was referring to in my previous comment. I may not have adequately stated what I was thinking. What is happening here is not specifically a result of the implicit double to float conversion (which does lose some precision, but this would not normally be noticed when the fractional portion of the value is truncated). Instead, this is a result of the float type's inability to accurately store integer values greater than 2^24. I believe that is what we were both getting at, but I expressed myself a bit poorly.

I have entered UE-34255 to have this investigated further.


more ▼

answered Aug 04 '16 at 09:28 PM

avatar image bstone Aug 05 '16 at 07:18 AM


Yes, that makes sense. Thanks for pushing it further.

(comments are locked)
10|2000 characters needed characters left
Viewable by all users
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question