inconsistant movedata hover 1

inconsistant movedata hover 1

Discuss your problems with the latest release of the engine here. Problems with games, maps or other utilities belong in their respective forums.

Moderator: Moderators

Post Reply
User avatar
FLOZi
MC: Legacy & Spring 1944 Developer
Posts: 6242
Joined: 29 Apr 2005, 01:14

inconsistant movedata hover 1

Post by FLOZi »

I'm running into a bug with my amphibious units,

inconsistant movedata hover 1 *unitname* LVA2

LVA2 is the name of my move class, its exactly the same as an XTA pelicans. The vehicles drive around fine but will not enter water. I'm thinking it is perhaps an FBI conflict?

Here is the FBI of one such unit:

Code: Select all

[UNITINFO]
	{
	UnitName=RUSBRDM-1;
	Version=1;
	Side=CORE;
	Objectname=RUSBRDM-1;
	Designation=RUSBRDM-1;
	Name=BRDM-1;
	Description=Amphibious Scout Car;
	FootprintX=3;
	FootprintZ=3;
	BuildCostEnergy=3092;
	BuildCostMetal=51;
	MaxDamage=100;
	MaxSlope=15;
	EnergyUse=5.6;
	BuildTime=536;
	WorkerTime=0;
	BMcode=1;
	Builder=0;
	ThreeD=1;
	ZBuffer=1;
	NoAutoFire=0;
	SightDistance=800;
	RadarDistance=0;
	SoundCategory=Jeep;
	EnergyStorage=0;
	MetalStorage=0;
	ExplodeAs=vehicle;
	SelfDestructAs=vehicle;
	Category=CORE TANK LEVEL1 WEAPON NOTAIR NOTSUB CTRL_G;
	TEDClass=TANK;
	Copyright=Copyright 1997 Humongous Entertainment. All rights reserved.;
	firestandorders=1;
	unitnumber=1256346;
	StandingFireOrder=2;
	mobilestandorders=1;
	StandingMoveOrder=1;
	canmove=1;
	canpatrol=1;
	canstop=1;
	canguard=1;
	MaxVelocity=3.705;
	BrakeRate=0.1;
	Acceleration=0.03;
	TurnRate=400;
	SteeringMode=1;
	ShootMe=1;
	EnergyMake=0;
	DefaultMissionType=Standby;
	maneuverleashlength=550;
	MovementClass=LVA2;
	Weapon1=UNI7,62mmMG;
	wpri_badTargetCategory=NOTAIR;
	BadTargetCategory=NOTAIR;
	canattack=1;
	NoChaseCategory=VTOL;
	Stealth=1;
	Corpse=RUSBRDM-1_damaged;
	canhover=1;
	waterline=0;//9
	}
Any ideas?
User avatar
Kuroneko
Posts: 483
Joined: 03 Jan 2005, 05:32

Post by Kuroneko »

iirc, that error means that the movement class doesn't exist. I had the same error when porting some older custom units over to Spring, all I had to do was make a new class and it was all good.
User avatar
FLOZi
MC: Legacy & Spring 1944 Developer
Posts: 6242
Joined: 29 Apr 2005, 01:14

Post by FLOZi »

The class DOES exist, and when the fbi doesn't have canhover=1; it doesn't throw the error.
User avatar
FLOZi
MC: Legacy & Spring 1944 Developer
Posts: 6242
Joined: 29 Apr 2005, 01:14

Post by FLOZi »

*BUMP*

Incase anyone was wondering; SJ has confirmed hover movement classes need HOVER hardcoded in the name.
Post Reply

Return to “Help & Bugs”