Dt is way too fast (DEF-3146) (SOLVED)

Bugs
#1

I did some testing between all the different time measurement you can use in defold, and I found something of a “bug”.

wtfdt
wtfdt.PNG498×903 28.2 KB

When using settings it moved 4 seconds every minute compared to every other type measurement. This could be caused by a rounding error, so I tested that and got a shift of sround, half of the built in timekeeper when using the same amount of didgets as the built in dt. I think the dt should be inproved to fix some of the limitations with it, it’s just annoying to work with sometimes.

(Sorry for breaking the 666 bugs in defold)

1 Like
#2

Try this https://github.com/dapetcu21/defold-dtfixup

2 Likes
#3

Hi @Vincent, what platform are you running on?

#4

Windows 10

1 Like
#5

How is “exact time” measured in your example? Could you share the project with me if possible?
johan.beck-noren[at]king.com.

#6

It is by using socket.gettime, but not adding the difference every frame. I have shared it with you, but every time I synchronize I get this error
wtferror
and it duplicases the Project
errorwtf

So I don’t know if it is the right version I have shared ¯_(ツ)_/¯

#7

The sync issue should be solved now/soon (see Gui node anchoring for more details)

1 Like
#8
#9

A fix for this is in the beta release of 1.2.126. If you want you can try it out here: http://d.defold.com/beta/

In any case the fix will be in the stable release of 1.2.126 some time early next week.

5 Likes
#10

Awesome! Is there a beta version of bob.jar I can use? We’re supposed to send our game to some publishers today and my build scripts require bob.jar. It’d be awesome if I could include the fix in this build.

#11

Just grab the sha1 from http://d.defold.com/beta/info.json and use that to build the proper URL to any of the release artefacts listed here: http://d.defold.com/stable/

4 Likes
#12

and good luck with publishers! Be sure to share how it goes. We care for you =]

1 Like
#13

Released!

6 Likes
#14

Works great!

5 Likes