Sonic and Sega Retro Message Board: StreakThunderstorm - Viewing Profile - Sonic and Sega Retro Message Board

Well, its not false. Blueprints are commonly used for rapid prototyping because they are much easier and faster to set up than coding and compiling.

Precisely. They said you can make an entire game front to back all in blueprint.

I haven't updated the build. I fixed the teleport into walls at lower framerates.

As far as blueprints go:

I've been actively engaged in the epic community. I watch the twitch streams and I partake on the forum. Epic has clearly stated themselves that there is little to no difference in what blueprints can do in terms of in-game stuff like movement and collision. You can make an entire game in blueprints completely. When you start getting into advanced things is when you may need to code it yourself if its not already part of the engine. Although Sonic seems to be hard to get a grasp of, its really damn simple in terms of what is needed to actually make his movement work. Any issues with the movement itself is most likely due to my own errors and not knowing how to set things up. For example, I made a really big difference when I moved the movement and collision system into a loop. I didn't know the proper way to make epic's loops work but once I finally understood, I boosted the framerate on my own machine from 60 - ~85 with less teleporting into walls.

I will be uploading and releasing Sonic Unreal Worlds alpha 0.8 very soon.



Edit:

https://github.com/S...c-Unreal-Worlds

For those of you who don't use github, just click download as zip on the lower right hand corner.

There's nothing C++ can do that you can't do with Blueprints in terms of this engine.

Anyways, I've worked on the collision and I'm happy to say I have successfully made it more stable. I'll be releasing the change soon once I upgrade it to UE4 4.7.2

Give it a test run. See how it feels to you. I'm following the physics closely from Sonic Worlds from MMF2.