SnipG's Recent Forum Activity

  • I did not flip something, maybe i did bad example. But in physic game, world gravity 0 or immovable physic object are very often ingame.

    Physic itself ofc does not involve with rendering, but behavior itself still moves object with textures, and if there is some bug, it will impact gpu and other aspect of game.

  • Was doing some bug report to issue tracker and was sent to here, to discuss why is it happening as physic behavior should not affect GPU. If there is someone who knows it better, or bug is just happening with my pc, not sure about this.

    Example:https://onedrive.live.com/?cid=F559A24F927C9F9F&id=F559A24F927C9F9F%211020&parId=F559A24F927C9F9F%21145&o=OneUp

    Having example in fullscreen and taping to create new sprites. In c3runtime gpu will very high and already at 150 sprites it will drag fps to ~30fps and gpu 100%. While in c2runtime gpu is around 10% and fps stays 60.

    I am pretty sure physic sprite in c3runtime, when its set to immovable or world gravity 0, is still handled in a way that it somehow is constantly moving, triggering some webgl batching problems etc, while c2runtime has this covered.

    So is there someone who can clarify how is physic, in this case, affecting GPU, or its something else?

  • Neat little game like that dan-ball.jp/en/javagame/dust in which you can make similar effects youtube.com/watch

  • Maybe they are 2d fluids, they are made to look like particles. I doubt its full physic engine or shaders

  • This has been happening even before 120/121 etc. In some strange cases webgl just crashes in preview(results black screen) and then editor view is blank, even tought you can still click and select objects. Ordinary it happens when doing some tests with huge amount of sprites.

    You can get similar crash in shadertoy.com when viewing some examples there.

    It has never happened with just 1 preview test, but over time while you have done like 5-6+ test. So there could be some kind of leak.

    I got different console error when it has happened. "WebGL: "Context_Lost_Webgl: loseContext: context lost"

  • C3 runtime uses WebGL2 while C2 runtime uses Webgl1. So your browser does not support Webgl2 or it has been disabled.

  • I reported issue in 118 about LoS it got fixed in 119. It was combination of LoS + Obstacle(tilemap in my case). So try maybe deleting some Obstacles and if you find one which fixes it, you can recreate and report the issue.

  • If you use worker then try without it, if gpu % goes higher then cpu %(with worker) it can crash. You can check it in canarly with gpu % and cpu %.

  • Did some quick tests.

    Sprite with bullet + fade. Before (111 stable)- C2 ~10400 sprites vs C3 5500 sprite at ~30 FPS.

    After update (112 Beta) - C2 ~10 400 vs C3 around same as C2 ~10 000, but seems maybe 2-3% slower.

    Bullet behavior on sprite (111 stable) - C2 ~ 11000 vs C3 ~9500. (112 beta) - C2 ~11000 vs C3 ~ 14 000

    Did some extreme test. Sprite with fade,bullet,Solid,Flash,DestoryOutsideLayout,Rotate:

    (111 stable) C2 ~7700 vs C3 ~ 1800. (112 beta) C2 ~ 7700 vs C3 6700.

    When sprite has 1 behavior it is better in 112 Beta and in 111 in most cases, but if multiple behaviors are added, C3 is same or bit slower in come tests.

    Just Fade on sprite, is around same in 111 stable and 112 beta. C2 - 15 000 vs C3 ~25 000.

    Sine same in 111 and 112: C2 ~ 23 000 sprites vs C3 ~ 34 000.

    Test are results with 30 fps, so when you try achieve 60fps, results maybe be different. Done it with my own tests to give some overview.

    C3 peforming a bit slower is to do with C3 trying to match C2 runtime, so it is faster but doing extra work to match C2.

    It seems really nice that C3 is getting better with every update.

  • Is layout grid bugged or which grid is running out for you ?

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • It is most likely a typo, it should be inside that previous event. If keyboard or gamepad buttons are not down, set walking to false once. Atm trigger once is seperated, it sets walking to false each tick, which is bad behavior.

  • I tried chrome bug report apk on samsung S9, with default browser chrome or samsung internet 7.2.10.33. Can't reproduce it. Does anyone even have some solid example that fails, or some game example?

SnipG's avatar

SnipG

Early Adopter

Member since 8 Jul, 2016

Twitter
SnipG has 2 followers

Trophy Case

  • 8-Year Club
  • Entrepreneur Sold something in the asset store
  • Forum Contributor Made 100 posts in the forums
  • RTFM Read the fabulous manual
  • Email Verified

Progress

12/44
How to earn trophies