Scraps 0.2.5

Having 50+ people play scraps over the weekend showed up a few issues. The latest builder release (0.2.5) tries to address these. I also silently put up a 0.2.4 release about a week ago which contained some other fixes.

The things I noticed were:

1. A lot of people try to click and drag parts while holding the mouse button instead of clicking and then dragging. I knew this happened but I didn’t realise that so many people would try it this way first – probably a third. It was a bit ugly because not only did it not pick up the part but it dragged the tooltip along which is a bit confusing.

So ideally I’d allow either method, but that’d take a few code changes and be slightly hacky since the GUI normally only detects button up events rather than button down. I’ve fixed the tooltip issue so at least it’s more obvious that your drag didn’t work. I’ve also pushed the tooltip updates to my Asset Store tooltips so now you can auto-hide tooltips based on distance moved.

2. The random freezing of physics happens quite a lot. Another one that was known but I didn’t realise how often it happened. Sometimes the physics froze on the build screen for no good reason, with Freeze Physics still unticked. I never found a reliable way to reproduce this but it’s probably fixed now. I found some dodgy code that was most likely causing it and fixed it up.

3. On two occasions someone placed a weapon and it’d spin around forever, including into areas it shouldn’t be able to move. This turned out to only happen when a weapon’s min horizontal angle was reduced to exactly 0 degrees. In the code it’d come out as 360, which of course is technically correct but since it’s represented internally as 0, the weapon would never quite get there causing it to spin around forever.

Altogether, the changes since the last posted update are:

2013-10 – 0.2.5
– Just a few minor tweaks to things
Bug Fixes:
– [Build screen] Hopefully fixed the occasional random freezing of physics
– [Build screen] Stopped tooltips staying up when people drag things instead of clicking them
– Fixed some more weapon available range calc stuff
– [Game] Ever had a weapon just kinda randomly spin around instead of aiming where it should? Fixed that too

2013-09 – 0.2.4
– Fixed up 3D sound settings
Bug Fixes:
– [Build screen] Fixed hovering over weapons affecting the results of the cockpit visibility test
– Reinstated the two mysteriously missing snap points on large engine
– [Build screen]Fixed build screen lighting
– [Game] Fixed the small blip of audio that happened when pausing, minimising and then restoring
– [Build screen] Fixed weapon range display showing up through other parts (the code for this was really dumb – what was I thinking?)
– Improved weapon range calculations so weapons shouldn’t slightly clip through stuff anymore (maybe)

Bookmark the permalink. Both comments and trackbacks are currently closed.


  1. Scott
    Posted October 4, 2013 at 8:36 pm | Permalink

    1.2.5 was the version of Minecraft I liked the most
    (too tired to form intelligent comment for now)

    • Scott
      Posted October 4, 2013 at 8:40 pm | Permalink

      I think I need to get some sleep, it’s 3:30 AM and I read 0.2.5 as 1.2.5 and my brain is shutting down

      No, wait, the email clearly states 1.2.5 (image showing the email)
      I’m confused now

      • bill
        Posted October 4, 2013 at 8:48 pm | Permalink

        Oh yeah, you’re not crazy, I messed it up. But then I fixed it.

  2. Andrey ScorpyX
    Posted October 11, 2013 at 11:10 pm | Permalink

    Ha! I remember when in my FPS game
    weapon infinitely rotated because of the same problem
    Then I remembered Unity3d tutorial which advised
    “better perform all turns in Quaternions and then transferred it to Eulers”
    and.. it solve my probleme because Quaternions have 4 axis
    and just can do this trick like Eulers with (0 -> 360)

    • Andrey ScorpyX
      Posted October 11, 2013 at 11:12 pm | Permalink

      oops – i mean
      “..Quaternions can’T do this trick..”

    • bill
      Posted October 12, 2013 at 9:57 am | Permalink

      Yeah, the weapon range limits are defined on an X and Y axis (e.g. -20 degrees to 20 degrees) so I temporarily convert to Euler for that, which is where dumb stuff like this can happen.