1. Hey! Guest! The 35th GMC Jam will take place between November 28th, 12:00 UTC - December 2nd, 12:00 UTC. Why not join in! Click here to find out more!
    Dismiss Notice

Question - IDE Latest update broke my game's collisions.

Discussion in 'GameMaker Studio 2 Community Tech Support' started by SomeBlindGuy, Apr 4, 2018.

  1. SomeBlindGuy

    SomeBlindGuy Member

    Joined:
    Oct 18, 2017
    Posts:
    16
    Ever since installing the update earlier, the collisions in my game are completely messed up.

    My player object suddenly collides with walls in places where there are none.
    For some reason, all rooms past the second one still use the wall positions of the second room.

    I tested this by placing new walls in the second room, and as I expected, these new collisions also happen in later rooms.

    This applies to all the builds of my game that I tried.

    Help?

    PS: I wasn't sure which prefix to use.
     
    nihiven likes this.
  2. Nocturne

    Nocturne Friendly Tyrant Forum Staff Admin

    Joined:
    Apr 13, 2016
    Posts:
    6,982
    Please file a bug report and include a link to the project for the devs to test. You can then rollback the runtime in the Prefs > Runtimes window to a previous one and that should fix things until the devs can resolve the issue.
     
    Pfap likes this.
  3. Beechbone

    Beechbone Member

    Joined:
    Jul 10, 2016
    Posts:
    15
  4. JapaneseMeow

    JapaneseMeow Guest

    I'm having the same problem right now..
     
  5. Bladebss

    Bladebss Member

    Joined:
    Apr 8, 2018
    Posts:
    34
    I too am having this problem. The 2.1.4.202 runtime did not fix this.
     
    cookies1 likes this.
  6. cookies1

    cookies1 Guest

    Same here. It broke my game as well.
     
  7. abeldev

    abeldev Member

    Joined:
    Aug 17, 2017
    Posts:
    30
    Exact same thing is happening to me. Knew there was nothing involving my collisions that I did to cause a bug!
     
  8. adam_jd

    adam_jd Guest

    Relieved it's not just me! Spent like 2 hours going through all my objects and rooms and couldn't figure out what's was happening.

    Using 2.1.3.189 seems to prevent the issue for now.
     
  9. JimiThing85

    JimiThing85 Guest

    Same here, collisions don't work properly since 2.1.4, don't use physics or solid variable. 2.1.3.189 works fine, would love an update from the gamemaker team ASAP about what went wrong/when a fix is incoming. I know from my limited GML experience how hard coding can be even at a basic level lol, but it seems odd that they missed a glitch with something as basic as collisions, since it seems to be affecting lots of people and glitches physics based collisions as well.
     
  10. Ender102

    Ender102 Member

    Joined:
    Apr 10, 2018
    Posts:
    1
    From what I can tell, at least in my case, the bug has to do with persistence. Lets say I have invisible walls that are marked as solid in room1 and room1 is persistent. When the player proceeds to room2, which doesn't have said walls, they still run into the same walls as room1, even though they don't exist in this room. The persistence seems to be carrying them over somehow. If I start the game in room2, or turn off persistence in room1, the bug goes away. But of course, for the way my game works, I need persistence. I hope this post helps, because I'd really like to have this fixed soon...
     
  11. bluetrack

    bluetrack Member

    Joined:
    Jun 21, 2016
    Posts:
    51
    Same here. After the update, the player gets stuck in walls or in oneway moving platforms. (2.1.4.202 runtime hasn't fixed it).
     
  12. JimiThing85

    JimiThing85 Guest


    I think you're on to something, it would explain a lot of my mystery collisions/invisible objects suddenly appearing...
     
  13. abeldev

    abeldev Member

    Joined:
    Aug 17, 2017
    Posts:
    30
    Yep, this is what I figured out after about 3 hours. For some reason the collisions of the first room carry over
     
  14. LumeTurtle

    LumeTurtle Member

    Joined:
    Mar 31, 2018
    Posts:
    3
    The 2.1.4.203 update today still hasn't fixed my collisions. My player character is still sliding along walls they shouldn't and getting stuck on walls that they didn't previously.
     
  15. Bladebss

    Bladebss Member

    Joined:
    Apr 8, 2018
    Posts:
    34
    Yea new update didnt fix it for me either.. :(
     
  16. Brendan Wiuff

    Brendan Wiuff Member

    Joined:
    Apr 7, 2018
    Posts:
    9
    Same problem here. All rooms are existing at once. All collisions exist in the same space. It’s maddening but looks like a bug in the update. Will try to rollback to the old version.
     
  17. Nathan

    Nathan Member

    Joined:
    Jan 19, 2017
    Posts:
    53
    Having a similar issue since updating was mandatory. I have invisible objects colliding with breakable objects that tell the breakable what content it should contain. Neither are solid. None of them are working unless they start on the playable screen. Once the screen scrolls and objects activate, the invisibles get activated but the collisions don't work. I am not able to roll back my Runtime. I can install it but it gives me no option to use it. It automatically uses 2.1.4.203 I tried deleting the newest runtime and restarting GMS2 and it just reinstalls 203.
     
  18. LumeTurtle

    LumeTurtle Member

    Joined:
    Mar 31, 2018
    Posts:
    3
    The 2.1.4.212 update appears to have fixed my collisions! :)
     
  19. Nathan

    Nathan Member

    Joined:
    Jan 19, 2017
    Posts:
    53
    Did not fix any of mine. :\ Back to 189
     
  20. Dog Slobber

    Dog Slobber Member

    Joined:
    May 20, 2017
    Posts:
    283
    To change the current runtime go to the the masters section of preferences and doublelick on the desired runtime .

    It's not very intuitive and a bit finicky.

    This topic is an excellant example of why it's useless to state that you have the 'latest' version instead of actually posting the version number.

    There have been a few runtimes releasesd in a short period of time. With each addressing some, but not all

    Topic readers have no idea which runtime the poster is talking about and may even come to the conclusion the current 'latest' hasn't addressed the issue.
     
  21. Nathan

    Nathan Member

    Joined:
    Jan 19, 2017
    Posts:
    53
    The 2.1.4.212 update Still did not fix my collision issues that were recently introduced by the 2.1.4.202 Reverting back to .189 solves the problem for now until a new update addresses it.
     
  22. rwkay

    rwkay YoYo Games Staff YYG Staff

    Joined:
    Apr 12, 2016
    Posts:
    1,049
    @Nathan - file a bug (Help -> Report a bug) please so we can see what your issue is - we currently do not have any known collision issues, please help us fix the issue.

    You will need to attach a project (that is as simple as possible, please) for us to diagnose what the issue is.

    Russell
     
    Joe Ellis likes this.
  23. Nathan

    Nathan Member

    Joined:
    Jan 19, 2017
    Posts:
    53
    @rwkay I will have to ask my brother as he is the programmer. We have several hundred objects, scripts, etc so I have no idea how to simplify the project without everything breaking and not working anyway. I will update in this post once I speak with him about it, thank you.
     
  24. agentmonday

    agentmonday Guest

    Hi all. I am absolutely devastated to find that nothing works properly after the latest update - moving from room to room is completed broken and there invisible solids in various rooms. I feel like crying. 2 years into a project and this happens. Hope you get another update out very soon that fixes this issue.
     
    Kezarus likes this.
  25. Kezarus

    Kezarus Member

    Joined:
    Jan 14, 2018
    Posts:
    166
    Man, I love Game Maker, been using it since 2006, but that kind of thing scares me to the bone... I still use GM 1.4 because of that.

    But don't cry agentmonday, as Douglas Adams described on The Hitchhiker's Guide, Don't Panic. Yoyo will soon correct that and, if you don't want to wait, maybe try to reverse the update?
     
    Last edited: Apr 24, 2018
    Joe Ellis likes this.
  26. agentmonday

    agentmonday Guest




    Thanks Kezarus. I have forwarded a report so I can hopefully roll back the IDE because I have tried all the runtimes and they don't fix anything. The latest IDE was apparently mandatory. Yup, trying no to cry because that's two years of work there. Game Maker itself has been great to use, but I have to say that it's becoming a bit of a mess the way things are being handled. Thanks for the kind words.
     
    Kezarus likes this.
  27. rwkay

    rwkay YoYo Games Staff YYG Staff

    Joined:
    Apr 12, 2016
    Posts:
    1,049
    Please remember that you can use other runtimes with the new IDE so the mandatory upgrade does not force you to stay on the matching runtime - this is why we separated them.

    We found a bug with collisions and persistent rooms (especially a mix of persistent and non-persistent rooms) where the collision tree was not being updated on entry to the new room, we have fixed this internally and it will be released in the future.

    But please file a bug so we can check that your issue is fixed by this and is not some other issue that has not been discovered yet.

    Russell
     
    Joe Ellis, agentmonday and Kezarus like this.
  28. Ruimm

    Ruimm Member

    Joined:
    Nov 4, 2016
    Posts:
    127
    If you're targeting iOS then using runtime 2.1.3.x will not compile due to missing keys in the options file. :(
     
    agentmonday likes this.
  29. agentmonday

    agentmonday Guest

    Unfortunately, I have tried all runtime and the problem persists. I have even built a quick little game with a few rooms, and yet the problems persist. I have done a bug report as you suggest and will wait for a future IdE to fix these problems. Not much else I can do. It was heartbreaking to get these issues.
     
  30. gnysek

    gnysek Member

    Joined:
    Jun 20, 2016
    Posts:
    1,305
    If the problem exists on 2.1.3.189, then it's your code which broke something, as 2.1.3.189 didn't changed since release in December :)
     
    Menik likes this.
  31. Nathan

    Nathan Member

    Joined:
    Jan 19, 2017
    Posts:
    53
    @rwkay Just to follow up, we have created a stripped down project file and submitted a bug report today. It shows that any of our content switching objects outside of the initial activated area do not work (collide) once they get activated. Thanks, I look forward to hearing a solution.
     
    agentmonday likes this.
  32. TheSpydog

    TheSpydog Member

    Joined:
    Jun 20, 2016
    Posts:
    67
    @agentmonday This is just a guess, but have you checked your sprite origins? Are they where they're supposed to be? I've seen a few people have some strange issues because updating their IDE somehow moved their sprite origins, causing the graphics and collisions to be out of sync. This appears to be separate from the runtime collision problems that have been widely reported.
     
    Kezarus likes this.
  33. agentmonday

    agentmonday Guest

    Thanks TheSpydog for the suggestion. Yes, I have tried this and a lot of other things. Yet, the issues persist. I have even made a simple little demo where you move from room to room following Shaun Spaldings code to see if that works but it does not.
     
  34. agentmonday

    agentmonday Guest

    I have made something similar and put in Shaun Spalding's code (to make sure it isn't just MY code) and the issue persists. Not much else I can do.
     
  35. SpaceNerd

    SpaceNerd Member

    Joined:
    Aug 12, 2018
    Posts:
    2
    Soooooooooooo... is my code broken or did no update fix this bug?
     
  36. Menik

    Menik Member

    Joined:
    Feb 19, 2018
    Posts:
    16
    Honestly, I appreciate how responsive the GM Team is but as I look over the community I really feel like we're all beta testers with stumped projects. I pretty much just hop from an bug, to a design flaw, to another bug, and I'm trying to maintain patience.

    Runtime 2.1.3.189 is no longer available to revert to (if that is the last runtime without this bug), unless there is another way to access it how can I move forward from here? I have a rare window to get a lot of work done on this project.

    Thanks.
     
  37. Toque

    Toque Member

    Joined:
    May 25, 2017
    Posts:
    1,074
    This is why I’m never in a hurry to update and think mandatory updates are crazy. Especially if you can’t revert back to old versions.......
     
  38. Menik

    Menik Member

    Joined:
    Feb 19, 2018
    Posts:
    16
    Touche. I sit here a fool thinking GM Studios 2 would ever be a safe space to update. Should've took what I learned from Windows 10. However, not being able to revert to any previous version sounds a bit unreasonable. Isn't this why the runtimes system exists?
     
  39. Dog Slobber

    Dog Slobber Member

    Joined:
    May 20, 2017
    Posts:
    283
    Except that version was a forced upgrade. People had no choice to upgrade and then no ability to revert back to a pre-2.14 runtime.
     
  40. Joe Ellis

    Joe Ellis Member

    Joined:
    Aug 30, 2016
    Posts:
    970
    HAHA this is so typical of yoyo games, how could they release an update with a bug that breaks all games and they know nothing about it?
    because... probably several reasons that I would probably get kicked off for saying, but on a positive note, they will fix this cus its in their interest
     
    gnysek likes this.
  41. Toque

    Toque Member

    Joined:
    May 25, 2017
    Posts:
    1,074
    I’m learning GML so there is times something doesn’t work and you wonder “is it my code or a bug?”

    It’s usually code. I wouldn’t know the difference anyways.

    It’s impossible to fully test an update with all scenarios. There will be bugs.
     
    Last edited: Aug 19, 2018

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice