Why error?
1246 10 2- happybabywzy
- Member
- 86 posts
- Joined: Feb. 2019
- Offline
- Soothsayer
- Member
- 861 posts
- Joined: Oct. 2008
- Offline
- happybabywzy
- Member
- 86 posts
- Joined: Feb. 2019
- Offline
- Soothsayer
- Member
- 861 posts
- Joined: Oct. 2008
- Offline
- GOgraphR
- Member
- 67 posts
- Joined: Oct. 2018
- Offline
As you are using already 4 floats, have you considered using floatToVector4 (/obj/geo/pointvop1/floattohvec1) ?
You could also set the const to produce a vec4. But I guess you have some other VOPs output being floats, right ?
An overview of what's available:
And don't get fooled, as you set it up,it shows no error. but as you go on the error re-appears.
You could also set the const to produce a vec4. But I guess you have some other VOPs output being floats, right ?
An overview of what's available:
And don't get fooled, as you set it up,it shows no error. but as you go on the error re-appears.
Edited by GOgraphR - May 13, 2023 13:41:53
- happybabywzy
- Member
- 86 posts
- Joined: Feb. 2019
- Offline
- Soothsayer
- Member
- 861 posts
- Joined: Oct. 2008
- Offline
- GOgraphR
- Member
- 67 posts
- Joined: Oct. 2018
- Offline
Soothsayer
It looks like a bug to me. Submit it and see what they say.
Got it nailed !!!
Right click on the culprit, and open the
Type properties
.in the
Parameter
tab you will find that input 1 is called vec
input 2 is called avec
But then, in the Code tab $hvec = $vec2; setcomp($hvec, $avec2.x, 2); setcomp($hvec, $avec2.y, 3);
So the parameter interface has different variable names than the script expects.
New Code Should be then
$hvec = $vec; setcomp($hvec, $avec.x, 2); setcomp($hvec, $avec.y, 3);
And there we go! It should work as intended
Edited by GOgraphR - May 14, 2023 19:42:55
- GOgraphR
- Member
- 67 posts
- Joined: Oct. 2018
- Offline
- happybabywzy
- Member
- 86 posts
- Joined: Feb. 2019
- Offline
- CYTE
- Member
- 685 posts
- Joined: Feb. 2017
- Offline
-
- Quick Links