oosyrag's Forum Posts

  • The lessons and concepts you learn from using the built in multiplayer plugin are 99% applicable to any net code you do in the future, regardless of the specific format or platform.

  • You can use any version of Construct 3 you want by using the direct link editor.construct.net/rxxx

  • It's definitely a thing and not an optical illusion where the game can freeze for a few ms from high cpu use, even on pc, even when fps is 60+.

  • For a single event,

    On collision with heart - Set health to min(health+10,health_max)

  • Add a For Each Enemy condition.

  • If you don't want the follower to cut corners and get stuck, there are a few options to try:

    1. Use pathfinding.

    2. Have the player drop or otherwise keep track of waypoints for the follower, so the follower follows the player's path exactly and doesn't cut corners.

    3. Use line of sight to trigger a switch over to pathfinding when line of sight is lost, until line of sight is regained.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • How about collision filtering, where the player ignores the follower's collision box entirely, while keeping the follower collision box enabled all the time?

  • Disable the 'Enable BBCode' property of your text/spritefont object.

    You can also use \ to escape the [ character, but that's less useful in a user input type situation like yours.

  • Ran some tests to try to reproduce. It's much more noticeable for me when my estimated cpu usage gets high, according to the debug preview, at about 70%+. FPS stays above 55, but it's when it changes that jank is noticeable, especially for linearly motion. Lowering the number of objects/cpu load to under 50% made the FPS much more consistent.

    Turning off Vsync actually made it worse for me, as it drove the CPU use (and fps) up, causing significantly more jank, even though the fps was high.

    If the source is actually a CPU limitation, see if there's anything you can do to lower CPU utilization. If it happens in an empty project with low CPU utilization, I'm going to guess that some background software is possibly taking CPU time away from the game, like for example how some antivirus softwares can potentially slow a system to a crawl when running a scan at high priority. Not sure if that's a thing that can happen on a mobile device though, depending on how the device prioritizes it's CPU. Maybe some sort of power saving throttling? I doubt that would happen when actively using the device though.

  • That's not really true:

    Not sure if you really forget on purpose or ????

    as on the videos, they clearly showed you the settings before recording at 60 FPS please do not invent false accusations.

    Yes, It was one of the tests at 19FPS trying different crazy configurations as they told you just for testing but all the rest of the videos were at 60PFS as they show you clearly on that video.

    https://www.dropbox.com/s/sj84pw9ffdmy1w4/Stutters%20Recording.mp4?dl=0

    Settings: https://www.dropbox.com/s/ta2r9376yuqwu4f/c22.png?dl=0

    I never saw this follow up video at 60 fps, just the one you posted at low fps. I have no idea why your cacti are jumping like that.

    I find it funny that you still going on with the same subject where you clearly couldn't make even one video smooth without stuttering after a whole night of trying.

    This is the best you could do:

    https://www.dropbox.com/s/bbmrvggjkoapinv/framerate.mp4?dl=0

    Your video with the blue objects is clearing stuttering and this is one demo with just two events and a few objects on the screen so really it should have been very easy for you to make but you couldn't, though you still carry on with the same thing.

    If I was you I would definitely not bring back the topic after that night lamo ))

    If you consider the blue bars stuttering, we have decidedly different definitions of what stuttering is. Looking back at it, I do see some stuttering on the blue bars now, but only right after hitting play from stop, but not when I rewind/scrub back to the beginning after it's already playing. I'd chalk that up to my computer being a potato as it loads the video into memory. Regardless point was to show the difference between recording at a low fps and high fps. Which has nothing to do with the OP's topic at all.

    Though not sure what has to do that topic with the OP's topic as the topic you mentioned was for recording videos for trailers etc... and the OP has stutters at the Gameplay not recording.

    I understand that the OP has stutters for gameplay, I was saying that it is harder to see the problem from a video when the recording framerate doesn't match the game framerate.

  • You would want to do some vector addition - The original speed and angle of the bullet added to the speed and angle of the player. The most straightforward way would be to take the x and y velocities separately and just add them to their respective velocities. Unfortunately the bullet behavior doesn't have access to individual velocities on each axis.

    The neat thing is you can have multiple bullet behaviors on the same object. So add a second bullet behavior to the bullet object, and set the angle and speed of the second bullet behavior to the angle and speed of the player object. Assuming you're using custom movement like in the example, it would look like so: 

    -> Bullet: Set Bullet2 angle of motion to Player.CustomMovement.MovingAngle degrees
-> Bullet: Set Bullet2 speed to Player.CustomMovement.Speed

  • It may or may not cause issues. It's hard to say, a lot depends on the user's device. Precisely because it's hard to say is why I prefer to play it safe.

    Larger textures can definitely cause issues in regards to limited VRAM. It just doesn't make sense to me to risk potential problems for something that people may or may not be able to take advantage of in the first place (or even notice a difference at all).

  • It really is hard to tell from the video, it looks mostly fine/smooth to me. Probably doesn't help that the video is recording at 30fps. I don't think it's a big deal on something that the user normally wouldn't be focused on, especially at high speeds. The wheels and train and tracks look great (from the video at least, I don't doubt that it's worse in person as you mentioned).

    I have a minor suspicion you may be nearing the limits of your device, as the fps as shown was at the low 50s and even dips below 50 at the beginning, and you said it looks fine on PC. I wouldn't normally call that a stable fps. I do note that it gets back to around 60 in the latter half, but I'm also not clearly seeing your jank/jitter either.

    If I were to pursue this I would try taking everything out except the foreground plants (especially any physics actors), and seeing if it makes a difference on the device.

    Edit: Any parallax on the layer? Or just varying speeds between foreground and background objects?

    Another long shot to consider - are you updating your debug text every tick? Try disabling the text updates to see if it makes a difference. I've had issues with this before where my debug text was slowing everything down, although mine was significantly more text objects to display the contents of a data array.

  • Personally, I wouldn't target 4k resolution for a 2d game.

    It becomes more about pixels per inch at that point. Most users won't be able to discern a difference unless their screen is huge like a TV or something.

    I'd rather target a larger audience with lower end devices, unless cutting edge, industry leading, high fidelity graphics are a huge selling point of my game.

  • Got a minimal example project or video? It would be useful to troubleshoot your issue, or for the devs to look into. I've seen jank and jitter mean different things to different people.

    For example, your sprites could be jittering back and forth position wise at 60 fps if there is a positioning issue such as the previously mentioned pixel rounding. It can happen when your camera and object are moving at the same speed but with slightly offset timing. There can also be pinning issues if you're using a pinned camera where the camera position updates one tick later. This can happen no matter how high your fps is.

    One time in discord someone was complaining about their game recordings showing "jank" when running at 60 fps, but it was because their videos were recorded at 19fps or something silly like that.

    It's highly likely your stuttering/jank/jitter has nothing to do with fps at all.