Got it, is a deprecated method since Unreal 4.12. Ok, we’re rolling again
My word, the same video re-recorded 4 times due to a chain of errors. It won’t beat me, it just means I work later until it’s done.
OK, two new videos and 10 new quiz questions will be with you in the next 20 minutes
This is flagged as correct answer (last one). But it has a typo with the closing bracket after Location.
Bad copy/paste errors!
GetWorld()->SpawnActor<AProjectile>(
ProjectileBlueprint,
Location),
Rotation)
);
Grr, Udemy keep doing this to our quizzes! It is some post-processing they do after the event.
I have fixed this and strongly reported the bug to them, thanks for pointing it out.
Quiz feedback.
[spoiler]
FMath::Clamp(RelativeSpeed, -1.0, +1.0);
This will fail because the system doesn’t know whether to interpret +/-1 as float or double.
Is kind of misleading as it will be interperated as a double and then you’ll get a mismatch of types (float, double, double). Then a note saying to make that version compile you would need to do FMath::Clamp(RelativeSpeed, -1.0f, 1.0f);
How many times is it OK to write very similar code before thinking if there’s a better way to generalise?
Should probably be re-worded to say what’s the maximum as 1 is technically correct with that wording.[/spoiler]
All fixed, thanks
“Adding a Quit Button” including self-collision fixes coming soon.
Just noticed this on the Quiz answers for Clamp
[spoiler]"Arguably this is dangerous because the rounding from float to int is happening implicitly."
Rounding wouldn’t happen, conversion from float to int would truncate.
As well as the reasoning of “will be interpreted as floats.” for the first two answers gives the indication that the one for templated int is the only one with implicit conversion. Yet all of the examples you gave have them, int -> float or double -> float; As the F/f suffix denotes a float and without it you define a double.[/spoiler]
You’re so helpful Dan.
Fixed Thanks again Dan
Not sure if this was supposed to be part of the challenge or if you were trying to get people to check against isHovered but OnClicked actually has the behaviour you described.
You passed the extra points challenge
We’re rolling, Physics Materials just shipped. Fly-by-wire control systems next.
3 new videos live yesterday, hoping for the same today
Thank you for mentioning my HoverTank project post in the end of lesson 147. Very honored!
@ben, on lecture 149 the challenge resource links are not added to the course list yet.
Thank you, I’ll get to those resources, I appreciate it.
I think I care too much sometimes. I spent the entire day refactoring the way we work with components because I was uncomfortable with the prototype even though it works (see the refactor branch on GitHub if you like)
I’ll get to recording tomorrow once the implications have sunk in, and it’s late here now.
In the meantime enjoy yesterday’s 3 videos and rest assured it’ll be worth it in terms of clarity.
I feel like the current implentation is seriously overcomplicating the problem of how to move the tank. Especially considering how it was previous version of this section and the Unreal’s training stream of creating a tank, which is similar to that.
I have seen that, we are making it more physical. It is complex but the idea is to learn as many re-usable tools as possible, and I think you will.
Those resources against 149 are there now, thanks again