You should probably use trails for this. Beams are meant more for static A-B rays.
Unless someone wants a “laser” of specific length, since Trail effect doesn’t have MaxLength property (yet).
Just finished my work for the Cabin Challenge that has been going on around Twitter, possibly one of the best events off the Roblox site that I have enjoyed doing!
The game may be played here:
mmm, got that new shop feel
https://i.gyazo.com/b0a093047fc61b3bfdaedfd6d3a43438.mp4
New shop! and each tank has an icon now…
each… tank… of all 95… gets an icon…
ah nostalgia…
please tell me you’ll add that system where, the one time you decide to load you’re super amazing ammo it decides to miss the entire volley.
Rewriting the round system for Downhill Dash.
Got bored and decided to continue on an old build I made ages ago. I will never finish this thing most likely, but hey, who cares? hoh hoh hoh
:^)
It’s possible to calculate one by using d = st
Welcome to Roblox, where we create amazing creations by (ab)using the wrong things.
Made a timer to show when prisoners can be unlocked, probably gonna add another one to show when they can be locked up again
Elaborate please
Figured out how to render idle & render with distribution!
Managed to make my renderer work magnitudes faster (doesn’t scale perfectly, but around 8x-9x faster from my preliminary testing). It sends bits of the image to be rendered to each client. Clients send everything to server. Once the entire thing is rendered all clients get a copy of the render. Clients are again given chunks to render, except this time they do Post-Processing.
Results are pretty cool.
Old render system: 168.4 seconds
New render system: 19.3 seconds
Here’s the picture rendered with AA on the new render system. It’s rendering 4x the pixels yet still finishes in under 100 seconds - over a minute sooner than the old render system.
Next is reflections, transparency, neon, textures, & bump maps! I’m finally able to move on now that I’ve helped reduce my performance bottleneck a bit.
You should make a blog site & post your updates on there.
I’d love to see a more in-depth look on how you do some of this stuff.
There was a thread involving private modules, and it got me thinking that I could figure out the contents of the module by replacing its environment with dummy values that report when they’re being accessed. I’ve upload the result of my efforts here:
The first iteration is Dummy.lua
. This replaces an environment with a dummy userdata that has all of its metamethods defined. When the dummy is accessed, such as by indexing or being called, it returns more dummies, allowing it to stand in for any instance, table, or function. It worked surprising well for my purposes.
The second iteration is the Proxy module. This wraps around a function environment, creating a bridge between the function and the original environment. Once the bridge is in place, it can be used to report accesses, spoof values, or deny access entirely. The Proxy.rbxlx
file shows it in action.
All of this was written in a day, so it’s not very refined, but anyone is free to have fun with it.
About your Hotel Rooms favorite feature:
In the favorites tab, when you click a star to remove a favorite from the list, it shouldn’t disappear immediately. They may have accidentally clicked star. I believe it might be better to let the item persist until you change tabs or maybe reload the entire UI (in this case, open and close the hotel room window.)
If they unfavorite from the start page, it should, of course, remove it from the favorites immediately (and in this new case, reload the list to remove rooms not favorited.)
My two cents you might find worth using.
My heart, what is this feeling…such joy
That’s genius. Bravo