Fstorm Light

[deC9r]

If you use a fstorm light with target mode and turn it later off, the position coordinates to the origin point get lost. The last position is then 0 | 0 | 0 instead of the "real" position to the origin point.

[Karba]

If you use an fstorm light with target mode and turn it later off, the position coordinates to the origin point get lost. The last position is then 0 | 0 | 0 instead of the "real" position to the origin point.

what 3ds max version do you use? 2017?

[Sylk]

In fact its weird, at reOn, target position is "restored" to previous (target to origin but light looks to previous target position), but when you move light, target is updated and reset to origin (and light is reorient to target to origin) and if moving target, it jump to another position (light follows target).

And wow!... by undo operation, previous target positions are wrong, but more serious, a target clone (to origin) is appeared, same name... see pic.



It looks like missing viewport refreshments/updates after executing functions.

[deC9r]

I'm using 3ds max 2016.

[Sylk]

Not ended. When i undo this cloning, clone desappears, but if i redo... 2 clones appears (the deleted + new clone), and it add new clone for each undo/redo operation :s

Edit: another bug, target is missing when creating light w/ target checked (it's just non targeted light)

[Sylk]

Making vid to show you these crazy behaviors: Same for FSCamera, except targeted creation works but no targeted creation creates target anyway.

MAX 2017
FS 0.2.6
Drivers 372.70
WIN 10

[Karba]

I see. 3ds max targeting system is a pain. Even VRay light crashed 3ds max when I did some tests.
I will check it.

[Sylk]

Thanks.

It's less worse with SunLight but also impacted (target cloning)

[Sylk]

Actually the light "size" input field is its radius, so the real light size is equal to 2x the input size.

Two solutions
- Rename size to radius
or
- Multiply input value by 2 (to show 1m instead 0.5m)

I prefer the second one.

Also with Sphere and Disk shapes "size y" should be disabled.


Thanks for all

[Karba]

Actually the light "size" input field is its radius, so the real light size is equal to 2x the input size.

Two solutions
- Rename size to radius
or
- Multiply input value by 2 (to show 1m instead 0.5m)

I prefer the second one.

Also with Sphere and Disk shapes "size y" should be disabled.


Thanks for all

There reason is
When you switch between plane and disk, the size stays the same. I would rename size to half size/radius.