R0J0hound's Forum Posts

  • It's basically a flood fill. For the wires start at the power source and then power all the connected wires, then loop over those wires and power what is connected to them and repeat. To address wires being cut you can set everything to be not powered before spreading the power from the source.

    The hull breach can be done similarly, only the fill starts from outside the ship.

  • The function is cr.angleTo(x1, y1, x2, y2) and it's in common_prelude.js. It's a helper function that is used throughout the runtime, so the likelihood of it breaking later on is near zero. There are also a lot of other functions in that file that can by useful.

  • It's a difference between webgl and html canvas rendering. Webgl only draws the pixels inside a polygon whereas html canvas draws along the edge as well. For a solution you can use a sprite for the line and paste it to paster.

    Here's a way to position a line:

    https://www.scirra.com/forum/viewtopic.php?f=147&t=76296&p=631921&hilit=line#p631921

  • Just to add that the "pick by uid" condition is the exception to the rule about picking since r127.

    https://www.scirra.com/construct2/releases/r127

  • You don't always need an expert to answer every question. If the question isn't directly tied with c2 the internet is a vast resource that can provide solutions or tips on how things are done. Even if it isn't then you can expiriment with the lab which is c2. My computer is filled with examples I've done to figure out how things work.

    I'm not saying you shouldn't ask questions, rather there are ways to figure it out on your own.

    Also keep in mind that most experts don't just know an answer, but if it sparks their interest and they have the time they sometimes can find a solution. The key word being "time". And all users, including you and even the brand new users can be one of the "contributing experts" if you take the time to find an answer to a question.

  • QuaziGNRLnose

    Ok, I found where the webgl texture handle is in the __webglTexture attribute of WebGLRenderTarget.

    var rendertexture = new THREE.WebGLRenderTarget(100,100 );
//texture to use with setTexture()
rendertexture.__webglTexture[/code:2w4vnv08]

The problem that I've found after that is the texture still won't work since by default textures aren't shared between different contexts.  But there is a way to share it:
[url]http://www.khronos.org/webgl/wiki/SharedResouces[/url]

From that page I found this tidbit of code that shows what needs to be done to share textures:
[code:2w4vnv08]var gl1 = someCanvas.getContext('webgl');
var sg1 = someCanvas.getExtension("WEBGL_shared_resources");
var gl2 = someOtherCanvas.getContext('webgl', {
    shareGroup: gl1.shareGroup
});
var sg2 = someOtherCanvas.getExtension("WEBGL_shared_resources");
var tex = gl1.createTexture();
sg1.releaseSharedResource(tex);
sg2.acquireSharedResource(tex, gl.READ_ONLY, function() {
   gl2.bindTexture(gl.TEXTURE_2D, tex);
});[/code:2w4vnv08]

I'm still working out the details for getting it working but a few points I have so far.
1. The first context doesn't need to be created, we can get it from this.runtime.gl.
2. For the second context it seems we have to create the canvas and context for WebGLRenderer first and then pass them as parameters like this: [code:2w4vnv08]var renderer = new WebGLRenderer({"canvas":mycanvas, "context":mycontext});[/code:2w4vnv08] The context creation can likely be copied basically from what threejs already does plus the shareGroup stuff.
3. The bindtexture() function should be replaceable by the set Texture() function.

I hope to have it more ironed out later.

Edit:
Well it seems that resource sharing isn't implemented as of yet...

Edit2:
After further testing the idea won't work.  I also tried making threejs use the same canvas and context as c2 but it's giving errors, probably due to conflicts in gl states from the two.  So Ashley's solution is probably the best you can get at the moment.

  • I did about the same thing in my canvas plugin to get a webgl texture and had the same effect of being slow.

    If you look in the text object it uses a function from Glwrap that just copies the pixels from a canvas to a webgl texture instead of loading a new texture each time. I haven't used it yet but it should be a bit faster especially since it should give less for the gc to collect.

    That sounds interesting that three.js can render directly to a texture. As far as I'm aware c2 uses just a standard webgl texture handle. I'll try to investigate furthur when I get to my PC.

  • anticloud

    Feel free, I don't have any restrictions on the use of my plugins.

  • The closest you can do is perhaps use the canvas plugin (third party). With it you can get individual pixels from just the object's image. Besides that there isn't a way currently to get the color under the mouse for the whole game area.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I'd imagine the performance would be better after exporting. It's hard to design for this since the texture atlas is done automatically and you're still bound by a maximum texture size.

    To see if your idea would be faster you'd need to make a test either way and measure the performance. This is assuming that's where the bottleneck is at in your game. My machine is weak with html5/javascript so logic is often the bottleneck instead of rendering. Well I have a slow rendering issue as well since my graphics card is in driver limbo, so I'm hit by both sides.

  • Ashley can probably answer more precisely and you can find some more info on C2's renderer on Ashley's blog, but I can give some overview. Basically images are moved to video memory once and when rendering webgl is told which texture to use, the opacity and the quad's four corners' xy and uv coordinates. C2 uses sprite batching to group sprites with the same texture together and reduce the draw calls to lesstexture switching and sending bigger chunks of the quad vertices. Now as to your question I imagine if you had only two instances of one object and each had a different frame then that would be two draw calls. However on export C2 creates texture atlas' of the frames if it can, so then it may take only one call. To be more exact about a draw call, it is only done once per frame in webgl. Everything else is just sending info to webgl to use when the frame is drawn.

  • Look in the pin behavior. At least I think that's the behavior that does it, there are others. The function was called tick2() but now it's called posttick or something like that. The function is usually right after the tick function.

  • You can use Browser.ExecJS("'\x41'") to do any ascii letter from a two digit hex. In this case it's "A".

    It's not needed though since you can use " " and newline. Backspace seems it would be useful but it does nothing in javascript. You'll have to do something link set text to left(text, len(text)-1) instead.

  • Here's something that works.

    https://dl.dropboxusercontent.com/u/5426011/examples21/clearWhite.capx

    To make it work with an imgUrl change the executeJs in event 2 to something like this:

    "this.clearFill('"& Canvas.imageUrl&"'," & int(TextBox.Text) &");"