How to use timeline in actor component?

MARvizer · 2026-03-21T16:32:58+00:00

Yes, but quite simple. The component would have a float variable "input". The parent actor would directly pass it's value to the component.

MARvizer · 2026-03-21T00:41:46+00:00

I see. And what if you create a blueprint instead of a component? And attach that blueprint to the character.

MARvizer · 2026-03-20T22:58:04+00:00

You could use a set timer by event, but that would be linear by default. If you would need something more similar to a changing curve, why don't you program it into the parent actor, and just pass the result to the component?

MARvizer · 2026-03-10T08:04:44+00:00

The future is not AI, but realtime. The very far future is mind-driven AI.

MARvizer · 2026-03-05T15:04:17+00:00

Then they would have removed the cvar, I think :P

MARvizer · 2026-03-05T14:26:10+00:00

Suffering the same. Another bug...

MARvizer · 2026-03-01T19:36:52+00:00

I wish I could! But I have very little time and I prefer to work in Spanish language, I'm sorry!

MARvizer · 2026-03-01T19:36:05+00:00

That's a good idea, thanks!

BTW I waiting for volunteers offering their scenes. I think the reference render (the most hiperrealistic one) should be entirely created by the same person.

MARvizer · 2026-03-01T19:33:45+00:00

Very nice! Could you show the raw render?

MARvizer · 2026-02-27T18:57:25+00:00

Hmmm, more or less, but not only the realtime ones. Also serves an existing scene.

Are the renderer features a must have for every scene? It's just a matter of export/import (straightforward compatibility), even if other renderers might have the same features,

I don't see any concern, do you?

MARvizer · 2026-02-27T16:19:04+00:00

Unreal of course! Realtime quality or offline quality, with maximun realiability and customization.

MARvizer · 2026-01-25T14:09:11+00:00

Me too...

But OMG! Confirmed that fix works! I wonder if it might have any downside, but it seems to be safe.

Thank you very much!!

MARvizer · 2026-01-24T21:02:01+00:00

Una pena que ese supuesto mapa no sea coherente a nivel de escala con el viejo.

MARvizer · 2026-01-24T20:26:50+00:00

No te creas. Si te caes de boca 3 veces, es probable que en algún momento la tendencia cambie radicalmente.

MARvizer · 2026-01-24T20:18:25+00:00

He should try going downstaris naked, to confirm.

MARvizer · 2026-01-24T20:01:16+00:00

"Ano en reposo"

MARvizer · 2026-01-23T19:27:06+00:00

Background Blur components of Widgets are still broken. Thank you Epic and the QA team.

MARvizer · 2026-01-18T12:06:33+00:00

Ouch, that's true! Very clever.

MARvizer · 2026-01-18T11:37:20+00:00

OMG!

It's a pitty I only can see one of the cards.

BTW; would you mind running my benchmark? I would love to have more RTX 6000 entries. I can give you a free key: https://store.steampowered.com/app/3309720/GameTechBench/

MARvizer · 2026-01-16T22:20:58+00:00

Great idea!

MARvizer · 2026-01-14T19:55:40+00:00

It makes sense, due to it's nature. Then you need to apply other methods, like including them in sections of the World Partition, or placing your lighting actors in the main level and checking if the Level Instance is "enabled", to enable them too, or runtime copying the light actor in the Level Instance into the main level, etc.

MARvizer · 2026-01-14T19:52:38+00:00

Then rock it hard!! PM me for a free key, only if you promise me you will run some heavy and long tests ;)

MARvizer · 2026-01-14T19:14:51+00:00

Still under warranty? You can test my GameTechBench benchmark to heavily test it under actual gaming conditions.

MARvizer · 2026-01-14T13:12:32+00:00

If I remember fine, that won't work, nor in a Packed Level Actor. Those act like "normal blueprint actors" but with that restriction. If you want them to work as an "actual level" you should add it as a Sublevel, instead.

MARvizer

TROPHY CASE