R0J0hound's Recent Forum Activity

    It was a friendly request by the guy that gave the most of his time trying to help. No need to get grumpy.

    I think today is a nice day for a stroll.

  • Scroll down to “contact us” and you can find the email there?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • No need. Oosyrag covered it.

    In this context it’s fine using -infinity for volume. It converts to 0 anyways internally when the decibels are converted back to the 0-1 range for webaudio

    I mean with the formula

    Decibels = 33*log10(percent/100)

    We get approximately

    0db for 100%

    -5db for 75%

    -10db for 50%

    -20db for 25%

    -infinity db for 0%

    So decibels and percent are pretty interchangeable in that regard. Fading with one unit vs the other would give different results for sure. For a slider I’d use percent. With the numbers I’m not seeing how the top half would barely do anything.

    Construct and Audacity are the only pieces of software I’ve used that has decibels. I’ve certainly never played a game where volume was anything but a percent. Audio apis such as webaudio and fmod set volume in the 0-1 range, so basically a percentage.

  • Those debug console error messages are seldom helpful. Could it be an issue with a third party plugin? Maybe. Some were never tested with the minifier so that could be the issue. My only suggestion is to try exporting with the minifier turned off.

  • If you exported to the arcade and uploaded the exported file it should work.

  • Fixed.

    * drag based on where the mouse clicks now like you had it before.

    * also fixed the janking craziness. Turns out near a tilt of 90 things could go haywire. Fix was to limit tilt to range 1 to 89.

    dropbox.com/scl/fi/ljuplixdxjtghe23ijzdo/2d3dcam_Test.c3p

  • Here's one possible solution. Can't make an example with the free version.

    + layer 1: force own texture
    |-+ light: force own texture, effect darken, transparent no, color black, 
    |-------- light gradients with destination-out blend
    |-+ level: level stuff
    + layer 0: background

    Basically you'd have a light layer that's black with the light gradients with the destination-out or additive blend. The layer has force own texture so we can apply it to another layer.

    Below that you have a normal layer with all of your layer.

    To show a normal background layer under all that you'd place the light and level layers as sub-layers to a new layer with force own texture. Finally add a bottom layer with the background.

  • For 1.

    Sounds like a bug. When a texture is created from an image the code specifies whether the texture repeats or is clamped. So looks like construct recognizes that it’s the same texture and reuses it but doesn’t change the repeat mode of the texture.

    For 2.

    Tiledbg has a texture per instance. By default it loads the default one when creating, but when you load a texture it replaces it on that instance alone.

    Sprites have their textures in an animation structure that’s shared between instances. So if you replace a texture it affects all instances.

    I thought they added a way to add frames at runtime too for sprites. But overall the textures are loaded in specific ways per type.

  • logic would probably be along the lines of :

    every 0.5 seconds
    -- enemy has los to player
    -- -- enemy: find path to player
    -- -- enemy: set mode to "seek"
    -- [X] enemy has los to player
    -- -- enemy: stop following path
    -- -- enemy: set mode to choose("walk", "stand", "turn")
    
    enemy: mode = "walk"
    -- enemy: move forward
    
    enemy: mode = "turn"
    -- enemy: rotate choose(-90,90) degrees clockwise
    -- enemy: set mode to "walk"
    
    enemy: on path found
    -- enemy: follow path

    Or something like that.

  • Oh strange since it’s smooth on my end. I’ll have to test again. Maybe add a trace of the mouse path to debug.

    Either you’re moving the mouse in a path I didn’t test or the easing is flawed on other refresh rates? You can try to set t to 100*dt or something instead of what it has now and see if that affects things.

    It’s probably easy to switch it back to moving relative to where it clicked on the ground. Could also rotate based on where we clicked on the ground too, but then we’d need a separate control for tilt.

    Edit:

    Did you change any of the values? When I had t=exp(-100*dt) the ease was super gradual.

R0J0hound's avatar

R0J0hound

Member since 15 Jun, 2009

Twitter
R0J0hound has 155 followers

Connect with R0J0hound