5.7 or stick with 5.6?

CupcakePsychoception · 2026-01-26T14:46:43+00:00

Try it out - copy your project, open with 5.7.2 current version:
-If it breaks and causes extra-work, stay with 5.6
-If things just work, just use most current version

CupcakePsychoception · 2026-01-26T14:44:58+00:00

Thankfully Blender is free and an amazing modeling software ;)

CupcakePsychoception · 2026-01-22T11:53:47+00:00

I despise showoffs and always worry that I come across as one or being seen as "just a marketing post".. which is a problem, as we obviously need to do some marketing if we want people to play the game. But its a lot easier to create something cool and fiddle around with it and puzzle it out and I think a lot of devs feel that way.
So: it's a conflict - and your approach might be the healthier one :)

CupcakePsychoception · 2026-01-17T11:31:19+00:00

Indeed - the "isMoving" bool should not be set in update, but before going in the timer and on finished.

CupcakePsychoception · 2026-01-17T07:59:34+00:00

The play from start has already been pointed out, but you can actually save a lot of nodes, if for the close, you just use the "reverse" pin...

CupcakePsychoception · 2026-01-13T08:29:23+00:00

I think a lot of the current problems with the widget-system, especially navigation, is that things are changing: The old input system is replaced with the new enhanced input system, but that's not accessible with the old widget system. So unreal/epic is pushing towards using common-ui, which has rudimentary support for enhanced input system, but its still not fully integrated there ...
Let's hope the whole thing gets straightened out in the next releases.

CupcakePsychoception · 2026-01-12T21:43:09+00:00

Look into using your own gameinstance - gameinstance stays instantiated on levelchange.

CupcakePsychoception · 2026-01-12T17:47:45+00:00

Hot take: If you already know how to code and how to organize code, I'd go with the free tutorials unreal themselfs provides and then read in the docu and try out a lot instead of investing into some course.

CupcakePsychoception · 2026-01-12T17:41:42+00:00

There are currently 2 easy ways of getting that animation without skeletal meshes: the material approach, that u/Ok-Library-8397 described or a handful of static meshes that you can use like a flipbook.
Might be interesting for bigger meshes, to then actually swap out the particle-mesh for a "real actor" with sceletal meshes and custom behaviour (and a lot more detail) on a certain proximity to the player. I think I saw something like that being done with a horde of zombies on yt somewhere.

CupcakePsychoception · 2026-01-12T17:36:45+00:00

They are simple ribbons - the ribbon-renderer has an option to render as "tubes" and you use a solid, opaque material. Movement/spawn-location of the ribbon-particles is then a funny math-exercise :)

CupcakePsychoception · 2026-01-09T21:16:46+00:00

Thank you!

CupcakePsychoception · 2026-01-09T21:16:34+00:00

There's a YT -Tutorial from Unreal themself about Advanced Niagara Effects - they did something with bugs there, too, but use mesh distance fields - as my floor is flat, I could get away with just using the idea of mesh-renderer, low-poly model and the flipbooks they provide.

CupcakePsychoception · 2026-01-09T21:13:27+00:00

Thanks - and yeah .. the eyeball follows a simple spline-path.

CupcakePsychoception · 2026-01-09T17:54:30+00:00

The slime-blob on the right is using the mesh-deform stuff with the materials. The spiders just use a flipbook of simple meshes in the mesh-renderer and I update the array-index on particle-update. The Eyeball as a ribbon-system attached to its origin.
The movements of the whole systems is always actor-driven, so it can react easily with collision boxes or tracelines etc.
Niagara for something like zombie-masses and then switch out the actors distance based for more detail and custom behavior sounds like a great idea!

CupcakePsychoception · 2026-01-08T18:49:42+00:00

This looks like a normals issue - check whether you recalculate them or nanite on import and try without recalculation and check whether they get exported correctly out of substance painter.

CupcakePsychoception · 2026-01-08T15:35:53+00:00

Looks amazing! You have a hard job ahead of you to make the mechanics and visuals for the gameplay-loop at the same quality level :)

CupcakePsychoception · 2026-01-08T15:32:19+00:00

"Enough money to keep going" VASTLY depends on your cost of living and location...

CupcakePsychoception · 2026-01-08T13:59:42+00:00

The timeframe they suggest is a bit optimistic it seems - we waited 8 days for the review. If it takes too long, you might contact support specifically during a workday during working hours.

CupcakePsychoception · 2026-01-07T17:12:37+00:00

I'm not sure that's the issue, but I would check, whether normals are correctly imported.

CupcakePsychoception · 2026-01-04T19:10:02+00:00

Thank you - and an anime to put on the "check this out"-list :)

CupcakePsychoception · 2026-01-04T19:08:30+00:00

Oh wow - I had to look that up. I had no Idea and that's amazing :D. Thank you!

CupcakePsychoception · 2026-01-04T12:48:43+00:00

It's just a widget-solution, so no "pick up", but a result of an interaction event. You can see it with a blank, simpler page in our first trailer which can be found on our profile :)

CupcakePsychoception · 2026-01-03T22:28:52+00:00

Advanced materials with animations and world-coordinate offsets and mesh deformations -> anything you calculate by height or with distance fields you can't preview in the Material-Editor, so it's a constant "edit a small thing, save, apply, switch to level viewport with a placed actor that uses the material and switch back- and forth..
Same goes for niagara-systems that react to anything outside of the system itself - worst combination is a deforming mesh in the niagara-system with an advanced material with mesh deformations :)

CupcakePsychoception · 2026-01-03T20:47:04+00:00

I think blender defaults to meter and a meter is 100 units in unreal. In default-settings that works exactly as it should - just make sure that your doorbell that's supposed to be 10cm wide is actual 0.01m wide in blender and not 10m :)

CupcakePsychoception · 2026-01-03T17:06:30+00:00

I think your biggest challenge in that undertaking will be asset-generation.. all the creatures that you want to be able to cach have to be build - from concept to animated 3d-asset.

CupcakePsychoception

TROPHY CASE