having trouble figuring out what's wrong with my mod...

**mrlaird** · 28th Mar 10 11:46 PM

hello all, i just recently got interested in modding hw2. ive been through about every tut in the tanis shipyards but i'm still having trouble getting my new models to work.

when i load up a game it loads all the way until dustcloudgroups and then it goes to desktop. ive gone over my .ship file and my .hod so many times ive lost count. and i have no idea what i should be looking for in the .log (and i thought .ships were a bunch of gibberish, geez

lol)

log info

Homeworld2.exe caused an Access Violation in module Homeworld2.exe at 0023:0047b045.
Error occurred at 3/29/2010 09:36:58.

Call Stack:
0x0047B045: GSLobbySessionDesc::operator= (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\Homeworld2.exe)
0x002246B5: lua_error (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\lua.dll)
0x00224749: lua_error (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\lua.dll)
0x0022BF45: lua_settagmethod (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\lua.dll)
0x00224751: lua_error (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\lua.dll)
0x002247EE: lua_error (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\lua.dll)
0x0022481E: lua_call (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\lua.dll)
0x00224A13: lua_dobuffer (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\lua.dll)
0x0046C43F: GSLobbySessionDesc::operator= (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\Homeworld2.exe)
0x00476061: GSLobbySessionDesc::operator= (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\Homeworld2.exe)
0x00442A1E: GSLobbySessionDesc::operator= (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\Homeworld2.exe)
0x004317E4: GSLobbySessionDesc::operator= (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\Homeworld2.exe)
0x00588138: getLibraryID (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\Homeworld2.exe)
0x0056EAC7: getLibraryID (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\Homeworld2.exe)
0x0056EDC5: getLibraryID (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\Homeworld2.exe)
0x0056EFDC: getLibraryID (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\Homeworld2.exe)
0x00491EDC: GSLobbySessionDesc::operator= (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\Homeworld2.exe)
0x00494781: GSLobbySessionDesc::operator= (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\Homeworld2.exe)
0x0049034A: GSLobbySessionDesc::operator= (E:\Program Files (x86)\Sierra\Homeworld2\Bin\Release\Homeworld2.exe)

**Dim@** · 29th Mar 10 1:00 AM

Not again!

The file you are looking for is "Hw2.log"
NOT errorlog.txt!

**mrlaird** · 29th Mar 10 1:33 AM

yea sorry, ive noticed quite a few people doing this, i wasn't really sure about it. i can't seem to find this ".log" anywhere

edit: my bin/logfiles folder is empty i don't know where else to look

i'm guessing this would be the only other thing...but it's not a .log, i can't find anything with a .log extension anywhere.

log?

**Dim@** · 29th Mar 10 2:31 AM

This is the right file.
And it IS called Hw2.log.
Perhaps you don't have your system showing extensions?

That doesn't show any errors.

Try adding "-luaTrace" to your shortcut (after "-overrideBigFile")

**mrlaird** · 29th Mar 10 2:57 AM

strange...it does show up just as a txt though. anyway it's still doing the same thing with the -luaTrace in there.

log

**scarbrow** · 29th Mar 10 3:14 AM

you are using v1.0 of homeworld 2. You need to update it to version 1.1.1

**mrlaird** · 29th Mar 10 4:02 AM

ugh...still the same

log

**scarbrow** · 29th Mar 10 4:41 AM

UTIL -- filepath failure, path doesn't exists 'E:\Program Files (x86)\Sierra\Homeworld2\data\locale\english'

That is where your next problem is. Either with the english.big or with the file(s) you are overriding.

**mrlaird** · 29th Mar 10 7:08 AM

Quote:
UTIL -- filepath failure, path doesn't exists 'E:\Program Files (x86)\Sierra\Homeworld2\data\locale\english'

That is where your next problem is. Either with the english.big or with the file(s) you are overriding.

i'd tried doing that before but all it did was change all my menu buttons to the $1234 stuff

**TON_Viper** · 29th Mar 10 12:35 PM

Try going into a bit more detail:

Which files have you added to the HW2 folder? Make sure you only included files that you have made a change in.

Have you only added a single ship, or have you done more than this`?

**mrlaird** · 29th Mar 10 2:12 PM

yea i was a little vague :-/ haha.

Well i am using the famed "data.exe" but i do have a unfBig if extracting the big file is any easier, I added to the race/startingfleet/buildingresearch for the race, and my ship (yes only one so far) into the data/ship directory. i tried just using a gimble of an already ingame weapon on it. I've tried just throwing the ship in with the startingfleet of the hiigs and it still does the same thing... im figuring it has to do with it's .ship file.

.ship

-- Pretty-Printed using HW2 Pretty-Printer 1.21 by Mikail.
-- LuaDC version 0.9.19
-- 5/23/2004 7:24:39 PM
-- LuaDC by Age2uN
-- on error send source file (compiled lua) and this outputfile to Age2uN@gmx.net
--
NewShipType = StartShipConfig()
NewShipType.displayedName = "$1833"
NewShipType.sobDescription = "$1833"
NewShipType.maxhealth = 16000
NewShipType.regentime = 1200
NewShipType.minRegenTime = 450
NewShipType.sideArmourDamage = 1.2
NewShipType.rearArmourDamage = 1.2
NewShipType.isTransferable = 1
NewShipType.useEngagementRanges = 1
NewShipType.unitCapsNumber = 2
NewShipType.SquadronSize = 1
NewShipType.formationSpacing = 250
NewShipType.passiveFormation = "dockline"
NewShipType.defensiveFormation = "broad"
NewShipType.aggressiveFormation = "delta"
NewShipType.mass = 100
NewShipType.collisionMultiplier = 1
NewShipType.thrusterMaxSpeed = 200
NewShipType.mainEngineMaxSpeed = 200
NewShipType.rotationMaxSpeed = 50
NewShipType.thrusterAccelTime = 5
NewShipType.thrusterBrakeTime = 2
NewShipType.mainEngineAccelTime = 8
NewShipType.mainEngineBrakeTime = 2
NewShipType.rotationAccelTime = 0.75
NewShipType.rotationBrakeTime = 0.3
NewShipType.thrusterUsage = 0.5
NewShipType.accelerationAngle = 40
NewShipType.mirrorAngle = 0
NewShipType.secondaryTurnAngle = 0
NewShipType.maxBankingAmount = 20
NewShipType.descendPitch = 20
NewShipType.goalReachEpsilon = 30
NewShipType.slideMoveRange = 100
NewShipType.controllerType = "Ship"
NewShipType.tumbleStaticX = 10
NewShipType.tumbleStaticY = 20
NewShipType.tumbleStaticZ = 5
NewShipType.tumbleDynamicX = 2
NewShipType.tumbleDynamicY = 10
NewShipType.tumbleDynamicZ = 5
NewShipType.tumbleSpecialDynamicX = 2
NewShipType.tumbleSpecialDynamicY = 10
NewShipType.tumbleSpecialDynamicZ = 5
NewShipType.relativeMoveFactor = 3
NewShipType.swayUpdateTime = 2
NewShipType.swayOffsetRandomX = 10
NewShipType.swayOffsetRandomY = 10
NewShipType.swayOffsetRandomZ = 10
NewShipType.swayBobbingFactor = 0.15
NewShipType.swayRotateFactor = 0
NewShipType.useTargetRandom = 1
NewShipType.targetRandomPointXMin = -0.3
NewShipType.targetRandomPointXMax = 0.3
NewShipType.targetRandomPointYMin = -0.61
NewShipType.targetRandomPointYMax = 0.29
NewShipType.targetRandomPointZMin = -0.89
NewShipType.targetRandomPointZMax = 0.5
NewShipType.dustCloudDamageTime = 160
NewShipType.nebulaDamageTime = 200
NewShipType.fighterValue = 0
NewShipType.corvetteValue = 0
NewShipType.frigateValue = 12
NewShipType.neutralValue = 0
NewShipType.antiFighterValue = 0
NewShipType.antiCorvetteValue = 0
NewShipType.antiFrigateValue = 12
NewShipType.totalValue = 12
NewShipType.retaliationRange = 5500
NewShipType.retaliationDistanceFromGoal = 160
NewShipType.visualRange = 1000
NewShipType.prmSensorRange = 5000
NewShipType.secSensorRange = 6000
NewShipType.detectionStrength = 1
NewShipType.TOIcon = "Diamond"
NewShipType.TOScale = 1
NewShipType.TODistanceFade0 = 9000
NewShipType.TODistanceDisappear0 = 7000
NewShipType.TODistanceFade1 = 4500
NewShipType.TODistanceDisappear1 = 3500
NewShipType.TODistanceFade2 = 12000
NewShipType.TODistanceDisappear2 = 35000
NewShipType.TOGroupScale = 1
NewShipType.TOGroupMergeSize = 0
NewShipType.mouseOverMinFadeSize = 0.045
NewShipType.mouseOverMaxFadeSize = 0.1
NewShipType.healthBarStyle = 1
NewShipType.nlips = 0.000125
NewShipType.nlipsRange = 6000
NewShipType.nlipsFar = 0.00015
NewShipType.nlipsFarRange = 10000
NewShipType.SMRepresentation = "HardDot"
NewShipType.meshRenderLimit = 13000
NewShipType.dotRenderLimit = 10
NewShipType.visibleInSecondary = 1
NewShipType.minLOD = 0.25
NewShipType.minimumZoomFactor = 0.6
NewShipType.selectionLimit = 150000
NewShipType.preciseATILimit = 0
NewShipType.selectionPriority = 75
NewShipType.militaryUnit = 1
addAbility(NewShipType, "MoveCommand", 1, 0)
StartWeaponConfig(NewWeaponType, "Gimble", "Missile", "vgr_heavymissile", "Normal", 2500, 10000, 0, 0, 0, 2, 0, 0, 0, 4.0, 0.0, 0.0, 1, 0, 120, 120, 1.0, "Normal", 1, 0, 0)
StartShipWeaponConfig(NewShipType, "vgr_Heavyconcussionmissilelauncher", "Weapon_Launcher1_Position", "Weapon_Launcher1_Position")
StartShipWeaponConfig(NewShipType, "vgr_Heavyconcussionmissilelauncher", "Weapon_Launcher2_Position", "Weapon_Launcher2_Position")
StartShipWeaponConfig(NewShipType, "vgr_Heavyconcussionmissilelauncher", "Weapon_Launcher3_Position", "Weapon_Launcher3_Position")
StartShipWeaponConfig(NewShipType, "vgr_Heavyconcussionmissilelauncher", "Weapon_Launcher4_Position", "Weapon_Launcher4_Position")
addShield(NewShipType, "EMP", 310, 20)
NewShipType.battleScarMaxTriBase = 75
NewShipType.battleScarMaxTriInc = 100
NewShipType.sobDieTime = 1
NewShipType.sobSpecialDieTime = 1
NewShipType.specialDeathSpeed = 40
NewShipType.chanceOfSpecialDeath = 0
NewShipType.deadSobFadeTime = 1

or i did have an idea though, is it possible that a model could be too large for the game to cause it to crash?

**Dim@** · 29th Mar 10 11:25 PM

Um, this line:

Code:

StartWeaponConfig(NewWeaponType, "Gimble", "Missile", "vgr_heavymissile", "Normal", 2500, 10000, 0, 0, 0, 2, 0, 0, 0, 4.0, 0.0, 0.0, 1, 0, 120, 120, 1.0, "Normal", 1, 0, 0)

Should be in a *.wepn file, in the weapon folder, not in the *.ship file.

**mrlaird** · 30th Mar 10 12:05 AM

really? i was under the impression if you wanted to modify the weapon then you'd put it in the .ship...oh well, umm but yea still nothing.

log.... again

**Dim@** · 30th Mar 10 12:58 AM

Have you read the Making the Keepers a Playable Race tutorial?

It describes, in detail, EXACTLY what you need to do to make a weapon.

**mrlaird** · 30th Mar 10 1:35 AM

Have you read the Making the Keepers a Playable Race tutorial?

It describes, in detail, EXACTLY what you need to do to make a weapon.

yea that was actually the first thing i did. i can sit and do it w/o having to even look at the tutorial now. it would be nice if somebody could post a more "advanced" topic of the same thing. i only understand what moe has explained in his topic, so sort of what he showed i don't understand anything else that would go into these files.

**MatthCoFreak** · 30th Mar 10 6:51 AM

Was thinking of doing a "Create your ship from scratch and get it ingame" tutorial someday. Maybe I should start working on it.

**mrlaird** · 30th Mar 10 8:22 AM

Was thinking of doing a "Create your ship from scratch and get it ingame" tutorial someday. Maybe I should start working on it.

haha that would be greatly appreciated ^_^

**Dim@** · 30th Mar 10 1:51 PM

Doesn't that kind of exist, though?

Keeper's tutorial?

**mololu** · 30th Mar 10 1:58 PM

That's more of a 'Create your ship from an existing ship' without the additional bits like which files you need etc.

After a month of adding stuff I still keep figuring out 'doooh you also need that to make it work like I want' so some sort of tutorial for beginners would probably be good.

Then again, it isn't that hard to figure out for yourself. It's just time-consuming and sometimes quite frustrating.

Though, let's be honest, does anyone really create ships from absolute scratch? I tend to copy existing stuff and modify it as needed/add things to it. Never mind, I think this went a little off topic.

**mrlaird** · 30th Mar 10 2:56 PM

does anyone really create ships from absolute scratch? I tend to copy existing stuff and modify it as needed/add things to it

well i did for this, and i'm sure im not the only beginner that tried.

I would just copy the existing stuff but i want my model in there. if i had a spare .hod that i could just tinker with i'd be fine but none of the other .ship/.events files are accompanied by a .hod file besides the bentus so i'm lost as to how i would mess with a ship that's already in the game.

EDIT: Ok i must be tarded because i obviously messed something up somewhere, I totally restarted, remade the keeper as playable and i've made a "new ship" folder with a copy of the bentus files in and i simply replaced the bentus model with my own, and it finally works!

uhh kinda

now here's the kicker...my ship should be flying horizontally, but instead it is standing vertical, front facing down and top facing back. now i know this has something to do with the xyz values of the model. is it possible or how would i change this in wings3d?

**Dim@** · 30th Mar 10 9:14 PM

none of the other .ship/.events files are accompanied by a .hod file

That's because the *.hod files were not included in data.zip, since they take up a lot of space.
You need to extract those yourself.

If you want to, I found this useful, extract the whole *.big file somewhere, then paste in data.zip (overwriting the compiled files). Then, you can also overwrite with the RDN tool files, which are better than the data.zip ones. Either way, you now have the entire contents of Homeworld2.big, and you do not need to extract it again.

**mololu** · 30th Mar 10 9:22 PM

What dim@ said is exactly what I've done concerning the HODs.

As for the ship, you probably got the axis mixed up in Wings. Shoot me if I'm wrong but Blue (Z) is forward, green (Y) is up and red (X) is left/right.

You can whole hods in cfhoded up I wouldn't do it unless you dont' have an alternative. The editor sometimes really screwes up the hod when you do that. If you don't want to use wings again, there is a transform mesh option in cfhoded but you're better off just geting the model fixed in wings.

I've found (use wings myself) that importing an existing .obj (ok you'd have to extract the .hods out of the game files and then extract a mesh out of those) and using that as a size and direction reference is the simplest.

Hope this made any sense. It's late/early...

**mrlaird** · 30th Mar 10 10:49 PM

the bentus .hod seems to work fine but this will definately be easier thanks dim@, but one thing is there something that will get rid of the gibberish in the .ship files?

oh and i found the rotation button in CfHODed and fixed my models so they fly straight now.

**scarbrow** · 30th Mar 10 11:58 PM

once the files have been 'un-bigged' they then need to be decompiled to make them readable. luaDC or the batch luadc can be used for this.

**mrlaird** · 31st Mar 10 1:09 AM

i should be safe just moving the .hods to the ships when i want to use them tho right? that's all i wanted..i still have the already decomped .ships. besides i can't seem to find a working link for LuaDC or CFLuaDC

**mololu** · 31st Mar 10 4:27 AM

Yes that works fine. The HODs are usable as is out of the big, just copy them into your folder with the decompiled luas.

Something to remember is that some ships also need .mad and .madstate files (animations) to work correctly and may look odd without them.

**MatthCoFreak** · 31st Mar 10 9:36 AM

You can whole hods in cfhoded up I wouldn't do it unless you dont' have an alternative. The editor sometimes really screwes up the hod when you do that. If you don't want to use wings again, there is a transform mesh option in cfhoded but you're better off just geting the model fixed in wings.

I never had any issue with CFHodEd screwing things up, believe me, I always have to transform the meshes somehow when creating a new hod from scratch (which I have to do very often as I work for HHF and I'm their only hodder) and given that I know zilch about modeling and don't even have a modeling software on my computer, I always use the transform option of CFHodEd for that. It is perfectly stable and I have yet to see anything screwed up by CFHodEd. Excepted, of course some issue during importing, but once it's correctly imported, you can do whatever you want with it.

**mololu** · 31st Mar 10 10:06 AM

I know.

I was talking about the 'rotate hod' option that rotates the WHOLE hod. That Transform is stable I know. I use that all the time too.

Sorry if I was unclear.

**mrlaird** · 31st Mar 10 12:56 PM

ok well im happy now...^_^ ive replaced some of the models, moved hardpoints yadayada...

but now i'm having problems with the shaders in the cfhoded and my textures...parts are glowing that shouldn't and it looks smeared (like spilling bleach on blue jeans.) if i just leave the old hw2 shaders for the original models it still works...just not what i'm looking for.

maybe there was a tutor i overlooked?

**mololu** · 31st Mar 10 1:00 PM

What exactly do you mean with shaders? The shader for ships should always be set to 'ship' (without the '').

If you mean the textures, there are two textures used by every model, $diffuse and $glow. The first tells the game what colors to use where + primary team color (I think) and the second tells the game how to light the model + sedondary team color.

There's a pretty comprehensive tutorial on textures here, as for importing the textures, follow the example set by the existing ships.

Edit: oh yeah, I've found when importing from wings --> hoded you need to watch out for two things:

1) make all edges hard in Wings (select edges --> hardness --> hard)

2) Do not reverse UV map and do not recalculate normals when importing to CfHodEd.

Hope this helps somehow.

**mrlaird** · 31st Mar 10 1:08 PM

What exactly do you mean with shaders?

i mean by the shader parameters in the materials tab, my ships glow where they shouldn't.

oh and thanks for the pointers on wings....good thing i dont even know what half that stuff is so i doubt i'll mess that up :P

**mololu** · 31st Mar 10 1:22 PM

If they glow where they shouldn't, it's probably something with the $glow part of the material, at least that's what it sounds like. Parts that are green on the $glow texture will glow ingame.

**mrlaird** · 31st Mar 10 1:34 PM

that's the thing idk what it is. i'm afraid to remove any of original shaders because idk what it's going to do.

EDIT: if i knew what the $mask $glow $diffuse actually ment that would be helpful too

**mololu** · 31st Mar 10 1:45 PM

$mask is for the badge.

$diffuse is the color of the model (as in the normal texture you apply in wings, with the skin you want on the model).

$glow is the same texture as $diffuse except that the shades of blue are used to determine how light/dark that area of the model is. On this layer, any parts made green will glow.

**mrlaird** · 31st Mar 10 2:59 PM

ok...umm badge? lol

**TON_Viper** · 31st Mar 10 3:16 PM

Essentially, it's a team logo. It's the symbol you see on the side of your ships. It has its own shader for some reason.

**mrlaird** · 31st Mar 10 3:29 PM

oh ok then, well ive got my smaller ships figured out now...just some of my bigger ones have more than one texture and i just have to figure how to get them all to work on there....

it seems the shader parameters are effecting how they look and where they are but i dont know how/why. i.e. i'll import both textures but they both cover the same places unless i mess around with the shader parameters then they invert posistions. it looks like one is supposed to be a low quality and the other's a high quality.

EDIT: nothing nevermind

**mrlaird** · 1st Apr 10 12:51 AM

well the stretch of good luck is over....

i now have a new problem....i cannot zoom out from my mothership without it dissappearing.

i haven't the slightest clue where i would begin to fix this one

**Dim@** · 1st Apr 10 1:08 AM

This line in the *.ship file:

Code:

NewShipType.meshRenderLimit =

Change it to something bigger. It controls at what distance the ship stops rendering. (Which may be relative to the CM, or other values, but anyway, if you make it big it will work).

Also, may I suggest that you go through the ship file and read values. Many of them are quite useful and self explanatory. Some are not particularly obvious, but you can work them out if you try them, or look them up here, on Karos Graveyard, or in the RDN tools ShipTuning.xls spreadsheet (which is what the devs used to make those ships originally).

PS:
Here is the section of Karos Graveyard about *.ship variables:
http://hw2wiki.net/wiki.hw2.info/VariableShip.html

And this is what it says about meshRenderLimit:

meshRenderLimit = <fDistance>: The screenspace size that defines when the mesh stops rendering and only TO remains. • The distance at which the ship disappears from view.

EDIT: Hmmm ... according to that, you might need to make it smaller ... try both ways. I normally take the line from the *.ship of whatever ship's hod I'm using, or as close as possible in size to it.

**mololu** · 1st Apr 10 9:15 AM

This behaviour might also be caused by missing LOD meshes.

Homeworld uses so called Level Of Detail. Lod 1 has the most polies, lod 3 (or 4) has the least. They're used to cut down the ammount of polies needed to be rendered when ships are far away.

If you only added one LOD but the .ship file has multiple LODs, it will disappear as soon as the game switches LOD (specified by camera distance from the ship).

Two ways to fix this:

1) Add more LODs to the mesh in the HOD

or

2) look at the following lines in the .ship that describe when the LOD is to be changed:

Code:

NewShipType.upLOD = 4000
NewShipType.upLOD = 5950
NewShipType.downLOD = 4015
NewShipType.downLOD = 5965

**MatthCoFreak** · 1st Apr 10 9:18 AM

Have a look on all the lines containing "LOD" too. If your mesh doesn't have any LOD, remove all those lines from your .ship.

**mrlaird** · 1st Apr 10 1:19 PM

i went and changed the up/downlod in the .ship file and its fine now, thanks much ^_^.

**mrlaird** · 1st Apr 10 4:59 PM

okay i have a few final questions, then i should be good (hopefully :P ),

my mothership is still a little bit too big for the hyperspace plane, is it possible to make it bigger? or even change the fx completely?

pertaining to weapons development, i have figured out how to add my new weapons, add impact sounds for the weapons, and change weapon parameters (.wf settings, weaponfire scripts, etc)

when i was adding audio to my new weapon i noticed in the weaponfire scripts you can alter where my weapon gets it's impact sound from but i didn't see where you can change the sound the weapon makes when it fires.

i hadn't looked at them but i figured i would also need to ask about it anyways. in the art/fx for the weapons, is it possible to change the colors of projectiles (i.e. changing lasers from blue to red (lasers are all i'm really interested in color changing if it's possible.))

also i really appreciate the help you guyss have given me so far, everything ive done so far works perfectly.

**Dim@** · 1st Apr 10 6:39 PM

my mothership is still a little bit too big for the hyperspace plane

What do you mean by that? If you mean the plane doesn't quite cover it, you need to increase the size of the motherships' Collision Mesh (The bounding box determines the size of the Hyperspace effect). Changing the fx is limited to variations on the theme of a square covering your ship up, unfortunately - it is hardcoded.

For the weapon sound, I think "hit_sfx" is the hit sound, "nopenetrate_sfx" is the sound of hitting a defence field, and "bullet_sfx" is the sound of firing. But I may be wrong.

And yes, you can change anything you like about a weapon, from it's sound and colour to it's shape and size. You can alter the scripts in the art\fx folder manually, or you can use the FX Tool, (available in the RDN tools), which is a bit buggy. To change the colour only, you can simply modify the textures to different colour ones.

**mrlaird** · 1st Apr 10 7:23 PM

To change the colour only, you can simply modify the textures to different colour ones.

i can do this in GIMP 2 right?

EDIT: never mind, i found that the weapon i'd decided to mod didn't have the fire_sfx line, it was just missing that. seems to be missing from karos also, maybe there's a way somebody can update the weaponfire.

EDIT: also is there an area in there concerning art/fx .luas? because it seems like there's variables in there to change width and such but i have no idea whats going on.

parameters are epsilonwidth and width with 4 variables which i assume to be (not sure), x, y, z (1, 2, 3, 4)

**mrlaird** · 29th May 10 4:19 AM

before someone calls grave digging *which yea it technically is* im currently deployed in the military and had gone to an area that lacked interenet....but anywho umm i figured i would have got a response by now >.>

ive also came upon a new issue of creating engine burns...im fine on my smaller ships but they just look silly on the bigger ones and i'm not even really sure where to start on making a bigger burn.

any help is always appreciated

**ajlsunrise** · 1st Jun 10 9:28 PM

First off... This is technically in the wrong forum... I'll PM a moderator shortly to have them move it for ya.

Second... I'm not entirely sure what your question now is about. From what I see, everything has been answered already.

**Grabnutz** · 2nd Jun 10 7:34 AM

moving to main forum

**mrlaird** · 3rd Jun 10 10:34 AM

First off... This is technically in the wrong forum... I'll PM a moderator shortly to have them move it for ya.

Second... I'm not entirely sure what your question now is about. From what I see, everything has been answered already.

ah cool thanks..

well i'd been looking at the tools and found the .rot tool and got my colors changed or the lasers so that's fine, but now I had an idea about changing the size. Would it work if i just changed the size of the graphic in .dds format in photoshop?

As for the engine burns, i don't want a glow on my bigger ships... i would just like to have a larger burn. and when i make any changes to the values in the setEngineBurn line of my .ship files i end up with a quite large, but funky/pulsing burn that i can't see unless im zoomed into the burn itself then i can't see anything else. essentially it looks like my ships have a sun following them around.

I just wanted to know if there was a way i could export a smaller one from another ship and import it into wings3d or some other program so i can see what i'm doing instead of randomly punching in a bunch of numbers and restarting the game over and over.

**MatthCoFreak** · 3rd Jun 10 10:28 PM

well i'd been looking at the tools and found the .rot tool and got my colors changed or the lasers so that's fine, but now I had an idea about changing the size. Would it work if i just changed the size of the graphic in .dds format in photoshop?

I'd say yes, try that. If not, there are other ways to achieve that.

I just wanted to know if there was a way i could export a smaller one from another ship and import it into wings3d or some other program so i can see what i'm doing instead of randomly punching in a bunch of numbers and restarting the game over and over.

You'll see that HW2 modding is a lot of trial-and-error

having trouble figuring out what's wrong with my mod...

Thread Tools