There are a couple of issues with the latest update. -Physics are still broken. When a spinner hits something with a significant amount of force, it will teleport around. This happens during matches as well.
-Brushless motors are laggy while being placed. Most of the game runs perfectly smooth, but when a brushless motor is first being placed, it becomes very laggy. After the motor has been placed the game handles fine.
-Flippers are broken and cannot fire. All pneumatic pistons are unable to be controlled, making all flippers completely unusable.
-Old F30-400 motors have been moved downward (this was addressed in the last update and can be fixed easily, so it isn't much of a problem)
-Motors have very poor torque. An E-Tek powered horizontal barely pushes the opponent at all, E-Tek vertical spinners that could once self-right from their own power can't any more, and all lifters, grabbers, and crushers that used motors with rotation limits have been rendered completely useless. There is no gearing that can fix some of the lifters I've made, or allow any of my spinners to have significant power.
-A small diameter spinner that weighs more than a large diameter spinner is better. As you can see in the videos, a smaller spinner that weighs more will spin up much faster and lose less power per hit than a larger diameter spinner with less mass. The large bar spinner takes much longer to spin up and loses all momentum when it hits the box and throws itself, but the heavier, smaller spinner can consistently throw a box into the ceiling and retain its speed.
These problems aside, this game is shaping up to be amazing and I can't wait to see what comes next.
Would there be an AI pack released for these Battlebots (in RR2)?
My intent is to have AI programming be part of the in-game experience. You can go with the default AI, or modify the code using the in-game editor.
Please note that once we get the physics, damage, and weapon systems worked out over the next few months, I intend to go back and rewrite AI with all of the new inputs.
I expect that lots of people will be posting AI code here on GTM that people will be able to copy-paste into the game for their robots.
But, does that mean that all these bots from 'Battlebots' I can find and if so, what codes do they need?
Adding on to what Min and Code were saying, most spinners have drastically increased in power. [ Quoting of attachment images from other messages is not allowed ] My lightweight breaks the scales with how much energy it holds [ Quoting of attachment images from other messages is not allowed ]
I mean, you are using a HW brushless motor on a lw
Will give the new build a go now that im awake
That’s true, but it was working at realistic speeds and energy in the February 16th build.
A problem I’ve run into while building is that the 3-inch wheels have almost no health (0.05 hp). This makes it extremely difficult to make low or smaller robots, since the wheels come off at the slightest touch. The 4-inch wheels have hundreds of times more health than the 3-inch and can withstand a much more realistic amount of hits, so I’m not sure if this lack of HP is intentional or not.
If Kupa and Wham aren't in a position where they're comfortable enough to release the AMT, then it clearly isn't in a functional enough state to make high quality arenas in. It's completely reasonable to want the tool, but it's going to be released no matter what and I'm sure you can muster the patience to wait. If you want to make arenas so badly, just use blender for now, as anything you make in there can easily be imported into the AMT later on. Pestering Kupa to release the tool is not going to make it come any faster, and there is no point in releasing it when it isn't done. Just be patient.
Ugh. It kills me to say this, but there is a way to reset the motors back to a similar configuration we had before, hiding them in the process. It won’t be perfect though. Alignment will be off. Attachment points won’t be in the exact same spots.
But there is a way to make it happen. I just hate it because it will become a legacy problem that will never go away.
Is it worth doing if the motors don’t go exactly back to the way they were before?
I agree with Kix, even if the motors are slightly off, we could easily readjust them and it would be far better than what they are like now. Although it's a shame that there's no perfect way to add the new motors and not mess up legacy robots, it seems like resetting the old motors and hiding them is best option there is.
One solution to this problem that I can think of is to set the old 30-400s back to the old attachment points. This would fix the problem where old robots have broken motors. The new 30-400s could still have the new attachment points, which would fix the broken robots we have and still keep the new motor attachment points in the game.
Adding onto what Cyar was talking about, I built SMEEEEEEE in RR2, but made the wedge out of a scaled up chassis. For some reason, every robot it fights seems to take amplified damage and falls apart incredibly easy, even though SMEEEEEEE is just a wedge.
I have finally completed a functioning multibot AI. It's still in a pretty basic form, but it works. Keep in mind this is not the full AI, but the code that you have to paste into another AI (Default AI, Hammer AI) to make it work. This is because it can function with any bot type.
It works with a 3-way multibot as well, which I'll release if anyone wants it. If you have any questions, just ask me on the RA2 discord since nobody is ever active on GTM anymore.
The buggy spinners started midway through the fight, when nobody was even in the pit. I could still drive the robot fine. We got this to happen a second time, but nothing after that. We don’t have a consistent method of triggering the glitch. P2 was the main source of the problem. At some point the bar started teleporting off of the axle and was able to clip through the floor and other robots. The same thing happened to P1 later, but not quite to the same extent.
Would you mind sending the .RR2Bot files for P2 and P3? I want to see if there is something weird going on...
Here's the bot file for Infrared. I'm not sure what physics stats we were using though, as this was on Kix's computer.
Ok so we stumbled upon this. Something is wrong with collisions, also the fact that physics is unoptimised, casuing the whole match to run at low fps at 500tick (my cpu usage was at maybe 30%)
I love it! This is so great!
I'm probably suffering from "Developer Eyes Syndrome" and can't see everything that you guys see, but I see 2 things here that need fixing:
1. The spinners should have come to a stop. Either or that or they should have broken off. For whatever reason that didn't happen and the now-invisible blur cylinders were still spinning and working their magic.
2. The lag is due to the fact that there is a literal pile of colliders on top of each other, all interacting. The only way to minimize this is to reduce the number of interacting colliders.
Have you guys found a reliable way to reproduce #1? It looks like P2 and P3's spinners didn't come to a stop, even though they were out of the arena. Is this correct? Were the weapons still turned on for P2 and P3?
I think I have found and fixed the "Pit Blender" problem. It turns out that when a robot is disabled, it would lose player input and maintain the existing state of the control signals. Super scary when this happens in a real-life competition -- you have to wait until the batteries die on the robot.
In any case, this will be fixed in the next release.
The buggy spinners started midway through the fight, when nobody was even in the pit. I could still drive the robot fine. We got this to happen a second time, but nothing after that. We don’t have a consistent method of triggering the glitch. P2 was the main source of the problem. At some point the bar started teleporting off of the axle and was able to clip through the floor and other robots. The same thing happened to P1 later, but not quite to the same extent.
Ok so we stumbled upon this. Something is wrong with collisions, also the fact that physics is unoptimised, casuing the whole match to run at low fps at 500tick (my cpu usage was at maybe 30%)
Ah, yes. My overhead bar decided to fly around and destroy everything while we were fighting it. It looked like it stopped being able to collide but could still do damage.
Show Posts
