When storing time.time() in a game property, the game property doesn't return the same time #41490

New Issue

Roderick Gadellaa · 2014-08-19T11:21:42+02:00

Roderick Gadellaa commented

2014-08-19 11:21:42 +02:00

System Information
Windows 7 x64, Intel 3000 graphics

Blender Version
Broken: 2.70a f93bc76

Short description of error
In the game engine, when setting a game property (type float) of an object to time.time() and then printing it, it returns not the same value as you have set.

Exact steps for others to reproduce the error

Set Blender in game engine mode
Create an object and assign it a game property named "thetime", type float
Create a sensor (always or keyboard) and a controller (python), attach them to eachother

Python code:

thetime = time.time()
print(thetime)

prints something like 1440000.1348

obj["thetime"] = thetime
print(obj["thetime"])

prints something like 1440023.0

It looks like the object (which is basically C++ code?) is using doubles while python can only handle floats?

It does work when I convert the time to int (and also set the game property to type float)

**System Information** Windows 7 x64, Intel 3000 graphics **Blender Version** Broken: 2.70a f93bc76 **Short description of error** In the game engine, when setting a game property (type float) of an object to time.time() and then printing it, it returns not the same value as you have set. **Exact steps for others to reproduce the error** Set Blender in game engine mode Create an object and assign it a game property named "thetime", type float Create a sensor (always or keyboard) and a controller (python), attach them to eachother Python code: thetime = time.time() print(thetime) > prints something like 1440000.1348 obj["thetime"] = thetime print(obj["thetime"]) > prints something like 1440023.0 It looks like the object (which is basically C++ code?) is using doubles while python can only handle floats? It does work when I convert the time to int (and also set the game property to type float)

Roderick Gadellaa commented

2014-08-19 11:21:42 +02:00

Changed status to: 'Open'

Roderick Gadellaa commented

2014-08-19 11:21:42 +02:00

Added subscriber: @rejhgadellaa

Marcin Nijaki commented

2014-08-19 15:21:43 +02:00

Added subscriber: @marcino15

Marcin Nijaki commented

2014-08-19 15:21:43 +02:00

Float property has limit.
If you want store exact time, you must use string property obj["thetime"] = str(thetime)

Float property has limit. If you want store exact time, you must use string property obj["thetime"] = str(thetime)

Roderick Gadellaa commented

2014-08-19 16:43:21 +02:00

@marcino15 thanx for the quick reply. I hope you mean this to be a workaround and not a fix? :)

Python uses doubles (doesn't have floats, I mixed that up in the OP) and since the game engine uses python for programming it would make sense if the game properties are of the same type as python's types since python does not have the option to choose (thus the C/C++ side should adept).

In other words: game property floats should be of type double.

@marcino15 thanx for the quick reply. I hope you mean this to be a workaround and not a fix? :) Python uses doubles (doesn't have floats, I mixed that up in the OP) and since the game engine uses python for programming it would make sense if the game properties are of the same type as python's types since python does not have the option to choose (thus the C/C++ side should adept). In other words: game property floats should be of type double.

Marcin Nijaki commented

2014-08-20 10:10:09 +02:00

This is correct work and not need to fix.

Arnaud Loonstra commented

2014-08-21 10:53:11 +02:00

Added subscriber: @sphaero

Arnaud Loonstra commented

2014-08-21 10:53:11 +02:00

I tend to disagree. I think storing time as a string is indeed a workaround. I'm not sure how the the game engine handles float game properties internally but if it creates a situation likes this because of float <> double conversion it would make sense to set the float game property as a double internally.

Jorge Bernal commented

2015-05-16 01:40:32 +02:00

Added subscriber: @JorgeBernalMartinez

Jorge Bernal commented

2015-05-16 01:40:32 +02:00

it is not easy to increase the precision from float to double in property code. It would involve changes which affect to int and timer properties also (data variable used by int/float would have to pass to 8 bytes).

Porteries Tristan commented

2015-05-18 22:46:12 +02:00

Added subscriber: @panzergame

Porteries Tristan commented

2015-05-18 22:46:12 +02:00

Changed status from 'Open' to: 'Archived'

Porteries Tristan closed this issue

2015-05-18 22:46:12 +02:00

Porteries Tristan self-assigned this 2015-05-18 22:46:12 +02:00

Porteries Tristan commented

2015-05-18 22:46:12 +02:00

Hello, BGE convert as much as possible properties in his own type and in this case in float. So you have to set it in a tuple to keep the precision.

obj["time"] = (time.time(), )

I don't think that is a wrong behavior to contrain the user to use as minimum hight precision value.

Hello, BGE convert as much as possible properties in his own type and in this case in float. So you have to set it in a tuple to keep the precision. ``` obj["time"] = (time.time(), ) ``` I don't think that is a wrong behavior to contrain the user to use as minimum hight precision value.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

When storing time.time() in a game property, the game property doesn't return the same time #41490