Fire.Face

Feature Requests Engine Features
#1

This is a fairly simple suggestion, basically have an Enum.NormalId to define which face the fire goes towards.

Currently its the top, so if we could Fire.Face = Enum.NormalId.Front, it would go forward relative to the brick.

#2

That sounds like a really good idea,
Do you think it’ll just face the direction? or would it spawn from the face?

#3

No

Vector3 Fire.Direction instead

#4

[quote] No

Vector3 Fire.Direction instead [/quote]

Why over-complicate?? Surface makes the most sense, it can be easily edited for basic builders and if that was put in it would make unnecessary calculations for people wanting to make just a simple directional fire. Not to mention other part “effects” use NormalId (SpotLight SurfaceLight) I just feel like this would be inconsistent and pointless.

Related to the OP, I totally agree ATM it looks funny when you have a torch or something hanging from ceiling as the flame goes inside of the part.

#5

Fire.Direction isn’t over-complicating it. As a developer I would much rather have an unlimited number of directions than six.

SurfaceLight.Face makes sense because the object’s behavior is directly tied to a specific surface rather than a specific direction. SpotLight should’ve had Direction instead of Face. Continuing to use a bad style for the sake of consistency will only result in many objects being bad instead of just one.

#6

Hey, what do you need?

#7

[quote] No

Vector3 Fire.Direction instead [/quote]

What if Fire.Direction.magnitude != 1?
Fire.Heat → deprecated B)

#8

[quote] No

Vector3 Fire.Direction instead [/quote]

#9

[quote] No

Vector3 Fire.Direction instead [/quote]

[/quote]

Fire.Direction = Vector3.new(0.71, 0.71, 0)
print(Fire.Face)
#10

Fire.Direction would be better than Fire.Face, imo, because it’d give more control over what direction the fire is actually facing in relation to the part rather than having the direction being dependent on the part itself.

#11

[quote] No

Vector3 Fire.Direction instead [/quote]

[/quote]

Because API bloat

#12

On topic: I’m more for the Vector3 direction, it’s a bit more flexible, and I like flexible

#13

[quote]
Because API bloat [/quote]

True, but It would still be nice for less-skilled players to be able to easily choose a face just like a decal.

#14

I agree with Vector3 Fire.Direction.
But how would it work?
X Y Z are all angles from the top?

#15

Opinion:

Fire.Direction

For the present:

Fire.Heat = -20
#16

[quote]
Because API bloat [/quote]

True, but It would still be nice for less-skilled players to be able to easily choose a face just like a decal.[/quote]

I don’t see less-skilled players catching on fire because Position is a vector. Making it a face is just absurdly oversimplifying it.

#17

[quote] [quote=“Echo” post=155228]
Because API bloat [/quote]

True, but It would still be nice for less-skilled players to be able to easily choose a face just like a decal.[/quote]

I don’t see less-skilled players catching on fire because Position is a vector. Making it a face is just absurdly oversimplifying it.[/quote]

And making it less flexible!

#18

[quote] I agree with Vector3 Fire.Direction.
But how would it work?
X Y Z are all angles from the top? [/quote]

It would be in object space relative to the part, so 0,1,0 would be top, 1,0,0 would be right, 0,0,-1 would be front, etc…

For you people arguing about using faces, you can just do

face = Enum.NormalId.Front fire.Direction = Vector3.FromNormalId(face)

#19

Use Vector3 Fire.Direction
and add a method
Fire:SetFace(Enum NormalID)
which simply sets Fire.Direction for newbie players

#20

Also won’t fire just be obsolete with the new particles coming out soon?