Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: zookeeper on November 26, 2009, 10:59:14 am

Title: Feature request: allow $uvec to override turret normal
Post by: zookeeper on November 26, 2009, 10:59:14 am: It'd be handy if a turret subobject which uses $uvec and $fvec could also feature an extra property ("$normal_from_uvec"?) which would tell the game to use the uvec as the turret's normal (overriding any turret normal that might have been set in the turrets section). In most (all?) cases they're supposed to be exactly the same, and it's rather annoying to have to copypaste the uvec value from the properties box to the turret normal field and then change the commas to colons...once per every turret per every time you convert. Pretty much anything that allows you to do things in the modelling app before exporting, instead of having to do it in PCS2 every time you convert, is good.

Of course an alternative would be to have PCS2 simply check if the turret has an uvec set, and if yes, then use that as the default value for the turret normal, but the chances of anyone implementing new stuff into PCS2 and then releasing new versions seem much more slim.
Title: Re: Feature request: allow $uvec to override turret normal
Post by: Aardwolf on November 26, 2009, 02:30:31 pm: Problem is, not all turrets have their barrels pointing straight up. Take a look at the watchdog/cerberus. Heck, a lot of turrets don't have their barrels pointing straight up.
Title: Re: Feature request: allow $uvec to override turret normal
Post by: zookeeper on November 26, 2009, 02:44:34 pm: Quote from: Aardwolf on November 26, 2009, 02:30:31 pm
Problem is, not all turrets have their barrels pointing straight up. Take a look at the watchdog/cerberus. Heck, a lot of turrets don't have their barrels pointing straight up.
I don't see how that'd be any kind of a problem. Elaborate?
Title: Re: Feature request: allow $uvec to override turret normal
Post by: Aardwolf on November 26, 2009, 02:50:54 pm: Hm...

I thought you were talking about having it do it automatically. As long as it's not automatic, then no, it wouldn't be a problem.

Too bad Kazan is letting PCS2 die... really I reckon it'd be more popular if he'd just fix the 'nothing works' bug... and maybe changed source code rights / commit rights so that others can help. I wonder if the license he's using forbids us from taking the code and creating our own SVN version based on it...
Title: Re: Feature request: allow $uvec to override turret normal
Post by: chief1983 on November 26, 2009, 08:57:12 pm: Well I don't want to piss him off but I'm pretty sure anything hosted on Sourceforge is under some license that allows forking. I could be wrong though.
Title: Re: Feature request: allow $uvec to override turret normal
Post by: Aardwolf on November 26, 2009, 09:03:00 pm: Quote from: chief1983 on November 26, 2009, 08:57:12 pm
Well I don't want to piss him off but I'm pretty sure anything hosted on Sourceforge is under some license that allows forking. I could be wrong though.

I already started a separate topic (http://www.hard-light.net/forums/index.php?topic=66743.0) about this one.
Title: Re: Feature request: allow $uvec to override turret normal
Post by: Wanderer on November 27, 2009, 10:24:14 am: Code is now in to force turret_normal into same as the uvec if both uvec and fvec have been properly defined
Title: Re: Feature request: allow $uvec to override turret normal
Post by: chief1983 on November 27, 2009, 11:04:45 am: Would it make more sense to not be an override, but a fallback in the case of omission?
otherwise I can see some people not realizing it's on and wondering why changing one isn't making anything happen.

(If that sounds familiar I copy-pasta'd from #scp)
Title: Re: Feature request: allow $uvec to override turret normal
Post by: zookeeper on November 27, 2009, 11:31:23 am: Thanks Wanderer. This will be very handy. :yes: