Internal error during load up to match when tinkering with generic WH

Bug #896122 reported by SSTG
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ares
Fix Released
Medium
AlexB

Bug Description

Was working to create a kinetic warhead SW once I had put the SW on its list and ran the game to test a IE appeared tested this with other countries and they all seem affected by this

##### ADDITIONAL INFORMATION #####
SW and WH coding

[PsychicPulseSpecial]
UIName=Name:YAPPET
Name=Lightning Storm
IsPowered=true
RechargeVoice=00-I156
ChargingVoice=
ImpatientVoice=
SuspendVoice=
RechargeTime=10
Type=GenericWarhead
Action=Custom
SidebarImage=PDOMICON
ShowTimer=yes
DisableableFromShell=yes ; gs this determines which superweapons are turned off by the checkbox
Range=1.4
LineMultiplier=3
Cursor.Frame=32
Cursor.Count=5
Cursor.MiniFrame=43
Cursor.MiniCount=8
Cursor.HotSpot=Center
GenericWarhead.Warhead=GattArtyWH
GenericWarhead.Damage=10000

[GattArtyWH]
CellSpread=2.5 ;1.5 ;.9
Wall=yes
Wood=yes
Verses=10%,7%,5%,55%,65%,45%,9%,90%,4%,15%,25%
Conventional=no
InfDeath=3
AnimList=NUKEANIM
Rocker=yes
ProneDamage=35%
;Particle=ArtyFlashSys
;CLDisableBlue=true
CombatLightSize=2000%
AffectsAllies=no
Bright=true
ShakeXlo=2
ShakeXhi=2
ShakeYlo=2
ShakeYhi=3
WeaponShakeXlo=2
WeaponShakeXhi=2
WeaponShakeYlo=2
WeaponShakeYhi=3
IsLocalShake=yes
Bullets=yes
MinDebris=1
Max Debris=2
DebrisTypes=QUAKE
DebrisMaximums=2

[QUAKE]
Name=Quake Ripples
Image=TIRE
Elasticity=0.0 ;0.1 ;1.0
MinAngularVelocity=1.0
MaxAngularVelocity=5.0
MinZVel=1.0 ;30.0
MaxZVel=5.0 ;38.0
MaxXYVel=12.0
Duration=16
ExpireAnim=QUAWAVET
Damage=5000000
DamageRadius=900000
Warhead=KineticCannonWH
Translucent=no

[KineticCannonWH]
Verses=0%,0%,0%,0%,0%,0%,0%,0%,0%,0%,0%
CellSpread=1.5
InfDeath=3
Rocker=yes
ImmunityType=Kinetic
AnimList=SHELLWAVE

Tags: sw
Revision history for this message
SSTG (sstg) wrote :
Revision history for this message
AlexB (alexander-b) wrote :

[GattArtyWH]
MinDebris=1
Max Debris=2
MaxDebris isn't set. I don't know whether having a minimum of 1 and a maximum of 0 can crash the game. Mathematicians would crash in this case for certain.

WeaponShakeXlo=2
WeaponShakeXhi=2
WeaponShakeYlo=2
WeaponShakeYhi=3
IsLocalShake=yes
I smell a rat...

ImmunityType=Kinetic
...a dead rat...

You aren't by any chance trying to combine Ares with other patches, are you? Like with NPatch or NPatch Extended?

Revision history for this message
SSTG (sstg) wrote :

that may explain something I was talking to apollo about this warhead and he gave me the code from the RS weapon which probably is was theres Npatch there guess I didn't make a check on that

Revision history for this message
DCoder DCoder (dcoder1337) wrote :

Cursor.HotSpot=Center

[SuperWeapon]►Cursor.HotSpot= (HotSpot X, HotSpot Y)
    Specifies the coordinates on the cursor that are considered to be the 'tip' – that is, the point from which the click event will handled. HotSpot X should be one of "Left", "Center" or "Middle". HotSpot Y should be one of "Top", "Middle" or "Bottom".
    For example, Cursor.HotSpot=Left,Top will treat the top-left corner of the cursor as the tip. Default is "Center,Middle".

Revision history for this message
DCoder DCoder (dcoder1337) wrote :

Fixing the parser not to crash the game is one changed line - I say we should do that.

Revision history for this message
AlexB (alexander-b) wrote :

Sure.

Revision history for this message
SSTG (sstg) wrote :

fixed up those errors and it started working again thanks for that

Revision history for this message
Bug Importer (bug-importer) wrote :

Code related to this issue has just been checked in!
Author: AlexB
Location: trunk, r1026
Commit contains DLL: Yes
Revision comment:
Fixed issue #1232: Reset the carryall flag when a unit is paradropped.
Fixed issue #1509: Implemented DCoder's proposal for the Cursor parser.

Drawing a SHP unit's shadow used the wrong field to determine whether the unit was on a Carryall.
SVN: http://svn.renegadeprojects.com/Ares/1026

Revision history for this message
Rogan (pdrogan) wrote :

No crash nor IEs occurred when I used Cursor.HotSpot=Center on one of my SW.

Used trunk r1056.

Revision history for this message
DCoder DCoder (dcoder1337) wrote :

Thanks for testing!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.