There's some code that does maths, but at least one of the variables it uses doesn't exist.

And its located in the Projectiles BP? I didnt think that was a problem?

It's a script error. The error itself is in the script. The variable that is missing might be in the blueprint; that's for you to work out.

I looked at the script. I made it into this:



And there are still problems.

Look at the loop at the line number that the error message points to. What does it do with OffsetEmitter? What does it try to pass to it as the last parameter, in both cases?

The variables are undefined... It seems that when I made


into

The Error doesnt seem to appear anymore.

Right, that's because it looks for self.PolyTrailOffset[i], where i is the index of the emitter in self.PolyTrails. So you just need as many offsets as trails.

Thats what I thought when I had a closer look at DefaultProjectiles.lua.

Have you tried out my Beta yet? =p

So ya, I am trying to make a Missile Projectile that has a special effect...

On Impact, I wanted the targeted unit to change sides to that of the attacking unit for 3 minutes. It shouldnt effect Experimentals, or Commanders/SCUs.

I looked up in LUADOC, and the closest thing I can find is ChangeUnitArmy, yet I have no idea how to do it...

Anyone up for this challenge?

Im having a problem with a T4 Mobile arty unit... It doesnt seem to deploy on its own, and when I tell it to fire, It Deploys, yet the Barrel sounds like somethings caught in the gears, not allowing it to target units....

However, When I tell it to attack again, it sometimes works, and sometimes doesnt X-x

Any idea why?

Not without at least pastebinning the script and bp, and the log if there are errors.

Which unit's script/bp did you use as a base, and what type of changes did you make to the bp re: animations / reload times / etc?

Unit BP: http://pastebin.com/9Ka9jbtv
Unit Script: http://pastebin.com/vtsKcCFS

I used the Cybran Mobile Arty as the base. (URL0304)

Nothing shows up in the log. Only things I changed were the weapons Range, Damage, Bone stuff, Projectile and added camera stuff.

Also, I changed the Faction stuff, so it would only be built by the ordos. Had to add in a few things so it was an experimental and so it was built by the T3 Engineers and ACU

I don't see anything extremely glaring, but there are a few potential issues:

The TargetCheckInterval is too high - keep it to <= 1, as this could cause target acquisition issues, forcing the weapon to start repacking too quickly.

Likewise, the WeaponRepackTimeout should probably be longer than the TargetCheckInterval. I don't really know why all the T3 mobile arty have a WeaponRepackTimeout of 0, but they have a pretty quick unpack/repack animation, so it's not the end of the world if they get interrupted in the middle of their animation, unlike a T4 artillery that likely takes a long time to pack/unpack.

I see you're using the same bone for pitch and yaw. If the mesh is rigged correctly, that can work, but if not, that can cause aiming/animation problems. Likewise, depending on which bones the animation manipulates, it might be causing a fight between the weapon's aim manipulator and the unpack animator. If you look at the Scathis blueprint, it has a WeaponUnpackAnimatorPrecedence of 0 (the default, actually), which I assume allows the aim manipulator to rotate the yaw bone while the weapon is unpacking. If you can't solve the issue any other way, play around with this value, both higher and lower than the aim manipulator precedence (which defaults to 10 if AimControlPrecedence isn't set in the bp).

I actually got it to work =o I dunno what was wrong...

Now, Last problem for that unit... Is there any command for the script to make it immobile when its deployed? Cause when its deployed, The unit still spins around when its told to force fire. It doesnt do this when its not deployed...

This is the part of the script I need to tweak:



I dunno the command to replace

with something that completely stops it from moving. I know that it is this that still allows the unit itself (And not teh turret only) to turn.

..and false to make it mobile again.

So there is a SetImmobile command =p BlackOps would of benifited from that with their old basilisk XD Thanks Mithy, Now its just a matter of Balancing my Experimental Mobile Artillery XD

Ok, Onto the AI =o I tried to do it the easiest way, Like making CustomUnit support like in most mods, with a Hooked BaseManager.lua file. It somewhat works, however, The ACU doesnt move, and I get this error:



Would the problem be in my BaseManager file?

Again, it gives you the exact line number of the error. Figure out what that line is trying to do, and trace it back until you find the table/data that it's missing.

I got it to load successfully. No Errors. However, the darn ACU still doesnt do anything X-x

The AI code is pretty expansive, and there are faction-specific plans, items, etc in many files. If there aren't any guides for adding AI support for a faction, you'll have to browse through all of the files in /AI and find any faction-specific data that needs to be added.

There is no guide... And I have looked for all the faction specific stuff... Theres weeks of work there that needs to be done X-x

Guess that means I need to wait for Nomads to come out, and use their AI for the Ordos. (Less incompatability issues then I think?)

I have a small impact issue with the ordos. Im not sure how it effects Multiplayer, but it seems that whenever the SCU is spawned, and when the new BuildShader effect is used, the game 'stops' for half a second, and resumes like normal. The other factions do not cause this type of problem.

Any ideas as to what is causing it?

(Note: The Current Ordos Version has this problem only with the SCU)

Looking at the effect you posted could be putting a strain on the engine what did u do to make the shader why didn't u just copy cybran one and change the colour?

Changing the Colour would require adding a new part to the mesh.fx becuase the colour of the cybran effect is determined by the shaders themselves. So Unless someone makes a new shader, Im gonna be sticking with the one I have.

If I knew how to port over the Shader effects (Build effect/Shield) from SC2 to FA, I would do it in a flash.

Well if you find out what shader works the effect changing the color should be easy? you can replace that file cant you?