[Vlad]

Hi

After upgrading to 2.0.1 my log is flooded with:

VPlayTask: the dt would have been higher than 0.1 seconds, set the cap to 0.1s to prevent unwanted effects, the dt was: 0.154

VPlayTask: the dt would have been higher than 0.1 seconds, set the cap to 0.1s to prevent unwanted effects, the dt was: 0.154

VPlayTask: the dt would have been higher than 0.1 seconds, set the cap to 0.1s to prevent unwanted effects, the dt was: 0.154

VPlayTask: the dt would have been higher than 0.1 seconds, set the cap to 0.1s to prevent unwanted effects, the dt was: 0.154

VPlayTask: the dt would have been higher than 0.1 seconds, set the cap to 0.1s to prevent unwanted effects, the dt was: 0.154

VPlayTask: the dt would have been higher than 0.1 seconds, set the cap to 0.1s to prevent unwanted effects, the dt was: 0.154

VPlayTask: the dt would have been higher than 0.1 seconds, set the cap to 0.1s to prevent unwanted effects, the dt was: 0.161

 

and performance quickly degrade

what does this means?

 

thanks,

Vlad

• This topic was modified 9 years, 11 months ago by  vladest.

[Vlad]

Another this happens when number of entities on scene higher than 5

Also CPU load in this case is 100%

My system is Ubuntu 64bit 14.04

• This reply was modified 9 years, 11 months ago by  vladest.

[ChristianFelgo Team]

Hi Vlad,

what is causing the performance drain is hard to tell without knowing more about your game.

The first step would be to start QML profiler and test on which parts of your game code the most time is spent. Alternatively, you can try by deactivating specific functionality where you think most processing time is spent. Or add a toggle button which allows changing this behavior at runtime where you then see the effects immediatelly.

Also, you can have a look if this performance issues go away in release mode which usually runs a lot faster.

Cheers, Chris

[Vlad]

Hi Chris

my main concern that it was work ok in previous Felgo (2.0.0)

 

br,

Vlad

ps. is there a way to reduce number of debug messages in debug builds? Ideally, I want to see only mine messages

[Vlad]

I’ve took QML trace and its looks like performance degrade in painting seriously when animations > 5. FPS drops dramatically

I can send trace file

[ChristianFelgo Team]

Hi Vlad,

could you please extract a test case and post it here? After our performance tests, the performance should actually be better than with 2.0.0 and 1.x.

Cheers, Chris

[Vlad]

Hi Chris

 

I’ve created test project, but it too big to insert it here

How can i sent it to you?

 

Thanks,

Vlad

[AlexFelgo Team]

Hi vlad,

you can send it to support@felgo.com.

Thank you!

Cheers, Alex

[Vlad]

Hi

 

I’ve did some more investigations. It seems that performance impact is the rotating of the image within entity.

So, I’ve created simple pure QML Quick2 test with rotating stars:

import QtQuick 2.2
import QtQuick.Window 2.1

Window {
    visible: true
    width: 480
    height: 320
    Grid {
        anchors.fill: parent
        Repeater {
            model: 100
            delegate:     Image {
                id: sprite
                source: "rotaring_star_solid.png"
                width: 32
                height: 32

                RotationAnimation on rotation {
                    from: 0; to: 360;
                    direction: RotationAnimation.Clockwise
                    duration: 1000
                    loops: Animation.Infinite
                    running: true
                }
            }
        }
    }
}

here is 100 rotating stars, which takes only 15-20% of CPU

 

Probably this will give you some hints where the problem may be

br,

Vlad

[Vlad]

Also I’ve noticed, when performance started to degrade, physics almost stops to work: no collision detection etc

[ChristianFelgo Team]

Hi Vlad,

this error relates to an issue we had in debug builds since Qt 5.3 usage in the physics system. We’ve fixed it and now performance is good as before – we’ll add this fix to the next Felgo release 2.0.2, ETA this week.

In the meantime, please use the release build which does not have this bug.

Thanks a lot for reporting,
Chris

[Vlad]

Hi Chris

 

thanks for the info

However, unfortunately, I can observe the problem even in release build with PerformanceTest I’ve sent to you

br,

Vlad

[ChristianFelgo Team]

Hi Vlad,

please wait til tomorrow’s release of Felgo 2.0.2, and then let us know if the problem still exists or if it also works for your case.

Cheers, Chris

[Vlad]

Hi Chris

 

it seems its fixed now

 

Thanks!

[ChristianFelgo Team]

That’s good to hear Vlad!

Cheers, Chris