lokesen's Forum Posts

  • I don't have any problems. If you are using Construct2's image editor, it leaves 1px space if you crop or resize with it.

    It's hard to tell what the problem might be without seeing the capx.

    Does turning pixel rounding help in project settings?

    Why would you wan't 1px space between your tiles? I would like them to just touch without any gap between.

    A background looks pretty silly with 1px line between the tiles...

  • When two different tiled backgrounds are touching or overlapping, a thin white line is formed like this:

    dl.dropbox.com/u/4759481/Tile_problem.png

    I have tried to work around this issue, but it always seems to eat up much of the time I should use to create my game.

    If the darned engine need to create a line between the tiles - why not a transparrent one that can't be seen???.

    To me - this is by far the worst thing about C2 and makes it very hard to make a professional looking game.

    I really do hope somebody has a solution to this - or at least a work around. :)

    Thanks!

  • I think Awesomium is probably to blame for most of the stability issues.

    By the way, I can't get any WebGL shader effect to work in Awesomium with R104. Works fine in Chrome all of them.

  • Same here.

    I got all sorts of crashing with Awesomium and R104.

    Also related to everything fullscreen.

  • I got three problems at the moment with fullscreen.

    1. Fullscreen in Awesomium makes Awesomium crash 95/100 times in r104:

    This happens within the first 10 sec.

    Before I bother Ashley about this, can somebody please see if you got the same problem. I have tried this on two different computers (Nvidia/Ati based). I had a few issues before r104, but now it's almost every time.

    2 and 3. Fullscreen in Chrome:

    When using F11 to get into fullscreen, everything is fine. But when I use the browser request fullscreen, there is a single pixel wide white line in the left side of the picture, and generally much much worse fps compared to the F11 method.

    Hope some of you guys have experience with these issues. I don't wan't to post this in the Bugs section, because I wan't to confirm if others have these issues.

  • I also noticed some increase - maybe about 10-15 procent on my slow test machine (Amd E-300).

    Beside from that, I can now get all the things that was broken in the 0.103 branch to work again. Thank you for that change Ashley - that was a hugr deal for me :)

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Hi Lokesen!

    I will suggest ezvid.com - have some good experience with this free software :-)

    I'll try that - thanks.

  • Maybe is your CPU a little bit old for the settings you are using?

    Maybe - it'a a slightly overclocked i5 2500k.

    It doesn't matter much if it's low res, high res, uncompressed, mpg4, mpg2 or other codecs. I'm recording to a SSD and it's not my system drive. But that doesn't seem to matter.

  • I already tried them - very choppy recordings for me.

    Other suggestions?

  • How do you guys manage to capture nice quality videos of your C2 games? Every time I try, I get terrible framerates even though the game runs 60fps while capturing.

    How and what software do you use?

  • Ashley

    Oh I didn't know that. I'll cross my fingers - my game would do well With the Apple people I think.

  • r105 would be fantastic :)

    Ashley - would it be possible to make the Awesomium exporter for mac too in the future?

  • Just wanted to let you guys know that Awesomium 1.7 RC3 is finished and the team is just preparing the documentation now.

    So very soon we will have a much faster exe exporter with direct to window rendering! Yay! I'm so psyched about this!

    Can't way to try this - because I know Ashley will include this in one of his next updates. Let's hope RC3 is all we hoped for.

  • Same problem here - looking forward to the update :)

    I get it if two objects is destroyed within about 0.05 sec or less.

  • Last I heard from them, they already solved the problem. We just need to wait for their next update so Ashley can include it in his next update.

    Awesomium is a tad less regular on the releasing front though.