Forged Alliance Forever

Re: When weapons don't fire

2018-08-08T00:40:32+02:00

I tried blender, couldn't figure out how to use it to save my life! And maybe it was something I was lacking, but I could only ever see a tiny portion of an imported model, on the rare occasion I was able to import successfully! Between that, and several other CAD programs, I basically stick with coding. Though not for lack of trying! About the only CAD program that makes sense to me is the Lego one. Stud.io is what it's called, but that's probably because it has preset shapes to use, and intuitive visuals.

Statistics: Posted by stardust — 08 Aug 2018, 00:40

Re: When weapons don't fire

2018-08-07T07:48:52+02:00

Blender is a nice 3D editor. It's free and you have plugins to import and export supcom 3D models.

Statistics: Posted by Franck83 — 07 Aug 2018, 07:48

Re: When weapons don't fire

2018-08-07T01:16:08+02:00

Yeah, modifying an existing model can be harder then creating a unit from scratch

Statistics: Posted by Uveso — 07 Aug 2018, 01:16

Re: When weapons don't fire

2018-08-06T17:24:33+02:00

Hmm, I had a feeling that was it. So let's say I copy the weapon code from another unit and copy-paste it into my prototype. As long as I preserve the muzzle bone from the original, I SHOULD be able to get it to work without having to use a 3D modeling program, correct? Even if I just use the weapon itself without the turret?

*tries it*

Shucks, didn't do anything. MOST INTERESTING. It didn't break anything at least!

Statistics: Posted by stardust — 06 Aug 2018, 17:24

Re: When weapons don't fire

2018-08-06T01:53:53+02:00

Lets say you have a ship with a flare antimissile system.
The antimissile flare weapon is attached to the ShipBone "FlareBone".

If you now change the flare weapon with a nuklear launcher that was attached on the old unit at bone "NukeBone",
then you need to rename the bone from the launcherblueprint from "NukeBone" to "FlareBone".
Thats all, the weapon should work now.

Now you want to attach a weapon turret to the same place.
A Weapon turret has 3 bones; "PitchBone", "YawBone" and "MuzzleBone".

Because the ship has only 1 available bone for the weapon, you can't add that weapon there.
In this case you need a 3d model program and add 2 more bones or it will not work.

Statistics: Posted by Uveso — 06 Aug 2018, 01:53

Re: When weapons don't fire

2018-08-04T17:08:56+02:00

Right. But how will the game engine know where and what to use if I toss in, say, the bone for the Cerberus turret onto a given unit?

Also, was able to fix the problem with Orbital Wars Reborn not attacking anything. But it only seems to work in my debugger, with no real errors worth mentioning. If I launch the game thru the FAF client, they still just sit there.

Statistics: Posted by stardust — 04 Aug 2018, 17:08

Re: When weapons don't fire

2018-08-04T07:53:56+02:00

stardust wrote:
Is there a quick and easy way of changing the name of a weapon bone? Or does one need modeling programs for that?

If you want to change the name of a bone you need a modeling program.

But there is no need to rename a bone inside the model.
You only need to copy the model-bone-name into the blueprint file.

Just be sure you use the same name inside the model and the blueprint file.

Statistics: Posted by Uveso — 04 Aug 2018, 07:53

Re: When weapons don't fire

2018-08-04T01:13:02+02:00

Bump. An update.

Is there a quick and easy way of changing the name of a weapon bone? Or does one need modeling programs for that?

Statistics: Posted by stardust — 04 Aug 2018, 01:13

Re: When weapons don't fire

2018-07-26T23:43:20+02:00

Shucks. Thanks anyways, and don't sweat it I will keep tinkering with it.

Statistics: Posted by stardust — 26 Jul 2018, 23:43

Re: When weapons don't fire

2018-07-26T02:43:22+02:00

If those turrets where anti air wepaons, then maybe the pitch angle is to low, so the weapon can't aim to the ground ?

(I don't have time to check another mod^^)

Statistics: Posted by Uveso — 26 Jul 2018, 02:43

Re: When weapons don't fire

2018-07-26T00:43:50+02:00

Very cool! I will try something. Looking thru your most recent link, I can put them all into a single file, but get rid of the menagerie of existing lua files I have? Most of them are garbage, I suspect.

Am still tinkering with the old Orbital Wars Reborn as well. I lowered the elevation of the big ships a bit, and added all the layers all the weapons could fire at (was just air beforehand) but still no glorious pew pew of lasers. Nothing in the restrictions or the target priorities jumped out at me as preventing any sort of fire effect, but any attempt by any big ship to attack any hostile target... well, it's like an anti-air tower not attacking tanks. And I'd really like to figure this out.

Here's what i've got:
https://www.dropbox.com/sh/8tfabrnn9mwp ... VHWFa?dl=0

Statistics: Posted by stardust — 26 Jul 2018, 00:43

Re: When weapons don't fire

2018-07-25T05:31:35+02:00

stardust wrote:
As for AI support, how does one go about fixing that so the AI - particularly Sorian Water AIs - will make use of the new stuff?

Shift-Y = BuildAiScripts

You only need to press [SHIFT]+[y] and the mod will print all AI tables into the log.
Remove the "info: " from each line, and you can copy past the tables to your files inside /mod/lua/CustomUnits/

I also made a smal tutorial:
http://forums.faforever.com/viewtopic.php?f=41&t=14688

Statistics: Posted by Uveso — 25 Jul 2018, 05:31

Re: When weapons don't fire

2018-07-25T02:51:38+02:00

Not showing up, but I am still working through the list of errors you found.

As for AI support, how does one go about fixing that so the AI - particularly Sorian Water AIs - will make use of the new stuff?

Statistics: Posted by stardust — 25 Jul 2018, 02:51

Re: When weapons don't fire

2018-07-25T02:03:23+02:00

Last thing, you need to focus the game window or the key shortcuts will not work.
If you click on the log window and try then to use one of the shortcuts you will only hear a ping sound.

Statistics: Posted by Uveso — 25 Jul 2018, 02:03

Re: When weapons don't fire

2018-07-25T02:05:05+02:00

If you installed it right and activate it, then you should see at least this inside the "Moho Log" Window opened with [F9]:

Code:: INFO: Uveso Debugger: [unitdebug.lua, line:22] - Starting debugger INFO: Supreme Commander: Forged Alliance version 3696 INFO: Uveso Debugger: [UnitDebug.lua 59] - version.lua = true - Gameversion=(3696) INFO: Supreme Commander: Forged Alliance version 3696 INFO: Gameversion=(3696) INFO: - Shift-H = Print KeyBindings INFO: INFO: - Shift-Q = ModUnitCheck INFO: - Shift-W = ValidateCategories INFO: - Shift-E = ValidateUnitIcons INFO: - Shift-R = Validate Strategic Icons INFO: - Shift-T = CheckDisplayAbilities INFO: - Shift-Z = Check Selection Size INFO: - Shift-U = Check Unit Enhancements INFO: - Shift-I = Unit Statistics INFO: INFO: - Shift-A = CkeckWeaponAnimation INFO: - Shift-S = ModWeaponProjIDCheck INFO: - Shift-D = ModDisplayMeshCheck INFO: - Shift-F = ModUnitSoundCheck INFO: - Shift-G = ModWeaponSoundCheck INFO: INFO: - Shift-Y = BuildAiScripts INFO: - Shift-X = GetUnitList INFO: - Shift-C = Game File Check INFO: INFO: - Shift-V = Execute function Check() INFO: - Shift-B = CheckBlacklistedUnits INFO: - Shift-N = Check localisation INFO: - Shift-M = Print localisation INFO: H Q W E R T Z U A S D F G Y X C N M (V B) INFO: Uveso Debugger: [UnitDebug.lua 70] - Default Moddirectory to check= (NAVAL UNIT PACK 1.0) INFO: Uveso Debugger: [UnitDebug.lua 71] - If you want to change the default Moddirectory go to "UnitDebug.lua" Line 69)

Do you have those lines in your log ?

[Edit]
If you use the checks with [SHIFT]+[s] or [SHIFT]+[d] then the game will freeze for 30 or more seconds. Just wait, it will come back.
And don't open the "F1" key menu, this will overwrite the keysettings from the debugger mod.

Btw, did you know, if you are play/test in skirmish mode, you can restart the game by pressing [CTRL]+[F10] to reload all unit scripts.

Statistics: Posted by Uveso — 25 Jul 2018, 01:54