Editing S-Foils

[JeremyaFr]

WIP

- I've fixed the rotation angle.
- I've added a line to show the rotation axis.

- I've added a button to save the OPT file.
- The ini file is now saved.

EDIT: link removed

Before testing, I recommand to make a backup of the ini and/or txt files for the craft being tested.

[JeremyaFr]

To be honest leaving the SFoilsAnimationSpeed at the default 1 and the speed at 1 wouldn't bother me, but GT asks if the animation could be slowed down, so is there any way to make the slowed down animation smoother?

Not currently. The game engine uses integers for the mesh rotation angle values. It is not possible to change that. When the values are converted to radians, they are multiplied by 0.0245436728. So 1 unit means 1.4°.

The rotation angle is dependent from the lenght of the "Look" vector. So I think the vector length can be used to slow down the rotation while still being smooth. I've not tested that.

[JeremyaFr]

WIP

I've added a button to save the OPT file.

[JeremyaFr]

WIP

The ini file is now saved.

On saving, the ini file is updated. If a txt file already exists, it will also be updated.

[Rebelyell]

Sweet! Great work!

[Darksaber]

Works ok thanks

[Vince T]

Tested it on the VSD and it works great! Thanks Jeremy!

[JeremyaFr]

UPDATE

Hello,
I've added Xwa SFoils Editor to Xwa Opt Editor.

[Darksaber]

Brilliant

[MamiyaOtaru]

Related to this, would it be possible to create a tool that would allow you to import an opt into it, then using sliders, or a text based interface like your hangar editor assigned to whatever rotational axis that the S-foil / landing gear animations use, use it to rotate the meshes to a desired open/closed angle, then allow you to export the mesh rotation data into the relevant ship.ini file? This would really help with not having to go ingame to see if your animated meshes are rotating to the correct position several times.

Nice suggestion.
I am working on it.

Edit: I used the hook downloader to update all my hooks and I don't think the S-foils hook is updating since CTRL+L seems to do nothing. Also it seems dated as of 23JAN19.

The hook upload is fine. You can check the date here: https://github.com/JeremyAnsel/xwa_hook ... sfoils/zip

can I assume that for this to look right in game, I will need updated ship files? Using the files in that zip the sfoils work (aside from the guns staying in place) but there is no landing gear (presumable because of lack of FlightModels\[Model]SFoilsLandingGears.txt files). I'm eager to see sfoils and landing gear separate, but I can wait until someone makes those files

*FEW MINUTE$ LATER*

Or I can make them myself Copied the missing gun entries from xwing.ini to XWingSFoils.txt, and put the remainder into XWingSFoilsLandingGears.txt and they both work (separately). It was pretty easy to tell which was which since the wing/gun angles all match hah

[Bman]

Hi Jeremy, can you give an example of how the AssaultGunboat.ini file should look (syntax), specifically the LandingGears Hook ? Ctrl + L

[Pilot]
x, x,x,x, for rotating pilot head

[SFoils]
x, x,x,x, for the actual rotary wings

CloseSFoilsInHyperspace = 1
SFoilsAnimationSpeed = 1

[SFoilsLandingGears] = 0 or 1 ? Is this a section header or a normal syntax statement ? Can it be here too, or does it only go into an AssultGunBoatSFoilsLandingGears.txt .txt file ?
x,x,x,x for rotary landing gear meshes

Also what order should the above sections/statements be in?
Thanks!

[Darksaber]

this is my AssaultGunboat.ini

Code: Select all

;AssaultGunboat.ini

[Camera]
;Camera X,Y,Z
X = -300
Y = 500
Z = 70

FamX = -300
FamY = 500
FamZ = 70

[Pilot]
;mesh index, angle, speed, behavior
12, 32, 2, 2

[SFoils]
;mesh index, angle, closing speed, opening speed
4, 50, 2, 2
5, 50, 2, 2
6, 88, 2, 2
7, 88, 2, 2

CloseSFoilsInHyperspace = 0
SFoilsAnimationSpeed = 1

[SFoilsLandingGears]
;mesh index, angle, closing speed, opening speed
10, 128, 8, 8
11, 128, 8, 8

[Size]
ClosedSFoilsElevation = 55
ClosedSFoilsElevationInverted = 55

[Sound]
EngineSoundInterior = 5
EngineSoundFlyBy = 5

EngineSoundWash = 1

WeaponSoundBehavior = Empire

[WeaponColor]
WeaponColor = 0
WeaponColor282 = 0
WeaponColor283 = 0
WeaponColor284 = 2
WeaponColor285 = 2

WeaponImpactColor_3100 = 80C71585
WeaponImpactColor_3200 = 80FF0000
WeaponImpactColor_3300 = BF55FF00
WeaponImpactColor_3400 = 804A0080
WeaponImpactColor_3500 = BFFFE700

WeaponImpactColor282 = BF55FF00
WeaponImpactColor283 = BF55FF00
WeaponImpactColor284 = 80C71585
WeaponImpactColor285 = 80C71585

EnergyBarColorLaserHigh = FF00FF00
EnergyBarColorLaserLow = FF009E00
EnergyBarColorIonHigh = FFDB1893
EnergyBarColorIonLow = FF961065

WeaponLightColor282 = 0
WeaponLightColor283 = 0
WeaponLightColor284 = C71585
WeaponLightColor285 = C71585

To open or close s-foils, use the V key. To deploy or retract landing gears, use the Ctrl+L key. You can't open the other when one is open.

I suppose the [Headers] can be in any order, I like to do them alphabetical

[SFoilsLandingGears] is a section header, you now need both if your craft has Landing Gear, if not just use the [SFoils] header

[Bman]

Thanks DS. That's perfect. I came up with similar configuration after I posted. The problem I was having was that the landing gears were rotating constantly on AI wingmen craft. I discovered that changing the mesh type from rotorarycommandsystem to rotarywing mesh works. So mesh type does matter in most cases. I have files I need to send you too pretty soon. Thanks mate.

EDIT: The EngineSoundWash = 1 statement you posted above, only applies to starships. I don't think it works for fighter craft.

[Darksaber]

You can actually leave Landing Gear mesh type as 1-MainHull on the opt, as long as it is set in the txt/ini file it should rotate

[Vince T]

Got a problem here. ...
WIth the latest release the NPC Sfoils no longer close in hyperspace. Could you take a look?

[JeremyaFr]

Hello,

I've checked the s-foils hook.
It seems that all is fine.

By default, the s-foils don't close when entering into hyperspace.
This feature has to be set on a per-craft basis by setting "CloseSFoilsInHyperspace = 1" in the [SFoils] section.

[Vince T]

This is weird. I didn't change anything in the ini file and it did work before

[JeremyaFr]

In the WIP version of the hook, the default value for CloseSFoilsInHyperspace was 1. I have then modified it to 0 as a DTM request.

May I suggest to set the default value as "0" (if it's possible)?
Most of the crafts does not have s-foil, but have landing gears. This new feature should be restricted to X-Wing, B-Wing, U-Wing, VSD and few others...
Thanks!!!!

So without editing the ini files, in the WIP version the S-Foils automatically close by default, but in the stable release, since the default value is inverted, this feature has to be explicitly enabled for a specific craft.

Maybe I can add a global default value in a config file for the hook?

[Vince T]

Hm, I had set it to 1 already ... I wonder if the rotary gun turrets might be interferring here?

[Rookie_One1]

bug report time : the s-foil sound play at hyperspace when you have landing gears meshed activated in the in ini file (tested with the Y-Wing)

[JeremyaFr]

Thanks for the bug report.
Good catch.

I've fixed it.
Please redownload the hook.

[Rookie_One1]

Thanks Jeremy! That was quick!

[JeremyaFr]

UPDATE
Hello,
i've updated the sfoils hook.

I've fixed a bug introduced in the last fix.

The bug was that the S-Foils don't automatically open at mission start. I've fixed it.

[St@rkiller]

UPDATE
Hello,
i've updated the sfoils hook.

I've fixed a bug introduced in the last fix.

The bug was that the S-Foils don't automatically open at mission start. I've fixed it.

Thanks a lot! This fixes my issue with the A-Wing (doesn't wants to fire because the "S-Foils are closed")

[JeremyaFr]

UPDATE

Hello,
I've updated the sfoils hook.

You can now set the initial state of the s-foils and landing gears.

Suppose that the mission is "[MissionDir]\[Mission].tie".

To override the mission data, create a file named "[MissionDir]\[Mission].txt" or create a section named "[mission_tie]" in "[MissionDir]\[Mission].ini".
The format is a line per replacement.

To replace the flight group s-foils state, the format is: "fg", fg number, "close_SFoils", 1.
To replace the flight group landing gears state, the format is: "fg", fg number, "open_LandingGears", 1.