Defold 1.3.6 BETA

[AGulev]

Could you pls try to setup this value to 0.5 or 1 and check if it’s the same ?

[Dragosha]

@AGulev

Could you pls try to setup this value to 0.5 or 1 and check if it’s the same ?

the same.

Also I tryed add appmanifest with exluded the profile. The same results.

But release build gets 3.5% CPU:

@britzl

My first guess would have been that it is the profiler, but when you also mention GPU then I’m not so sure. Can you also test a release build?

UPD:
I don’t understand what happening. After moving the windows toolbar to the right for make screenshot I see that my project has 5% instead ~30 % CPU with enabled profiler.

UPD2. I think something wrong with my PC. It’s not a 1.3.6 beta issue at all.

[Dragosha]

Another interesting thing. I have a code base that migrated from one prototype to others. This code created a save file via defsave. Now I noticed that the old prebuilt prototype (PC executable) does not run properly on my PC, but works correctly on other PCs. What happened? Bingo! The new prototype built with 1.3.6. overwrote the save file. And the old project can’t load it. Because: ERROR:SCRIPT: defsave.defsave:130: Unsupported serialized table data: version = 0x4 (current = 0x3)

[britzl]

@Dragosha

Now I noticed that the old prebuilt prototype (PC executable) does not run properly on my PC, but works correctly on other PCs. What happened? Bingo! The new prototype built with 1.3.6. overwrote the save file. And the old project can’t load it. Because: ERROR:SCRIPT: defsave.defsave:130: Unsupported serialized table data: version = 0x4 (current = 0x3)

This is to be expected. An old client will not be able to open a save file with a newer format.

Note: we’ve added support for much larger save files with more keys.

[Dragosha]

@britzl

This is to be expected. An old client will not be able to open a save file with a newer format.

Note: we’ve added support for much larger save files with more keys.

yes, it’s ok. Think, this point should be add to release notes.

[britzl]

@Dragosha

Think, this point should be add to release notes.

You’re right. I’ve added it.

[Alex_8BitSkull]

This is a pretty major change. Is there a way to convert old save files? If not, it means games with live save files are locked to a before 1.3.6 or after.

I vaguely remember something about old versions of Defold not being supported after some time, but can’t remember in what way the support lapses.

In practice it seems to me that, for example, Fates of Ort now must use 1.3.5 or older, right?

[Potota]

@Alex_8BitSkull

Is there a way to convert old save files? If not, it means games with live save files are locked to a before 1.3.6 or after.

Old save files can still be loaded by new Defold versions and the engine will save them in the new format, overwriting the old one.

@Alex_8BitSkull

In practice it seems to me that, for example, Fates of Ort now must use 1.3.5 or older, right?

Nope, everything will continue to work unless you downgrade the Defold version of your game.

[Dragosha]

@Alex_8BitSkull

In practice it seems to me that, for example, Fates of Ort now must use 1.3.5 or older, right?

Don’t worry, everything will work fine. I encountered this problem only because I experimented with beta and then ran a project built on old versions using the same save file. This is clearly not a case for players.

[Alex_8BitSkull]

Thanks both and sorry for the panic!

[britzl]

@Alex_8BitSkull

In practice it seems to me that, for example, Fates of Ort now must use 1.3.5 or older, right?

No, each version of Defold has loaders for all save file formats up to the most current save file format for that version. 1.3.5 support version 1, 2 and 3.

With the release of 1.3.6 we use a new format to support larger files with more keys, hence the move to save file format 4. But as per above, 1.3.6 also supports loading of version 1, 2 and 3.