Radiowaves's Forum Posts

  • It does not work.

    First of all, it glitches.

    Secondly, the underlaying object still does not stay at 10px offset at all times relative to screen edges.

    Vers 1: https://imgur.com/a/SLjeL5S

    Vers 2: https://imgur.com/a/jtPPgJG

  • Set scroll does not quite work. It acts like parallax.

    I have Object A on layer 1 and Object B on layer 0, both at the same position and turning, in same hierarchy. I want the Object B to be offset on Y axis 10px, so as the both objects turn, the Object B always remains offset in one direction and the offset is not dependent on the angle of Object A.

    When I use "set layer scroll", the object B is all over the place as object A moves. I don't quite understand it, I don't want the layer to be offset exponentially as I have "scroll to" behaviour on Object A as it happens here:

    https://imgur.com/TvMeBGF

    There are workarounds for this, like pinning both objects to separate pivots of one non-turnable parent object. But I am thinking this could be solved more easily with just offsetting a layer since I will have many objects like this. After all, we can turn a layer, set its scroll -- why not an offset/position? Is this an oversight?

  • Consider that your isometric grid is just an array, you can even use a real array to store the data. The placement and angle of the cells is just math, where you need to offset each cell.

    Write a function that compares data in an array and returns true/false value. Then write another function that calls this function for each adjacent cell.

    Or am I misunderstanding something? Seems pretty straight forward to me.

  • Anyone?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I remember in C2, pin behaviour had different pinning methods, like rope style, lever style etc. This seems to be missing in C3. C3 also has hierarchies which already duplicate pinning behaviour, so without the different pinning methods, pin behaviour seems redundant and deprecated.

    I am wondering why pin behaviour exists. Is it only for running C2 projects?

    Also, how can I replicate different pinning methods present in C2 either by hierarchy or pin behaviour? Or do I have to use something else instead and/or write my own pin mechanic?

  • I don't mean parallax. I mean I want the layer to scroll the same way as a game, but need it to be offset 10px in Y axis.

    Or is there a way to pin an object so that it is always offset on y vector?

  • I have simple project. In reality this should not even be a megabyte large, but when I export the project as exe with construct built in tools, file size is over 300mb.

    I know in todays world and age it is not considered as large, but I find it ridiculous.

    How can I make the executable smaller? Is there some other exporter that I can use or can NWjs be modified to exclude most of the stuff?

  • Same here. That is the issue I feared with subscription based products. You build your project on it, and one day it is all gone. Why would I need Internet connection anyway for construct?

    EDIT:

    C3 now starts, but previewing does not work.

  • "Or presumably if the ui layer has a parallax of 0,0 then you could just use:

    viewportWidth(“ui”)/2"

    That is precisely what I have, but somehow the viewportWidth(“ui”)/2 stopped working somehow. I did change viewport size...

    So as of now I assume it should be viewportLeft("UI") + (viewportWidth(“ui”)/2), but I don't understand why.

  • I got it to work with ViewportMidX("UI"), but I am still wondering how could I calculate it manually.

  • I got this to work before. But now I am at the point if I don't know if I broke something or something got broken with construct 3 update.

    I want to center the panel on X axis on screen. I used int(ViewportWidth("UI") / 2) before, but it does not work anymore. Also getting the window inner width via PlatfromInfo and setting it based on that value does not work. It all worked before, until it did not... It is all off to the left side of window a bit, kind of odd.

    Switching the "unbounded scrolling" option on layout on/off does not affect the behaviour.

    I am also trying to account for screen scaling, most of the 4k monitors are set to 200% scale, but can also be set to 175% etc, which messes up the rendering. -- How do I account for that?

    Can someone also explain to me in which cases ViewportWidth can be something other than Window inner width, it is supposed to be viewport..? I presume if layer is scaled up?

  • You do not have permission to view this post

  • You can use float(), and probably make a separate condition with "?" expression that checks if it is float or string.

  • You do not have permission to view this post

  • You do not have permission to view this post