Hey all! We’re gonna start posting shipnotes here so you can leave comments and feedback directly each week. Thanks for reading, and without further ado, here’s our update this week:
TLDR
We’ve fully moved to the upgraded bean and added a few changes and options to make the experience closer to that of the classic bean.
Drivable vehicles are now available in Rooms 2!
Custom locomotion updates, new chips, and more!
Rooms 2
Start your engines, drivable vehicles are now available in Rooms 2! Find the Rally Buggy, Classic Coupe, Wolf Ride, and Trusty Pickup Truck in the MakerPen palette.
The new Particle VFX Constant and Play Particle VFX At Position nodes allow you to play a particle effect using Circuits! You can even create your own custom Particle VFX in Rec Room Studio and then use those effects with Particle VFX Constant.
Added a set of chips to attach objects to player avatars. This enables costume functionality in Rooms 2!
Added missing chip descriptions for Rooms 2 chips.
Share Camera polaroids can be printed in Rooms 2 rooms.
Audio values can now be set for object properties directly from the config panel.
Avatars
Beans now locomote smoother (they’re less bouncy).
The bean avatar head has been moved forward by 4cm to replicate the old bean look.
Idles stand more up-straight. The hip/body moves around a bit rather than being “land-locked” producing less leaning/bending.
Hands are animating again when idle (this goes for full body as well!)
Suggested items in the Avatar Customization menu now include popular items made by our community.
Added a fix for the mouthbrows!
Added a fix for eye gleam on bean avatars.
Circuits
Circuits Messages have been delivered! They’re an alternative to Events that are much easier to reuse across rooms and inventions. They’re as flexible as the “Generic Room” event is, but with a LOT less boilerplate circuitry needed to filter actions and fetch parameters. Let us know what you think of them in the Discord or Creator Forum!
Custom Locomotion updates:
Input events are now available in the global scope, e.g. On Locomotion Sprint Button Input.
Added local player variants of locomotion state events, e.g. On Local Player Jumped.
Added the “Rec Room Object Try Get Property” chip to beta. This chip combines Rec Room Object Has Property and Rec Room Object Get Property - it outputs both a bool for whether or not the property exists on the given object and the value of the property itself. If the property does not exist, it outputs a default value set by one of the chip’s inputs.
Added the “Find and avoid Edge” and “Find and avoid Obstacle” chips. These will have some more detail in the comments on the creator forum if you wanna know more about how to use them!
Fixed a bug that could cause the ‘Audio Player Set Time Stamp’ chip to break when used without an active audio clip.
General Improvements & Bug Fixes
The Maker Pen now only blocks custom locomotion when you’re flying, making it easier to mix creation and play!
Fixed a bug where disabling jump input while flying would leave you trapped in the air.
Dropping the maker pen will now make you stop flying so you can get right back into the action.
Weapons with configurable object damage now have a default object damage value equivalent to their default player torso damage value.
And here’s some extra notes and instructions for the “Find and avoid obstacle” and “Find and avoid edge” chips we released this week:
Find and avoid Obstacle Chip
Detects an Object in the Source Direction up to the Max Distance (m)
The dimensions of the Detection Cast is (W x H x D), starting from the source.
If the source is an object, it will use the Object’s collider Center, otherwise the Vector3 source Position.
If the Source Object is a Rec Room Object, the object will be filtered out from collision detection
The Jump Height is how high the source can jump to go over obstacles
The hover height is how high the source hovers above the ground
The Rotation will determine the Final Direction if an obstacle is found [-90: turn left, 90: turn right] the rotation is relative to the object normal unless From Obstacle is false
Optimized Direction will show an alternate direction if one side of the source doesn’t find an object
Find and avoid Edge chip
Detects an Edge in the Source Direction up to the Max Distance (m)
The dimensions of the Detection Cast is (W x H x D), starting from the source.
If the source is an object, it will use the Object’s collider Center, otherwise the Vector3 source Position.
The Drop Height is how far the source can drop from an edge
The hover height is how high the source hovers above the ground.
The Rotation will determine the Final Direction if an obstacle is found [-90: turn left, 90: turn right] the rotation is relative to the edge normal unless From Edge is false
Optimized Direction will show an alternate direction if one side of the source doesn’t have an edge
Why remove Classic Bean entirely? You guys should’ve kept the option to use Classic Bean, most of the player base used Classic bean over new bean and full body.
Js bring back the old bean. It’s better and is way easier to play on. You should still keep the option to switched but pls js bring it back. it bugs my game way to much
Hey guys!
I love what this update added for creators, but lag has recently been out of hand. I’m sure staff are already aware internally of the glitch with the favorite system that allows players to lag others.
However, the lag I’m experiencing is tied to the creation UX. Specifically the makerpen UI is lagging devices significantly on changing menus, searching things, and other. It feels like a chore to even navigate makerpen menus right now.
I personally will halt working on my creations until this is fixed, there is no way I can just work on things when the game runs at 15 frames per second.
Classic Bean was classic, and I wish the RR development team would’ve waited to remove the classic bean when the new bean body is fully refined.
RR is buggier than ever and the new beans are not very good. Like clothing items not fitting or costumes clipping. As well as the animation. Or the hunchback. Please bring old bean bodies back until new bean body is actually ready.
When “personas” get added i’ll make the switch but, right now RR is too buggy to run. Old bean bodies would work until its fully ready.
(For those who don’t know, “personas” will be custom animations used with the new bean body, so you are able to replicate the old bean perfectly.) Confirmed by a developer
The change of making flying stop when dropping the makerpen is really cumbersome for VR players as dropping and picking the makerpen back up in quick succession is the fastest way for someone to stop editing or deselect everything and forcing flying to stop when doing so makes creating while flying an annoyance. making this a toggleable setting would be the best of both worlds.
Why remove classic bean? I personally haven’t met a single player in game who wanted the removal, it’s clear nobody asked for the new bean avatars, so why remove it?
why can’t we just keep the old bean the new one isn’t good at all no one asked for full body or the new bean we were all happy with the original bean bring it back and have more people again playing
I’m not sure if we’re aware of a favorite system bug, can you detail what this is or share a video?
For your Maker Pen UI issue - you experience this even in a room alone with nothing in it? Or does it get worse as you have more objects or people in the room? If so it may not be a UI issue. It may be an issue of loading more shapes or info for the Maker Pen as you open up the UI. A video of what you’re experiencing here, in a new / blank room, would be interesting to see if its a pure UI issue.
what is ‘not very good’ about the new beans? please be specific. ‘its not good’ is not helpful feedback for us to give to engineers who are interested in specifics here.
