shinkan's Recent Forum Activity

  • Why do you need to keep exporting anyway? It's intended that preview mode covers your everyday work and test cycle. Is there a problem using the Crosswalk test apps?

    I don't have an access to wi-fi and only thing I can do to test on mobile is:

    • build in XDK and wait 10-20 minutes (upload, build, download) each time
    • connect my phone via USB and test it using XDK test/debug options - which takes only export time of waiting.

  • If you skip PNG recompression isn't it a near-instant export?

    It's a bit faster but still takes about 10-15 seconds and still exports all of the images - no compression = bigger in size.

    Been observing folders I'm exporting to and most of this time goes to sprite sheeting animation frames.

    I'm using raw and not yet optimized images, so they are 512x256 with a lot of opacity around. But i believe this will be a final image size, only content will differ.

    8 of this images [attachment=1:3ct90yhd][/attachment:3ct90yhd]

    are made into something like this [attachment=0:3ct90yhd][/attachment:3ct90yhd]

    Aphrodite

    Yes, that's what I ask for.

    "Skip png compression" still export images.

  • Expansion files sound really nice!

  • Ashley could you add an option to export only events/logic without exporting/recompressing images?

    I have a small project - 17 events only, but quite few small and medium sized sprites.

    Every time when I press export it takes about 30-35 seconds to finish, due to recompression and sprite-sheeting of all objects.

    All I do is changing and modifying events without touching any of sprite images or even opening image editor - and every time after export, Images folder looks the same.

    I'm optimizing, testing and debugging in XDK and long exports really slows down this process.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Ashley

    Could you please add a "Set angle of motion" to Bullet behavior properties?

    Simply for ease, to not have to set +1 events for initial objects setup or runtime creation.

    Edit: Example

    If you have 10 objects on same layout and you want to set different (not random) angle of bullet motion for each one of them. Then: 

    on start of layout  object 1: Set bullet angle of motion to XXX degrees
                    object 2: Set bullet angle of motion to XXX degrees
                    ...[/code:2io4xtg1]
That's 10 extra - easy, but extra actions to insert.

But if you have 10 instances of same object on layout then you need specify each one of them:
[code:2io4xtg1]on start of layout
[ul]
	[li]object var = 1 | object: Set bullet angle of motion to XXX degrees[/li]
	[li]object var = 2 | object: Set bullet angle of motion to XXX degrees[/li]
[/ul]...[/code:2io4xtg1]
That's 10 extra sub-events.

Adding this one parameter you could simply copy one instance, set angle of motion. Copy another one, set angle of motion... etc = none unnecessary events at all.

  • Unbounded scrolling set to Yes lets you make you levels no matter how big or small they are. When you turn it on it will center viewport on XY: 0,0 coordinates, so you need to scroll it to your player avatar position.

  • You can't change layout size on runtime. Use unbounded scrolling instead.

  • Did you try saving and loading simple text files?

  • Do you want to spawn them on specific places over the layout? or just wherever but outside windows size?

  • When you creating new blank project in XDX you will get a folder in location specified in XDK. In this folder there is already a folder called "www".

    All you need to do is to export Android from C2 to XDK projects\"Your project name"\www

shinkan's avatar

shinkan

Early Adopter

Member since 21 Nov, 2008

Twitter
shinkan has 8 followers

Connect with shinkan

Trophy Case

  • 16-Year Club
  • x5
    Coach One of your tutorials has over 1,000 readers
  • Educator One of your tutorials has over 10,000 readers
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • Enduring Visitor Visited Construct.net 90 days in a row
  • Unrelenting Visitor Visited Construct.net 180 days in a row
  • Continuous Visitor Visited Construct.net 365 days in a row
  • RTFM Read the fabulous manual
  • Email Verified

Progress

25/44
How to earn trophies