Pilot meshes animation

[Darksaber]

Hi Jeremy, just a quick question, it it possible to add the rotating head meshes to anything beside craft

I only ask, as you know I have the HangarWorkStand.opt with a Figures added to them, either a StormTrooper or a Rebel Soldier, it's possible to set the heads to rotate?

I tried setting the heads as RotaryCommunicationSystem, and I also added a HangarWorkStand.ini adding the [Pilot} section to it, but it didn't work the head remained static.

just wondering if it is possible to alter an offset to do this, as it would add a bit more dynamic to the hangar

Just thought the Hangar Crane Rotates, but that is quiet random and it also rotates 360 degrees, so using or replacing that wouldn't be ideal, as the figure would look like girl from the Exorcist lol

Thanks, this is just a query not a necessity

[JeremyaFr]

Hello,
I've tested the "HangarWorkStand" in DSUCP v2.6.59.

I've added a [Pilot] section to "HangarWorkStand.ini":

Code: Select all

; HangarWorkStand.ini

[Pilot]
;mesh index, angle, speed, behavior
19, 50, 2, 0

I've launched the Pilot Proving Ground and the result is that the mesh rotates.

[Darksaber]

Blimey, I realise what I did now, I created the HangarWorkStand.ini added the info, what I didn't realise was that I the opt I wanted to add the rotation to was call RebHangarWorkStand.opt

the in the default.ini

I changed {HangarObjects} to
FlightModels\HangarWorkStand.opt = FlightModels\RebHangarWorkStand.opt

But all I needed to do was to add a RebHangarWorkStand.ini

And yes it rotates

Derrrrrr!!

Thanks Jeremy, I must have been tired

[JeremyaFr]

UPDATE

Hello,
I've updated the pilot hook.

You can now define a different animation when the cockpit is displayed.
This can be used to fix a bug with the vanilla A-Wing.

To define wich meshes are animated when the cockpit is displayed, create a file named "FlightModels\[Model]PilotCockpit.txt" or create a section named "[PilotCockpit]" in "FlightModels\[Model].ini".
When the "[PilotCockpit]" is empty, the values of the "[Pilot]" section are used.
The format is the same as the "[Pilot]" section.

Sample:

Code: Select all

;AWingPilotCockpit.txt
;mesh index, angle, speed, behavior
empty

[Darksaber]

So this is just for pilot/droid meshes only?

Just a thought, you know in some opts we have what looks like redundant meshes i.e. cubes/faces that correspond rotating meshes in the base, exterior and/or cockpit opts

So take the xwing base opt for example the rotating wing meshes are 1, 2, 3, 4, so in the Exterior opt they have to be the same meshes 1, 2, 3, 4, this is not a problem right, the Cockpit opt is then the same meshes 1, 2, 3, 4

But what if you couldn't see the wings in the cockpit (you can, but lets pretend you can't) so if you couldn't see the wing those meshes would be pointless, so I would remove the wings, but then meshes 1, 2, 3, 4 become other meshes, which when you pressed the "V" key other meshes would rotate, which you don't want, so to resolve this problem small cubes or faces are placed within the opt hidden from view these cubes or faces then become meshes 1, 2, 3, 4 replacing the wings and rotate unseen.

But what if you didn't need these cubes or faces within the cockpit opt????

I'm thinking more of the ini files for this as it would mean including 3/6 more *.txt files, plus I'm not even sure it can be done or if it is easier just to keep the cubes

But is it possible to add sections to ini file

[SFoils]

[SFoilsExterior]
(if section empty or doesn't exist then the values of the "[SFoils]" section are used.)

[SFoilsCockpit]
(if section empty or doesn't exist then the values of the "[SFoils]" section are used.)

[SFoilsLandingGears]

[SFoilsExteriorLandingGears]
(if section empty or doesn't exist then the values of the "[SFoilsLandingGears]" section are used.)

[SFoilsCockpitLandingGears]
(if section empty or doesn't exist then the values of the "[SFoilsLandingGears]" section are used.)

You see where I'm going with this?

Like I say I'm not sure if it's possible of if it's worth the hassle, it will probably be easier just to add the hidden cubes, plus it might be too confusing having different sections with different rotating meshes.

I'm beginning to talk myself out of this idea, seemed to be not a bad idea at first, but I'm not so sure it is now.

Jeremy, if it is possible but too much hassle, don't bother doing it, just let me know if it would have been possible I think it would be best to keep it as simple as possible, meaning the way it is at the moment

Thanks

[JeremyaFr]

Hello,

The pilot hook is just for pilot/droid meshes only.

For your suggestion,
Yes, it is possible.
But I think that it would be confusing to add multiple sections with S-Foils data. Isn't it simpler as it is? Maybe add the cockpit sections?

The main reason to separate the cockpit section was to fix the animation with the vanilla A-Wing, without the ini or txt files.

[Darksaber]

Like I said above it would be too confusing, so yes leave it as it is please

It was just an idea, that when thought through properly wasn't such a good idea

(nice to know it could be done)

Thanks for the answer though

[keiranhalcyon7]

Your suggestion made sense to me, DS.

What, exactly, is this vanilla A-Wing animation bug?

[JeremyaFr]

Use the previous version of the pilot hook, and a vanilla A-Wing.
Go to the Pilot Proving Grounds and switch craft to the A-Wing.
You will see the cockpit animation.

[Bman]

.

[JeremyaFr]

UPDATE

Hello,
I've updated the pilot hook.

I've added support for object replacement.

[JeremyaFr]

UPDATE

Hello,
I've updated the pilot hook.

You can now define pilot animations for the hangar droids.

[Bman]

Thanks Jeremy. Could this hook also allow mesh animations in general for any hangar objects ? Some are static and didn't rotate last time I tried:

;ModelIndex_203_RebelPilot (replaced by CustomCharacter.opt)
;ModelIndex_204_ImperialPilot (replaced by CustomCharacter.opt)
;ModelIndex_205_CivilianPilot (replaced by CustomCharacter.opt) etc ....
;ModelIndex_206_ZeroGStormtrooper
;ModelIndex_207_ZeroGUtility
;ModelIndex_210_SatB
;ModelIndex_211_SatC
;ModelIndex_212_SatD
;ModelIndex_214_ProbeCapsule
;ModelIndex_215_BuoyC
;ModelIndex_216_BuoyB
;ModelIndex_217_BuoyRendez
;ModelIndex_218_BuoyFaux
;ModelIndex_219_MineA
;ModelIndex_220_MineB
;ModelIndex_221_MineC
;ModelIndex_46_MoleMiner
;ModelIndex_47_EscapePod
;ModelIndex_48_EscapePodA
;ModelIndex_192_LaserBat
;ModelIndex_193_IonBat
:ModelIndex_XXX_ConnetorRod and other Internal DS .opts


Thanks, sorry if this is wrong channel.